Prepare Strapi media images with portable embedded metadata.
Drop your images, describe your content types and project. ExifInjector generates IPTC titles, alt text, keywords and copyright before files enter your Strapi media library.
Drop Strapi media images here
JPG, PNG, WebP - click or drag
Strapi Media Library
Pre-filled settings for Strapi users
What the Strapi template does
No technical metadata knowledge needed. Fill in what you know about your Strapi content - ExifInjector handles the rest.
01
Portable file metadata
IPTC fields travel with the image beyond Strapi's database — across APIs, CDN and frontends.
02
Adds project credit
Embeds organization name, copyright and creator metadata into every Strapi media file.
03
Works before upload
Process images outside Strapi and push clean files via upload — no plugin needed.
Ready to optimize Strapi images?
Use the Strapi template inside ExifInjector. Upload your images above, fill in your details, and download ready files in minutes.
First images free · No account required to try · Image quality preserved
Why Strapi media library image metadata matters
Strapi's media library stores assets that power multiple content types and can be served through REST or GraphQL APIs to any frontend. Images without embedded IPTC metadata depend entirely on Strapi's database for their description — context that is lost when files are downloaded directly, served through a CDN, or migrated to a new CMS. Embedded metadata is the only context that survives every layer of abstraction.
3M+
Strapi deployments globally — file-level metadata ensures images remain self-describing across every deployment and migration
REST + GraphQL
Strapi's dual API means images are served in many contexts where embedded metadata is the only reliable source of truth
0
plugins required — ExifInjector processes images completely outside Strapi
How to add metadata to Strapi media library images
Prepare images before upload
Gather images for your Strapi content types before uploading to the media library. ExifInjector supports JPEG, PNG, WebP — all formats Strapi accepts.
Enter content type and project context
Add your organisation name, Strapi content type (article, product, category, author), project channel, and relevant brand keywords.
Generate API-ready metadata
AI creates IPTC titles and descriptions that work as useful image context across REST and GraphQL API consumers. Organisation credit and copyright are embedded in every file.
Upload to Strapi media library
Upload processed images via the Strapi admin panel. The embedded metadata is served with the file through your CDN and is visible to Google when it crawls your Strapi-powered frontend.
Strapi media library: with ExifInjector vs without
| Feature | With ExifInjector | Without |
|---|---|---|
| Context across API consumers | File carries title + description for any API client | Context requires Strapi database query |
| Google Images visibility | IPTC metadata indexed by Google from CDN-served images | Google reads only page-level alt text |
| Migration safety | Metadata survives CMS migrations | Metadata lost if database is not migrated |
| Attribution | Organisation + copyright in every file | No attribution outside Strapi |
| Plugin required | None | N/A |
Frequently asked questions
Updated June 2025Does Strapi read embedded IPTC metadata from uploaded images?
Strapi does not automatically populate media library fields from embedded IPTC metadata. The IPTC data travels with the file when served through Strapi's upload provider (local or cloud storage) — it is readable by Google when your pages are crawled, and by any API consumer that handles the raw file.
How does embedded metadata help when migrating from Strapi?
When migrating content from Strapi to another CMS, the database fields (titles, descriptions) are often migrated but the image files themselves may lose their associated metadata during the process. Embedded IPTC metadata is inside the binary file — it survives any migration that transfers the actual image files, regardless of what happens to the database.