sRGB or Adobe RGB for Stock: What Agencies Require

Agencies deliver in sRGB, so sRGB is what you upload. Each agency's published rule, why Adobe RGB files shift, and the export that keeps your edits intact.

Every large stock agency delivers files to buyers in sRGB, so sRGB is what belongs in the file you upload, even when you edited in something wider. Adobe Stock states the requirement outright, Shutterstock asks contributors to convert before uploading, and Dreamstime lists sRGB among its file rules. Adobe RGB is a working space, not a delivery space.

That settles the decision, but it leaves the more useful questions open. Why does an Adobe RGB JPEG sometimes sail through review and then look flat on the agency page? Why do saturated greens survive one conversion and collapse in another? And what does a correct export actually look like in Lightroom or Camera Raw? Those are the parts worth getting right once, because every file you submit afterwards inherits the answer.

What sRGB and Adobe RGB actually do differently

Both are RGB color spaces, which means both describe color with the same three channels and the same 0-255 numbers per channel in an 8-bit file. The difference is what those numbers mean. A color space is a set of instructions for interpreting the numbers, and Adobe RGB's instructions cover a wider range of real-world color than sRGB's, particularly in cyans and greens.

The practical consequence is that the number 0,255,0 is a different green in each space. In Adobe RGB it is a more saturated green than sRGB can represent at all. So if a file carries Adobe RGB numbers but something reads it as sRGB, every color shifts toward the muted side, and the shift is largest exactly where your image is most saturated. Nothing is corrupted; the numbers are simply being read with the wrong dictionary.

This is why the embedded profile matters more than the space you chose. A profile is the file telling every downstream program which dictionary to use. Strip it, and software falls back to an assumption, which on the web is almost always sRGB.

What each agency publishes

The rules are not hidden, but they are worded differently enough that contributors read them as different rules. Adobe Stock's photo submission requirements name the format and profile together as a single specification. Shutterstock's technical requirements for images take the opposite approach: they describe what the library delivers and then advise you to convert, warning that other profiles may shift during conversion. Same outcome, different framing.

Color profile and format rules by agency

Adobe Stock requires JPEG with an sRGB profile at 4-100 MP and up to 45 MB. Shutterstock delivers in sRGB, accepts JPEG and TIFF from 4 MP, and asks contributors to convert before upload. Dreamstime lists RGB and sRGB, JPG only, 3-70 MP. Alamy specifies high-quality RGB JPEG at quality level 8 or above, over 17 MB uncompressed, without naming a profile.

Alamy is the interesting case. Its uploading guidance asks for high-quality RGB JPEGs at baseline standard and sets its threshold by uncompressed file size rather than megapixels, but it does not name a profile. Silence is not permission. The delivery pipeline still ends in sRGB, so the sensible reading is that sRGB is expected and simply not written down.

Notice also that each agency pairs its color rule with a size rule, and the two get checked in the same pass. If you are rebuilding an export preset, fix both at once rather than discovering the second one after a rejection. The resolution minimums by agency are worth reading alongside this, because a file that satisfies Adobe's 4 MP floor can still miss Alamy's uncompressed threshold.

Why an Adobe RGB upload looks wrong once it goes live

There are two failure modes, and they look identical to the contributor while being completely different underneath.

The first is a silent conversion. The agency receives an Adobe RGB file, sees a valid profile, and converts it to sRGB on ingest. That conversion is competent, but it is not free: colors that sat outside the sRGB gamut have to be pulled inside it, and the renderer picks how. A field of saturated foliage or a turquoise pool comes back a shade duller than the version you approved on your calibrated monitor. The file is accepted, the thumbnail is fine, and nothing tells you anything happened.

The second is worse. The profile gets stripped somewhere in the chain, often by an export preset set to not embed the profile, or by a resizing step that rewrites the file. Now the Adobe RGB numbers are read as sRGB numbers, which is not a conversion at all but a misreading. Skin tones go waxy, blues go grey, and the whole image loses the snap you built into it. This is the version buyers see in search results, next to competitors whose files were tagged correctly.

Neither failure produces an error message, which is precisely why contributors keep repeating it across thousands of files. The fix lives entirely in the export step.

The export that keeps your edits intact

The distinction that matters here is between converting a profile and assigning one. Converting recalculates every pixel value so the color stays visually the same in the new space. Assigning leaves the numbers alone and just relabels the dictionary, which changes how the image looks. Converting is what you want on export. Assigning is a repair tool for files whose profile went missing, and reaching for it by mistake is how a batch gets ruined in one click.

