Sending the same file to Shutterstock, Adobe Stock and Alamy is not a duplicate upload — all three are non-exclusive and expect it. The problem worth solving is sending the same file twice to one agency, or shipping a batch of near-identical frames. Both are refusal categories, and both usually come from losing track of what already went where.
Three different problems share the word “duplicate”
Same file, several agencies — allowed by design
Shutterstock states its position plainly in its content exclusivity policy: it operates on a non-exclusive basis, you retain full copyright, and you may upload work to Shutterstock that is already selling elsewhere, or upload elsewhere work already selling on Shutterstock. Adobe Stock and most other microstock agencies work the same way.
The one thing that breaks this is an exclusivity agreement you signed somewhere else. Shutterstock's own guidance points at exactly that risk — if another platform requires exclusivity for a file, you cannot sell that file anywhere else, including Shutterstock. So the check before wide distribution is not “is this a duplicate” but “have I committed this file to anyone exclusively.”
Same file, same agency, twice — a rejection
This is the one people mean when they say duplicate upload. Shutterstock refuses it under “Previously Submitted Content” or “Submitted to a Different Account”, and the second label carries real weight: it means the file already exists in someone else's contributor account, and the help page notes that submitting content you do not own or control can cost you the account.
For an honest contributor this usually has a boring cause — a re-run batch, a folder uploaded twice after a failed transfer, or a file that moved between drives and got picked up again by a scanning tool. It is a bookkeeping failure, not a rights problem, but the rejection reads the same either way.
Near-identical frames — the expensive one
Adobe Stock treats similarity as one of the top reasons it refuses content, and its distinct content guidelines define it wider than most contributors expect: the same subject from slightly different angles or distances, identical concepts with minor colour or filter variations, sequential shots from one moment with little meaningful difference, and — notably — different images carrying identical titles and keywords, which signals they serve the same customer need.
That last criterion is the one automation makes worse. If a tool writes one metadata set across a whole folder, forty distinct frames can be flagged as serving one need purely because their titles and keywords match. The images were fine; the metadata created the duplicate.
Why contributors lose track in the first place
Nobody re-uploads a file on purpose. Duplicates appear because the record of what was sent lives in several places at once, and none of them is authoritative.
- Partial batches. A transfer fails at file 380 of 500. You re-run it, and the first 379 arrive a second time.
- Re-exports. The same shot exported again at a different size or with new retouching gets a new filename, so no local check catches it, but the agency's visual matching does.
- Drive migrations. Archives get copied to a new disk, a scanning tool indexes the copy, and previously submitted work re-enters the queue.
- Mixed methods. Some files go by FTP, some through a web form, some through a third-party tool. Each records its own history, and no view covers all three.
The fix is structural rather than clever: one place that knows which file went to which agency and when, and one rule about what gets to touch that record.
Tools people actually use, and what each does about duplicates
StockSubmitter
A desktop application that has been in the market over a decade. Its own site lists 40 supported agencies and a per-agency submission model: a free tier gives 33 submissions per month to each agency, with paid tiers stepping up to unlimited. Uploading files is free and unlimited; only the submit-for-review step is metered. It tracks approval status and sales, which is the record you need when checking whether something already went out.
The main constraint is the platform: the desktop build is Windows only, and its site directs macOS users to the browser-based Microstock+ instead. Passwords stay on your own machine, which some contributors prefer and others find awkward when working from two computers — because then the submission history lives on two machines too.
Microstock+
The browser-based sibling of StockSubmitter, from the same company. Its site lists 33 supported agencies and states that it monitors files after they have been sent for review, so you can see the approval status of every file at every agency. For duplicate prevention that server-side history is the strongest thing on offer here — it does not vanish when you change computers.
The trade-off is where credentials live: Microstock+ states that passwords are kept on a remote server in encrypted form, whereas the desktop product keeps them locally. Which of those you prefer is a judgement about your own risk tolerance, not a question with one right answer.
Xpiks
A cross-platform desktop tool for Windows, macOS and Linux. Xpiks edits XMP, IPTC and EXIF metadata directly, uploads over FTP, SFTP or FTPS to predefined or custom hosts, and checks files for problems before they go out. Two paid Pro features bear directly on this topic: upload history, and a similar-images view for spotting near-duplicates before you submit them.
Its limitation is scope. Xpiks is a strong metadata and transfer tool, not a portfolio system — it moves files where you point it and records that it did so, but it does not follow what the agency later decided about them. If you want approval outcomes in the same place as submission history, this is not that tool.
Wirestock
A managed pipeline rather than a tool you drive. You submit once, Wirestock handles metadata and distribution to its partner agencies, and it takes a share of the royalties those assets earn. Because one party controls the whole distribution step, duplicate submissions are largely designed out — the platform knows what it sent and where. Check the current commission on their own site before deciding; rates change.
The cost is control and margin. You give up a percentage of every sale for the life of the asset, and you accept their metadata decisions and their agency list rather than your own. For contributors who value not thinking about the pipeline, that is a fair trade. For contributors optimising long-term earnings on a large portfolio, the arithmetic usually goes the other way.
The agencies' own portfolio tools
Every major agency gives you a portfolio view where you can search what you already have live with them. It is free, it is authoritative for that one agency, and it is the only record the agency itself considers true. What it cannot do is answer a cross-agency question: nothing inside Adobe's portfolio knows whether a file also went to Pond5 last March.
Used well, they are the audit layer rather than the working record — the place you verify against when a tool's history and your memory disagree.
Rastock AI
Rastock AI generates metadata from the image itself and delivers to 10+ agencies over FTP or SFTP, applying each destination's rules separately rather than shipping one identical metadata set everywhere — which is what makes forty distinct frames look like one asset to a reviewer. Delivery status is tracked per file per destination, so the record of what went where is a single view rather than several. The feature breakdown and the supported destinations are both public.
Where it does not fit: if you want a single company to handle submission, moderation follow-up and payment on your behalf, a managed service does more of the work. Rastock does not take a revenue share and does not claim ownership of your files, but it also does not stand between you and the agency — the contributor accounts remain yours to manage.
When to use which
- Under a few hundred files a year, on one computer: the agencies' own portfolio views plus a spreadsheet are genuinely enough. Adding a tool adds a second record to keep in sync.
- Windows, high volume, many agencies, want approval status in one place: StockSubmitter or Microstock+, depending on whether you want the history on your machine or on their server.
- macOS or Linux, and you want metadata written into the files themselves: Xpiks, with upload history enabled so the record survives past the transfer.
- You would rather not run a pipeline at all: a managed service like Wirestock, accepting the royalty share as the price of never thinking about it.
- You want per-agency metadata rules and no revenue share, with delivery tracked per destination: Rastock AI.
A routine that prevents duplicates whatever tool you use
- Cull before metadata, not after. Choose the two or three strongest frames from a sequence while you still remember the shoot. Adobe's guidance is explicit that submitting only the most distinctive variations is the intended behaviour.
- Give every file one permanent identifier and never rename it. A re-export at a new size should keep the same base name plus a suffix, so a text search finds both versions.
- Vary titles and keywords across a series, even when the frames genuinely differ. Identical metadata is itself a similarity signal, which is also why cleaning up old keyword sets tends to help more than contributors expect.
- Move finished batches out of the staging folder the moment a transfer confirms. An empty staging folder is a record you cannot misread.
- Treat a failed transfer as a partial one until proven otherwise. Check what landed before re-running, rather than resending the whole batch — which is where multi-agency upload automation earns its keep, because it resumes rather than restarts.
If you want to test the per-destination approach against your own archive, Rastock AI runs a 14-day free trial with no card required, and the plans are on the pricing page. Two weeks is enough to push one real batch through and compare the rejection notices against what you were getting before.
Frequently asked questions
Can I upload the same photo to multiple stock agencies?
Yes, in almost every case. Shutterstock's exclusivity policy states that it operates non-exclusively, you keep full copyright, and you may sell the same work on other agencies. Adobe Stock and most microstock platforms work the same way. The exception is content you have committed exclusively to one platform — that file cannot be sold anywhere else while the agreement holds.
What does “Previously Submitted Content” mean on Shutterstock?
It means the file has already been submitted — either by you or, under the related “Submitted to a Different Account” label, in another contributor's account. Shutterstock does not accept duplicate content. For most contributors the cause is a re-run batch or a re-indexed archive, but the second label is treated seriously because it can indicate content the submitter does not own.
Why does Adobe Stock reject my images as similar content?
Adobe defines similarity broadly: the same subject from slightly different angles or distances, identical concepts with minor colour or filter changes, sequential shots from one moment, and different images carrying identical titles and keywords. That last one catches a lot of automated workflows — distinct frames get flagged simply because one metadata set was applied across the whole folder.
How do I keep track of which files went to which agency?
Keep one authoritative record and verify it against agency portfolios rather than the reverse. Tools like Microstock+ hold submission and approval status server-side so it survives a change of computer; Xpiks Pro keeps an upload history locally. Whichever you use, the failure mode to avoid is several partial records — an FTP log, a spreadsheet and a memory — with no single view.
Does re-exporting an image at a different size count as a duplicate?
To a filename check, no — which is exactly the problem. To an agency's visual matching it is the same image, so a re-export submitted alongside the original is likely to be refused. If you re-export for retouching or a size change, replace the file rather than adding it, and remove the earlier version from your portfolio first where the agency requires that.
Is it worth using a tool just to prevent duplicate uploads?
Below a few hundred files a year, usually not — the agencies' own portfolio search plus a simple spreadsheet is enough, and a second record only creates a sync problem. Above that, and especially across five or more agencies, a single tracked view pays for itself in avoided refusals and in not re-keywording work you already published.