Integrations > Strapi CMS
| Type | File Picker |
| Plan | Premium |
| Set-up | Standard |
Strapi CMS Integration
Get a complete integration between Kontainer DAM & PIM and Strapi, the open-source, code-first CMS — built for Strapi v5.
With the integration, your editors can select images, videos, and files directly from Kontainer in Strapi’s admin panel — without ever uploading them to Strapi. Strapi stores only a lightweight reference to the asset; the file itself stays in Kontainer and is delivered via CDN, so you always work with the latest, approved version.
The solution is ideal for development teams building on Strapi v5 with Node.js 18+ and for companies seeking a flexible alternative to traditional CMS platforms.
Description
Reference-based media, not duplicate files
Strapi is an open-source, headless CMS built on Node.js. With the Kontainer plugin, Strapi never stores a copy of your assets. Instead, every file you select is saved as a JSON reference — including the CDN URL, thumbnail, dimensions, alt text, description, and any custom fields you’ve set up in Kontainer.
Because that metadata travels with the reference, editors don’t have to retype alt text or descriptions in Strapi, and your frontend can read them straight off the Strapi API response.
The plugin requires Strapi v5 (Strapi v4 is not supported) and Node.js 18 or later.
Benefits
Benefits of Kontainer’s Strapi plugin
✔ Select images and files directly from Kontainer inside Strapi’s admin panel
✔ No files are ever uploaded to Strapi’s media library — only a reference is stored
✔ Alt text, descriptions, and custom fields travel with the file automatically
✔ Apply a Kontainer download template (crop, resize, format) at the point of selection
✔ Always deliver the current, approved version of a file via Kontainer’s CDN
✔ Optional file usage tracking shows where each asset is actually used in Strapi
Features
How the integration works
✔ Installed as an npm package (@kontainer/strapi-plugin) directly in your Strapi project
✔ Adds a “Kontainer media” custom field to any content type via the Content-Type Builder
✔ Connect with just your Kontainer URL — no API keys or environment variables required
✔ Editors browse, search, and filter the Kontainer library, and can apply a download template before inserting
✔ Optional usage tracking polls Strapi to report where files are used — including drafts, locales, components, and dynamic zones
✔ Assets are served from Kontainer’s CDN via the reference’s URL, so your frontend always fetches the latest file
Why?
Why integrate Strapi with Kontainer?
Strapi is often used when development teams want full control over data models and a flexible API for their frontend. Without a central DAM, files end up duplicated into Strapi’s own media library, with no easy way to tell which version is current or to keep alt text and metadata consistent.
By integrating Strapi with Kontainer, you get:
✔ One single source of truth for your digital assets — nothing is duplicated into Strapi
✔ Alt text, descriptions, and custom fields carried automatically with every reference
✔ Less manual work for editors and developers
✔ Visibility into where assets are actually used across your Strapi content, with optional usage tracking
Kontainer manages your assets, while Strapi manages your content and frontend.
Use Cases
How the integration is used in practice
- Product data and e-commerce
Product pages in Strapi can reference the correct product images from Kontainer, so the same approved image is used everywhere it’s needed. - Marketing and campaign sites
Marketing teams can build landing pages and campaign sites in Strapi, where images and videos are always the latest approved assets from Kontainer. - Multi-brand and multi-market setups
Companies with multiple brands or markets can reuse the same Strapi components while the correct, localized assets are pulled from Kontainer as references. - Structured content modeling
Developers can add the Kontainer media field to any content type, so files and their metadata are referenced directly from Kontainer via the API — without ever being stored locally.
Support
Links and Support
Contact Kontainer’s customer service to learn more about the integration between Kontainer and Strapi.
We are happy to help with setup, training, and best practices.
Please write to us at support@kontainer.com
You can also read about our API in our Helpdesk here.
FAQ
The integration lets editors and developers select and insert files from Kontainer directly inside Strapi’s admin panel. Strapi never stores the file itself — only a reference (including the CDN URL, alt text, and custom fields) — so the asset stays centrally managed in Kontainer.
You can access images, videos, documents, graphics, and other file types stored in Kontainer. Metadata such as alt text, descriptions, and custom fields comes along automatically with the reference.
No. Files stay in Kontainer and are never uploaded to Strapi’s media library. Strapi only stores a small JSON reference — including the CDN URL, thumbnail, dimensions, and metadata — pointing back to the asset in Kontainer.
Yes. The plugin requires Strapi v5 (Strapi v4 is not supported) and integrates naturally with the frontends Strapi typically powers, such as React, Next.js, and Vue. Your frontend reads the file’s CDN URL and metadata directly from the Strapi content API response.
You’ll need Strapi v5, Node.js 18 or later, and a developer with access to your Strapi codebase and the ability to deploy. Setup involves installing the plugin as an npm package, adding the Kontainer media field to a content type via the Content-Type Builder, rebuilding the admin panel, and entering your Kontainer URL under Settings.
Since all assets are managed centrally in Kontainer, all teams always work with the same approved and up-to-date files — regardless of which channel or campaign they’re used in.
Yes. Editors can browse, search, and filter files from Kontainer directly within the Strapi editor, and optionally apply a Kontainer download template (crop, resize, format) before inserting.
Permissions and versioning are managed centrally in Kontainer. Because Strapi only holds a reference rather than a copy of the file, editors and developers are always working against the current, approved version in Kontainer.
Assets are served directly from Kontainer’s CDN via the reference’s URL, so load times are reduced compared to hosting files in Strapi’s own media library — which benefits both user experience and SEO.
Yes, optionally. Kontainer can poll your Strapi instance and show you where each asset is used — including drafts, locales, components, and dynamic zones. This is set up under Settings → Integrations in Kontainer, using a token generated from the Kontainer settings in Strapi.
Contact us at support@kontainer.com for a no-obligation conversation.
We’ll confirm your Strapi version and technical setup, and can walk your developers through the setup guide: https://helpdesk.kontainer.com/article/strapi-integration-guide/