Pond5 Rejection Reasons and How to Fix Them

Needs Edits, Returned and Rejected mean different things on Pond5. The reasons behind each, the codecs it refuses, and which files you can resubmit.

Pond5 separates its outcomes in a way most agencies do not, and the distinction decides your next move. A returned file is nearly approved and goes back through the same queue once you fix what is missing. A rejected file usually has to be re-uploaded instead, because the problem is a glitch or an unsupported codec rather than the paperwork.

Four statuses, and why the label matters more than the note

Most contributors read the curator's note and skip the status, which is the wrong way round. The note tells you what was wrong with this file. The status tells you which kind of work fixes it, and the two kinds are not interchangeable: one is a text edit inside the portal, the other is a trip back to your editing software and a fresh export.

Needs Edits means the file is sitting in your account and has not reached a curator. Pending for Review means it has. Returned means a curator looked at it and wants something added. Rejected means it did not survive, and on Pond5 that outcome generally points at the file itself rather than its description.

Needs Edits is usually not a rejection at all

This is the status that wastes the most contributor time, because it looks like a verdict and is normally just an unfinished step. Pond5 applies it in three situations: the files uploaded and processed but no title, description or keywords were added; the metadata was added but the items were never sent to curators; or the items did go to curation and came back for further edits.

The middle case is the one that quietly stalls accounts for weeks. Adding metadata does not submit anything. You have to select the items, choose Submit from the Actions dropdown and click Execute, at which point they move to Pending for Review. A contributor who keyworded everything carefully and then closed the tab has a library of finished files that no curator will ever see.

Returned: the three reasons curators actually name

Pond5 describes a return as curators being almost ready to approve the file with something missing, and it publishes the reasons rather than leaving you to guess. There are three: the item is missing a title, keywords or a description; the title or keywords are in a language other than English; or a necessary attachment is absent, such as a signed model or property release.

All three are cheap to fix and cheaper to avoid, and none of them says anything about the quality of the footage. That is the reassuring part of a return: the clip itself passed. If returns are a pattern in your account rather than an occasional event, the cause is almost always a submission routine that treats metadata as optional, and the fields Pond5 requires and their exact limits are worth fixing once at the template level rather than per file.

The language rule catches contributors who work in two languages more often than it catches anyone careless. English is required in the title and keywords, and a single stray non-English term is enough for a return even when the rest of the record is complete.

Pond5 statuses and what each one needs from you

The four Pond5 upload statuses with the reasons behind each: Needs Edits and Returned are fixed inside the portal and resubmitted, while Rejected generally requires a fresh export because the cause is a glitch or an unsupported codec.

Rejected: the codec list that decides it before curation

Pond5 names three codecs it refuses, and they account for a large share of outright rejections: Motion JPEG, AVI and non-native MP4. The last one is the trap, because an MP4 is not a codec and a file that opens perfectly on your machine can still be a re-wrap of something Pond5 will not take. The container is expected to be MOV or MP4, and anything arriving as AVI is meant to be converted before upload rather than after a rejection.

The accepted side is published as a preference order rather than a flat list, which is useful information about how the platform thinks. Unmodified camera-native codecs come first, R3D included, followed by the ProRes variants, then Avid native DNxHD and DNxHR, then H.264 and H.265, then Photo JPEG, with Animation or PNG reserved for clips carrying an embedded alpha channel.

The practical reading is that a transcode costs you standing. If your camera original is already in an accepted codec, sending it untouched is the strongest submission you can make, and every intermediate re-encode moves you down that list rather than up it.

Clip length, frame rate and the specs that fail quietly

Pond5 asks for clips in the range of 5 to 60 seconds. That is a narrower window than it sounds once you are cutting from longer takes, and it is the specification most often missed by contributors coming from a documentary or event background, where a usable shot might run two minutes.

Frame rate is a fixed list rather than a range: 23.98, 24, 25, 29.97, 30, 47.95, 47.96, 48, 50, 59.94 and 60. A conformed or retimed clip that has drifted to something outside that set is a file-level problem, not a metadata one, which puts it on the rejection side of the line.

Resolution is handled more leniently. Pond5 says it generally accepts any resolution while preferring HD and 4K, but smartphone and drone footage carries a minimum of 1080p, and archival material is expected to be converted to 1080p with anything lower considered case by case. File size caps run to 3 GB for HD or lower, 5 GB for 4K, 5K and 6K, 6 GB for 8K, and 3 GB for vertical footage, which is worth knowing before a long 4K take fails on size alone.

Audio is the rejection contributors do not expect

Pond5's guidance is that audio should generally be stripped before upload, with exceptions for editorial content and for clips where the sound is genuinely essential. Where audio is kept, it is expected to come from decent microphones at a sensible level, and the platform states plainly that in-camera microphone audio will most likely be rejected.

