How do I automate stock footage uploads to Adobe Stock, Shutterstock, Pond5 and Getty?
What you can safely automate in a stock footage upload, agency by agency: file checks, XMP, FTP, CSVs. What must stay manual, and what the terms say.

You can automate most of a stock footage upload: the file checks, the repairs, the metadata and the transfers to Adobe Stock, Shutterstock and Pond5. Getty's ESP has no FTP, and no agency we checked offers a public upload API (read September 2026). Keep three things manual: review before upload, Submit, and any resend.
I build Rushlot, a Mac and Windows app that automates this for my father's underwater footage, so I am not neutral. Every timing below comes from our own live accounts, and I also show what you can do without our app. A value marked measured was read on a live contributor account.
Which parts of a stock footage upload can you automate?
Almost everything between your finished export and the agency's queue. The exceptions are the steps where a person's judgement is the point.
| Step | Automate it? | How | The limit |
|---|---|---|---|
| Check the file against specs | Yes | ffprobe, or a spec checker | It cannot judge shake or grading |
| Remove audio, convert HEVC | Yes, on a copy | ffmpeg | Never touch your original |
| Draft titles and keywords | Draft only | From your own title, one set per agency | Every word still needs reading |
| Review each clip | No | You | The last moment a mistake is cheap |
| Write the metadata into the file | Yes, last | ExifTool | Adobe and Pond5 read it; ffmpeg strips it |
| Transfer the file | Yes, on three agencies | SFTP, FTPS or FTP | Getty needs its web page |
| Apply a CSV | Partly | The agency's own import page | It is a browser step |
| Check that it arrived | Yes, reading only | Byte count, then the portal | "Not found yet" is not "failed" |
| Press Submit | No | You | Rushlot never does |
| Resend a missing clip | Never automatically | You, after looking | This is how duplicates happen |
Which upload route can a script use on each agency?
Three agencies give you a file server, and only one of those is gated. Getty gives you a web page.
| Agency | Route a script can use | What still needs the browser | Timed on our accounts |
|---|---|---|---|
| Adobe Stock | SFTP, qualified accounts only; otherwise none | Web upload for accounts without SFTP | Sign-in in 2.1 s (2026-09-03) measured |
| Shutterstock | Explicit FTPS, port 21; its help names no threshold | The CSV import and Submit | 17 clips, 7.81 GB in 6.5 min (2026-09-16) measured |
| Pond5 | FTP, explicit FTPS also works measured | Apply CSV and Submit | Lot of 15 clips in 9.8 min, processing and CSV included (2026-09-16) measured |
| Getty / iStock | None: ESP in the browser, no FTP or SFTP measured | The upload, the CSV and Submit | One clip in 11.5 s (2026-09-08) measured |
Your line will change those times. The caps will not: Shutterstock takes 100 video clips in any 7 days (help, dated 2025-04-21), and Adobe has a weekly limit it does not publish. Automation does not lift either one.
The detail of each route, with hosts, logins and the export that passes all four, is in upload stock footage to multiple sites.
Is there an API that uploads to stock agencies?
No public one that we found. Adobe states that it has no contributor API. Shutterstock's API reference lists a few read-only contributor endpoints and none that uploads or submits (read in September 2026). We found none for Pond5 or for Getty and iStock.
So, as far as we can see, a tool that uploads to these agencies has the same doors you do: the file servers and the agencies' own web pages. Rushlot uses those. A product page that promises "direct integration" should tell you which door it means.
What can you script yourself in ten minutes?
The file work. These commands ran on a test clip with ffmpeg 8.1 and ExifTool 13.55 on 8 November 2026. They write new files and leave your originals alone.
Copy every H.264 .mov in a folder into MP4 with no audio track. -n refuses to overwrite anything:
mkdir -p out
for f in *.mov; do ffmpeg -n -v error -i "$f" -map 0:v -c copy "out/${f%.mov}.mp4"; done
This only works for H.264 sources: HEVC needs a real conversion. Check what you got:
ffprobe -v error -select_streams v:0 -show_entries stream=codec_name,width,height,r_frame_rate:format=duration -of default=nw=1 out/clip.mp4
Then write the title and keywords into the copy, as the last step before upload. With -sep, one comma-separated value becomes a real list:
exiftool -overwrite_original -sep ", " -XMP-dc:Title="Green sea turtle over a coral reef" -XMP-dc:Subject="green sea turtle, coral reef, underwater" out/clip.mp4
Read it back. The keywords should come out separated by bars:
exiftool -G1 -a -sep " | " -XMP-dc:Title -XMP-dc:Subject out/clip.mp4
The transfers can then go through FileZilla or Cyberduck, with one saved site per agency: Adobe's and Pond5's passwords for these servers are not your website passwords. Adobe and Pond5 are the only agencies that read this metadata; the other two need a CSV.
What should you never automate?
Three things: the review, the Submit and the resend.
The review. On Adobe, 12 clips delivered by SFTP with an embedded title and keywords were in the In review tab two days later, with nothing clicked in the portal (2026-09-07) measured. On that route, the upload is the submission. A review after it comes too late.
The Submit. Some tools press it for you. StockSubmitter's pricing page defines a submission as "sending it for review automatically", and CyberStock's guide describes a mode that "fills everything and clicks Submit" (both read 2026-09-27). We chose the opposite. The person who filmed the clip should be the last one to look at it. That is a product choice, and it costs clicks.
The resend. This one we learned the hard way. On 17 September 2026, a lot of 32 clips went to Pond5, and our automated check found only 6 of them. On 18 September we read that as 26 lost clips and sent them again. All 26 had arrived the first time, under names Pond5 had cut at 80 characters. The result was 26 duplicate pairs on one account. The lesson is in stock footage duplicate upload: a check that does not find a clip does not prove the upload failed. No script should be allowed to act on that by itself.
Do the agencies' terms allow automation?
Partly unclear, and the honest answer depends on the door. This is what we could read.
| Agency | What we read | Date read |
|---|---|---|
| Adobe | General Terms §6.6 forbids accessing the services "by any means other than the interface we provide or authorize"; §6.7 forbids circumventing access restrictions. The Contributor Agreement has no clause on automation that we found, and §8.1 allows suspension "without prior notice" | 2026-09-25 |
| Getty Images | Site Terms forbid "using any data mining, robots or similar data gathering or extraction methods" and "circumventing, disabling or otherwise interfering with security-related features". The contributor agreement was not read | 2026-09-25 |
| Shutterstock | Full terms not readable from where we tried. A search result suggests limits on robots and data gathering; we could not confirm it on the page. The 2023 contributor terms update has no clause on automation that we found | 2026-09-25 |
| Pond5 | Full terms not readable from where we tried. A search result suggests limits on automated access; we could not confirm it on the page | 2026-09-25 |
On Adobe's forum, a volunteer expert wrote in May 2024 that automated submission is not allowed. That is a volunteer's reading, not Adobe's text, and we found no Adobe statement either way.
Here is how we read it. Sending a file to the server an agency runs for that purpose is what the server is for. Driving an agency's web pages with software is greyer, and Rushlot does that too: in your own signed-in window it uses Adobe's web uploader when you have no SFTP, Getty's ESP and the Shutterstock and Pond5 CSV imports, and it reads portal pages to see what arrived. If a security check appears, it stops and hands the window to you, and it never solves a CAPTCHA. After about five sign-ins in 15 minutes, Getty showed an anti-bot challenge on our account measured, so a script that signs in again and again will be noticed. No tool, ours included, can tell you any of this is free of risk. Read your own agreement.
Where does the time really go?
In the metadata and the checks. The transfers above take minutes. Each agency then wants its own title length, keyword count and fields, and two of them ignore what is in the file.
My father, Hervé Berthou, films the underwater footage Rushlot was built for and sells it on all four agencies as Seafootage. He put 60 videos on the four marketplaces in about 1 hour with Rushlot, against about 40 hours before, and he already used ChatGPT for the metadata then. That is one contributor's estimate, and he is my father: read it as that, not as a promise.
Which tools automate stock footage uploads?
Several, and they differ on who presses Submit and where your files go. All of this comes from each vendor's own pages, on the date shown.
| Tool | Read on | Uploads to | Who presses Submit | Runs on |
|---|---|---|---|---|
| StockSubmitter | 2026-09-27 | 40 agencies listed, some upload-only | The tool: "sending it for review automatically" | Windows; online version for macOS and iOS |
| Microstock+ | 2026-09-27 | 33 agencies, delivered "from our servers" | The tool can "auto submit" | Any browser |
| SendStock AI | 2026-11-08 | Any agency with FTP or SFTP | Its pages do not describe pressing Submit | Windows, macOS, web |
| MetaMule | 2026-11-08 | Pond5, Shutterstock and Adobe Stock by FTP; a CSV for each marketplace | Its page does not say | macOS, Windows |
| CyberStock | 2026-09-27 | Its CyberPusher tool, with a full-automatic mode | The tool in full-automatic mode; you in semi-automatic | Web |
| Rushlot | 2026-11-08 | Adobe Stock, Shutterstock, Pond5, Getty ESP | Never the tool. You do, except that an Adobe SFTP delivery goes into review on its own | Mac and Windows |
The stock video submission tools comparison has the detail. For one tool at a time: Rushlot vs StockSubmitter, Rushlot vs MetaMule, Rushlot vs SendStock AI, or all comparisons.
A checklist before you automate anything
- Work on copies. Nothing should ever write to your original clip.
- Pick one file naming rule that fits every agency: 76 characters or fewer, letters, digits and underscores. The Pond5 file name sanitizer checks one.
- Write the metadata last, after every conversion.
- Keep one record per clip and per agency: what was sent, when, and how many bytes arrived.
- Stop at the first error instead of retrying blindly, and never let a script resend.
- Respect the caps with a weekly lot you can review.
- Press Submit yourself, after looking.
What have we not measured?
- Whether an agency treats a large automated lot differently from the same lot sent by hand. None says so.
- How long a 1 to 4 GB clip takes through Adobe's web uploader.
- Whether Shutterstock's and Pond5's full terms say more than we could read.
If your backlog is the real problem, stock footage metadata backlog sets out the order I would clear it in. Rushlot runs on Mac and Windows: the download page has the waiting list.
Frequently asked questions
Most steps can, but three should not be. Checks, repairs, metadata files and transfers can run by themselves. Reviewing each clip before upload, pressing Submit and resending a missing clip should stay with a person, because a mistake after upload is slow to fix and a resend can create a duplicate.
No. Adobe states that it has no contributor API. Automation on Adobe means SFTP for accounts Adobe calls qualified, or its web uploader for everyone else.
Not for creative video on the account we measured on 2026-09-08. ESP offered drag and drop, upload from device, or Dropbox, and no FTP or SFTP.
It depends on the door you use. Using an agency's own file server is what that server is for. Adobe's terms limit access to interfaces it provides or authorizes, Getty's forbid robots for data gathering, and we could not read Shutterstock's or Pond5's full terms. Read your own agreement, because no tool can make this risk-free.
We think not. A person should look at each clip first. Rushlot never presses Submit. On Adobe SFTP, files with an embedded title and keywords went into review with nothing clicked, so on that route the review has to happen before the upload.
The file work: checking specs with ffprobe, removing audio with ffmpeg on a copy, and writing the title and keywords with ExifTool. The transfers can then go through FileZilla or Cyberduck, with one saved site per agency.
We found no published figure. One contributor, Hervé Berthou, whose son builds Rushlot, went from about 40 hours to about 1 hour for 60 videos on four marketplaces, by his own estimate. Your result depends on your clips and your line.
Sources
- Adobe General Terms of Use, §6.6 and §6.7 (published 2025-10-03), read 2026-09-25
- Adobe Stock Contributor Agreement, Product Specific Terms, §8.1 (effective 2024-06-18), read 2026-09-25
- Adobe Community, Automation for Adobe Stock contributor via API, Community Expert reply (2024-05-14), a volunteer's view and not Adobe's text
- Getty Images Site Terms of Use (last updated August 2025), read 2026-09-25
- Shutterstock, How do I upload content via FTPS? (dated 2025-04-21), read 2026-10-29
- Shutterstock, Is there an upload or submission limit for images and video? (dated 2025-04-21), read 2026-10-29
- Pond5, Using the FTP uploader (updated 2024-11-05), read 2026-10-27
- Vendor pages for StockSubmitter, Microstock+ and CyberStock, read 2026-09-27; MetaMule and SendStock AI, read 2026-11-08
- Measured on live accounts: Adobe SFTP sign-in 2026-09-03 and deliveries in review 2026-09-07; Getty ESP 2026-09-08; Shutterstock and Pond5 FTPS 2026-09-11 and 2026-09-16
- Measured on a live Pond5 account: 26 duplicate pairs from a misread dry run, 2026-09-17 to 2026-09-19
- Every command on this page run on ffmpeg 8.1 and ExifTool 13.55 against a synthetic test clip, 2026-11-08
- Hervé Berthou (Seafootage), the author's father: 60 videos on four marketplaces, about 40 hours before and about 1 hour with Rushlot (his own account, 2026-10-28)




