heictosize

HEIC → JPEG · 200KB target

Compress HEIC to 200KB or less.

100% in your browser. No upload. Never exceeds your target.

  • Hard target limit
  • No upload
  • Free, no signup
JPEGPNG

When to use this

  • Visa applications that allow up to 200KB for the photo or a document scan.
  • Profile photos for services with a generous 200KB ceiling.
  • Document or certificate scans uploaded at up to 200KB.
  • Online forms that accept JPEG and a maximum of 200KB.

Tips

  • 200KB is generous — use the full allowance to keep maximum detail; there's no benefit to going smaller than the form allows.
  • Aim a couple of KB under 200KB; some forms round up and reject a file that is exactly on the limit.
  • If your form allows less, switch to that target — see compress HEIC to 100KB or 50KB.

Getting an iPhone HEIC photo down to 200KB is one of the more forgiving size targets you’ll meet online — enough room to keep a photo looking good, but still small enough to need a real reduction from the multi-megabyte original. A visa application, a document scan, or a profile photo upload with a 200KB ceiling will reject anything larger, usually with no guidance on how to get there. This tool does exactly that: you type 200, and it returns a JPEG at or under 200KB, with no upload and no guesswork.

Why 200KB is a generous target

A 200KB limit shows up wherever a service wants a reasonably high-quality photo but still needs it to be reasonably small — easy to store and upload on most connections. You’ll see it on visa and passport application systems, document and certificate upload portals, and profile-photo forms that permit a larger file than a basic avatar.

The catch is that phones still don’t produce 200KB photos. An iPhone shooting HEIC — the default since iOS 11 — typically produces a single photo of 1 to 5 megabytes, with a 12-megapixel shot commonly landing around 1.5 to 3MB. Hitting a 200KB target is therefore a 10× to 30× reduction — far less aggressive than tighter targets, which is why 200KB results tend to look close to the original. Doing it precisely by hand, however, is still painful: change a setting, export, check the size, repeat.

A purpose-built 200KB HEIC compressor removes the trial and error. Instead of asking you for a quality setting, it asks for the one number the form cares about — the size in KB — and hits it directly.

Who needs a 200KB HEIC compressor

A 200KB photo cap is most common in situations that want a high-quality but bounded file:

In each case the requirement is the same: a JPEG, at or under 200KB, that looks good. That is exactly what this tool produces.

How to compress HEIC to 200KB, step by step

The tool is intentionally simple — no account, no settings menu, nothing to install.

  1. Open the compressor on this page. The engine loads once, in your browser, the first time you visit.
  2. Drop your HEIC photo into the box, or click to select it. The moment you choose a file, the tool decodes it and shows a preview, so you can confirm you picked the right photo before doing anything else.
  3. Set the target to 200KB. It is preset, but you can type any number.
  4. Click Compress. The tool searches for the best result that fits under 200KB, usually within a second or two.
  5. Compare the before and after side by side to see exactly what changed.
  6. Download the result — a JPEG named with the target size, ready to upload.

If the form later complains, type a slightly lower number (say 195KB) and compress again. Some forms round up at the boundary, so landing a few KB under is safer than landing exactly on 200KB.

How the compression actually works

It helps to know what the tool is doing, especially since 200KB is a target where you usually get to keep most of the quality. Compression runs in four stages, all in your browser.

1. Decode the HEIC

HEIC is a container holding image data compressed with HEVC (H.265). Browsers other than Safari cannot render HEIC directly, which is why pointing an <img> at a raw HEIC file shows nothing. The tool decodes the HEIC into raw pixels with a WebAssembly module, entirely on your device. No pixel data is sent anywhere.

2. Try the highest quality that fits

With raw pixels ready, the tool encodes them to JPEG. JPEG lets you choose a quality level from 1 to 100 — higher quality looks better but produces a larger file. The tool performs a binary search across quality levels to find the highest quality that still fits under 200KB. A binary search is efficient: rather than trying quality 70, then 71, then 72, it jumps to the middle, checks whether that fits, and narrows in within a handful of attempts.

3. Protect a quality floor before resizing

This stage is what protects how the photo looks. Older “hit a target size” approaches kept lowering quality until the size fit — sometimes crushing quality into the low teens, which produces visible blockiness and mosaic artifacts, especially around faces and skin. That is exactly wrong for a visa or document photo.

