Compress HEIC to 500KB — exactly.

Getting an iPhone HEIC photo down to 500KB is one of the most forgiving size targets you’ll meet online — enough room to keep a photo looking essentially untouched, but still a real reduction from the multi-megabyte original. A high-resolution document scan, a certificate upload, or a print-quality web image with a 500KB ceiling will reject anything larger, usually with no guidance on how to get there. This tool does exactly that: you type 500, and it returns a JPEG at or under 500KB, with no upload and no guesswork — typically a 5–15× reduction from the source HEIC.

Why 500KB is a generous target

A 500KB limit shows up wherever a service wants to accept a high-quality, detailed image but still bound it for storage and upload. You’ll see it on document and certificate upload portals, visa and ID systems that accept a document scan (not just a headshot), large profile images, and print-quality web images where legibility of fine text matters.

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

A purpose-built 500KB 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 500KB HEIC compressor

A 500KB photo cap is most common in situations that want a high-quality, detailed file but still bounded:

• High-resolution document or certificate scans. Portals that accept a scanned ID, certificate, contract, or supporting document sometimes set a 500KB maximum so fine text stays legible while storage stays predictable.
• Visa and ID systems accepting document scans. Some immigration and ID systems permit a larger upload for a document scan than for a headshot, and 500KB is a typical generous ceiling.
• Large profile or member images. Services that permit a larger profile picture than a basic avatar — print-quality or high-resolution headshots for directories, professional listings, and membership platforms.
• Print-quality web images. Editorial, portfolio, and listing images that need to stay sharp on retina screens but still load quickly.
• Forms that accept JPEG only. A 500KB JPEG cap forces conversion from HEIC and a modest reduction in one step.

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

How to compress HEIC to 500KB, 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 500KB. It is preset, but you can type any number.
4. Click Compress. The tool searches for the best result that fits under 500KB, 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 495KB) and compress again. Some forms round up at the boundary, so landing a few KB under is safer than landing exactly on 500KB.

How the compression actually works

It helps to know what the tool is doing, especially since 500KB is a target where you usually get to keep almost everything. 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 500KB. 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 document scan where fine text must stay legible.

This tool instead enforces a quality floor. It lowers quality only so far, and if even that floor still exceeds 500KB 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 500KB, this stage almost never triggers — virtually all photos fit at the quality floor without any resize.

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

On the rare occasion a resize is needed, the tool uses a Lanczos resampling filter — the gold standard 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 500KB. The result is the best-looking JPEG that fits the target, given the source.

What to expect from a 500KB photo

At 500KB, the honest expectation is an almost untouched image — near-full resolution, at high quality, with no visible loss for a typical document scan, certificate, or large profile image. A 500KB budget comfortably holds even a detailed photo, so the tool almost always keeps the original resolution and only lowers quality within the protected floor.

A few practical expectations:

• Almost no resize. Even a detailed 12-megapixel photo frequently fits under 500KB at the quality floor, so for most inputs the full resolution is preserved — often 2000–4000+ pixels on the long edge.
• Fine text and detail stay sharp. Because the tool holds a quality floor and resizes only as a last resort (rarely at 500KB), small text in a document scan and fine detail in a certificate remain legible — which is the whole point of a generous size allowance.
• Faces and skin stay clean. With quality reduction minimal at this target, portraits look essentially identical to the source.
• The output is a single JPEG, no animation or transparency — just the still image in the format forms expect.

If the result does resize more than you’d like, the likely cause is an unusually large or extremely detailed source (a very high-resolution scan or a noisy photograph). 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 500KB:

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 500KB is more than enough for a clean headshot (which compresses well) and still comfortable for a busy document scan full of fine text — even though the scan starts from the same pixel count.

What 500KB actually buys you

For a typical document scan, certificate, or large profile image, 500KB is enough to keep near-full resolution — often 2000–4000+ pixels on the long edge — at a high quality, with fine text remaining legible and edges staying crisp. This is why 500KB suits detailed document and scan uploads where readability of small 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 the best quality that fits — which is exactly what a hard 500KB 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 500KB 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.

• File size. Set the tool a few KB under what the form states (e.g. 495KB for a 500KB limit) to be safe against rounding.
• Pixel dimensions. If a form specifies exact pixels, crop or resize in your phone’s editor to match, then compress. The tool preserves your dimensions unless it must shrink them to hit the target — at 500KB, that’s rare.
• Aspect ratio. Many ID and document photos want a specific ratio (square, portrait like 3:4, or A4 for scans). Crop to the required ratio before compressing.
• Color and background. Some forms want a white or light background — a capture-time concern, not a compression one.

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 500KB is a common ceiling where the system accepts either a headshot or a supporting document scan. Beyond file size, expect rules around dimensions, background, and framing.

• Dimensions. Many countries specify the print size (e.g. 35×45 mm) and an equivalent in pixels at a given DPI. Crop to the required size in your phone’s editor before compressing.
• Background. Usually plain white or light grey, evenly lit, without shadows or patterns. This is a capture-time concern.
• Framing. Head centered, facing the camera, neutral expression, no glasses in some jurisdictions. These are photography requirements the compressor cannot change.

Because 500KB is generous, you can comfortably satisfy the dimension and quality requirements together — the photo stays sharp and 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:

• Square (1:1). Used by many web platforms and some ID systems.
• Portrait 3:4 or 4:5. Common for passport-style photos.
• 35×45 mm (portrait). Used by many countries’ visa and ID photos — roughly 413×531 pixels at 300 DPI.
• 2×2 inches (square). Used by US passport and visa photos — roughly 600×600 pixels at 300 DPI.
• A4 portrait. Common for document scans — crop to the paper shape before compressing.

At 500KB the final pixel dimensions are almost always preserved, so these digitization guidelines are fully achievable.

Troubleshooting

The form still says the file is too large. Some forms round up. Re-compress targeting a few KB lower (495KB or 490KB) 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 (high-resolution scans, multi-megabyte originals) take longer because decoding and encoding scale with pixel count. This is normal and still finishes in a few seconds, all on your device.

The result looks resized when I expected full resolution. This is very rare at 500KB but can happen with unusually large or extremely detailed sources (a high-DPI document scan, for example). Crop to the subject first to give the tool a cleaner, smaller input.

Privacy: nothing leaves your device

The photos people compress for visas, IDs, and document uploads — passport portraits, certificate scans, contract 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 passport, ID, or document scan, running everything locally is both a privacy guarantee and a speed advantage — no round trip to a server.

How this compares to other approaches

• A generic online compressor. Uploads your photo, exposes you to ads and tracking, and gives you a quality slider rather than a target size, so you still guess and re-check. It also sees your photo.
• A phone editor or photos app. Can export HEIC as JPEG, but doesn’t target a file size. You get whatever the chosen quality produces and iterate manually.
• Desktop image software. Powerful, but overkill for one photo, and usually not on the phone where your HEIC lives.
• This tool. Purpose-built: type the KB target, get a JPEG that fits, locally and privately, with no setup.

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

Related target sizes

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

• A generous ceiling. The 500KB target above, for high-res scans and large uploads where detail matters.
• Slightly tighter. A 200KB HEIC compressor for visa photos and document scans with a moderate cap.
• The most common ceiling. A 100KB HEIC compressor covers the limit most forms set.
• Tight caps. A 50KB HEIC compressor, a 30KB HEIC compressor, and a 20KB HEIC compressor for small avatars and strict portals.
• Plain conversion. Convert HEIC to JPG without targeting a size, or reduce HEIC file size more generally.

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