Why a Website or Form Rejects Your Image, and How to Fix It

Read the message before changing anything

Error text is the cheapest clue. "Unsupported file type" points at format or extension. "File too large" or "exceeds 2 MB" is about bytes. "Image too small" or "minimum 600 pixels" is about dimensions. "Invalid image" or "could not process" usually means the content does not match the label, or the file is damaged. Note the exact words before you start, because they decide where to begin below.

Seven checks in order

1. Format. Look at the extension and compare it with the list the form accepts. Most accept JPG and PNG; many do not accept WebP, AVIF, BMP, GIF or SVG, and few accept HEIC. If yours is not on the list, convert to JPG, or to PNG when the image needs transparency or contains sharp text.
2. File size in megabytes. Compare the file with the stated limit. A limit of 2 MB is common for forms. Reduce pixel dimensions first, because they cost the most bytes, and lower quality only if the file is still too large.
3. Pixel dimensions. Forms can set both a minimum and a maximum. A 24 megapixel photo can be refused for being too large, and a 300 pixel thumbnail for being too small. Resize down to fit; a small image cannot be enlarged without losing quality, so a minimum has to be met at the source.
4. Color mode. Photo workflows sometimes produce CMYK or 16-bit images, which some programs and websites cannot handle. A converter that re-creates the picture as ordinary 8-bit RGB (as this one does) removes that problem.
5. Extension and contents. Check that the file is what its name says (see the next section).
6. Metadata. Rarely a reason for refusal, but very large embedded data, or an orientation flag the site mishandles, can cause trouble. A photo that arrives sideways is the common sign; the converter applies the orientation before re-creating the image, as the metadata article explains.
7. HEIC. A photo from an iPhone may be HEIC even though it looks like an ordinary picture. Convert it; the HEIC guide says where that is possible.

The file that says .jpg but is something else

A name is only a label. Programs that read the beginning of the file, which is what most upload scripts do, identify the real format from the contents. I made a test by saving a 1920 by 1080 PNG under the name fake.jpg and a real JPEG as real.jpg, then ran the Unix file command on both (output shortened):

fake.jpg: PNG image data, 1920 x 1080, 8-bit/color RGB, non-interlaced
real.jpg: JPEG image data, JFIF standard 1.01, baseline, precision 8, 1920x1080, components 3

fake.jpg was 4,036,108 bytes because the data inside is PNG, not compressed JPEG. A form that checks the contents rejects it as "invalid image" or accepts it only to fail later; a form that trusts the name may pass it through and break downstream. The same happens when someone renames a HEIC or WebP file to .jpg. The cure is to rebuild the image rather than rename it. Converting it again writes a new file whose extension and contents agree.

That test shows how a format mismatch can inflate a file. The picture inside fake.jpg, saved as a genuine JPEG at quality 90, came to 448,583 bytes, about a ninth of the PNG. A flat graphic with text would go the other way, so test your own file.

Size limits: how to estimate before you resize

File size follows pixel count loosely. Halving both dimensions leaves a quarter of the pixels, and the file usually falls sharply, though not exactly to a quarter because compression efficiency depends on the content. So if a 4000 by 3000 photo (12 megapixels) is refused at 2 MB, try 1600 by 1200 (1.92 megapixels, 16 percent of the pixels) first, then read the size on the results screen.

The converter's maximum size menu works on the longest side and never enlarges. If you need an exact pixel dimension, such as 600 by 600, you will have to crop and resize in an editor, since this tool offers neither cropping nor arbitrary dimensions.

Four worked cases

A 6.8 MB photo refused at a 2 MB limit. Cause: pixel count. A 4000 by 3000 photo has 12 megapixels, more than any screen form needs. Fix: reduce the longest side to 1600 pixels (1.92 megapixels, 16 percent of the pixels) and check the new size on the results row; if it is still above 2 MB, lower the quality slightly.

A picture that uploads sideways. Cause: the camera stored the image upright by an orientation flag in the metadata, and the site ignored the flag. Fix: re-create the image with the rotation applied to the pixels, which the converter does automatically when it re-creates the file.

A logo that turns black or gains a white box. Cause: transparency that the destination cannot handle. Fix: convert to PNG if it accepts that, or to JPEG with the right background color, as the transparency article describes.

It uploads from the laptop and fails from the phone. Cause: the phone saved HEIC. Fix: convert to JPEG, or switch the camera format as described in the iPhone settings guide.

Special cases worth recognising

• Animated GIF or WebP: forms that expect still pictures may refuse them. Converting keeps only the first frame.
• SVG: many forms do not accept vector files for photos or avatars. Rasterize it to PNG at the pixel size you need.
• Uppercase extensions and spaces in names: usually harmless, but some old scripts are picky. Renaming to simple lowercase letters and digits costs nothing.
• Works on one device, fails on another: a typical sign of HEIC or of a browser that cannot decode the format at all.

Before you retry the upload

After any fix, open the new file in a viewer and look at the extension, the size on disk and the pixel dimensions, which most file managers show in a properties window. Then upload it again. Retrying with the same file and hoping for a different result rarely works, since the checks a form performs are deterministic. If the form still refuses the new file, the message will usually differ from the first one, and that difference tells you which check you passed. Work through the remaining checks in order and stop at the first one that applies.