Skip to content
FileBelow

Requirements by destination

Every specification here was read off the platform’s own documentation, and every page shows the link and the date it was checked. Where a platform publishes dimensions but no file size limit, we list the dimensions and leave the size blank rather than inventing a plausible number.

This list is deliberately short. A destination is only added when we can find and cite an official page for it, because someone whose passport photo or product listing is rejected on our say-so has been actively harmed. If a platform you need is missing, it is because we could not verify it — not because we forgot.

What kind of image are you preparing?

The sixteen destinations below are grouped by the kind of problem they set rather than alphabetically, because the constraints inside a group tend to be alike — and knowing which group you are in is often more useful than knowing one number.

Video and channel artwork

The images around a video rather than the video itself. What these have in common is that they are all displayed at wildly different sizes — a thumbnail fills a television and also appears 120 pixels wide in a sidebar — so the constraint that matters is legibility when small, not resolution when large.

App store listings

Store artwork is reviewed as well as validated, so meeting the numbers is necessary and not sufficient. These specifications are also the strictest on this list about exact dimensions, because store layouts are pixel-designed and will not scale an odd size gracefully.

Official and government forms

The only category here that routinely sets a *minimum* file size as well as a maximum, and the only one where getting it wrong costs a fee or a delay rather than a repost. These are the specifications worth checking against the notice you were sent as well as against this page.

Selling and publishing

Product and cover images, where the picture is the thing being sold rather than a decoration around it. The ceilings tend to be generous and easy to exceed anyway, because photographs of products come straight out of a studio at full sensor resolution.

Business profiles and advertising

Images that appear beside content somebody else came to read, at a size and a crop the platform chooses. Composition matters more than resolution here: an asset that cannot survive being cropped towards a different shape will be cropped anyway.

Using these numbers

Each destination page opens the tool with that specification already applied, so the dimensions, the ratio, the format and any size limit are set together in a single pass rather than one at a time. If you would rather see what is wrong before changing anything, the requirement checker reports every rule against your file and processes nothing until you ask it to.

Where a destination is not listed, the numbers you were given still work: type them into the compressor or the resizer directly. Nothing here is required to use the tools — the specifications exist so that you do not have to go and find the numbers yourself.

How this list is maintained

A destination is added only once somebody has opened its official documentation and recorded the URL and the date. That is slower than copying from another tool site, and it is the entire reason this list can be trusted — the methodology behind it explains why the sourcing discipline is the asset rather than the numbers themselves.

Changes are recorded in the record of specification changes, and the whole database is published as machine-readable JSON with every source and date included, free to use.

Missing or wrong?

Platforms change their requirements without announcing it, and we check these pages on a schedule rather than continuously. If something here disagrees with the official source, the official source is right — please let us know and we will correct it and record the change in the changelog.

If the destination you need is not listed, the tool still does the job: take the numbers from whatever the form told you and enter them on the home page as a size limit, dimensions, or both.

Check a file against one of these

The requirement checker takes a destination and your image and reports every rule with a pass or a fail, plus what your file actually is — so you find out which requirement you are breaking before the upload form declines to tell you.

Use this data yourself

The whole database is published as JSON at /image-size/specs.json, with the source URL and verification date on every record. It is free to use, with or without attribution, and it is served with permissive CORS headers so you can fetch it directly from a browser.

One condition that is a caveat rather than a licence term: the dates are the whole guarantee. A record is accurate as of its lastVerified date and not afterwards, and anything building on it should check sourceUrl rather than trusting a value indefinitely. That warning is in the file itself, because whoever consumes it will never read this page.