This tool instead enforces a quality floor. It lowers quality only so far, and if even that floor still exceeds 200KB at full resolution, it stops lowering quality and starts resizing instead. The principle: trade pixels before you trade visible quality. At a generous target like 200KB, this stage often never triggers — most photos fit at the quality floor without any resize.

4. Resize with a high-quality filter, then retry

When a resize is needed, the tool uses a Lanczos resampling filter — a high-quality method for downscaling photographs, preserving edges and fine detail far better than the faster bilinear filters many tools default to. After resizing, it repeats the quality search on the smaller image and loops until it lands under 200KB. The result is a JPEG that fits the target, given the source.

What to expect from a 200KB photo

At 200KB, the honest expectation is a near-full-resolution image with limited visible change for a typical headshot or document. A 200KB budget comfortably holds a standard photo, so the tool often keeps the original resolution and only lowers quality within the protected floor.

A few practical expectations:

If the result does resize more than you’d like, the likely cause is an unusually large or extremely detailed source. Cropping to the subject first (in your phone’s editor) helps the tool spend the budget on what matters.

How photo file sizes actually work

A JPEG’s size in bytes comes from three things, and understanding them sets realistic expectations for 200KB:

  1. Pixel count (resolution). More pixels means more data to encode. A 12-megapixel photo has roughly four times as many pixels as a 3-megapixel one, so all else equal it produces a larger file.
  2. Quality level. JPEG is lossy: a higher quality keeps more detail and a larger file; a lower quality discards detail for a smaller file.
  3. Image complexity. Fine detail, noise, and busy texture compress poorly (larger file at the same quality), while smooth areas like sky or a plain wall compress well (smaller file at the same quality).

That third point is why two photos at the same resolution and quality can come out very different sizes. It also explains why 200KB is generous for a clean headshot (which compresses well) but tighter for a busy document scan full of fine text — even though both start from the same pixel count.

What 200KB actually buys you

For a typical headshot or document photo, 200KB is enough to keep more resolution at a high quality — visibly clean, with legible detail. This is why 200KB suits visa and document uploads, where readability of faces and text matters and the allowance is large enough to preserve it.

Why a target-KB tool beats a quality slider

A normal image editor asks for a quality number and hands you whatever size results. That is backwards for forms: the form cares about the size, not the quality. A target-KB compressor inverts the question — you give the size, the tool finds a suitable quality that fits — which is exactly what a hard 200KB ceiling demands.

HEIC vs JPEG: why the output is JPEG

Two reasons the output is JPEG, not HEIC.

First, almost no online form accepts HEIC uploads. Forms expect JPEG or PNG. HEIC is an Apple-pushed format with uneven support outside the Apple ecosystem, and most form systems reject it outright.

Second, JPEG reaches a target size like 200KB cleanly while keeping high quality. JPEG was designed for photographs and produces files that look good at modest sizes; the same photo as a PNG would be several times larger for no visible benefit. Since the goal is to fit under a size limit, JPEG is the right output.

So the conversion from HEIC to JPEG is the point, not a side effect. Your original HEIC is never modified.

Photo requirements by use case

Forms specify different combinations of file size, pixel dimensions, and aspect ratio. The tool handles file size directly; for the others, a little prep in your phone’s editor helps.

Always confirm the exact requirements on the specific form, since they vary. The tool removes the most common hard blocker, which is the file-size ceiling.

Passport, visa and ID photo guidance

Visa and passport photos have some of the strictest combined requirements of any form photo, and 200KB is a common ceiling for the upload. Beyond file size, expect rules around dimensions, background, and framing.

Because 200KB is generous, you can usually satisfy the dimension and quality requirements together — the photo stays legible, which is what visa systems check for. Crop to the exact required size first, then compress.

Common aspect ratios and dimensions

ID and form photos use a small set of standard shapes. Crop to the right one before compressing:

At 200KB the final pixel dimensions are usually preserved, so these digitization guidelines are typically achievable in full.

Troubleshooting

The form still says the file is too large. Some forms round up. Re-compress targeting a few KB lower (195KB or 190KB) and try again. The tool always lands at or under the number you type.

The form rejects the format. The output is a standard JPEG with a .jpg extension, which virtually every form accepts. If a form specifically wants .jpeg, renaming the extension works — the contents are identical.

The photo won’t preview or compress. Make sure you are uploading a genuine HEIC/HEIF file, not a renamed extension or a screenshot. An interrupted transfer can produce an incomplete file; re-saving the original fixes it.

Compression feels slow. Large source files take longer because decoding and encoding scale with pixel count. This is normal and processing time varies with the device and pixel count, all on your device.

