iStock Rejection Reasons and How to Fix Them

iStock publishes no public rejection code list. Here is what its reviewers demonstrably check, which rejections are permanent, and how to fix a batch.

iStock keeps its rejection reason labels inside the signed-in contributor help centre, so the tidy lists of codes you find elsewhere are mostly reconstructed from memory. What iStock and Getty do publish openly is the set of things a reviewer checks — copyright, third-party trademarks, releases, generative AI and whether the file was made for stock at all — and those five account for most rejections before quality ever enters the conversation.

Why you cannot find an official iStock rejection code list

The Getty Images contributor help centre is a signed-in application. The articles that explain submission status notifications and the reasons files may not appear in search results live inside it, which means they are invisible to search engines and to anyone who is not already an accepted contributor. Public contributor pages cover applying, specs, exclusivity and payment — not the wording a reviewer picks from a dropdown.

This has a practical consequence. Any article that gives you a confident list of named iStock rejection reasons is either quoting another article that did the same, or reproducing labels from the signed-in centre without saying so. Neither is a source you should plan a shoot around. The honest approach is to work backwards from what Getty states publicly about acceptance, because every one of those statements is a rejection waiting to happen.

What reviewers demonstrably check

Copyright ownership comes first, and it is binary. iStock requires that you hold the copyright in what you submit or are an authorised representative of whoever does. This is the reason a second shooter's frames, a client's brief output, or a file lifted from a shared drive cannot be submitted even when nobody would notice — the declaration you make at upload is the thing being checked, not the pixels.

Third-party intellectual property is next, and Getty's wording is unusually direct: submissions must not contain third-party copyrighted material, and logos and brands appearing in an image must be hidden or removed, with retouching given as the example method. That covers more than a signage shot. Packaging text, patterned fabric with a licensed print, artwork on a wall behind your subject, a phone screen showing an app, and the shape of a recognisable product all live in this category.

Releases are the third, and the most common cause of a batch failing rather than a file. Getty requires a release for any recognisable person and any recognisable property, and supplies its own forms in fourteen languages once you are accepted. A release held in a folder is not the same as a release attached to the image. The detail of what reviewers actually look for on a release is worth reading before you shoot people rather than after.

Generative AI is the fourth, and here iStock is stricter than much of the market. Getty does not accept files created or modified using generative AI models, naming Stable Diffusion, DALL-E, Midjourney and Adobe Firefly as examples; iStock states the same and adds that limited retouching with AI tools on original work is allowed. There is no disclosure path, which is what separates it from the agencies that accept AI work if you declare it. Even application samples must be non-AI.

The fifth is whether the file was made for stock at all. On the video side iStock says this outright: showreels and edited narrative work are not accepted, and samples should be clips or work intended for stock use. The equivalent on the stills side shows up in Getty's editorial guidance, which says new contributors must add to existing content rather than duplicate current products and services, and that acceptance has a high threshold.

Manipulation sits slightly apart because it applies hardest to editorial work. Getty's editorial policy requires content to be free of manipulation and bias, says retouching must stay consistent with established accepted practices, and prohibits anything that alters the factual representation of the subject or scene. For creative work, the governing document is Getty's Creative Content Retouching and Modification Requirements, dated May 2025 and published inside the contributor centre — which is to say it exists, it is current, and you can only read it once you are in.

Accept or reject? Eight files at the iStock door

Eight submission cases scored against the rules iStock and Getty publish openly: copyright ownership, third-party copyrighted material, visible logos and brands, model and property releases, the generative AI ban with its retouching exception, and the requirement that video be intended for stock rather than edited narrative work.

The technical thresholds nobody will give you a number for

Noise, sharpness, chromatic aberration, dust, banding, posterisation — these are real rejection causes at every agency, and iStock publishes no acceptable values for any of them. The numeric specs that do circulate on Getty domains come from a submission requirements document footer-stamped for 2008, which covers TIFF master sizes, black and white point values and film ISO ceilings, and which does not mention iStock anywhere. Quoting it as a current iStock standard is a mistake that looks like research.

So treat technical rejections as a craft problem rather than a specification problem. View at 100% before you submit, not fitted to screen. Check corners and edges, not the centre. Look at the shadow areas on anything shot above base ISO. The specs that are published — the iStock file and field requirements — are about format and size, and clearing them tells you nothing about whether the image is clean enough.

Similars are a portfolio problem, not a file problem

The rejection that frustrates people most is the one where nothing is wrong with the image. Getty's stated position for new contributors is that they must add to existing content rather than duplicate current products and services. That is a statement about the library, not about your file, and it means a technically perfect frame can be declined because eleven near-identical frames already exist — including eleven of your own. The general pattern of similar-content rejections across agencies applies here with full force.

The fix is editorial rather than technical: cull before you submit. From a set of twenty frames of the same subject, pick the three that differ in a way a buyer would care about — orientation, copy space, expression, season — and leave the rest. Submitting all twenty does not raise your odds, because the ones that get through compete with each other for the same search position afterwards.

