Reduce HEIC file size — to any target.

An iPhone HEIC photo is rarely a small file. A single shot from a modern iPhone lands at 1 to 5 megabytes, sometimes more — far too large for an email attachment, a form upload, a web page, or a chat message that is meant to be quick. “Reduce HEIC file size” is the broad version of the problem: you don’t necessarily need a specific number, you just need the file smaller, and you need it smaller without ruining the photo and without handing it to a stranger’s server.

This page is for that case. Type any target in kilobytes — 50, 100, 200, 500, or whatever your form or inbox allows — and the tool lands at or under it, exactly, in your browser. No upload. No account. No quality slider you have to babysit.

Why reduce HEIC file size

The reasons for shrinking a HEIC fall into a handful of common patterns, and they all share one thing: the original is bigger than the destination wants.

• Forms with a file-size limit. Government portals, exam registration sites, visa applications, job application systems, and membership platforms routinely cap uploads at 100KB, 200KB, or 500KB. Cross the line by a single kilobyte and the upload is rejected, usually with no guidance on how to get under.
• Email and messaging. Many email providers reject attachments over 25MB, but even well under that ceiling, a multi-megabyte HEIC bloats a message, loads slowly on mobile data, and arrives in an inbox where the recipient may not even be able to open HEIC at all.
• Web pages and apps. If you build or edit a website, a 3MB hero image drags the whole page down — load times, layout shifts, bounce rate, search ranking, the lot. A web image should weigh in the low hundreds of kilobytes, not the megabytes.
• Storage. A library of multi-megabyte HEIC files adds up fast. Shrinking the ones you don’t need at full fidelity — receipts, casual shots kept for reference, photos destined for a form anyway — frees up meaningful space.
• Compatibility. Reducing a HEIC almost always means re-encoding to JPEG, which is the format the rest of the world actually accepts. Smaller and more compatible in one step.

Whatever the reason, the shape of the problem is the same: the file is too big, you need it smaller, and you’d prefer not to upload it to a random website to get there.

Who needs to reduce a HEIC

A surprising range of people run into this, usually at the moment they need to send a photo somewhere:

• Applicants. Anyone filling out a government form, an exam registration, a visa application, or a job application where the upload cap is in kilobytes, not megabytes.
• Parents and students. School portals, scholarship applications, and university admissions systems frequently cap photo uploads at tight limits.
• Travellers. Visa and immigration systems the world over specify both pixel dimensions and a file-size ceiling for the uploaded headshot.
• Web editors and developers. Anyone who needs a page’s images to load fast and meet Core Web Vitals without throwing away the photo entirely.
• Office admins and small-business owners. Document scans, product photos, and certificate uploads often hit a portal’s size ceiling.
• Anyone emailing from a phone. A few HEIC attachments can blow past an inbox limit before you notice.

In every case the requirement is the same: a JPEG, at or under a specific size, ideally without the photo looking degraded. That is exactly what a target-KB tool produces.

Why HEIC photos are so large in the first place

HEIC (High Efficiency Image Container) has been the default capture format on iPhones since iOS 11, and it is genuinely efficient — a HEIC file is typically about half the size of an equivalent JPEG at the same quality. So why are iPhone photos still multiple megabytes?

Because the source data is enormous. A modern iPhone captures 12 megapixels at minimum — roughly 4000×3000 pixels — and newer models stitch multiple exposures, capture wider color, and preserve more highlight and shadow detail than older phones. All of that information has to go somewhere.

The practical result:

• A standard 12-megapixel HEIC is commonly 1.5 to 3MB.
• A shot with depth data, night mode, or heavy HDR detail can push to 4MB or more.
• ProRAW or ProRes captures (if you’ve turned them on) can be 10MB to 25MB or more per frame.

So HEIC is not the villain — it’s already doing more work than JPEG would. The villain is the sheer amount of data a modern phone captures. When a form says “100KB maximum,” you’re asking for a 15× to 40× reduction from that starting point, and that takes a real tool, not a save-as-JPEG.

How small can you go

There’s no single answer, because the smallest sensible size depends on what’s in the photo and what it’s for. Honest guidelines:

• 50KB and under. Headshots, ID-style portraits, avatars. A tightly cropped face still looks clean at 50KB; a busy landscape does not.
• 100KB. The most common form ceiling. Comfortable for portraits and ID photos, tight for detailed scenes.
• 200KB. A generous allowance — usually enough to keep a photo near full resolution with little visible loss.
• 500KB. Effectively full quality for most phone photos. Useful when a form is generous but the original HEIC is still too big.
• 1MB and up. For email or web use, where you want smaller than the raw capture but not aggressively compressed.

The tool will hit any target down to roughly 5KB. Below that, you’re fighting the laws of data: there is only so much a 5KB file can hold, and the result will be visibly reduced.

How photo file sizes actually work

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

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 setting keeps more fine detail and produces a larger file; a lower quality discards detail for a smaller file.
3. Image complexity. A photo full of fine detail, noise, or busy texture compresses poorly (larger file at the same quality), while a smooth photo with flat areas like sky or a plain wall compresses 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 is also why cropping tightly to your subject helps: removing busy background detail lets the encoder spend its byte budget on the part that matters, instead of wasting it on texture you’re about to shrink past the point of legibility.

Why a target-KB tool beats a quality slider

