Usually one step
A typical photo compresses under 100 KB with no visible change. Just enter 100 as your target KB and upload - the tool automatically searches for the highest quality that fits, and only reduces pixel dimensions if quality adjustment alone genuinely can't reach your target.
How the compression actually works
Our tool first tries every reasonable JPEG quality setting at your photo's full size, searching for the highest one that still fits under 100 KB. Only if nothing at full size works does it also reduce the pixel dimensions proportionally, then search for the best quality again at that smaller size. At 100 KB, the large majority of ordinary photos succeed through quality adjustment alone, keeping their full original resolution intact.
For web pages
Also resize the photo to the width it will actually display at using our Resize Image tool. A picture shown in an 800 px column does not need to be 4000 px wide - shipping an unnecessarily large image to a small display area wastes bandwidth and slows down page load for no visible benefit to the visitor.
Where 100 KB limits show up
Job portals, school and university forms, ID and KYC uploads, and many website builders limit images to around 100 KB. It's also a good target for photos on your own website, where smaller images make pages load faster on mobile connections specifically, which matters a great deal for visitors on slower networks.
JPG or PNG for 100 KB?
For photos, use JPG - it's designed for them and reaches 100 KB easily, since JPEG's compression approach handles smooth photographic color transitions far more efficiently than PNG's lossless method. PNG is better for screenshots, logos and text, but a PNG photo is usually several times larger at the same visual quality. If you start with a PNG photo, our PNG to JPG converter handles that conversion before you compress.
Who actually needs this, and why
Job applicants and students uploading a photo to a portal with a 100 KB cap on image uploads. Website owners and bloggers wanting every image on their site to load quickly without manually adjusting export settings for each photo individually. Online sellers preparing product photos for a marketplace that enforces its own upload size restrictions.
A quick check
Open the compressed image next to the original at the same zoom. If you can't tell them apart, the compression has done exactly what it needed to without any visible cost. If you see blocky edges around faces or text, that's usually a sign the source photo was unusually large or complex relative to the target, and resizing the dimensions a little before compressing again tends to produce a cleaner result than pushing quality lower at the original size.
Privacy
Your photo is processed on our servers over an encrypted connection and deleted automatically after processing. There's no account required and no watermark added to the result.
Why 100 KB is one of the more comfortable targets
Compared to tighter limits like 20 KB or 50 KB, 100 KB gives the automatic quality search substantially more room to work with before it ever needs to touch pixel dimensions at all - most reasonably-sized photos clear this limit through quality adjustment alone, which keeps their full original resolution intact. This is a big part of why 100 KB shows up so frequently as a default across job portals, school forms, and website builders: it's small enough to keep uploads and page loads fast, while being large enough that most ordinary photos reach it without any visible quality sacrifice.
What happens with an already-small photo
If your source photo is already under 100 KB, the tool recognizes this and returns the file largely as it is, rather than forcing unnecessary further compression on an image that already meets your requirement. There's no benefit to compressing harder than the limit you've actually set.
Resizing for display versus resizing for file size
It's worth keeping two separate goals in mind when preparing a photo for a website: hitting a target file size, which this tool handles, and matching the photo's pixel dimensions to how large it will actually display on the page, which is a separate consideration this tool doesn't automatically know about. A photo resized to exactly match its display width, then compressed to a reasonable file size, loads faster and looks just as sharp as an unnecessarily large image compressed down to the same file size - the resize step removes genuinely wasted pixel data that compression alone can't fully compensate for.
Batch processing several photos
If you have multiple photos that each need to land under 100 KB - a set of product photos, several staff headshots - running each one through individually and checking its result is the more reliable approach, since different photos compress by different amounts depending on how much visual detail and complexity each one actually contains.
Keeping your originals
Before compressing, it's worth saving your original, full-quality photos separately from the compressed versions you actually use - different destinations sometimes call for different size targets, and starting fresh from a clean original each time produces a better result than compressing an already-compressed file a second time, which tends to compound quality loss unnecessarily, leaving a visibly worse result the second time around than a fresh original would have produced.
Choosing between compression and conversion
If you're trying to get the smallest possible file at a given visual quality, and you're not locked into a specific format by a form's requirements, converting to WebP generally achieves a smaller result than compressing a JPG to the same visual quality, since WebP's underlying compression technology is more efficient. Use this tool when a plain JPG under a specific KB target is what you actually need; consider a format converter instead when the smallest possible file size matters more than staying in JPG specifically for whatever you're uploading it to, and where the destination actually accepts that format in the first place.