Most stock contributors handle categories and model or property releases inside the agency portal, one asset at a time. Only a few tools carry both through a bulk pipeline: StockSubmitter, Microstock+, Xpiks with its release plugin, and Wirestock. Metadata-first tools like PhotoTag.ai and Rastock AI write titles and keywords in bulk but leave signed releases to the portal.
Why categories and releases break bulk workflows
Titles, descriptions and keywords are the easy part of stock metadata. They are text fields, they travel inside IPTC and XMP, and any AI tool can write them into a file. Categories and releases are different, and that difference is why most contributors still open the agency portal even when they have automation elsewhere in the pipeline.
A category is not free text. Each agency keeps its own closed list, and the value only exists in that agency's namespace. Adobe Stock asks you to pick one category from a list of 21 and suggests one automatically through Adobe Sensei; Shutterstock lets you assign up to two categories per submission. There is no IPTC field that means "Adobe category 5 and Shutterstock categories 3 and 11" at the same time, so a tool that wants to set categories has to hold a per-agency mapping table and push each value through that agency's own submission channel.
A release is not metadata at all. It is a signed legal document — a PDF or image — that must be uploaded separately and then linked to the assets it covers. Shutterstock requires a separate model release for each recognisable person in the frame, so a photo with five recognisable models needs five release attachments. Releases are also required in cases people forget: a visible tattoo on an otherwise unrecognisable body part, a nude or sexually suggestive concept even when the model is unrecognisable, and illustrations or animations made in the likeness of a real person.
So the honest framing is: "attach releases automatically" almost always means "store the signed PDF once, then reuse it across many submissions" — not "generate the release for you". Any tool claiming more than that is worth reading carefully.
Tool comparison: who actually handles categories and releases
Six tools contributors commonly evaluate for this, with what each is genuinely good at, how it charges, and where it stops.
StockSubmitter / Microstock+
- Best for: contributors who want one desktop app to fill metadata, attach releases and submit to dozens of agencies in a single pass. It is the most complete release handling in this list: files carry a release-count badge (1R, 2R, 3R and so on) on the thumbnail, and it can import releases created in Easy Release.
- Pricing model: tiered subscription with a free tier — a free plan covering a limited number of submissions per month, rising to a flat monthly fee for unlimited submissions. Uploading files themselves is not metered.
- Main limitation: the interface is dense and the learning curve is real. Microstock+ is the cloud successor built by the same team, and it routes files through its own servers before delivering to agencies, which some contributors are not comfortable with. Its AI keywording is not the product's strength — metadata quality is on you.
Xpiks
- Best for: photographers who prefer a local desktop editor with tight control over metadata. Strong at multi-file editing, keyword presets, autocompletion, spellcheck, copy-paste of metadata between artworks and CSV export.
- Pricing model: paid tiers, with model release handling available as a plugin on the higher plan. The release plugin uses the Shutterstock template, which other marketplaces generally accept, and lets you produce a release without opening a PDF editor.
- Main limitation: release creation lives behind the plugin marketplace on the top tier, so it is not part of the baseline product. Category assignment across many agencies is not its focus, and the app is desktop-bound — no server or scheduled batch mode.
Wirestock
- Best for: contributors who want releases stored once and reused across everything they submit through the platform. Release creation is genuinely well built into the submission flow, and stored releases can be reattached to later images and videos.
- Pricing model: commission-based rather than subscription — a percentage of sales, historically around 15% on sales distributed to partner agencies and 30% on direct sales from the platform.
- Main limitation: the important one, and it is recent. Wirestock has moved toward supplying creative multimodal data to AI labs, and under its updated terms it stopped licensing new content submitted after 20 January 2026 to content marketplaces. If your goal is distribution to Adobe Stock, Shutterstock and similar agencies, verify current terms before building a pipeline on it.
PhotoTag.ai
- Best for: adding AI titles, descriptions and keywords to a batch quickly, especially inside a Lightroom Classic workflow. Also offers an API and translation into 15+ languages, which matters for agencies that reward localised metadata.
- Pricing model: credit packs, with a free allocation to start and a bring-your-own-API-key option that raises the daily ceiling considerably.
- Main limitation: no release management and no per-agency submission. It writes metadata and exports CSV; categories and releases stay in the portal. Best suited to lower monthly volumes.
Agency-native portals (Adobe Stock, Shutterstock)
- Best for: correctness. The portal is the only place where a release is definitively accepted, and it is where category lists are authoritative. Adobe Sensei suggests a category on upload, which removes most of the guesswork for single files.
- Pricing model: free — it is part of being a contributor.
- Main limitation: it does not scale. Assigning categories and attaching releases per asset in a browser is the exact bottleneck that pushes contributors to third-party tools once volume passes a few hundred files a month.
Rastock AI
- Best for: the metadata and delivery half of the pipeline at volume — AI-written titles, descriptions and keywords, IPTC and XMP embedding, per-agency CSV export, and direct FTP or SFTP delivery to 25+ agencies. Its copyright guard flags visible trademarks, logos and recognisable faces before submission, which is useful precisely because it tells you which files will need a release.
- Pricing model: subscription, with no revenue share and no ownership claim on your files. Metadata is exportable as IPTC, XMP and CSV, so nothing is locked in.
- Main limitation: Rastock does not store or transmit signed release documents. It will tell you a file needs one; uploading and linking the signed PDF still happens in the agency portal. If release storage is the single feature you are shopping for, StockSubmitter or Wirestock cover it and Rastock does not.
When to use each tool
StockSubmitter/Microstock+ vs Rastock AI
Use StockSubmitter or Microstock+ when release attachment is a daily operation — people photography, lifestyle shoots, anything with recognisable faces in nearly every frame. The release badge and per-agency submission are worth the interface. Use Rastock AI when metadata quality and delivery volume are the bottleneck and releases are occasional: AI keywording, IPTC embedding and FTP/SFTP to many agencies at once, with the handful of released files handled in the portal.
Xpiks vs Rastock AI
Use Xpiks if you want a local desktop app, full manual control of every keyword, and are willing to buy the top tier for the release plugin. Use Rastock AI if you would rather not sit in a metadata editor at all and want the pipeline to run to the agencies without a per-file pass.
Wirestock vs everything else
Wirestock's release handling is strong, but its model is a commission on your sales rather than a fee for software, and its 2026 shift toward AI-lab data licensing changes what "distribution" means on the platform. Choose it deliberately, after reading current terms — not by default because release storage is convenient.
PhotoTag.ai vs Rastock AI
Both are metadata-first and neither handles releases. PhotoTag.ai fits a Lightroom-centred workflow at modest volume with credit-based pricing. Rastock AI fits multi-agency delivery at scale, where per-agency CSV formats and FTP batches matter more than a Lightroom panel.
If you are under 500 files
Do it in the portal. At that volume the agency's own uploader plus a metadata tool is faster than configuring a submission pipeline, and Adobe's automatic category suggestion removes most of the friction. Automation earns its keep when the same release has to be attached to hundreds of files across several agencies.
A workable division of labour
Most contributors running real volume end up splitting the job rather than looking for one tool that does everything. A pattern that holds up:
- Shoot-level release capture. Collect and sign releases at the shoot, not months later. Name the file after the shoot and the model so it can be matched to assets by folder.
- Bulk metadata separately from releases. Generate titles, descriptions and keywords across the whole folder and embed them into the files, so the metadata travels with the asset regardless of which submission route it takes.
- Flag before you submit. Run a check for recognisable faces, visible logos and trademarks so you know which files are blocked pending a release, instead of discovering it through a rejection.
- Split the batch. Released files go through whichever route can attach the document; unreleased editorial and object work goes through the fast bulk channel.
- Map categories per agency, once. Build the mapping table for the agencies you actually use and reuse it — this is a configuration job, not a per-file decision.
The rejection cost of getting this wrong is asymmetric. A weak keyword set loses you some search visibility; a missing release gets the file refused outright, and repeated refusals affect how an agency treats your account. Our guide to Adobe Stock rejection reasons covers the release-related refusals in detail, and the stock photography workflow guide places release capture in the wider shoot-to-sold sequence.
What to check before committing to a tool
- Does it store the signed release, or only remind you that one is needed? These are very different features described with similar words.
- Can one stored release be reattached to future uploads, or does each submission need a fresh upload?
- Does it maintain category mappings for the specific agencies you use, or only for the two or three largest?
- Does the pricing take a share of your sales, or charge for the software? Commission models get more expensive as you succeed.
- Can you export your metadata as IPTC, XMP or CSV and walk away? If not, you are betting your archive on the vendor's continuity.
On that last point: Rastock AI charges a subscription, takes no revenue share, claims no ownership of your files, and keeps metadata exportable as IPTC, XMP and CSV. The full capability list is on the features page and current tiers on the pricing page. It is the right tool for the metadata and delivery half of this problem, and the wrong one if signed-release storage is your primary requirement.
Frequently asked questions
Can any tool automatically attach model releases for me?
Partly. StockSubmitter and Microstock+ store signed releases and attach them to submissions, showing a release-count badge on each thumbnail. Wirestock stores releases and reuses them across submissions made through its platform. Xpiks can generate a release via a plugin on its top tier. None of them sign the document for you — you still capture the signature at the shoot.
How many model releases does one photo need?
One per recognisable person. Shutterstock states that a photo with five recognisable models requires five separate release attachments. Releases are also required for a visible tattoo on an otherwise unrecognisable body part, for nude or sexually suggestive concepts even when the model is unrecognisable, and for illustrations created in the likeness of a real person.
Why can't categories be embedded in the file like keywords?
Because categories are agency-specific closed lists, not a standard metadata field. Adobe Stock asks for one category from its list of 21; Shutterstock allows up to two per submission. There is no IPTC or XMP field that carries both agencies' values simultaneously, so category assignment has to happen per agency at submission time.
Does Rastock AI handle model releases?
No. Rastock AI generates metadata, embeds IPTC and XMP, exports per-agency CSV and delivers files over FTP or SFTP to 25+ agencies. Its copyright guard flags recognisable faces, logos and trademarks so you know which files need a release, but the signed document itself is uploaded and linked in the agency portal.
Is Wirestock still a viable distribution route in 2026?
Check current terms before relying on it. Wirestock has shifted toward supplying multimodal creative data to AI labs, and under its updated terms it stopped licensing new content submitted after 20 January 2026 to content marketplaces. Content submitted before that date remains under the earlier terms. Its release handling is good; its distribution scope has changed.
At what volume is a submission tool worth it?
Roughly when portal work stops fitting into the gaps of your day. Under a few hundred files a month, the agency uploader plus a metadata tool is usually faster than configuring a pipeline — and Adobe suggests a category automatically. Above that, especially with releases repeating across many files and agencies, the setup cost pays back quickly.