- Forms that reject a photo without stating a size limit
- “This file exceeds the maximum allowed size” errors
- Photos straight from a phone, which are usually several megabytes
Upload rejected for size
Your image is too large.
You do not need to know the exact limit to fix this. This tool starts at 2 MB, which passes most upload forms, and tells you the precise byte count so you can go lower if the form still complains.
No signupNo watermarkLocal processingVerified before download (“under 2 MB”)
Exact-size image engine
Set the ceiling. We find the fit.
Processed here0 bytes uploaded
Maximum size
Drop your imageor choose from your deviceJPG · PNG · HEIC · WebP · AVIF · up to 40 MB
01 / TARGET-SPECIFIC GUIDE
Why this ceiling
When the form will not tell you the number
Most upload forms reject a file without saying what they would have accepted. Rather than guessing with quality percentages, start at a limit that clears the majority of forms and adjust once. If you do know your limit, use the exact-size tool for it instead — the result will keep more detail.
Aim under the boundary, not at it
Systems disagree about whether a megabyte is 1,000,000 or 1,048,576 bytes, so a file sitting exactly on the stated limit is sometimes still rejected. Leaving a small margin costs almost no visible quality and removes a whole class of failure. The same ambiguity applies at every limit, which is why the exact byte count is shown rather than a rounded figure.
- The reported byte count is comfortably under the limit, not level with it
- The subject is still clear at the size the form displays it
- The file is a JPG — many forms reject PNG, HEIC and WebP on format alone
02 / THE DIFFERENCE
A measured result
Compression is an action.
Compatibility is an outcome.
Inspect
We verify the file signature, dimensions, format, and size before planning a change.
Search
The engine tests dimension and quality combinations instead of applying a generic preset.
Validate
The output is checked independently against the actual byte limit before it is called ready.
03 / HOW IT WORKS
Adaptive exact-size engine
Every byte has a job.
A percentage slider cannot know your upload limit. FileFit starts with the constraint, preserves a high visual-quality floor, then uses the available byte budget as fully as the image allows.
- 01Decode safelyTrue file type, real dimensions
- 02Find the scaleLargest useful pixel area
- 03Refine qualityIterative search, not a preset
- 04Prove the resultSize, format, image, privacy
05 / STRAIGHT ANSWERS
Before you drop a file
Nothing vague.
How do I find out my actual upload limit?
Check the error message first, then the form's help page. If neither states a number, 2 MB clears most forms; if it is still rejected, step down to 1 MB and then 500 KB. Each attempt here takes seconds because nothing is uploaded to a server.
My file is small enough now but still gets rejected. Why?
It is probably the format, not the size. Many forms accept JPG only and reject PNG, HEIC or WebP outright. Everything produced here is a JPG, so that failure mode is already handled.
Is a smaller file always worse?
Below a point, yes. This tool searches dimensions and quality together rather than crushing quality alone, and it reopens the finished file to confirm it is valid before you download it.
Does the image upload anywhere?
No. The image is decoded, resized, encoded, and checked inside your browser. Network transfer for the image is zero bytes.
What happens to GPS and camera metadata?
It is not copied into the new JPEG. The result contains the rendered image pixels, which also avoids spending the size budget on invisible data.
Which image formats can I start with?
FileFit accepts JPG, PNG, HEIC, WebP, and AVIF images and produces a standard JPEG result. iPhone HEIC photos work directly. It checks the file signature instead of trusting only the filename extension.