Image to Target Size

Reduce a photo to a chosen maximum KB size. Export JPG or WebP locally, with optional dimension reduction when compression alone is insufficient.

Loading tool...

Processing happens locally in your browser. Your input is not uploaded to a processing server.

Meet an upload limit without guessing

Many online forms reject a photograph because its file size exceeds a fixed limit even when the picture looks perfectly reasonable. An application may accept only an image below 50 KB, 100 KB, or another stated maximum. Repeatedly saving at random quality settings is frustrating because the relationship between quality and file size changes with every image. A detailed outdoor photograph compresses differently from a plain document scan or a simple portrait.

This tool works toward a maximum byte budget rather than an exact visual quality score. It tests browser export settings and, when allowed, reduces dimensions until it finds an output that fits. The result is a new JPG or WebP file. A size target is a ceiling, not a promise that every available byte will be used. An image that is comfortably below the limit is usually more useful than one padded to an arbitrary exact size.

Read the receiving form's requirements first

File size and image dimensions are separate requirements. A portal may demand a small byte count and a particular width and height at the same time. Meeting one does not guarantee the other. Check accepted formats as well: WebP can be efficient, but older forms may accept only JPG. If a form uses the word JPEG, a JPG export normally refers to the same underlying format, although the service may still enforce a particular filename extension.

This page treats one KB as 1,024 bytes and reports the actual byte count. Some services use decimal kilobytes, where one KB means 1,000 bytes. If a strict service rejects a file near the boundary, choose a slightly smaller target instead of assuming the server is wrong. Leave room for inconsistent definitions and confirm the uploaded preview before submitting an important form. No compressor can promise acceptance by a service whose rules are unknown or change without notice.

Balance sharpness, dimensions, and format

Lowering JPG or WebP quality usually reduces file size but can introduce visible artifacts around text, faces, and high-contrast edges. Reducing pixel dimensions can save more space, especially when the source is far larger than the intended display. It also removes detail permanently from the exported copy. The option to allow smaller dimensions is therefore a practical tradeoff, not a free improvement.

For a document screenshot, inspect small letters after compression. For a portrait, check facial detail and the outline of the subject. Avoid repeatedly compressing an already compressed export; return to the original when trying a different target. This tool uses a white background when rendering transparent source areas, so a transparent logo will not remain transparent in the result. If transparency or exact lossless pixels are required, use a suitable format workflow and reconsider whether the receiving limit is compatible with that requirement.

Use a repeatable submission workflow

Start with the best original that you are permitted to use. Remove unnecessary surrounding space with a crop before compression if the form allows it, because irrelevant pixels still consume the file budget. Choose the output format accepted by the destination, set a maximum below the published limit, and decide whether changing dimensions is allowed. After exporting, inspect both the pixel dimensions and the reported bytes rather than relying only on the preview.

If quality reduction alone cannot meet the target while dimensions are locked, the tool reports that limitation instead of pretending the output qualifies. Raising the limit, allowing resizing, or cropping the source are the next useful options. A very tiny target can make an image unreadable even if technically achievable. For identity documents and official photographs, clarity and compliance matter more than forcing the smallest possible file. Keep the successful export with your application records so you do not have to repeat a destructive conversion later.

Keep a reliable image workflow

Keep the original photograph in a separate folder before making an edited copy. A downloaded result should have a name that describes its purpose, such as a submission photo or a review sheet, rather than replacing your camera file. Check the result in the program or website that will actually receive it. An image can look correct in a browser preview yet be rejected because the receiving service expects different dimensions, a different format, or a smaller byte count.

Browser image exports create new pixel files. They should not be treated as preservation copies of the source, and embedded camera information, color profiles, or print settings may not survive. When color accuracy or documentary integrity matters, retain the source and use an appropriate professional workflow. Canvas rendering can also vary slightly between browsers, especially for fonts and color management.

Images selected for this tool are processed on your device rather than sent to a conversion server by the tool. The website still needs to load its page and scripts, and ordinary website requests are separate from image processing. On a shared computer, remove sensitive downloads when finished. Close the page to release its working memory, and avoid opening several large photo jobs at once on a phone.

For a final check, open the downloaded file rather than only examining the working preview. Confirm that the filename extension agrees with the intended format and that the subject has not been clipped. If the picture will be printed, review a physical sample. If it will be uploaded, inspect the receiving site's own preview. Keep notes about successful dimensions and size limits for repeat submissions instead of repeatedly recompressing the same image.

Guide by . Report an issue or suggest a correction.

Frequently asked questions

Will the image be exactly the requested number of KB?

The target is a maximum, and the output may be smaller. Compression works in discrete encoded files rather than an exact byte dial. The tool reports the actual byte count so you can compare it with the receiving service's limit.

Can I keep the original dimensions?

Yes, turn off automatic dimension reduction. If the browser cannot reach the target using the available quality range, the tool reports that it could not meet the limit. It will not silently claim that an oversized result fits.

Why does a compressed image look blurry?

Aggressive compression and resizing remove detail. Increase the target size when possible, crop unnecessary areas, or start again from the original. Check text and facial features at full size before using an export for an important submission.

Related tools

Reference and further reading

MDN's browser image export documentation provides background on the relevant format, technology, or requirements. External services have their own policies and may change independently of this page.