How to Compress an Image Under 100 KB, Step by Step
To get a photo under 100 KB, work in this order: cut the pixel dimensions to the size the image is actually displayed, choose WebP unless a form or portal demands JPEG, then lower quality in steps of five until the file fits. Resizing does far more than the quality slider, and doing it first usually means you never have to push quality into the range where the image visibly falls apart.
Most file-size limits come from the same place: an upload form written years ago, a job application portal, a visa site, a marketplace listing. The limit is fixed, the instructions are vague, and the tool you use has to hit an exact number. Here is the process that reliably gets there.
First, agree on what 100 KB means
There are two common definitions and they differ by 2.4%:
- 100 KB = 102,400 bytes (the binary reading, 100 × 1024).
- 100 KB = 100,000 bytes (the decimal reading used by most upload forms and operating systems).
A file of 101,000 bytes is “100.6 KB” in one convention and “98.6 KB” in the other. Since rejection is the failure mode, aim for 95 KB or less and you satisfy both. The same logic applies to 200 KB and 500 KB limits: leave a 5% margin.
Do the arithmetic before you touch the slider
File size is roughly proportional to pixel count for a given content type and quality. Halving the longest edge of an image removes about 75% of its pixels, so a 4000 × 3000 photo (12 megapixels) at 1200 × 900 is about 1 megapixel. That single change often turns a 3 MB file into 300 KB before any quality reduction.
A rough starting point for photographic content, using WebP at quality 80:
| Target size | Longest edge | Where it is used |
|---|---|---|
| 20 KB | 500–600 px | Thumbnails, avatars, inline icons |
| 50 KB | 800–900 px | Blog images, email headers |
| 100 KB | 1100–1300 px | Forms, portals, article heroes |
| 200 KB | 1600–1800 px | Product pages, full-width photos |
| 500 KB | 2200–2600 px | Retina hero images, lightbox viewers |
These are starting points, not guarantees. A dense forest photo at 1200 px will be larger than a plain wall at the same size, because compression has more detail to preserve. Treat the table as the first guess and adjust once.
The five-step loop
- Crop before resizing. If the interesting part of the photo occupies a third of the frame, crop to it. You keep more detail at a smaller file size, and a form that asks for a portrait does not need the empty wall behind it.
- Set the longest edge from the table above. If the requirement says “minimum 1000 px wide”, use exactly 1000 px rather than 1400 “for safety” — every extra pixel costs bytes.
- Pick the format. WebP if the destination accepts it. JPEG if the form restricts types to JPG or JPEG. PNG only if the image needs transparency or is a screenshot with text.
- Start at quality 80. Check the file size. If it is still over budget, drop by five-point steps: 75, 70, 65. Stop at the first value that fits.
- Inspect at 100%. Zoom in on the area with the most detail and on any text. If letterforms are mushy or skies show blocky patches, go back one step and reduce dimensions instead.
In the PixelPress compressor this loop is one screen: set the output format, type a longest-edge value, drag the quality slider, and read the new size on each result card. The card also shows the percentage saved, so you can see when a further five-point drop stops buying much.
When the file still will not fit
It is a screenshot of text
Text has high-frequency edges that lossy compression handles badly, which is why a screenshot at quality 40 can be both small and unreadable. Reduce the width instead — most screenshots survive being shown at 900 px wide — or crop to the region that matters. If the destination accepts PNG, a PNG at reduced dimensions is often smaller than a JPEG that still looks acceptable.
It is a photo of a document
Deskew, crop to the paper edges and convert to grayscale if colour is not needed. A colour photo of a form wastes most of its bytes on paper tint and background shadow. Grayscale plus a 1600 px long edge typically lands well under 100 KB as JPEG at quality 75.
It needs transparency
JPEG cannot store transparency, so a transparent PNG forced into JPEG comes out with a black or white box behind the subject. Use WebP with alpha, or flatten deliberately onto the background colour the destination uses.
It is an animated GIF
Canvas-based tools keep the first frame only. If the animation is the point, a short video file is smaller and better quality than an animated GIF in almost every case.
Four mistakes that cost people hours
- Uploading the original to a compressor that only adjusts quality. Without resizing, a 12-megapixel photo needs quality around 20 to reach 100 KB, and it will look terrible.
- Using PNG for a photograph. PNG is lossless; a photo stored that way is typically several times larger than a JPEG at similar visual quality.
- Re-saving the compressed file. Each pass adds error. Keep the original and regenerate the copy at the final settings.
- Upscaling a small image to meet a “minimum dimensions” rule. Upscaling adds no detail and multiplies file size; start from the largest source you have.
Checking the result before you submit
Open the compressed file, not the preview thumbnail. Confirm three things: the file size in your file manager, the pixel dimensions in the image properties, and legibility at 100% zoom. Forms often reject on dimensions as well as bytes, and a file that passes the size check can still be refused for being 1199 px wide when 1200 was required.
If a portal strips metadata on receipt, the upload may end up smaller than what you measured locally — that is fine. If it re-encodes, expect a slight further loss; the margin you left matters more in that case.
FAQ
Why did my file get bigger after compressing?
Usually because the output format is PNG (lossless, so it can exceed a compressed JPEG input) or because the quality was set higher than the original's. Re-encoding an already-compressed JPEG at quality 95 can add bytes without adding visible detail.
Can I reach 100 KB with PNG?
For screenshots, line art and images with few colours, yes — especially at reduced dimensions. For photographs, rarely: a 1200 px photo as PNG is often 800 KB or more. Use WebP or JPEG for photographic content.
Is 100 KB enough for print?
No. Print needs far more pixels and far less compression than screen delivery. A 100 KB file is a screen asset; keep a high-resolution master for anything destined for paper.
Written by the PixelPress team. Last updated November 19, 2026.