Skip to content
FileBelow

Image requirement checker

Choose the destination and add your image. You will see which rules it breaks before the upload form tells you.

16:9 · at least 640px wide · under 2 MB · JPEG or PNG

or drag it here, or paste it

JPG, PNG, WebP, HEIC, AVIF and BMP. Your file is processed on your device.

Requirements read from YouTube’s own documentation on 2026-08-21. Platforms change their rules; if this looks out of date, tell us.

How do I check if my image meets a platform’s requirements?

To check whether an image meets a platform’s requirements, choose the destination below and add your file. FileBelow compares its dimensions, aspect ratio, file size and format against the numbers published in that platform’s own documentation, shows you every rule with a pass or a fail, and offers to fix the ones that processing can honestly fix.

The problem this solves

An upload form rejects your image and tells you almost nothing. “Image does not meet requirements.” Which requirement? By how much? The form knows and will not say, so you resize something, try again, and get the same message for a different reason.

This page inverts that. You pick the destination, add the file, and every rule that destination publishes is listed with a verdict and with your file’s actual value beside it. Not “too large” but “3.4 MB, and the limit is 2 MB”. You can see what is wrong before you spend another attempt finding out.

What gets checked

Whatever the destination actually specifies, which varies. Some publish exact pixel dimensions; some publish a minimum width and nothing else; some care about the aspect ratio but not the size; a few — official application forms, mostly — impose a minimum file size as well as a maximum, and reject anything under it.

The checker reports only the rules that exist for your chosen destination. It does not invent a file size limit for a platform that has never published one, because a requirement nobody imposed is as unhelpful as a missing one.

Then it fixes what it honestly can

Cropping to a shape, scaling to exact dimensions, compressing under a ceiling and converting between formats are all things that genuinely work, and one button does all of them in a single pass — which matters, because compressing and then resizing costs quality twice for no reason.

Two things it will not do. It will not enlarge a small image and describe the result as meeting a minimum-width rule, because the pixels are not there to add. And it will not pad a file to reach a minimum file size, because the only way to make a file bigger without changing the picture is to fill it with meaningless bytes. In both cases it says so and tells you what would work instead.

Currently checkable destinations

10 platforms, 16 specifications: YouTube, HM Passport Office, UK Visas and Immigration, Google Play, App Store Connect, Google Ads, Google Business Profile, LinkedIn, Amazon KDP, Shopify. Every one carries a link to the documentation it came from and the date a human last read it. The full list, with the numbers themselves, is at sizes by platform.

This list is deliberately short. Most sites in this category publish requirements for every platform you can think of, copied from each other, and quietly go stale — the numbers were right in 2021 and nobody has looked since. A specification only appears here once someone has opened the official page and recorded that they did. If a destination you need is missing, that is because the sourcing has not been done yet, and telling us genuinely moves it up the queue.

Common questions

Where do these requirements come from?
Each one was read off the platform’s own documentation or help centre, and the page shows you the link and the date it was last checked. Nothing here is copied from another tool site or recalled from memory. If a platform changes a number, the requirement is wrong until someone tells us — which is why the source and the date are on screen rather than hidden.
Why does it say a problem cannot be fixed?
Because some cannot. If a destination needs an image at least 1280 pixels wide and yours is 500, no processing adds the missing 780 pixels — enlarging invents them, and the result is a blurry file that gets rejected for looking wrong instead of for being small. The same applies to a form demanding a minimum file size: padding a file with junk to reach it is not something this tool will do.
Does a pass here guarantee the upload will work?
No, and nothing could. This checks the requirements a platform publishes: dimensions, aspect ratio, file size and format. A platform can also reject an image for reasons it does not publish — content rules, a moderation queue, a bug in its own uploader, or a requirement it changed without updating its documentation. A pass means the measurable rules are met.
Is my image uploaded to check it?
No. The check reads your file’s dimensions and size in your browser and compares them against numbers already built into this page. Nothing is transmitted, and that remains true when you press the fix button — the processing runs on your own device too.
My destination is not in the list. What now?
Use the compressor or the resizer directly and type the numbers your form gave you. A destination only appears in this list once someone has read its official documentation and recorded where the numbers came from, which is slower than guessing but is the reason the list can be trusted.