HEIF to SVG Converter

HEIF to SVG — Should You Trace It, or Keep It Raster?

A .heif file is almost always a photograph. HEIF (ISO/IEC 23008-12, published by MPEG in March 2015) stores an HEVC-coded still image, and it is what iPhones have written by default since iOS 11. SVG is a fundamentally different thing: an XML description of shapes, paths and curves, with no pixels in it at all. Converting between them is not a repackaging — it is a trace, which throws away the photograph and rebuilds an approximation of it out of flat vector shapes. That is exactly right for a logo, icon, stencil or line drawing that happens to be saved as HEIF. It is exactly wrong for a camera photo, which comes out posterised, inaccurate, and frequently larger than the file you started with. Read the comparison below before you commit, and note the practical point in the how-to: the trace is only ever as good as the raster it is given, so rasterising the HEIF to a PNG you have actually looked at is where most of the quality is won or lost.

Trace It or Keep It Raster: Side-by-side

When Tracing a HEIF Actually Makes Sense

• The image is flat artwork, not a photo — a two- or three-colour logo, a monochrome icon, a stencil or a silhouette that someone saved or exported as HEIF.
• You need it to scale. A traced logo stays crisp on a business card and on a billboard, because there is no fixed pixel grid to enlarge.
• You want it as shapes you can recolour. The trace produces filled paths grouped by colour, which a vector editor can select and restyle.
• The destination demands SVG — an icon slot in a design system, an inline <svg> in a page template, a cutting or engraving machine that reads paths.

When to Keep It Raster Instead

• It is a camera photograph. No precision setting rescues a trace of continuous tone; the output is a mosaic of flat patches. Convert to HEIF to PNG for a lossless copy or HEIF to JPG for a small, universally readable one.
• It is a screenshot full of text. Every glyph becomes dozens of paths, and the result is both huge and slightly wrong.
• You just need it to open somewhere. HEIF to WebP gives the smallest modern web image; HEIF to PDF gives a document you can email or print.

How to Convert HEIF to SVG

1. Rasterise Your HEIF to PNG First: PNG is the ideal input for a tracer — lossless, so no compression ringing gets mistaken for an edge — and having the render in front of you is your chance to crop, raise contrast or downscale before any of it becomes paths. Run the photo through the HEIF to PNG converter and save the result.
2. Upload the PNG to the Tracer: Drag and drop the PNG onto the PNG to SVG page, or click "+ Add Files" to browse. You can queue several images and trace them all with the same setting.
3. Set Number Precision: Open Advanced Options and move the "Number precision" slider, which runs from 1 to 10 and starts at 6. It controls how many decimal places each traced path coordinate keeps — lower means a smaller file, higher means finer curves. The page's own note recommends 4 to 6 for most work.
4. Convert and Download: Click "Convert" and download your SVG. Files are uploaded over an encrypted connection, traced on our servers, and deleted automatically after a few hours. No sign-up, no watermark.

Number Precision: What the Slider Changes

One slider carries two jobs: it sets the colour precision used when pixels are clustered into regions, and the number of decimal places written into each path coordinate. It cannot add detail that was never detected, and the coupling puts a hard ceiling on the top of its range.

If the output looks blobby, precision is the wrong knob. The fix is a cleaner source: fewer colours, higher contrast, sharper edges, and a larger starting image so thin strokes survive the trace.

Common Problems and How to Fix Them

• "The trace stopped without producing a file." Two things are worth checking. Number precision at 9 or 10 stops the run outright, because one slider value feeds both the path precision and the colour precision and colour precision only accepts 1 to 8 — drop it to 8 or below. Otherwise, rasterise to PNG first and trace that; a plain, well-behaved PNG is the input a tracer is happiest with.
• "The SVG looks posterised and nothing like my photo." You traced continuous tone. Millions of subtly different colours cannot be described as a manageable number of filled shapes, so the tracer approximates them as flat patches. Keep the picture as a raster.
• "The SVG is bigger than the original image." A busy photo forces the tracer to emit thousands of paths, one per colour region, and that XML easily outgrows a compact HEVC-coded source. Simplify the artwork or accept that this image is not a vectorisation candidate.
• "Thin lines and small details disappeared." Small features fall below the tracer's speckle-filtering threshold and get dropped. Start from a larger, sharper, higher-contrast source so those strokes are several pixels wide.
• "I expected my layers and live text back." Tracing rebuilds a picture as filled shapes grouped by colour. Text becomes outlined paths, not editable type, and there are no named layers because the tracer never saw any.