This inverts the habit most people bring from photography, where leaving data in is harmless. Here the camera's scratch track is an active liability: the clip can be technically perfect and still fail because an on-board microphone picked up wind and handling noise. Muting on export is a one-setting change that removes an entire rejection category.

Grading sits in a middle zone worth understanding rather than guessing at. Moderate colour correction and effects are allowed, clips with no edits are preferred, and anything with filters applied is evaluated case by case. A heavy look is therefore not banned, but it is a judgement call you are inviting, and the safest version of a clip you care about is the clean one.

Your Pond5 upload came back. What now?

A short diagnostic that routes a Pond5 upload by its status: metadata and release problems are fixed in the portal and resubmitted, while codec, length, frame rate and audio problems need a fresh export and a new upload.

Review timing, and when to stop waiting

Pond5 quotes one to ten days for curation depending on volume, and approved items can take a few hours to around a week more to appear online while the site indexes them. That is a wide enough band that a silent fortnight is not automatically a problem, but it also means a file sitting untouched for a month is telling you something.

In practice a long silence is usually a Needs Edits item that was never submitted rather than a slow queue, which is why checking the status column beats waiting for an email. Contributors who opted into notifications do get a message when a status changes, so an account with no messages and no movement is worth opening and sorting by status.

Why the Submit button is missing

The Submit option only appears for verified accounts, which makes this the one blocker that looks like a broken interface rather than a rule. If the Actions dropdown has no Submit entry, no amount of metadata work will move your files, and the fix is completing account verification rather than re-reading the upload guide.

A pass that prevents most of this

Separate the two kinds of check, because they happen at different moments. The file-level items belong in your export preset and are fixed once: an accepted codec, a MOV or MP4 container, a cut between 5 and 60 seconds, a frame rate from the list, audio stripped unless it is genuinely needed, and the size under the cap for that resolution. Get the preset right and this whole rejection category more or less disappears.

The record-level items belong in your submission routine: all three text fields populated, everything in English, keywords in the 40 to 50 range, and the release attached before submission rather than after a return. Then the step everyone forgets, which is actually pressing Submit.

The record-level half is the part that scales badly by hand, because Pond5's 40 to 50 keyword expectation and English-only rule apply to every clip individually. This is ordinary work for a tool that handles video metadata as well as stills. Rastock AI generates titles, descriptions and keywords from the file itself, applies each agency's banned and mandatory keyword rules, and delivers over FTP or SFTP to 10+ agencies including Pond5.

What no tool does is re-export your footage. The file-level rejections stay yours, which is exactly why they belong in a preset rather than in a checklist you run per clip. Rastock charges a subscription rather than a share of your royalties, with a 14-day free trial and no card required.

What this comes down to

Pond5's rejection system is more informative than most, provided you read the status rather than only the note. Needs Edits and Returned both mean the footage was fine and the record was not, and both are fixed in the portal and resubmitted through the same queue. Rejected means the file was the problem, and editing the item will not change that.

Most contributors who think Pond5 rejects heavily are actually looking at a column of unsubmitted items, a scratch audio track they forgot to mute, or a transcode that landed on the refused codec list. All three are preventable before the upload, which makes this one of the easier agencies to run cleanly once the export preset is settled.

Frequently asked questions

What is the difference between Returned and Rejected on Pond5?

A return means curators were almost ready to approve the clip and something is missing from the record, such as a field, English text or a signed release. You fix it in the portal and resubmit. A rejection points at the file itself, usually a glitch or an unsupported codec, and those generally have to be re-uploaded.

Why does my Pond5 upload say Needs Edits?

Three situations produce it: the file processed but has no title, description or keywords; the metadata was added but the items were never sent to curators; or a curator returned it for further edits. The second is the most common, because adding metadata does not submit anything on its own.

Which video codecs does Pond5 reject?

Pond5 names Motion JPEG, AVI and non-native MP4 as refused. Files should arrive in a MOV or MP4 container, and its stated preference order starts with unmodified camera-native codecs including R3D, then ProRes, then Avid native DNxHD and DNxHR, then H.264 and H.265.

How long can a Pond5 clip be?

Pond5 asks for clips in the range of 5 to 60 seconds. Anything outside that window is a file-level problem rather than something you can correct in the metadata, so it means re-cutting and uploading a fresh export rather than editing the existing item.

Should I leave audio on my Pond5 footage?

Usually no. Pond5 says audio should generally be removed before upload, with exceptions for editorial clips and where the sound is essential. Where audio is kept it must come from good microphones at a proper level, and the platform states that in-camera microphone audio will most likely be rejected.

Why is there no Submit option in my Pond5 Actions menu?

The Submit option only appears for verified accounts. If it is missing, your files cannot reach curation no matter how complete the metadata is, and the fix is finishing account verification rather than changing anything about the uploads themselves.