Reduce any image below 100KB entirely in your browser. Targets 96KB by default to give a safe margin under common 100KB limits on job portals and HR systems.
Last updated: July 2026
96KB
Default Target
Safe Margin
Under 100KB
JPEG, WebP
Output
Private
No Uploads
Drop image here to compress to 96KB
JPEG, PNG, WebP, AVIF, HEIC. All processing stays in your browser.
Default target is 96KB. Change the target in the field above if your portal specifies a different limit.
Drop or select your image
JPEG, PNG, WebP, AVIF or HEIC. Nothing is uploaded, it stays on your device.
Confirm the target
Defaults to 96KB, a safe margin under a 100KB limit.
Binary search finds the highest usable quality
Searches quality to fit under the target. Trims dimensions slightly if quality alone would look bad.
Download your compressed image
Preview and size stats appear, click download to save the file.
Common reasons people compress images under 100KB
The 100KB limit is the most common file size restriction on job application platforms, university admission systems and professional examination portals. These platforms enforce the limit automatically, so you must reduce your image before attempting to upload.
Job application photo uploads
HR portals on Workday, SAP SuccessFactors and regional job boards frequently cap profile photos at 100KB. Your image must be below the limit before the form will accept it.
University and college admission portals
Admission and registration systems at universities across India, Nigeria, Pakistan and the UK commonly enforce a 100KB limit on applicant photographs.
Professional certification and exam registration
Competitive exam portals for civil services, engineering licensing boards and professional certifications typically require photos under 100KB for registration.
Corporate HR and intranet profiles
Internal HR systems and employee directory platforms often restrict profile photo uploads to 100KB to keep directory pages loading quickly.
When a portal says your file must be under 100KB, you might assume that a 99.9KB file will pass. Usually it does. But upload systems don't always count bytes the same way your operating system does. Some servers measure the raw file. Others measure the encoded form after the browser wraps it in a multipart HTTP request, which adds a small overhead. A file that reads as 99KB on your desktop has failed at the server end often enough that targeting 96KB has become the safer habit. It costs you nothing in visible quality and eliminates a whole category of frustrating retries.
There's also the question of what "under" actually means to the system. Most portals use a strict less-than check: exactly 100KB fails if their threshold is 100,000 bytes and your file is 102,400 bytes (which is 100 kibibytes, a common source of confusion). The difference between 100KB in decimal and 100KiB in binary is about 2.4KB. If you're cutting it close, that gap can be the difference between a submission that goes through and one that doesn't. Staying comfortably under removes the ambiguity. If your portal is stricter than 100KB, the compress under 50KB tool handles that with the same approach.
A lot of upload failures aren't about file size at all. They're about format. iPhone users shooting in HEIC, Android users with PNG screenshots, designers exporting WebP from Figma, these files hit portals that were built expecting a plain JPEG and get rejected before the size check even runs. The error message usually says something vague like "invalid file type" or just the generic size error again, which sends people off compressing a file that wasn't the problem in the first place.
JPEG is the one format every institutional portal accepts without question. It's been the standard for two decades and no upload system in government or HR has ever deprecated it. This tool outputs JPEG by default. If you're starting from a HEIC file from your iPhone, it converts and compresses in one step. If you'd rather handle the conversion separately first, the HEIC to JPG converter does that on its own, and then you can compress the result here. Either way, the output going into the portal is a standard JPEG that nothing will reject on format grounds.
This is the part people are most anxious about, and usually without reason. A professional headshot or passport-style photo displayed at 200 by 200 pixels on a recruiter's dashboard needs very little data to look sharp. At 96KB, the compression applied is typically light enough that you'd struggle to spot a difference between the original and the output even at 400 by 400 pixels. The binary search algorithm finds the highest encoder quality that still fits under the target, so you're never getting more compression than necessary.
The exception is very large images with high detail, like a photo taken in RAW or a high-megapixel camera image. In those cases the tool scales the dimensions down proportionally as well as compressing, which keeps the output looking clean rather than introducing heavy JPEG blocking. If you need the image to stay at its original dimensions and the quality result still isn't acceptable, the portal limit itself is the constraint, not the tool. For situations where the portal accepts files up to 200KB, the compress under 200KB tool gives you more headroom to work with.
Compressing to exactly 100KB instead of leaving margin
Servers sometimes count bytes slightly differently than your desktop does, and the decimal-vs-binary KB definition can add up to a 2.4KB gap. The 96KB default leaves enough headroom to avoid a rejection on a technicality.
Uploading a HEIC or WebP file the portal doesn't recognise
A lot of upload failures are format problems, not size problems. iPhone HEIC files and designer WebP exports get rejected by portals built expecting plain JPEG. Convert to JPEG first if a correctly-sized file still won't upload.
Not cropping first for a high-resolution source photo
A full-frame phone photo has far more pixel data than a headshot needs. Cropping to just the head and shoulders before compressing reduces how much quality has to drop to hit 96KB.
Assuming dimensions never change
At a tight target like 96KB, the tool will reduce dimensions slightly if that's the only way to keep quality above a usable floor. Check the result panel, if scaling happened, it's shown there.
Confusing a file-size limit with a dimension requirement
Many portals specify both a minimum pixel size and a maximum file size. Hitting one doesn't guarantee the other, check both requirements before you submit.
These systems process large numbers of applications and store photos in databases alongside other applicant data. A 100KB ceiling keeps storage predictable and ensures uploaded photos load quickly inside employer or admissions officer review dashboards. The limit is enforced at upload time so the image must be below 100KB before submission.
When a portal says the file must be under 100KB, any file below 100KB passes. You do not need to hit exactly 100KB. This tool targets 96KB by default, providing a small margin that accounts for any byte-counting differences between browsers and upload servers.
Yes. At 96KB a typical professional headshot or passport-style photo is indistinguishable from the original at the sizes employer portals display it. The tool searches for the highest quality that fits within the target, up to a ceiling of quality 90, so compression is minimal.
JPEG is the safest choice for any institutional portal, job board or government system. It is universally accepted. Use WebP only if you are certain the portal accepts it, as some older systems reject WebP files, or if you specifically need to preserve transparency, which JPEG doesn't support.
Usually not, quality alone is enough for a standard headshot or ID-style photo. But 96KB is a tight target, and if quality would otherwise have to drop low enough to look genuinely bad, the tool reduces dimensions slightly instead, so you get a clearer small image rather than a full-size but blurry one. The result panel shows the scale used if this happens.
Yes. All compression happens in your browser using WebAssembly. Your photo never leaves your device and is never sent to any server. This is especially important when dealing with ID photos and personal portraits.
Yes. Upload the PNG and the tool decodes it in the browser before re-encoding it as JPEG or WebP, there's no PNG output option. PNG files are often much larger than equivalent JPEGs, so a PNG profile photo that is several hundred KB will typically compress to well under 100KB with negligible visible difference.
No. The image is decoded to raw pixels and re-encoded during compression, so EXIF metadata, including GPS location and camera details, does not carry over to the output file. Worth confirming if you're submitting a personal photo and want to be sure location data isn't included.
This page compresses one image at a time. If you're submitting multiple documents to the same portal, you'll need to run each one through separately here.
No sign-up. No uploads. Drop your image above and download the compressed version in seconds.
