What this page answers
How IPTC keywords map into XMP-ready files, what still belongs in CSV exports, and where manual review is still required.
IPTC / XMP FAQ
IPTC Keywords for Stock Photos
Use this FAQ page to understand how IPTC keywords, XMP fields, and CSV exports work together in Stocktag before you publish to Adobe Stock, Shutterstock, Getty Images, and iStock.
Who it is for
Contributors and teams exporting stock metadata across Adobe Stock, Shutterstock, Getty Images, iStock, and similar marketplaces.
What not to expect
This is not a promise that every platform reads every IPTC/XMP field the same way. It is a workflow FAQ built to reduce preventable metadata mistakes.
How IPTC keywords map into XMP-ready stock files
In Stocktag, keywords, title, and description can travel in two directions: export-ready CSV files for marketplace upload, and embedded metadata for file-based handoff. The embedded path uses XMP-friendly structures so JPEG and EPS workflows can carry metadata with the file.
For contributors, the practical question is not “IPTC or XMP?” but “Which platform still needs CSV, and which parts of the file metadata should I review before upload?” This page exists to answer that operational question.
Use CSV when the marketplace upload form expects platform-specific columns
Use XMP embedding when you want metadata to travel with JPEG or EPS assets
Keep keyword order review in the workflow before export, not after upload
Treat embedded metadata as a handoff layer, not a guarantee that every marketplace will import every field identically
Why keyword review still matters before IPTC or XMP export
Embedding weak keywords does not make them safer. If the first terms are low-intent, repetitive, or unsupported, those problems travel into the file and into the CSV. Review comes before export for a reason.
That is especially important when Adobe Stock first-10 order matters, Shutterstock spam rules matter, or Getty/iStock controlled-vocabulary review needs a separate pass.
Push the strongest subject and concept terms to the front before export
Trim irrelevant keyword spam before it reaches CSV or XMP
Run Getty/iStock vocabulary review separately when that workflow applies
Use batch review to keep keyword rules consistent across the portfolio
When to use CSV exports instead of embedded metadata
CSV is still the safer choice when the marketplace expects specific column order, field naming, and keyword limits. Embedded metadata helps your files travel cleanly, but platform-specific CSV presets are what keep multi-marketplace upload operations predictable.
In practice, many contributors use both: review metadata once, export CSV for the upload interface, and keep embedded metadata in the files for downstream archive or handoff consistency.
Use platform presets when field names and limits differ across sites
Use embedded metadata when you want the asset package to stay self-describing
Keep CSV and XMP outputs aligned from the same reviewed metadata session
Do not maintain separate keyword sets by hand unless the platform rules truly diverge
Safe processing, local handling, and export boundaries
Stocktag already separates guest preview, browser-direct BYOK, and full studio export workflows. That matters for privacy messaging as much as for SEO messaging: local preview and browser-direct runs are not the same thing as offline processing.
The safe way to describe this workflow is simple: review metadata before export, understand where the request runs, and choose CSV, XMP, or both based on the target platform.
Guest previews run locally with sample flows before real processing starts
Browser-direct BYOK keeps the key out of Stocktag servers but still sends the request to the model provider
Full studio mode is for batch processing, QA, CSV export, and embedded metadata delivery
Privacy claims should stay precise: local preview, browser-direct, and full export are different modes
FAQ
Quick answers to the workflow questions that usually come up before CSV or XMP export.
Does Stocktag act as an IPTC keyword generator for stock photos?
It helps you generate and review stock keywords, then move them into CSV exports or XMP-ready embedded metadata workflows. The operational goal is cleaner stock metadata, not a standalone IPTC-only generator.
What is the difference between IPTC keywords and XMP embedding in this workflow?
For contributors, XMP is the practical embedding layer that carries title, description, and keywords inside supported files. CSV remains important when a marketplace expects upload-specific columns or platform-specific formatting.
Should I rely on embedded metadata instead of CSV exports?
Usually no. Embedded metadata is useful for file handoff and archive consistency, but platform-specific CSV exports are still the safer operational path when upload forms require exact columns and field limits.
Can I review keyword order before embedding metadata?
Yes. That is the intended workflow. Review first-10 ordering, trim irrelevant keyword spam, and approve the final set before generating CSV or embedded exports.
Does this page replace the main metadata generator?
No. This FAQ page explains IPTC, XMP, and CSV workflow decisions. Use the main metadata generator for production work, batch processing, QA, and marketplace-ready exports.
Related Pages
Open the workflow page that matches the next decision in your stock metadata process.
Open the stock photo XMP generator
/stock-photo-xmp-generator
Open the stock photo CSV generator
/stock-photo-csv-generator
Generate the full metadata set
/stock-photo-metadata-generator
Review Adobe Stock keyword order
/adobe-stock-keyword-order
Review Getty/iStock keyword workflow
/getty-keywords-generator
Support hub
Choose the fastest route to an answer
Use the assistant for quick guidance, email a real person for private or account-specific help, and keep product ideas visible on the feedback board.
Talk to a real personUse email for account, billing, security, private, or unresolved issues.support@stocktag.aiEmail human support
Share a product ideaStart a public request, follow its status, and continue the discussion.Open feedback board