"File Too Large" Error? How to Fix It in Under a Minute
September 7, 2026 · 6 min read
You pick a photo, hit upload, and the form rejects it. Sometimes it names a limit. Often it just says the file is too large and leaves you guessing.
Every guide to this problem tells you the same thing: resize, then compress. That advice is correct, and it is also the second step. The first step is working out what number you are aiming for, because "smaller" is not a target and guessing wastes more time than the compression does.
First, find the actual limit
The form is enforcing a specific number. Find it before you touch the image.
Read the error message properly. Many forms state the cap and people skim past it. "Maximum 2MB" and "maximum 200KB" are ten times apart and need completely different approaches.
Check the instructions near the upload button. Government portals, job application systems and university forms almost always publish the requirement, usually in small text above or below the field, or in a linked PDF of instructions.
Look for a minimum too. This trips people up constantly. Plenty of portals specify a range — say 10KB to 50KB — and will reject a file that is too small just as firmly as one that is too large. If you have compressed aggressively and it still fails, you may have gone under the floor.
Check whether the limit is about pixels, not bytes. These are separate constraints and a form can enforce both. A photo can be 150KB and still be rejected for being 4000 pixels wide, or accepted at 2MB because the only rule was dimensional. If the instructions mention something like "600 x 800", that is a dimension requirement and compressing alone will never satisfy it.
If nothing is documented anywhere, assume 2MB. That is the most common default for web forms, and if it fails, work down to 500KB.
Then understand why your photo is so big
A photo from a current phone is roughly 4000 pixels on the long edge, which is around 12 million pixels. Most upload forms display the image at a few hundred pixels wide. You are sending fifty times more data than the form will ever show.
This is the important part: file size is driven mainly by pixel count, not by quality settings. Compression can only do so much with 12 million pixels. Remove the pixels the form was never going to use and the size collapses on its own.
Typical figures for a 12MP phone photo, though yours will vary with subject matter and camera:
| What you do | Roughly what you get |
|---|---|
| Original, 4000px wide | 3–8 MB |
| Resized to 1600px | 400–900 KB |
| Resized to 1600px, quality 80 | 150–300 KB |
| Resized to 800px, quality 75 | 50–120 KB |
Notice that the resize does most of the work. Compression alone on a full-size photo often cannot reach 200KB without visible damage, while a resized photo gets there comfortably at a quality setting you would not notice.
The fix, in order
Step 1: Fix the format if it is wrong. Most forms accept only JPG, sometimes PNG. If your photo is a HEIC from an iPhone, it will be rejected regardless of size, often with the same unhelpful "file too large" message because the form's validation is poorly written. Convert it first with a HEIC to JPG converter.
Do not rename the extension. Changing .heic to .jpg does not change what is
inside the file, and the upload will fail in a more confusing way.
Step 2: Resize. Scale the long edge down to something sensible for the purpose. 1600 pixels is plenty for a document scan or a profile photo. 800 is fine for anything displayed small. Use the image resizer and keep proportions locked so nothing distorts.
Step 3: Compress to the target. Now aim at the actual number you found in the first section. Our compressor has a size mode where you enter the limit and it searches for the highest quality that fits underneath, rather than making you guess a quality setting and check the result over and over.
If there is no hard limit and you just need it smaller, quality 75 is a good default for photographs.
When it still fails
The image is a screenshot or contains text. Screenshots compress badly as JPG — sharp edges and text are exactly what JPG handles worst, so you get visible artefacts long before you get a small file. Try PNG if the form allows it, or resize less and accept a larger file.
You went below a minimum size. Recompress at a higher quality and check the result sits inside the stated range.
The dimensions are still wrong. Re-read the instructions for a pixel requirement. Some portals want an exact size and will not accept anything else.
The upload is timing out, not failing. A slow or unstable connection can produce an error that looks like a size rejection. Try a different network or browser before you compress the image any further.
The filename has unusual characters. Some older systems choke on spaces,
accented characters or very long names. Rename to something plain like
photo.jpg and try again.
A note on privacy
The files people compress for upload forms are frequently the sensitive ones — ID scans, certificates, medical paperwork, bank statements. Most online compressors upload your file to their server, process it there, and send it back. Their privacy policy governs what happens next, and you are trusting it.
Our tools run entirely in your browser. The image is decoded and re-encoded on your own device and never leaves it. You can verify this yourself: open your browser's developer tools, go to the Network tab, and compress a file. You will see no upload request. That check works on any tool making the same claim, and it is worth doing before you hand over a scan of your passport.
Doing it in bulk
If you are uploading twenty photos to a marketplace listing or a claim form, do not process them one at a time. Drop the whole batch into the resizer, apply one setting, then run the results through the compressor and download everything as a ZIP. It takes about as long as doing one file manually.
The short version
Find the real limit first, including any minimum and any pixel requirement. Fix the format if it is HEIC or WebP. Resize the long edge down, which does most of the work. Then compress to the specific number rather than guessing. Most "file too large" problems are two minutes of work once you know what you are aiming at.