The result looks resized when I expected full resolution. This happens with very large or extremely detailed sources. Crop to the subject first to give the tool a cleaner, smaller input.

Privacy: nothing leaves your device

The photos people compress for visas and IDs — passport portraits, document scans, certificate images — are sensitive. Your image never leaves your device. There is no upload, no cloud processing, no server that sees your photo. Decoding and compression happen locally in your browser through a WebAssembly module, and when you close the tab the data is gone. There is no account, no storage, and no analytics applied to your image.

This differs from most “online compressor” sites, which upload your photo, process it on a server, and send it back. For a visa or ID photo, running everything locally is both a privacy guarantee and a speed advantage — no round trip to a server.

How this compares to other approaches

For the specific job of “I have a phone photo and a form needs it under 200KB,” a targeted browser-side compressor is the most direct path.

Not every form wants 200KB. The same tool hits any target:

Whatever number your form states, type it and the tool lands at or under it — privately, in your browser, with no upload.

Frequently asked questions

Can it compress HEIC to 200KB or less?

Yes. It searches JPEG quality levels to land at or just under 200KB, and only shrinks dimensions if 200KB can't be reached at the quality floor — so the tool returns a file of 200KB or less, never over.

Is my photo uploaded to a server?

No. Decoding and compression run entirely in your browser via WebAssembly. Your HEIC file never leaves your device, nothing is stored, and there is no analytics on your image. Close the tab and it's gone.

Will a 200KB photo look good?

Yes — 200KB is a generous budget that usually keeps a photo near full resolution with limited visible change for a typical document or headshot. The tool holds a quality floor, so it only shrinks dimensions if the source is unusually large.

Why might it still reduce the resolution at 200KB?

Mostly it won't — a standard 12-megapixel photo often fits under 200KB at the quality floor. But if the source is very large or extremely detailed, the tool holds quality and shrinks dimensions with a high-quality Lanczos filter until it fits, rather than crushing quality into blocky artifacts.

How is this different from a quality slider?

A slider makes you guess the quality and re-check the size over and over. You enter 200KB and it hits that target directly — which is what form limits actually require. The size is the constraint, not the quality.

Does it work on Android or only iPhone?

It works in any modern browser (Chrome, Edge, Firefox, Safari) on any device. HEIC is most common on iPhone, but the file can come from anywhere — Android, a DSLR, a download, an email attachment.

Is there a file size limit?

There is no server quota because everything runs on your machine. The only limit is your device's memory. Very large HEIC files may take a second or two to process.

Is it free?

Yes — completely free, with no signup, no watermark, and no upload. There is no account and no plan to upgrade.

What format is the output?

JPEG (.jpg). Online forms almost always require JPEG or PNG, and JPEG reaches a target size like 200KB cleanly while keeping high quality. Your original HEIC is never modified.

Is 200KB enough for a visa or document photo?

Almost always. 200KB is a generous allowance that typically lets a headshot or document scan keep more resolution and good visible detail. If your form allows 200KB, using all of it keeps the most detail.

What if my form allows less than 200KB?

Type the number the form actually allows. For a 100KB cap see compress HEIC to 100KB; for a tight 50KB ceiling see compress HEIC to 50KB. Use the largest target your form permits so you keep the most quality.

Do I need to install anything?

No. It runs in the browser. There is no app, no plugin, no software to install, and no account to create.

Does the output keep my photo's metadata?

No — and for sensitive photos that is a feature. The result is a freshly encoded JPEG with none of the original's EXIF data, which means camera details and any embedded GPS location are stripped.

Will my photo stay the right way up?

After decoding, use Left 90°, Right 90°, or Reset beside the preview. The preview dimensions update immediately, and compression uses the rotated pixels.

Can I compress several photos at once?

One at a time. This keeps the tool simple, fast, and entirely local. If you have many photos to prepare, compress each individually — it only takes a moment per file.

Can it go smaller than 200KB?

Yes — any target down to 5KB works. Smaller targets will reduce resolution more, because a tighter file budget holds less detail.

Why is my original HEIC file so large?

Modern iPhones capture 12 megapixels or more and keep quality high, so a single HEIC photo is commonly 1–5 MB. Hitting 200KB is a 10–30× reduction from that starting point — modest compared to tighter targets.

Will skin tones and faces look natural?

Yes. The quality floor protects visible detail, so faces and skin tones stay clean rather than being crushed into blocky artifacts — especially at a generous target like 200KB, where quality reduction is minimal.