Prepare Contentful media assets with portable metadata.
Drop your media files, describe your content model and brand. ExifInjector generates IPTC titles, descriptions, alt text and copyright embedded in each file.
Drop Contentful media assets here
JPG, PNG, WebP - click or drag
Contentful Media Assets
Pre-filled settings for Contentful users
What the Contentful template does
No technical metadata knowledge needed. Fill in what you know about your Contentful content - ExifInjector handles the rest.
01
Portable file-level metadata
IPTC fields travel with the asset across every frontend — websites, apps, feeds and CDN.
02
Adds organization credit
Embeds brand name, copyright and creator metadata into every Contentful media file.
03
Works before upload
Process assets outside Contentful and upload clean files — no Space API changes needed.
Ready to optimize Contentful images?
Use the Contentful 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 Contentful media asset metadata matters
Contentful stores media assets that are served across multiple frontends — websites, apps, email campaigns, and APIs. Assets without embedded metadata lose their context the moment they leave Contentful's CMS fields. IPTC titles, descriptions, alt text seeds, and copyright embedded at the file level travel with assets across every channel — making them usable and attributable regardless of which system serves them.
3,000+
technology integrations with Contentful — assets are served across many channels where file-level metadata is the only reliable context
43%
of content teams reuse the same Contentful assets across more than three frontends per asset
0
Space API changes required — ExifInjector works on files before they enter your Contentful Space
How to add metadata to Contentful media assets
Export or prepare your media assets
Download assets from your Contentful Space or prepare new images before upload. ExifInjector supports JPEG, PNG, WebP, AVIF — all formats Contentful accepts.
Enter content model and project context
Add your organisation name, the relevant content type (blog post, product page, landing page), project channel (website, app, email), and brand keywords. This context drives metadata that works across all frontends.
Generate portable file-level metadata
AI generates IPTC titles, descriptions, and keywords that remain meaningful across any Contentful-powered frontend. Your organisation credit and copyright are embedded in every asset.
Upload to Contentful Space
Upload processed assets to your Contentful media library. The embedded metadata is served with the asset through Contentful's CDN — visible to Google, readable by any system that handles the raw file.
Contentful media assets: with ExifInjector vs without
| Feature | With ExifInjector | Without |
|---|---|---|
| Metadata portability | Title + description travels across every frontend | Context lives only in Contentful CMS fields |
| Google Images visibility | File-level metadata indexed alongside page content | Google relies on page markup only |
| Attribution across channels | Organisation + copyright in every file | Attribution lost when file leaves Contentful |
| Alt text seed | IPTC title usable as alt text in any frontend | Alt text must be re-entered per frontend |
| API delivery context | Raw file carries self-describing metadata | API consumers receive untagged binary files |
| Space API changes needed | None | N/A |
Frequently asked questions
Updated June 2025Does Contentful read embedded IPTC metadata from uploaded assets?
Contentful does not automatically populate content type fields from embedded IPTC metadata. However, IPTC data embedded in your image files travels with assets when they are served through Contentful's CDN — readable by Google, accessible to any system that handles the raw file, and persistent regardless of how many times the asset is used.
How does image metadata help headless CMS projects?
In a headless CMS architecture, the same image file is often served across multiple frontends — a Next.js website, a React Native app, and an email template. File-level IPTC metadata ensures that every frontend has access to the same title, description, and copyright, without requiring each frontend to separately query Contentful for that information.
Should I add metadata to Contentful assets used in marketing emails?
Yes. Marketing email images that carry embedded creator credit and copyright are protected when subscribers forward or share emails. IPTC metadata is also read by some email clients and spam filters as a quality signal, and the embedded description can serve as an accessible text alternative.