Storyblocks keeps two separate rejection lists — thirteen reasons for footage and animations, ten for templates — plus a set of technical specifications that fail a file automatically before a reviewer ever opens it. Working out which of the three stopped your submission is most of the job, because one is fixed by a re-export, one by a reshoot, and one cannot be fixed at all.
The whole package is reviewed, not just the clip
The review process page is blunt about scope. Every submission is reviewed in full, meaning the files, the metadata and the release forms, and if any component does not meet the standard the file is not accepted. A well shot clip fails on a missing release. A clip with a valid release fails on a keyword the scanner does not like. The verdict you receive names one reason, but the review looked at three things.
Reviews are handled by a dedicated full-time team rather than an automated scorer, and Storyblocks publishes no turnaround time, saying only that it depends on submission volume. Music is the exception: tracks are approved on a monthly publish date, typically in the first week of the month. Acceptance is also not an end state, because the library is reviewed periodically and content that underperforms is removed.
The specs that fail a file before a human sees it
Content that misses the technical specification is rejected automatically, so this is the cheapest list to check first. The submission requirements for video and animations accept HD at 1280x720, 1920x1080 and the vertical equivalents 720x1280 and 1080x1920; 4K at 3840x2160, 4096x2160, 4096x2304 and their vertical forms; and 8K at 7680x4320. Anything between those numbers is not a near miss, it is a non-delivery.
Frame rate has to be one of 23.98, 24, 25, 29.97, 30, 48, 50, 59.94 or 60. Containers are prescriptive rather than suggested: HD footage goes in a MOV, 4K accepts MOV, MP4 or raw R3D including a zipped R3D with its RMD sidecar, and 8K is MP4 only in H.264 or HEVC. Accepted footage codecs are Photo-JPEG at quality 75 to 90, MJPEG, Motion JPEG A and B, Apple ProRes 422 and 4444, DNxHD and H.264. Files carrying an alpha channel need the Animation or PNG codec. Where H.264 is used, the minimum bitrate is 50,000 kbps.
Duration and weight are capped per type. Footage runs three minutes or less, animations and templates five minutes or less, and 360 footage has a floor as well as a ceiling at thirty seconds minimum and five minutes maximum. HD files stay at or below 4 GB, 4K at or below 6 GB, templates at or below 2 GB, and 360 footage at or below 25 GB. For 360 work the height must sit between 960 and 4096 pixels, with monoscopic ratios of 4:1, 2:1 and 1:1 and stereoscopic ratios of 4:1 and 1:1.
Three further rules sit in the same list and catch people who did everything else right. Do not add your own watermark or copyright notice. Do not submit the same content in multiple formats or resolutions, which rules out the habit of hedging by uploading an HD and a 4K version of one clip. And footage must not be visibly interlaced, which is also repeated as a named rejection reason further down.
Audio is a special case because it is mostly not wanted. Content may carry audio only when the sound source is visible or implied by on-screen action, the track is free of noise and peaking, and it contains no copyrighted material such as recognizable voices or music. The metadata side of a submission has its own field-level rules, which the Storyblocks metadata requirements reference covers in full.
The thirteen footage and animation rejections
Past the automatic checks, the content quality rejection reasons for video and animations are published as a flat list of names with no definitions attached, which is why two contributors can read the same verdict and disagree about what it meant. They fall into four groups that behave very differently: capture craft, post-production, legal clearance, and market demand. Only the first two are fixed at the desk.
Storyblocks rejection reasons, grouped
Storyblocks publishes rejection reasons as names without definitions, so these thirteen entries keep the published wording and group them by what they actually require: capture craft (focus, stability, framing, lighting, audio), post-production (pixelation, interlacing, grading), legal clearance (releases, copyright, trademark, inappropriate content) and market demand (subject matter already covered).
Craft rejections are verdicts on the shoot, not the export
Low production value, out of focus, unstable camera, poor composition or framing, poor lighting and poor audio quality are the six that describe capture. Five of them cannot be rescued by re-exporting, which is the most common wasted move after a rejection. Resubmitting the same master with a different codec answers a question nobody asked.
Low production value is the one worth sitting with, because it is the only reason on the list that is a judgement about the whole clip rather than a defect in it. The requirements ask for commercial quality, professionally produced content, and that phrase is doing real work: the comparison is the paid library a buyer is already scrolling through, not the rest of your own card. Footage that would pass on a social feed routinely fails here.
Poor composition or framing has a specific commercial meaning too. A clip is being bought to sit under a headline, a lower third or a logo. Frames with the subject centred and filling the width give an editor nothing to work with, and that is a framing problem even when the shot is technically clean. Shooting wider than feels necessary, and leaving copy space on purpose, removes most of this category.
The post-production group is the one you can usually fix
Pixelation and noise, visible interlacing and poor post-production behave differently from the craft group because the master is usually fine and the delivered file is not. Visible interlacing is the clearest case: it is both a submission requirement and a named rejection reason, and deinterlacing from the master then re-exporting progressive resolves it outright.
Pixelation and noise is more often a bitrate story than a sensor story. H.264 carries a 50,000 kbps floor at Storyblocks, and an export that drops below it will show compression breakup on exactly the content that compresses badly — water, foliage, grain, smoke, anything with fine high-frequency detail. The instinct is to reach for noise reduction, which smears the detail and produces a second rejection. Re-export at an accepted codec and bitrate first, and only then decide whether noise is genuinely present. The same arithmetic between file weight and visible quality applies to stills, as the resolution requirements for stock photos set out.
Poor post-production is the catch-all for grading, keying and compositing that does not survive full-size inspection: edge fringing on a key, banding in a sky, a mask that breathes. Rendering the same timeline again changes nothing here. The stage that produced the artefact has to be reworked.
Legal rejections carry consequences the quality ones do not
Missing model or property release is the one rejection Storyblocks annotates on its own list, and the note matters: any video containing a minor requires a model release even when the content is marked editorial. The editorial route, which contributors often use to sidestep paperwork, is closed in that case. Keeping releases attached to files rather than filed separately is the structural fix, and the walkthrough on attaching releases to stock uploads covers how the major agencies expect that to arrive.
Copyrighted or trademarked elements has a partial escape route. Content with easily discernible logos or branding has to be marked editorial only, and it then has to meet editorial standards in its own right. That is a real path for a street scene with a shopfront in it. It is not a path for a product shot built around a mark.
Inappropriate content draws on the sensitive content standards, which cover graphic and sexual material, physical harm to people or animals, hateful or defamatory content, material that reinforces stereotypes against racial, ethnic or religious groups or the LGBTQIA+ community, and content supporting conspiracy theories. The page adds the only account-level consequence written into any of these lists: contributors who repeatedly submit inappropriate content or metadata will be removed from the platform. This is the one rejection that is worth treating as a warning rather than a result.
Accept or reject: Storyblocks edition
Six submissions judged against Storyblocks published rules: the H.264 bitrate floor of 50,000 kbps, the three-minute footage cap, the ban on submitting one clip at multiple resolutions, the model release requirement for minors even under editorial, the editorial-only route for discernible branding, and the library-coverage rejection that is a demand verdict rather than a quality one.
Adequately covered in the library is not a quality verdict
The thirteenth reason reads in full as subject matter adequately covered in current library, with the published note that the rejection is due to low earnings potential. It is the only entry on the list that says nothing about your file. The clip is fine; the shelf is full. Contributors who read it as a craft criticism tend to respond by reshooting the same subject more carefully, which produces the same answer.
It also travels in the other direction. Storyblocks reviews its existing library periodically and removes content that underperforms, so the same demand logic that blocks a submission can later retire an accepted clip. A portfolio here is not a deposit, and the practical response to this reason is a shot list aimed at thin subjects rather than popular ones.
Templates are judged on ten different things
If you submit After Effects or Premiere templates, the footage list does not apply to you. The template rejection reasons name low production value and not commercially viable, then shift to things that have no footage equivalent: plugins prohibited, uses an uncommon plug-in, preview contains copyrighted or trademarked elements, preview does not match project, project files contain copyrighted or trademarked elements, missing files or information, and unorganized project. The library-coverage rejection appears on both lists.
Three of those are housekeeping rather than craft, and they are the cheapest rejections on either list to avoid. Preview does not match project means the render you uploaded shows something the project file does not produce, usually because the preview was made from a later edit. Unorganized project is a review of your layer naming, folder structure and comp hierarchy. Missing files or information covers absent fonts, unlinked assets and skipped fields. None of these require a better idea, only a pass through the project before export.
Metadata is flagged before review, not rejected after it
One part of the process is more forgiving than the rest, and it is worth knowing because it changes where you spend effort. At the Ready to Tag stage, Storyblocks scans titles and keywords for inappropriate or sensitive terms and returns an alert listing the flagged words. You edit those terms and carry on; content with nothing flagged moves through to review. This is a gate with a doorbell rather than a lock.
Metadata is still reviewed afterwards, including on published content, and Storyblocks says derogatory terms are removed on those sweeps. So the flag is not the last word, it is only the first. The field-level rules — title and keyword limits, the English-only requirement and which routes metadata can arrive by — are in the Storyblocks metadata field reference.
What to do with the rejection you actually received
Sort it before you touch the file. If the reason names a specification — resolution, frame rate, codec, bitrate, duration, file size — it never reached a reviewer and a correct export fixes it. If it names post-production, the master is probably fine and one stage needs redoing. If it names capture, the clip is finished and the lesson belongs to the next shoot. If it names a release or a mark, the question is paperwork or an editorial reclassification. And if it names library coverage, nothing is broken and reshooting is the wrong response.
Most footage contributors are not submitting to Storyblocks alone, and the overlap between lists is smaller than it looks. The Pond5 rejection reasons are published with codes and definitions, which makes them easier to act on but not interchangeable, and the wider comparison of stock footage sites for contributors sets out which platforms gate on which stage. A clip cleared for one is not cleared for all of them.
Keeping one library compliant with several rulebooks
The awkward part of multi-agency delivery is that each destination enforces a different set of rules on the same file, and the rejection arrives days after you have moved on. Rastock AI generates titles, descriptions and keywords from the content itself and delivers over FTP or SFTP to 10+ agencies, with per-agency banned and mandatory keyword handling so a term that is fine at one destination is not carried into another that refuses it. The feature list covers the rollback side as well, which matters when a bad batch has already gone out.
There is no revenue share and no claim on your files, IPTC, CSV and XML export stay open, and the 14-day free trial does not ask for a card. None of that makes a soft clip sharp, which is the honest limit here: tooling removes the metadata and delivery rejections, and leaves the craft ones where they belong.
Frequently asked questions
How many rejection reasons does Storyblocks publish?
Two lists. Footage and animations have thirteen content quality reasons, covering craft, post-production, legal clearance and library coverage. Templates have ten, including plugins prohibited, preview does not match project and unorganized project. Separately, content that misses the technical specification is rejected automatically before review, which is a third failure mode that is not on either list.
Can I resubmit a clip Storyblocks rejected?
It depends which reason you received. A specification failure such as a wrong codec or a bitrate below the 50,000 kbps H.264 minimum is fixed by a correct re-export. Visible interlacing is fixed by deinterlacing from the master. Focus, framing, lighting and low production value are verdicts on the capture and a re-export will not change them. Library coverage rejections mean the file is fine and the subject is full.
Why was my technically perfect clip rejected?
Most likely with the reason subject matter adequately covered in current library, which Storyblocks attributes to low earnings potential. It is a demand verdict, not a quality one. The same logic runs in reverse on published work: Storyblocks reviews its library periodically and removes content that underperforms, so acceptance is not permanent either.
Does editorial marking remove the need for a model release?
Not for minors. Storyblocks states that any video content containing a minor requires a model release even if the content is marked editorial. Editorial marking does have a documented role elsewhere: content with easily discernible logos or branding must be marked editorial only, and must then meet editorial standards in its own right.
How long does a Storyblocks review take?
No general timeframe is published. A dedicated full-time team handles reviews and turnaround is said to depend on submission volume. Music is the documented exception, with tracks approved on a monthly publish date that is typically in the first week of the month. Reviews cover the files, metadata and release forms together, and a failure in any one of them stops the whole submission.
Will bad keywords get my file rejected at Storyblocks?
Not directly at submission. At the Ready to Tag stage, titles and keywords are scanned for inappropriate or sensitive terms and you receive an alert listing the flagged words to edit before the file moves on. Metadata is still reviewed later, including on published content, and repeatedly submitting inappropriate content or metadata leads to removal from the platform.