Pond5 accepts contributor files over FTP at ftp.pond5.com, but the transfer is only the first of four gates. Processing strips the metadata you embedded and builds preview files, the upload then stops in a status called Needs Edits, and nothing reaches a reviewer until you tag it and submit it yourself from the portal.
Where the web uploader stops being enough
Pond5 offers two upload paths, and its own documentation treats them as equals: an on-site HTML5 uploader and FTP. For a handful of clips the browser is fine. The reason contributors move to FTP is not a feature difference but a failure mode difference. A browser tab that loses its connection halfway through a 40 GB delivery leaves you guessing which files made it. An FTP client resumes, reports per-file status, and can be pointed at a folder and left alone.
What FTP does not do on Pond5 is shorten the sequence. This is the part that catches people arriving from agencies where an FTP drop plus a sidecar file is the whole job. On Pond5 the transfer and the submission are two separate actions, performed days apart if you are not careful, and the second one is manual.
The FTP host, and a password that is not your login
Pond5's FTP uploader documentation gives four connection details and one of them trips up almost everyone. The host is ftp.pond5.com. The username is shown in your FTP settings in the contributor portal. The port field is left blank. And the password is one you set yourself: it has to be at least eight characters and it has to differ from your Pond5 account password.
That last rule is a hard requirement, not a suggestion, which means a saved FTP profile using your login credentials will simply refuse to authenticate. You set or reset the FTP password from the same FTP settings screen, or from the Upload New File pop-up. Pond5 names FileZilla as an example client but does not require it; any standard FTP client works.
A successful sign-on shows the line Status: Directory listing successful in the client log. It is worth knowing that string, because it is the only unambiguous confirmation you have that the credentials are right rather than the server being slow. From there you upload by dragging from your local pane to the remote site pane.
Processing is a gate, not a delivery receipt
When a file lands, Pond5 processes it. Two things happen in that step: the platform scrubs the metadata, and it generates the low-resolution preview files that buyers see on the listing page. Processing is also where a file can be refused before any human looks at it.
A file that fails this stage appears as Processing Failed at the top of your Uploads page with a reason attached. Pond5 puts these at the top deliberately, and it is the one part of the Uploads page worth checking the morning after every batch. A failed file is not queued, not pending and not waiting on anyone; it is finished, and it needs a re-export and a re-upload.
Files that clear processing show Processing first and then move to Needs Edits. That status change is the signal that the file is ready for tagging. Until it appears, there is nothing you can edit, so a batch uploaded overnight is normally worked the following day rather than the same session.
Needs Edits is where stalled portfolios actually sit
Needs Edits is not an error and not a queue position. It means the file is accepted, previewed and waiting on you. Pond5 states the consequence plainly: files stay in Needs Edits until you submit them. There is no timer that eventually pushes them into review, and no reviewer is looking at them while they sit there.
This is the single most expensive misunderstanding on the platform. A contributor who uploads diligently every week and never opens the edit screen has a portfolio of files that will never earn anything, with no rejection notice to warn them. The Uploads page is showing the problem the entire time, but Needs Edits reads like a soft suggestion rather than a blocking state.
To clear it you open the file, choose edit, fill in the information Pond5 wants, and click save and submit for review. That click is the actual submission. Everything before it is staging.
What happens to a Pond5 file after you upload it
The six stages a Pond5 upload passes through, from the FTP transfer to the monthly payout: processing scrubs metadata and builds previews, the file stops in Needs Edits until you submit it for review, and approved files go on sale after a short indexing period. Payouts run monthly on the 15th once the balance reaches the payout limit.
Metadata does not travel with the file
Processing scrubs metadata. That one sentence from Pond5's documentation rewrites the whole workflow for anyone who keywords in Bridge, Lightroom or a dedicated metadata tool and expects the embedded fields to arrive intact. They do not. The IPTC and XMP data you wrote into the file is not what populates the listing.
There are two ways to get metadata onto Pond5 files. One is the edit screen, file by file. The other is Pond5's CSV uploader, which expects a specific set of column names and treats Originalfilename, Title and Keywords as mandatory. The exact field reference and character limits matter here, because a header spelled with a space or an underscore is not the header Pond5 is looking for.
The practical consequence for a multi-agency routine is that Pond5 needs its own metadata step even when every other destination in the batch reads the embedded fields. Writing the keywords once and mapping them to Pond5's rules as a CSV is the only version of this that scales past a few dozen files a week.
Releases go in their own folder
Pond5's FTP documentation gives exactly one folder rule, and it is easy to miss: model and property releases go in the Release folder. Not alongside the media, not in a subfolder named after the shoot. Release documents dropped into the same directory as the clips are not read as releases, and the file they belong to stays unreleased as far as the platform is concerned.
Uploading the release and attaching it to a file are also separate actions, handled from the portal rather than over FTP. If a shoot involves recognisable people or private property, plan on three operations per file rather than one: the media transfer, the release upload, and the attachment.
Near-duplicates are an upload problem before a metadata one
Pond5 advises against uploading many near-identical files, and it attaches real consequences to ignoring that. Its own documentation says the practice can lengthen review and may lead to a warning, and if the problem continues, removal of the account. That is a blunter statement than most agencies make about duplicates.
The reason it belongs in an upload discussion rather than a keywording one is that the selection has to happen before the transfer. Once forty variants of the same drone orbit are sitting in Needs Edits, deleting thirty-five of them is work you already paid for in bandwidth and in review goodwill. Pond5 also runs a duplicate-warning mechanism on the Uploads page, which is worth reading rather than dismissing when it appears.
A practical cut: one hero version per setup, plus a genuinely different alternative, such as a separate camera move or a materially different framing. Exposure brackets and frames a second apart are not different files.
Review, indexing and the payout clock
Pond5 does not publish a review time, and it is explicit about why. Its how selling works page says review times vary with submission volume and other factors such as bank holidays, and that review timing sits outside the support team's control. Asking support to expedite a batch is not a lever that exists.
Two details make the wait easier to plan around. You can keep uploading while files are pending, so a submission queue does not block the next batch. And approval is not the same moment as listing: files go on sale after approval plus a short indexing period, with the decision delivered by email and through the portal messaging system.
At the far end, payouts are processed monthly on the 15th, Eastern time, once your balance reaches the payout limit. That fixed date is the argument for getting a batch through submission early in a month rather than late: a file still sitting in Needs Edits on the 1st has no chance of contributing to that month's transfer.
Why is this Pond5 file not earning yet?
Walks a stuck Pond5 upload back to the stage it is actually sitting in, using the platform's own statuses: Processing Failed means re-export and re-upload, Needs Edits means the file was never submitted, and a submitted file is simply in a review queue whose timing Pond5 does not publish.
An order of operations that survives a real batch
Put together, the sequence that wastes the least time is: cull near-duplicates locally, export the files, set the FTP password once and save the profile, transfer the media to ftp.pond5.com and any releases into the Release folder, then stop. Come back when processing has run, clear the Processing Failed list first, and only then start tagging.
The tagging pass is where a CSV earns its place. Preparing one file of rows against Pond5's expected headers turns the slowest part of the workflow into a single import, and it is the only version of this that holds up when the weekly delivery is hundreds of clips rather than dozens. Finish by attaching releases, submitting everything for review, and checking the Uploads page once more so nothing is left behind in Needs Edits.
Running Pond5 as one destination among several
Pond5 is unusual among FTP-accepting agencies in that the transfer carries no metadata, so it cannot simply be added as another endpoint on an existing nightly job and forgotten. It needs its own metadata delivery and its own submission pass. Knowing what Pond5 actually rejects before the batch goes up removes most of the rework from that pass.
For contributors delivering to several agencies at once, the thing worth automating is not the FTP transfer itself but the part around it: generating metadata once, reshaping it per destination, and tracking which files landed where. That is the difference between a reliable nightly batch and a spreadsheet you no longer trust. Rastock AI delivers to 10+ agencies over FTP and SFTP, including Pond5, and the integrations list shows which destinations are wired in.
What it does not do is bypass Pond5's submission step, because no tool can: that click lives inside Pond5's own portal. What it can remove is the manual metadata assembly in front of it, including policy-aware keyword filtering and IPTC or CSV export you can take elsewhere. The feature breakdown covers the metadata and delivery side, and the pricing page lists the plans, with a 14-day free trial that does not ask for a card.
Frequently asked questions
What is the FTP address for Pond5?
Pond5's contributor documentation gives the host as ftp.pond5.com. The username is shown in your FTP settings inside the contributor portal, the port field is left blank, and you set the FTP password yourself rather than reusing your Pond5 login. Any standard FTP client connects, with FileZilla named as an example in Pond5's own walkthrough.
Does FTP upload carry my keywords to Pond5?
No. Pond5 processes every accepted upload, and that processing scrubs the embedded metadata while generating low-resolution previews. Whatever IPTC or XMP data you wrote into the file does not arrive as keywords on the listing. You add titles, descriptions and keywords inside the portal, or through Pond5's CSV uploader, after processing has finished.
Why are my Pond5 uploads not being reviewed?
Almost always because they were never submitted. Pond5 states that files stay in the Needs Edits status until you submit them, and no timer moves them into review on their own. Open each file, choose edit, fill in the required information, then click save and submit for review. Until that click, no reviewer is looking at the file.
What does Processing Failed mean on Pond5?
It means the file was refused during processing, before any human review. Pond5 shows these at the top of your Uploads page with a reason attached. The file is not queued and not pending, so there is nothing to wait for. Fix the underlying problem at export and upload the file again as a fresh submission.
Where do model and property releases go in Pond5 FTP?
Into the Release folder. That is the only folder rule Pond5's FTP documentation gives, and release documents left beside the media files are not read as releases. Uploading a release and attaching it to a specific file are also two separate actions, both handled from the contributor portal rather than over FTP.
When does Pond5 pay contributors?
Payouts are processed monthly on the 15th, Eastern time, once your balance has reached the payout limit for your chosen payout method. Because the date is fixed, files still sitting unsubmitted in Needs Edits at the start of a month cannot contribute to that month's transfer, which is an argument for clearing submissions early.