A normal image editor asks you for a quality number and hands you whatever size results. That is backwards for almost every real-world use of a reduced photo: forms, inboxes, and web pages care about the size, not the quality. A target-KB compressor inverts the question — you give the size, the tool finds the best quality that fits — which is exactly what a hard size ceiling demands. You stop guessing and start landing.

How to reduce a HEIC, step by step

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

1. Open the reducer 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 from your device. The moment you choose a file, the tool decodes it and shows you a preview — so you can confirm you picked the right photo before doing anything else. Most browsers cannot display HEIC directly, so the tool decodes it for you.
3. Type your target in KB. 50, 100, 200, 500, or whatever your destination allows.
4. Click Compress. The tool searches for the best result that fits under your target, usually within a second or two for a phone photo.
5. Compare the before and after. The original is shown next to the result so you can see exactly what changed.
6. Download the result. You get a JPEG file named with the target size, ready to send or upload.

If the destination later complains, or if you want a little safety margin, type a slightly lower number (say 95KB for a 100KB cap) and reduce again. Some forms round up at the boundary, so landing a few KB under is safer than landing exactly on the limit.

What to do before you reduce

A small amount of prep in your phone’s photo editor produces noticeably better results, because the tool then spends its byte budget on the part of the photo that matters.

• Crop to the subject. A tightly framed face or document keeps far more visible detail at a small size than a wide scene with lots of background. Cropping first is the single biggest win.
• Crop to the right aspect ratio. If your destination wants a square, a 3:4 portrait, or a 4:5 ratio, crop to that shape before reducing. The tool preserves your image’s dimensions unless it must shrink them to hit the target.
• Straighten and rotate. If your photo relies on an EXIF orientation tag to display upright, some downstream services ignore it. Rotate in the editor first so the pixels themselves are upright.
• Don’t worry about pre-converting. The tool takes HEIC directly, and HEIC preserves quality well before compression, so there is no need to convert to JPEG beforehand.

The tool handles the file-size part of the problem directly. The pixel dimensions, aspect ratio, and background are things only you can set — and a few seconds of cropping makes every target easier to hit cleanly.

How the reduction actually works

This is worth understanding, because it explains why the result still looks good even at aggressive reductions. 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 generally 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 using a WebAssembly module, entirely on your device. No pixel data is ever sent anywhere.

2. Binary-search the JPEG quality

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 your target. A binary search is efficient: rather than trying quality 50, then 51, then 52, it jumps to the middle, checks whether that fits, and narrows in within a handful of attempts.

3. Hold a quality floor, then resize

This is the part that protects how the photo looks. Older “hit a target size” tools 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 portraits and ID photos.

This tool enforces a quality floor. It lowers quality only so far, and if even that floor still exceeds the target at full resolution, it stops lowering quality and starts resizing instead. The principle is simple: trade pixels before you trade visible quality. A smaller but clean photo looks far better than a full-size but blocky one.

4. Resize with Lanczos, then retry

When a resize is needed, the tool uses a Lanczos resampling filter — the gold standard for downscaling photographs. Lanczos preserves edges and fine detail far better than the faster bilinear filters many tools default to, and it avoids the aliasing and jagged diagonals you get from simpler methods. After resizing, the tool repeats the quality search on the smaller image and loops until it lands under your target.

The result is the best-looking JPEG that fits whatever size you picked, given the photo you started with.

Pick your target

The most common targets people need are already covered by dedicated pages tuned for each form’s expectations. Common targets:

• 50KB — strict exam portals, small avatars, tight form caps.
• 100KB — the most common ceiling, used by countless government and exam forms.
• 200KB — generous allowance for visa photos, document scans, profile pictures.
• 500KB — effectively full quality; useful when the form is generous but the original is still too big.

For tighter or unusual limits: 20KB, 30KB. Type any number for a custom target — the tool accepts anything from 5KB up. If your destination allows more than the original, use the full allowance; there’s no benefit to going smaller than necessary.

Privacy: nothing leaves your device

The photos people shrink — passport portraits, exam registration headshots, visa images, medical document scans — are among the most sensitive files they handle. So this deserves to be said plainly.

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. When you close the tab, the data is gone. There is no account, no storage, and no analytics applied to your image.

This is a meaningful difference from most “online compressor” websites, which upload your photo to a server, process it there, and send it back. For a vacation snapshot that might not matter; for a passport or medical photo, it matters a great deal. Running everything locally is both a privacy guarantee and a speed advantage — there is no round trip to a server and back.

Reduce vs convert: what’s the difference

“Reduce” and “convert” sound similar but solve different problems, and it helps to know which one you actually need.

• Reducing means making the file smaller. The output is smaller in bytes than the input — that is the point.
• Converting means changing the format. HEIC to JPEG is the most common case, because most of the world (forms, browsers, Windows, Android, older software) doesn’t accept HEIC.

In practice the two overlap: shrinking a HEIC almost always means re-encoding to JPEG, so a single pass through this tool both reduces and converts. But if your only goal is to get a JPEG and you don’t care about the byte count, you want a converter: see Convert HEIC to JPG. If your goal is to hit a specific size — 100KB, 200KB, 500KB, anything — you want this tool.

Reduce HEIC, then move on

You don’t need a desktop suite, a paid app, or an upload-and-hope compressor to shrink an iPhone HEIC. You need a target in KB, a browser, and a tool that respects both the size and the photo. Drop the file in, type the number, and the result is a clean JPEG that fits — produced entirely on your device.

Pick a target above, or type your own. Whatever number your form or inbox allows, the tool lands at or under it — privately, in your browser, with no upload.