Image Compressor: Compress to 50KB, 100KB, 200KB or Any Exact Size

The formula

• Exact-size mode: binary search on encoder quality until output size is at or under the target KB
• Quality mode: single encode at your chosen quality (1 to 100)
• PNG with transparency: palette/quality steps keep the alpha channel instead of flattening to JPG
• If quality alone cannot reach the target, dimensions step down gradually until it fits

A worked example

A 4.2 MB phone photo with a 100KB upload limit: choose the 100KB preset and the compressor tests quality levels until the output lands just under 100KB, one click instead of five rounds of guessing with a slider.

More about the Image Compressor

Compress image to 100KB, 50KB or 200KB, the exact size mode

Job portals, exam forms, visa applications and government sites rarely ask for “a smaller photo”. They state a hard ceiling, under 100KB, under 50KB, under 200KB, and reject anything above it. A quality slider cannot answer that: you drag, export, check the size, drag again. Exact size mode answers it directly by searching quality levels automatically until the file fits the number you typed.

That is the feature the big names leave out. TinyPNG, for example, applies one fixed smart compression pass and gives you whatever size results. It has no target size setting at all. Here the target is the setting: presets for the three ceilings that come up most (50KB, 100KB, 200KB) plus a custom KB box for everything else.

Quality mode, batch mode and PNG transparency

When there is no hard ceiling, quality mode is the faster tool: around 80% quality, a photo typically shrinks 60 to 80% while looking identical on screen. Only aggressive settings below roughly 40% show visible blockiness, which is why every result shows its size before you download.

Batch mode applies the same target or quality to a whole set at once, a folder of listing photos, a scanned document set, a week of phone pictures. PNG files keep their transparency: logos and screenshots are compressed without being flattened onto a white background, which is where many quick compressors quietly ruin the file.

Why compressing in the browser is the private option

The photos people most need under a size limit are often the sensitive ones: passport scans, ID documents, exam registrations, medical images. Server compressors make you upload exactly those files to a machine you know nothing about. This compressor has no upload step at all, the encoding runs in your browser, and you can verify it in your browser’s network tab.

Re encoding has a privacy bonus: the fresh file carries no EXIF data, so the GPS coordinates your phone tucked into the original do not travel with the compressed copy.

A worked compression: from phone photo to a 200KB upload

Suppose your phone produces a photo of 4.8 megabytes, about 4,800 kilobytes, and a portal demands a file at or under 200KB. The reduction you need is 4,600 of those 4,800 kilobytes, a 95.8 percent shrink. Exact size mode hunts for it automatically: it tries a quality level, measures the output, then adjusts up or down until the file fits under 200KB with as much sharpness as the budget allows, instead of leaving you to drag a slider and export five test files.

Where does the saving physically come from? Mostly from the encoder discarding fine detail your eye barely registers, subtle texture in skies, grass and skin, while protecting edges and faces. If quality alone cannot reach a very small target, dimensions are the second lever: halving the width and height quarters the pixel count, since a 4,000 by 3,000 image holds 12 million pixels while a 2,000 by 1,500 copy holds 3 million. The tool only reaches for that lever when the target genuinely demands it.

Batch maths shows why this matters beyond single forms. Twenty listing photos averaging 3 megabytes each total 60 megabytes; compressed to 200KB each they total 4 megabytes, a 56 megabyte saving that decides whether an email sends, a listing uploads on slow connections, or a shared folder stays under its limit. Run the batch once with one target and every file gets the same treatment, each with its own before and after readout so the one stubborn file that resisted compression is easy to spot.

JPG, PNG or WebP: which format earns its size

For photographs, JPG remains the safe default: every portal, printer and phone accepts it, and its compression is designed exactly for the smooth colour gradients photos are made of. WebP typically squeezes the same photo smaller still at equal sharpness, and modern browsers display it happily, but some older form systems and office tools still reject it, if a portal names accepted formats, believe the portal, not the size saving.

PNG is the wrong tool for photographs and the right tool for graphics. A photo saved as PNG can be several times larger than its JPG twin because PNG compression is lossless and cannot discard the fine detail that makes photos heavy. Reserve PNG for logos, screenshots with crisp text, diagrams and anything carrying transparency, where its exactness is the point. Converting a photo from PNG to JPG is often the single biggest compression win available before quality settings even enter the picture.

Screenshots sit between the two worlds. A screenshot of text and interface elements compressed as JPG can develop fuzzy halos around letters at low quality, because sharp edges are exactly what JPG compression smears first. If the screenshot must stay readable at a small size, keep it PNG and accept the larger file, or raise the target size slightly. Readability is a requirement, not a luxury, when the screenshot is evidence, instructions or an exam answer.

Mistakes that get uploads rejected anyway

The commonest rejection has nothing to do with size: the file fits the kilobyte ceiling but fails a different rule, wrong pixel dimensions, the wrong format, or a colour profile the portal dislikes. Read the full specification before compressing, not just the headline number. A visa photo, for instance, can be demanded at exact dimensions as well as under a size cap, and compressing alone cannot fix a picture that is the wrong shape.

Re compressing an already compressed file is the quiet quality killer. Each save at a lossy quality level discards another layer of detail, so a photo compressed three times on its way through different tools looks noticeably worse than the same photo compressed once from the original. Always return to the original file when you need a different target size, and keep that original untouched somewhere safe, compression is a one way door for the copy you make from it.

Finally, do not chase the smallest possible file when the ceiling allows more. If a portal accepts 200KB, a file at 195KB looks better than one crushed to 60KB for no reason, because the encoder had three times the data budget to spend on detail. Exact size mode already aims just under your target for this reason. Set the target to the real requirement, not to an arbitrary smaller number, and let the tool spend the whole allowance on quality.

Compressing for email, storage and sharing

Not every compression job comes from a portal with a hard ceiling. Email inboxes reject or mangle very large attachments, shared drives fill quietly, and a family chat group does not need a 9 megabyte photo to show a birthday cake on a phone screen. For these jobs, quality mode at a sensible setting is the right tool: one pass at around 80 percent quality turns a heavy camera roll into files that send instantly, while the originals stay archived at full quality for printing and editing.

A practical routine keeps both worlds. Keep one folder of untouched originals, exactly as they came off the camera, and one folder of compressed copies named for their purpose, the 200KB set for listings, the email set, the website set. Because each compressed copy is generated fresh from the original, never from another compressed copy, every version carries the best quality its size allows, and deleting a copy costs nothing: it can always be regenerated.

Compress a passport scan to under 5 MB for the DV-2027 entry

New for this lottery cycle: DV-2027 entrants must also upload a JPEG scan of their passport’s photo and signature pages, and the file must be no larger than 5 MB. A phone scan at full resolution usually lands between 8 and 15 MB, so most entrants will need to shrink it once. Set exact size mode to 5 MB (or 4.9 MB for a safety margin), keep the format as JPEG, and always compress from the original scan, never from a copy that has already been compressed once.

Before you rely on the result, zoom it to full size and read it: names, dates and the passport number must stay perfectly legible, because a file that fits but cannot be read is no better than one rejected for size. A passport scan is also exactly the file you least want sitting on a stranger’s server, here the compression runs in your browser and the scan never leaves your device.

How to use the Image Compressor

1. Choose or drop one image, or a whole batch. JPG, PNG and WebP all work.
2. Pick a mode: Exact size (50KB, 100KB, 200KB presets or your own KB figure) or Quality (your slider, your call).
3. Press Compress and watch each file’s before/after size. Everything runs in your browser.
4. Download the compressed files one by one. No signup, no daily limit, nothing uploaded.