Why duplicate uploads get stock footage accounts suspended

A duplicate upload is a stock footage mistake that can cost more than the clip itself. Re-uploading a corrected file is what triggers Adobe's duplicate detection, and in the reports we have read it is the most-attested cause of contributor account suspension.

Adobe's contributor agreement does not mention duplicates at all. What it does say, in §8.1, is this: "We may terminate these Product Specific Terms, remove any Work, or suspend your account, without prior notice." Getty's upload dialog, read on 2026-09-11, asks you to agree that failing its upload requirements "can result in account suspension or closure".

Nothing below makes an account safe, and no tool can promise that. What follows are the rules each marketplace sets, what we measured, and two duplicates we made ourselves while building Rushlot, told plainly because they are the most useful part.

What counts as a duplicate

A duplicate is the same clip twice on the same marketplace. That includes:

• a corrected re-upload (a better title, a trimmed head, a fixed frame rate);
• a re-export of the same shot at another resolution or bitrate;
• the same file sent twice because the first send looked like it had failed.

Selling one clip on several marketplaces is a different thing. Pond5's FAQ states that it is non-exclusive by default and that the same clip may be sold on Adobe and Getty.

Adobe's refusal reasons also include one for resemblance. Its Not accepted tab, read on a live contributor account on 2026-09-16, uses the reason SIMILAR CONTENT IN OUR COLLECTION alongside QUALITY ISSUES and INTELLECTUAL PROPERTY REFUSAL.

The rules, marketplace by marketplace

Adobe Stock. On the account we measured, twelve clips uploaded by SFTP were found in the In review tab two days later, carrying their embedded title and keywords, with nothing clicked in the portal. So there is no quiet staging area where a mistake can be fixed before review. The only safe moment to correct a clip is before it is sent.

Pond5. The full sentence from Pond5's FAQ: "Resubmitting rejected content (or deleting and resubmitting pending content) will result in rejection". Pond5's upload-time duplicate detection is also reported to remember deleted files, and its legal guidelines link repeated submission to suspension. The way out is in place: Pond5's edit form and its Apply CSV correct a clip that is already on the account.

Shutterstock. Measured on 2026-09-11, Shutterstock ingested a file into the portal about two seconds after the transfer, and the file was gone from the FTPS root by the next listing. You cannot ask the server whether a clip is already there. The only thing that knows a clip was sent is your own record of it.

Two duplicates we made, and what they taught us

One file name in two folders (2026-09-17)

A lot we sent held the same shot twice: the contributor's own export, and a 1080p re-export made by mistake during our own work, under the same file name in two different folders. It went to Adobe, Getty and Shutterstock as a duplicate pair.

Every check we had compared file paths, and two folders make two different paths. Nothing looked at the name. Only Pond5 refused the pair, and only because Pond5 names a clip by its file name.

Since then Rushlot checks the name twice: once when a clip joins a lot, and again over the whole lot before any byte moves, for every marketplace. When two clips share a name, neither is sent. Not "the first one wins": the app cannot know which of the two is the footage you mean to publish, so it sends neither and tells you why. (One exception: if one of the two is already delivered somewhere and the other is not, the delivered one finishes its remaining marketplaces, one copy each, and its twin stays refused.)

Twenty-six pairs from a misread dry run (2026-09-18)

A 32-clip lot went to Pond5 over one FTPS session. Every transfer ended with 226 Transfer complete. Pond5's dry run, a check that lists which file names the account holds, then listed 6 of them and no more.

The next day's reading was: 26 clips were dropped. They were re-uploaded under shorter names. That reading was wrong. Pond5 stores a file name cut to 80 characters, the dry run is keyed on the full name, and 26 names were longer than 80. All 26 clips had been ingested the first time. The re-upload put 26 duplicate pairs on the account, which is exactly what Pond5's rule forbids.

The account's own catalogue export, read on 2026-09-19, showed every one of the 26 present under its name cut at 80 characters. Deleting the older copy of each pair was then authorised on 2026-09-19.

The lesson is not about Pond5's name length (the Pond5 FTP upload guide covers that). It is this: a check that does not find a clip does not prove the upload failed. The marketplace's own record is one read away, and it has to be read before anything is sent again.

"I can't see it" is not "it failed"

What each marketplace looked like when a clip seemed to be missing:

• Adobe Stock. On 2026-09-07 the portal's New tab was empty. The clips had moved on to In review, and the banner said moderation "may take up to 8 weeks". A listing of the SFTP drop returned nothing for any path, including invented ones.
• Pond5. A new clip sits in processing before any CSV can reach it: under four minutes for one 224 MB clip on 2026-09-11, about three minutes for a 15-clip lot on 2026-09-16. Until then it is simply not listed. The catalogue export is the account's own answer.
• Shutterstock. Its help centre says ingestion can take up to 72 hours. The account we measured saw two seconds, but a slow day is not a lost file.

A checklist before anything is sent twice

• Review before upload. Title, keywords, specs and the thumbnail frame, before the transfer.
• One file name, one clip. Look for the same name in two folders, and the same shot at two resolutions.
• Keep one record per clip per marketplace: what was sent, when, and how many bytes arrived.
• Read the marketplace's own record before any resend. Adobe: In review, Not accepted and your portfolio. Pond5: the catalogue export. Shutterstock: the Not submitted tab.
• Correct in place, never by deleting and re-uploading.

This is how Rushlot is built. Every clip stops for your review before upload. It keeps one record per clip and marketplace, refuses both clips of a same-name pair, and calls a clip it has not seen yet "not yet", never "lost". It never re-uploads. None of that is a promise about what a marketplace decides; it is the set of rules that keeps the same clip from being sent twice.