Image Metadata Explained: IPTC, EXIF and XMP

What IPTC, EXIF and XMP actually are, which fields stock agencies read, and how to embed keywords so they survive the trip to every platform.

# What Is Image Metadata? IPTC, EXIF and XMP Explained for Stock Metadata is not one thing. It is three standards doing three different jobs, and confusion between them is behind a surprising number of stock submission problems — keywords that vanish, fields that never wrote, files rejected for missing information the contributor was certain they added. ## The three standards **EXIF** is written by the camera automatically. It records technical capture data: shutter speed, aperture, ISO, focal length, lens, camera model, timestamp, and often GPS coordinates. You do not author EXIF; the device does. **IPTC** is descriptive and authored by you. Title, description or caption, keywords, creator, copyright notice, rights usage terms, and location fields. This is the standard built for publishing, and **this is what stock agencies read**. **XMP** is Adobe's extensible framework. It can carry IPTC fields plus application-specific data, and many modern tools write descriptive metadata into XMP. Most agencies handle both, but a tool that writes *only* to XMP occasionally causes fields to be missed on ingest. The practical summary: EXIF describes how the photo was taken, IPTC describes what it is and who owns it, XMP is a container that often holds IPTC data. For stock, IPTC is the one that determines whether your work is found. ## The fields that matter Of the many IPTC fields available, a handful do the work: **Title / Headline.** Short, descriptive, human-readable. On several agencies this becomes the visible title on the file's page. **Description / Caption.** A natural sentence describing the image. Written for a person, not as a keyword dump — keyword-stuffed descriptions are a documented rejection cause. **Keywords.** The search terms. Limits vary by agency: Adobe accepts 49 and weights the first ten most heavily, Shutterstock accepts 50, Alamy imposes no hard cap. **Creator and Copyright.** Your attribution and rights notice. Missing copyright information causes rejections at some agencies. **Location fields.** City, state, country. Important for editorial content, where accuracy is contractual rather than optional. **Rights usage terms.** Where licensing restrictions need to travel with the file. ## Why embedded metadata matters more than you would think Metadata written *inside* the file travels with it. Upload the same JPEG to six agencies and the embedded IPTC arrives at all six — no re-entry, no per-platform form filling. This is why the recommended workflow is always: write metadata locally, embed it, verify it, then deliver. The alternative — uploading first and entering metadata through each agency's web interface — multiplies your work by the number of agencies you submit to. For Adobe Stock this is not merely convenient. Adobe has **no CSV import route** for metadata; embedded IPTC is the only bulk mechanism available. Our [Adobe Stock FTP guide](/blog/how-to-upload-images-to-adobe-stock-using-ftp) covers that workflow. ## Where CSV still fits Embedded metadata cannot carry everything. Some platform-specific fields exist outside the IPTC standard: - Shutterstock's category assignments and editorial and mature-content flags - Freepik's mandatory `_ai_generated` tag These need a CSV. The strongest setup uses both: embed IPTC for everything portable, add a CSV for the platform-specific remainder. Our [Shutterstock CSV template guide](/blog/shutterstock-csv-template) covers the exact structure. ## Metadata gets destroyed more easily than you expect This is the failure most contributors hit at least once. **Messaging apps strip metadata.** Sending a photo through most chat applications removes it entirely. **Some social platforms re-encode files.** Downloading your own image back from a platform frequently returns a stripped copy. **Certain export paths discard fields.** Some conversion tools, and some "export for web" settings, drop IPTC silently. **Format matters.** Not every format carries every field. The discipline is simple: **transfer originals directly, and verify.** Open the file in a metadata viewer after embedding and confirm the fields actually wrote. Silent failure is the normal failure mode here — nothing warns you. ## Removing metadata Occasionally you want it gone. EXIF GPS data reveals precise locations, which matters for images of your home, your family or anything you would rather not geotag publicly. For images published outside stock, stripping EXIF — particularly GPS — is a sensible privacy step. For stock submissions, do the opposite: descriptive metadata is the entire mechanism by which your work is discovered. ## Writing metadata at volume Understanding the fields is straightforward. Filling them for thousands of files is not — at five to twenty minutes per image manually, metadata is the reason most portfolios are smaller than they could be. Rastock AI [generates the descriptive fields, embeds them as IPTC, exports per-agency CSVs and delivers over FTP](/features) to 25+ agencies. Our guide to [bulk metadata generation](/blog/bulk-metadata-generation-stock-contributors) covers the batch workflow, and plans by upload volume are on the [pricing page](/pricing). ## Summary EXIF is the camera's record, IPTC is your description, XMP is often the container. Agencies read IPTC. Embed it before delivery so it travels with the file, add CSV for platform-specific fields, and always verify it actually wrote — because when metadata fails, it fails silently. For the full picture, see our guide to the [stock photography workflow](https://rastock.ai/blog/stock-photography-workflow) — every stage from selection through metadata to delivery. ## Related reading - [Best Keywords for Artists Selling Online in 2026](https://rastock.ai/blog/best-keywords-for-artists-selling-online) - [Image Keywords for SEO: The Complete 2026 Guide](https://rastock.ai/blog/image-keywords-for-seo) - [How to Write Metadata for Stock Photos: The Complete 2026 Guide](https://rastock.ai/blog/how-to-write-metadata-for-stock-photos)

Frequently asked questions

What is the difference between EXIF and IPTC?

EXIF is written by the camera and records technical capture data — shutter speed, aperture, ISO, focal length, date, sometimes GPS. IPTC is descriptive and written by you: title, description, keywords, creator, copyright and rights information. Stock agencies read IPTC.

What is XMP metadata?

XMP is Adobe's extensible standard, which can carry IPTC fields and additional application-specific data. Many tools write IPTC data into XMP, and most agencies handle both, but writing to XMP only can occasionally mean fields are missed.

Which metadata fields do stock agencies read?

Primarily the IPTC descriptive fields: title or headline, description or caption, keywords, creator and copyright. Some agencies also read location and rights fields. Technical EXIF data is largely ignored for search purposes.

How do I embed keywords into a JPEG?

Use software that writes IPTC fields — Lightroom, Bridge, ExifTool or a dedicated metadata tool — then verify with a separate viewer that the fields actually wrote. Silent failures are common when tools write to XMP only or the format does not carry the field.

Does metadata survive uploading and sharing?

Not always. Messaging apps, some social platforms and certain export paths strip metadata entirely. Always transfer originals directly to agencies rather than through intermediaries that may re-encode the file.

Should I remove metadata before publishing images?

For stock submission, no — descriptive metadata is how you get found. For personal images published elsewhere, stripping GPS and camera data is a reasonable privacy measure, since EXIF can reveal precise locations.