Frequently Asked Questions

Does this embed the photo inside an SVG, or genuinely vectorise it?

It genuinely vectorises. The converter detects edges and colour regions and writes them out as real SVG paths and Bézier curves; it does not base64-encode the original picture into an <image> tag. That means the output is truly resolution-independent for suitable artwork, and it also means a photographic source is reinterpreted as flat shapes rather than preserved pixel for pixel.

Why rasterise the HEIF to PNG before tracing?

Because tracing quality is decided almost entirely by the pixels you hand over, and a PNG is where you get to decide what those pixels are. HEIF is a compressed HEVC-coded still built for photographs: it carries continuous tone across the whole frame, and it can carry HDR data and coding artefacts that a tracer will happily turn into paths. Rendering it to a lossless PNG first lets you look at the picture, crop to just the graphic element, raise the contrast so the edges the tracer is meant to find are actually distinct, and downscale a 12-megapixel capture to a size where a colour cluster means something. None of those adjustments are available once the file is a stack of Bézier curves, and every one of them changes the result more than the tracing slider does.

Will my iPhone photo come out as a clean, scalable vector?

No, and no setting changes that. A HEIF photograph holds continuous tone and an enormous number of distinct colours; the tracer has to approximate all of it as flat filled shapes, so the result is posterised and often larger than the source. Tracing was built for artwork with a limited palette and hard edges. For an actual photograph, HEIF to PNG is the conversion you want.

What Number precision value should I use?

Start at the default of 6 and only move it if you have a reason. The tool's own guidance is that 4 to 6 suits most use cases: crisp paths at a reasonable file size. Drop toward 1-3 when you want the smallest file and slightly rounded coordinates are acceptable, and push to 7 or 8 only when sub-pixel accuracy genuinely matters, such as feeding a cutter or engraver. Treat 8 as the real maximum: the same value is also sent as the colour precision, which only accepts 1 to 8, so positions 9 and 10 stop the run with an out-of-range error instead of producing a finer trace. Above about 6 the extra decimals mostly add bytes without changing what you see anyway.

Can I trace a photo if I first reduce it to a few colours?

You can, and it will look deliberate rather than broken — but it is a stylistic effect, not a faithful conversion. Posterising a photo down to a handful of colours before tracing produces the flat, screen-printed look you see on stencil-style portraits. If that is what you want, reduce colours and raise contrast in an editor first, then trace. If you wanted the photograph itself, keep it raster.

Will the SVG open in Illustrator, Inkscape and Figma?

Yes. SVG is a W3C XML-based standard with roughly 97% global browser support per caniuse, and every mainstream vector editor imports it — Illustrator, Inkscape, Figma, Affinity Designer, Sketch. What you will find inside is a stack of filled paths grouped by colour, which you can select, recolour and delete, rather than the layer structure of whatever created the original artwork.

How do I fix an SVG that traced almost right but has rough edges?

Clean up the source rather than the output. Increase the contrast between the shape and its background, remove JPEG-style noise and compression artefacts, and scale the image up before tracing so edges are several pixels wide. If a handful of paths are still wrong, open the SVG in Inkscape or Illustrator and edit those nodes directly — hand-correcting a nearly-right trace is far faster than hunting for settings that produce a perfect one.

What happens to my file while it is being converted?

It is uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, and nothing is shared or made public. Because the tracing runs server-side, the practical limit on a large or detailed image is upload size and time rather than anything about the machine you are sitting at.