Video rejections have their own trap

Two things catch video contributors at iStock. The first is the application format: video applicants submit YouTube links, and Vimeo and other platforms are not supported, so a link to the wrong host fails before anyone watches anything. The second is the showreel rule. A reel is exactly the wrong thing to send — it is edited, scored narrative work, and iStock says that is not accepted. Send individual clips of the kind you intend to license. After acceptance, video goes in as .MOV up to 3GB.

What happens after a rejection

Review timing is the other thing not to trust a number on. For applications, Getty's own pages contradict each other — the iStock and Getty work-with-us pages say about a week, the iStock contributor FAQ says within 30 business days. For per-batch review after acceptance, no figure is published at all. If you are waiting, you are waiting on an undocumented timeline, and any specific turnaround you read elsewhere is someone's average rather than a policy.

A rejected batch, from notice to resubmission

Walks the sequence after an iStock rejection: reading the notice inside the signed-in contributor centre, sorting rejections into fixable and permanent, repairing what can be repaired, culling similars, and resubmitting only what changed. Built from the rules iStock publishes about copyright, releases, logos and AI.

Fix the batch, not the file

Almost every rejection cause above repeats across a shoot. One signed-release gap usually means thirty of them, because the bystander who wandered into frame four stayed for the next forty. One visible logo usually means the whole set, because the product was on the table the entire time. Treating a rejection as a single-file event is what turns a ten-minute correction into a three-week drip of individual resubmissions.

So read a rejection as a question about the shoot. Which frames share this subject? Which share this location? Which were exported in the same pass with the same settings? Fix that whole group before resubmitting any of it. Because iStock content is mirrored into Getty Images search, the Getty Images rejection reasons are the closest companion reference, and the overlap between the two is large.

The one habit that prevents most of them

Run the compliance pass at capture, not at upload. Decide on set whether anyone in frame needs a release and get it there. Note any brand in shot while you can still move the bottle. Record which files had AI tools near them and what those tools did. By the time you are keywording three hundred images, the information you need to answer a reviewer's objection has already evaporated, and the only honest option left is to guess.

The same logic applies to metadata. A policy-compliant keyword set written once, at the point the file is described, costs nothing; the same set written after a rejection costs you the batch's place in the queue. If you want the longer view on how Getty and iStock read the fields you fill, the Getty and iStock metadata standards cover the ground on the description side.

Checking every file against every agency's policy by hand is the part that does not scale, which is the problem Rastock.ai exists to take off your desk: titles, descriptions and keywords generated and then checked against each agency's own rules, including banned and mandatory terms, with a rollback if a batch goes out wrong. The approach to keeping titles inside moderation policy is the same idea applied earlier. There is a 14-day trial with no card required, and no revenue share on anything you license.

Frequently asked questions

Where can I find the official list of iStock rejection reasons?

Inside your signed-in Getty Images contributor account. The articles covering submission status notifications and why files may not appear in search results sit behind that login, so they are not reachable publicly and not indexed. Lists of named iStock rejection codes published on open websites are reconstructions rather than sourced documentation, and should not be treated as authoritative.

Will iStock reject an image for having a visible logo?

Yes. Getty's contributor guidance states that logos and brands appearing in an image must be hidden or removed, giving retouching as the example method, and that submissions must not contain third-party copyrighted material. Legibility is the practical test. That extends past signage to packaging text, licensed fabric prints, artwork on walls and app interfaces on screens in frame.

Can I resubmit a file iStock rejected?

It depends which group the reason falls into. A missing release, a visible logo, a wrong format or an unculled set of similars can be repaired and resubmitted. A file that was generated with AI, that you do not hold copyright in, or that contains someone else's copyrighted work cannot be made submittable by any amount of editing, so resubmitting it only costs you review time.

Does iStock reject AI-generated images even if I disclose them?

Yes. Getty does not accept files created or modified using generative AI models and names Stable Diffusion, DALL-E, Midjourney and Adobe Firefly as examples; iStock states the same. There is no disclosure or labelling route that permits the submission. Limited retouching with AI tools on original captured work is allowed, which is a narrow exception rather than a general permission.

How long does iStock take to review my submission?

For applications, Getty's own pages disagree: the iStock and Getty work-with-us pages say roughly a week, while the iStock contributor FAQ says within 30 business days. For per-batch review once you have been accepted, no timeline is published anywhere publicly. Any specific figure you see quoted is somebody's observed average, not a stated policy, so plan without it.

Why was my technically perfect image rejected?

Most likely because of the library rather than the file. Getty states that new contributors must add to existing content rather than duplicate current products and services, and that acceptance has a high threshold. A clean, well-exposed frame can be declined because near-identical content already exists, including your own earlier submissions. The response is to cull harder before submitting, not to resend.