Compress Image to 100KB Online Free

Use Target Size mode instead of the quality slider. Set the number field to 100 and click Compress Image. The tool works backward from a target file size instead of asking you to guess a quality percentage.

Target Size mode approximates the target — it doesn't guarantee an exact byte count, because compression size depends on the image's own content (detail, noise, color range), not just the setting. If a portal enforces a hard 100KB ceiling, aim slightly under it (85–95KB) rather than exactly at 100.

Upload is limited to JPG, JPEG, PNG, and WebP. Output can be JPEG, PNG, WebP, or the original format. GIF, BMP, TIFF, and AVIF are not supported as inputs or outputs by this tool.

Use Target Size mode when a form or portal states an exact KB limit, like 100KB. Use Quality mode when you just want a smaller file in general and don't have a strict number to hit.

It depends on the source. A high-resolution photo usually still looks sharp at 100KB because there's detail to spare. A small or already-compressed image can show visible blur or blockiness at that size — check the preview before downloading either way.

Government portals, visa applications, and scholarship or job portals often set small size limits to keep their upload infrastructure fast and cheap at scale across large numbers of applicants, not because a small file is inherently better quality.

Yes. Set Max Width and Max Height to the pixel dimensions your form requires (for example 600x600) before compressing, so the tool resizes and compresses in the same pass instead of only shrinking file size.

Resizing reduces the pixel dimensions (width and height) of the image. Compressing reduces file size at the same dimensions by simplifying color and detail data. Large photos usually need both to reach 100KB without looking soft.

PNG uses lossless compression, which preserves every pixel exactly and works best for screenshots, logos, and flat-color graphics. JPG uses lossy compression, which discards some detail to shrink photographic images much further. For real photos, JPG or WebP will almost always reach 100KB more easily than PNG.

Yes, if the portal accepts WebP. WebP typically produces a smaller file than JPG at a visually similar quality, so switching the output format to WebP can help when JPG alone won't get under the limit. Many older government and visa portals only accept JPG, so check the requirements first.

No. Entering only a Max Width or only a Max Height keeps the original aspect ratio and scales proportionally. The image is not stretched or cropped.

No. DPI (dots per inch) describes print resolution and does not directly control file size on its own. File size limits like 100KB are almost always about the encoded byte size of the file, which this tool controls directly through pixel dimensions and compression quality.

Not on this page. The tool processes one image at a time. For several files, repeat the same Target Size setting for each one, or use the image resizer first if you also need to batch-adjust dimensions.

No. Compression runs in your browser using a Web Worker, so the image file itself is never sent over the network to complete the compression. This matters for ID photos, passport scans, and other sensitive images.

No. The tool keeps the file in the browser's memory for the current session only. Closing or refreshing the tab clears it, and nothing is saved to a server-side account or database.

Yes. The tool works in modern mobile browsers. Very high-resolution phone photos (12MP or more) may take a few extra seconds to process because the compression happens on the device itself rather than a remote server.

Recompressing an already-compressed JPG repeatedly causes generation loss — visible artifacts appear with little further size reduction. Always compress from the original, uncompressed source photo rather than re-running the tool on its own output.

Modern phone cameras commonly produce photos in the low single-digit megabytes. Reaching 100KB from that size typically requires meaningful compression and often a reduction in pixel dimensions, not just a quality tweak.

Rarely for photos with faces or fine detail — visible blockiness usually appears first. It can be acceptable for simple graphics or documents where fine detail doesn't matter as much. Always check the preview rather than assuming a percentage is safe.

This can happen if the source file was already highly compressed (for example, a JPG re-saved from a screenshot) and you selected a high quality setting or switched to PNG, which doesn't shrink photographic content well. Lower the quality setting or switch to JPG/WebP output instead.

Re-encoding an image during compression typically strips embedded EXIF metadata such as camera model and GPS coordinates, which is a privacy-positive side effect for photos you're submitting to a third-party form. If EXIF removal is the only thing you need, verify the specific metadata fields your use case cares about, since encoders can vary.

JPG and WebP compress photographic content most efficiently. PNG is better reserved for graphics, screenshots, and images with transparency, since it will struggle to reach 100KB on a detailed photo without heavy downscaling.

Yes, but a screenshot with flat colors and text usually compresses well as PNG already. If it's still over 100KB, converting to JPG or WebP with a moderate quality setting will typically shrink it further, at some cost to sharp text edges.

Some portals check pixel dimensions, file format, or a stricter internal limit in addition to file size. Re-check the form's exact requirements for format (JPG only, for example) and dimensions, and set Max Width/Max Height accordingly before recompressing.