Compress HEIC to 30KB — exactly.

Getting an iPhone HEIC photo down to 30KB is one of the tightest size targets you will meet online — and among the hardest to hit by hand. A subset of exam portals, small-thumbnail uploads, and strict membership or government forms cap photos at 30KB and reject anything larger, usually with no guidance on how to get there. This tool does exactly that: you type 30, and it returns a JPEG at or under 30KB, with no upload and no guesswork.

Why 30KB is such a tight target

A 30KB limit shows up wherever a service needs photos to be truly tiny and uniform — small enough to store at enormous scale, quick to upload on the slowest mobile connection, and cheap to verify by the thousand. You will see it on strict exam registration portals, small in-app thumbnail uploads, and certain membership or benefit systems that want a small, predictable file above all else.

The difficulty is that phones do not produce 30KB 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 30KB target is therefore a 40× to 100× reduction, and doing that precisely with a generic editor is painful: change a setting, export, check the size, repeat, overshoot, repeat again.

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

A 30KB photo cap is most common in situations that want a very small, predictable file displayed at a modest size:

• Exam portals. Standardized tests and certification systems in some regions cap candidate photos at 30KB so they can store and verify very large numbers of them cheaply. The photo is shown small next to a name, so a tiny file is all the system needs.
• Small thumbnails. Forums, membership sites, and in-app profile thumbnails sometimes set a 30KB ceiling for a tiny display photo that will never be enlarged.
• Government and membership forms. Certain identity, benefit, and licensing systems specify 30KB or less for the uploaded image.
• Forms that accept JPEG only. A 30KB JPEG cap forces conversion from HEIC and a large reduction in a single step.

In each case the requirement is the same: a JPEG, at or under 30KB, that still looks acceptable at a small size. That is exactly what this tool produces. The 30KB niche is distinct from both the 20KB target (which is typically for signature strips and tiny avatars) and the 50KB target (small avatars and thumbnails). If your form allows 50KB, use it — you will keep more resolution.

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

How the compression actually works

It helps to know what the tool is doing, especially at a tight target like 30KB where the result still needs to look acceptable. 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 30KB. A binary search is efficient: rather than trying quality 30, then 31, then 32, 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 an exam or thumbnail photo.

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

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

When 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 30KB. The result is the best-looking JPEG that fits the target, given the source.

What to expect from a 30KB photo

At 30KB, the honest expectation is a small but clean image. A 30KB budget cannot hold a large or detailed photo, so the tool will always reduce resolution — for a tightly cropped headshot, the result commonly lands around 250 to 450 pixels on the long edge, which is enough for a small exam-portal headshot or a thumbnail shown at a modest size.

A few practical expectations:

• Faces stay clear. Because the tool holds a quality floor and resizes only as much as needed, a headshot at 30KB keeps faces and edges sharp rather than turning blocky.
• Resolution reduction is expected, not a flaw. A 12-megapixel photo cannot fit into 30KB without heavy artifacting, so shrinking is the correct trade. The output is small in pixels but clean in appearance.
• The output is a single JPEG, no animation or transparency — just the still image in the format forms expect.

If the result looks too soft, the most likely cause is a busy, detailed source rather than a tight headshot. Cropping to the subject first (in your phone’s editor) makes a big difference at 30KB, because the tool then spends its tiny 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 30KB:

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, and it is especially important at 30KB: a tightly cropped headshot against a plain background fits far more cleanly than a wide, busy scene. Cropping before compressing is the single most effective thing you can do to improve a 30KB result.

What 30KB actually buys you

For a clean headshot, 30KB corresponds to roughly 250 to 450 pixels on the long edge at a sensible quality — enough for a small exam-portal headshot or a thumbnail, but not enough for a large or detailed image. This is why 30KB targets suit small ID-style photos and resist wide scenes.

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 30KB 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 small targets like 30KB far more cleanly. JPEG was designed for photographs and produces small files that look good; 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. 27KB for a 30KB 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 30KB, it almost always must.
• Aspect ratio. Many small form photos want a specific ratio (square, or portrait like 3:4). 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.

Common aspect ratios and dimensions

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

• Square (1:1). Used by many web platforms and small thumbnails.
• Portrait 3:4 or 4:5. Common for passport-style photos and candidate headshots.
• 35×45 mm (portrait). Used by many countries’ visa and ID photos — roughly 413×531 pixels at 300 DPI, though at 30KB the final file will be smaller in pixels than this guideline once the tool resizes to fit.

At 30KB the final pixel dimensions will be smaller than these digitization guidelines once the tool resizes to fit, but the aspect ratio you crop to is preserved.

Troubleshooting

The form still says the file is too large. Some forms round up. Re-compress targeting a few KB lower (27KB or 25KB) 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 still finishes in a few seconds, all on your device.

The result looks too soft. Crop tightly to the subject first. A headshot cropped before compression always looks better at 30KB than a wide scene — the detail budget goes to the face instead of the background.

Privacy: nothing leaves your device

The photos people compress to 30KB — exam portraits, ID-style headshots, membership photos tied to real identity — 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 an exam or membership 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

• 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 until it happens to fit — tedious at a tight target like 30KB.
• 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 phone photo and a form needs it under 30KB,” a targeted browser-side compressor is the most direct path.

Related target sizes

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

• Need a little more room? A 50KB HEIC compressor keeps clearly more resolution, and a 100KB HEIC compressor — the most common ceiling of all — keeps more still.
• Need the most quality? A 200KB HEIC compressor or 500KB HEIC compressor for forms with a generous ceiling, where your photo stays near full resolution.
• Need it even smaller? A 20KB HEIC compressor for signature strips and tiny avatars.
• Related tools. Convert HEIC to JPG for plain format conversion, or Reduce HEIC file size when you just want a smaller file with no specific target.

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