What should I do with this file?

Walks from the profile currently in your file to the right action: upload as-is for sRGB, convert to profile for Adobe RGB or ProPhoto RGB, assign before converting when no profile is embedded, and do not upload CMYK, which none of the agencies above list as accepted.

In Lightroom Classic the setting lives in the export dialog under File Settings, where Color Space should read sRGB. In Camera Raw it is the small underlined line at the bottom of the window. In Photoshop it is Edit, then Convert to Profile, with the destination set to sRGB, before you save a copy. In all three cases, make sure the option that embeds the profile stays on, and save the configuration as a preset named for stock delivery so nobody has to remember it again.

One thing worth checking on the same pass: the export step that writes your color profile is usually the step that writes your keywords and caption too, and a preset configured to minimize metadata quietly drops both. If titles or keywords have ever gone missing between your catalogue and the agency, that is almost always the export settings rather than the agency losing them.

Color-space mistakes that cost acceptances

These come up again and again in contributor forums, and every one of them is an export setting rather than a shooting error.

Color issues rarely arrive labelled as color issues. They surface as quality or technical refusals, which is why they are easy to misdiagnose as sharpness or noise problems. Reading through how Adobe Stock words its rejections makes the pattern easier to spot in your own batch history.

So should you work in Adobe RGB at all?

Yes, if you keep masters. Editing in a wider space means your archive holds color that sRGB cannot, which matters the day a client licenses a file for print, or an agency opens a higher-specification collection, or you decide to sell prints yourself. Converting down is lossy and one-directional, so the wide file is the one worth keeping.

No, if your workflow has no master stage. A contributor shooting JPEG and uploading the same file to ten agencies gains nothing from Adobe RGB and inherits every risk described above. In that case set the camera to sRGB and remove the problem at the source.

The honest version is that this is a two-file workflow. One wide master you never upload, one sRGB delivery you generate on demand. Everything that goes wrong with color spaces in stock photography comes from trying to make a single file serve both roles.

A one-minute check before a batch goes out

Color space is one of a dozen specifications that differ per agency while your files stay the same, which is the part of distribution that rewards automation. Rastock handles the metadata and the delivery side of that problem: titles, descriptions and keywords generated against each agency's own rules, then FTP delivery to 10+ agencies with per-agency status tracking, no revenue share, and free IPTC and CSV export if you ever leave. There is a 14-day free trial with no card required. The export preset that writes your sRGB profile is still yours to get right, and it is worth doing once properly.

Frequently asked questions

Does Adobe RGB give stock buyers better color?

Not in practice. Agencies deliver in sRGB, so the extra gamut never reaches the buyer. What it does reach is the conversion step, where saturated greens and cyans outside the sRGB gamut get clipped or remapped by whatever renderer the agency uses. Editing wide is useful for your own master files, but the file you submit should already be sRGB so that you control that conversion instead of inheriting someone else's.

Will an Adobe RGB file be rejected outright?

Sometimes, and that inconsistency is the real problem. Adobe Stock lists sRGB as part of its submission specification, so a mismatched profile can be refused on technical grounds. Other agencies accept the file and convert it silently, which means it passes review and then appears duller on the site than the version you approved. Neither outcome is good, and one export setting prevents both.

What is the difference between converting and assigning a profile?

Converting recalculates the pixel values so the image looks the same in the new space. Assigning leaves the values untouched and only changes the label, which changes how the image looks. On export you always want to convert. Assigning is a repair tool for files whose profile went missing, and using it by accident on a finished batch shifts every color at once.

How do I tell which profile a finished file actually has?

Open it in your editor and read the profile listed for that document rather than trusting the export preset you think you used. Most operating systems will also show it in the file information panel. The quicker sanity check is to view the file in a browser, which assumes sRGB: if it looks different there than in your editor, the profile is either missing or does not match the numbers inside the file.

Should I shoot raw in Adobe RGB or sRGB?

For raw files the camera setting is irrelevant, because a raw file has no color space until your converter assigns a working space during processing. Set the working space in the converter instead. The camera setting only matters if you shoot JPEG and upload those files without processing, in which case choose sRGB so the file you deliver is already correct.

Does the same rule apply to vectors and illustrations?

The delivery expectation is still RGB rather than print-oriented CMYK, but the specifications differ by file type and agency, and some accept EPS with its own constraints. Check the format-specific page for whichever agency you are submitting to, since an illustration pipeline that starts in a print color space is the most common reason vector submissions come back on technical grounds.