Image too large to upload? Check these three limits
“Image too large” can describe three different problems: too many bytes, too many pixels, or an unsupported file format. Changing the wrong thing wastes time and can make the image blurry without fixing the rejection. Find the destination's stated requirements first, then change only what fails.
1. Identify which requirement failed
- File size is the storage used by the file, normally shown in KB or MB. A limit such as “maximum 2 MB” is about bytes, not width or height.
- Dimensions are the width and height in pixels, such as 4000 × 3000 px. A site may set a maximum, a minimum, or an exact width and height.
- Format is the encoded file type, such as JPEG, PNG, or WebP. Renaming
photo.pngtophoto.jpgdoes not convert its contents.
Check the file's properties and compare all three values with the upload instructions. A file picker can suggest accepted types, but that filter is only a hint; the destination can still inspect and reject the selected file.
Compare file-size numbers carefully
File properties may round a value for display, so an image shown as “2 MB” can still sit on either side of a strict byte limit. Look for the byte count when it is available. Refentra uses decimal units: 1 KB is 1,000 bytes and 1 MB is 1,000,000 bytes. If the destination publishes a limit in bytes or uses MiB instead, follow its definition. Also check whether the rule says “less than” or “no more than”; those phrases can treat a file exactly on the boundary differently.
Choose the shortest fix
- If only the byte limit fails, use the 200 KB preset, the 2 MB preset, or enter the destination's real maximum in the target-size compressor.
- If dimensions and file size both fail, use Resize before compression in the target-size compressor. Enter dimensions within the allowed range, keep the aspect ratio when the destination permits it, and produce one output that addresses both limits. If only the width or height fails, the standalone image dimension resizer remains the shortest path.
- If PNG is rejected and JPEG is accepted, use the PNG to JPG converter. If WebP is rejected and JPEG is accepted, use the WebP to JPG converter.
Resize dimensions before final compression
When both dimensions and file size are over the limit, enable Resize before compression in the target-size compressor. Refentra renders the original once at the requested dimensions, then runs its bounded quality search on that raster. A smaller image usually needs fewer bytes to represent, and the combined job avoids an extra lossy intermediate save. Start again from the original if an attempt goes wrong.
- Enter the destination's maximum file size.
- Enable resize and set dimensions that satisfy its pixel rules.
- Choose a format the destination explicitly accepts, then run the combined job.
- Open the result and check fine text, edges, faces, and important details.
Treat a size requirement as a ceiling. A 1.86 MB file already meets a 2 MB maximum; there is no benefit in padding it to exactly 2 MB. Refentra searches for a useful encoded result at or below the selected target. Some images cannot reach a very small target at the tool's quality floor without reducing their dimensions, and the result reports that case.
For example, suppose a destination accepts JPEG up to 1600 px wide and 2 MB. A 3 MB, 4000 px wide PNG fails all three checks if PNG is unsupported. In the target-size compressor, set 2 MB, enable resize, enter a width of 1600 px with the aspect ratio kept, and select JPEG with a background that suits the image. The output is rendered once at the resolved dimensions and compressed to the byte ceiling in the same local job.
Watch transparency and legibility
JPEG does not preserve transparent pixels. Converting a transparent PNG or WebP to JPEG requires a solid background, so choose one that keeps logos, diagrams, and pale text visible. WebP can be a smaller option when the destination accepts it. For screenshots, forms, and graphics with small text, inspect the output at 100% zoom. If letters become fuzzy, use larger dimensions or a less aggressive byte target when the destination allows it.
If every requirement appears to be met
Do not keep degrading the image. Re-read the rejection for a hidden minimum dimension, aspect-ratio rule, file-count limit, or different limit for your upload category. Confirm the actual file type and byte count rather than trusting the filename or a rounded “MB” display. Then export a fresh copy with a simple filename and the correct extension, reload the destination, and try once more. A persistent rejection can also come from a corrupt file, an expired session, account storage, or a temporary destination-side problem. In that case, use the destination's help channel and include its exact error message.
No conversion can guarantee acceptance because the destination controls its rules and may change them. Keep your original file until the final copy has uploaded and displayed correctly.
Technical references
The browser's Blob size property reports file size in bytes. MDN also documents that the file input accept filter is a selection hint and that browser canvas encoders use a quality setting for lossy JPEG and WebP output in HTMLCanvasElement.toBlob().
This guide was drafted and edited with AI assistance. Its technical claims and tool links were checked against Refentra's current implementation and the cited MDN documentation.