HEIF to SVG Converter

Convert HEIF to SVG: Read This First

A .heif file is almost always a photograph — High Efficiency Image File Format (ISO/IEC 23008-12, published by MPEG in 2015) stores an HEVC-compressed still image, and it is the format iPhones save by default since iOS 11. SVG is a completely different thing: a vector format built from shapes and paths, not pixels. This converter does not wrap your photo inside an SVG; it traces the image and rebuilds it as flat vector shapes. Tracing is the right tool for logos, icons, line art, and flat high-contrast graphics — but a real photo traces poorly, collapsing into posterized blobs of flat color, losing fine detail, and often producing a file far larger than the original. Since most HEIF files are camera photos, the honest answer is usually: don't trace it. Convert to a raster format instead — HEIF to PNG, HEIF to JPG, or HEIF to WebP.

How to Convert HEIF to SVG

1. Upload Your HEIF File: Drag and drop your .heif file onto the page, or click "+ Add Files" to browse. You can queue several images and trace them with the same setting.
2. Set Number Precision: Open Advanced Options and adjust the Number precision slider (1–10). It controls how many decimal places the traced path coordinates keep — lower shrinks the file, higher retains fine detail. The page recommends 4–6 for most use cases.
3. Confirm Tracing Is the Right Call (Optional): Tracing follows exactly what is in the image. A sharp, flat, high-contrast graphic traces cleanly; an ordinary photo does not. If your HEIF is a real photograph, stop here and convert to a raster format instead.
4. Convert and Download: Click "Convert" and download your SVG. No sign-up, no watermark.

Walk-through: Why HEIF Is a Hard Case for Tracing

HEIF was designed to store continuous-tone photographs efficiently — HEVC compression, up to 10-bit and 12-bit color depth, wide color gamuts, and smooth tonal gradients. That is exactly the kind of image vector tracing handles worst. The tracer has to approximate every subtle gradient as a stack of flat-color shapes, so a photo turns into a mosaic of posterized patches rather than a sharp, scalable graphic. A typical iPhone photo has millions of distinct colors; the trace cannot reproduce them as paths without either flattening them into blobs or emitting tens of thousands of tiny shapes that bloat the file.

The Number precision slider does not fix this. Precision only sets how exactly each found path coordinate is written down, not how the trace finds shapes:

• Want the smallest file? Lower it toward 1–3. Coordinates round to fewer decimals, so the text is shorter; on suitable artwork the visual difference is invisible.
• Want to keep fine curves? Raise it toward 7–10, at the cost of a larger file. Beyond about 6 the extra decimals rarely change what you see — they mostly add bytes.
• Tracing a logo for the web? Stay around 4–5 for crisp edges and a compact file that loads quickly.

Precision cannot add detail the trace did not find. If the output looks blobby, the fix is a cleaner, simpler source image — not a higher precision value.

Common Errors and How to Fix Them

• "The SVG looks posterized, blobby, or nothing like my photo" — You traced a photographic HEIF. Continuous-tone photos have millions of colors and soft gradients that vectorizing collapses into flat shapes. Tracing is built for logos and line art; for a photo, keep it as a raster: HEIF to PNG or HEIF to JPG.
• "The SVG file is huge — bigger than the HEIF" — HEIF is highly compressed, so a busy photo forces the tracer to emit thousands of paths, one per color region, easily ballooning past the compact original. Simplify the source (fewer colors, higher contrast) or accept that this image is not a vectorization candidate.
• "Fine detail and thin lines disappeared" — Small features fall below the tracer's noise-filtering threshold and get dropped. Start from a larger, sharper, higher-contrast graphic so thin strokes survive the trace.
• "I expected my logo back as editable layers" — Tracing rebuilds the picture as filled vector shapes grouped by color, not as your original named layers or fonts. Text becomes outlined paths, not live, re-editable type.
• "I wanted to keep my photo's quality" — Tracing discards photographic detail by design. To preserve the picture, keep it as a raster like PNG for lossless quality.

When This Doesn't Work

Vectorization is the wrong tool for photographs, screenshots full of text, and any image with smooth gradients or thousands of colors — the trace will be inaccurate and the file bloated. Since the overwhelming majority of HEIF files are iPhone and camera photos, that covers most of them. SVG tracing shines only on flat-color graphics: logos, icons, stencils, silhouettes, and line drawings that happen to be stored as HEIF. If your goal is to view, share, or edit the picture, a raster conversion is what you want — HEIF to PNG for lossless quality, HEIF to JPG for a small shareable file, or HEIF to WebP for the smallest modern web image. For complex logos that need hand-cleanup, a desktop editor like Inkscape or Illustrator gives you manual control the automatic trace cannot.

Frequently Asked Questions

Does this embed the HEIF inside an SVG or actually vectorize it?

It vectorizes. The converter traces shapes and edges and rebuilds the image as real SVG paths and Bézier curves — it does not base64-encode the original photo into an <image> tag. That means the output is genuinely resolution-independent for suitable artwork, but it also means a photographic HEIF is reinterpreted as flat shapes rather than preserved pixel-for-pixel.

Will my iPhone photo convert to a clean, scalable vector?

No. A HEIF photo holds continuous tones and millions of colors, so tracing approximates it as many flat color shapes — the result looks posterized and is often larger than the original. Tracing is designed for logos, icons, and line art with limited colors and clear edges. For an actual photo, keep a raster format such as HEIF to PNG.

What value should I use for Number precision?

For most artwork, 4–6 is the sweet spot — crisp paths at a reasonable file size, and it is what the page recommends. Drop toward 1–3 for the smallest possible file when slightly rounded coordinates are acceptable; only push toward 8–10 if you genuinely need sub-pixel accuracy, since beyond 6 the extra decimals usually add bytes without a visible change. Precision never adds detail the trace did not find.

If I shouldn't trace a photo, what should I convert my HEIF to?

For viewing and sharing, convert to JPG — small and universally supported. For lossless quality, use PNG. For the smallest modern web image, use WebP. Reach for SVG only when the HEIF is actually a flat, high-contrast graphic such as a logo or line drawing.

Can browsers and design apps open the resulting SVG?

Yes. SVG is a W3C XML-based standard supported by Chrome, Firefox, Safari, and Edge — caniuse reports roughly 97% global browser support — and it imports into Illustrator, Inkscape, Figma, and most vector editors. In our testing, a flat two-color logo saved as HEIF and traced at precision 5 produced a compact SVG that opened identically in the browser and in Inkscape, while the same setting on a real HEIF photo produced a heavy, posterized file.

Is my file kept private?

Yes. Your HEIF is uploaded over an encrypted connection, traced on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, and nothing is shared or made public.