Add your HEIF file
Drop one or more .heif files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Tracing a .heif image to .svg redraws it as outlined colour shapes, so the result can be scaled, recoloured, or fed to a cutter or embroidery digitizer. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Tracing a .heif image to .svg redraws it as outlined colour shapes, so the result can be scaled, recoloured, or fed to a cutter or embroidery digitizer. A .heif file uses the High Efficiency Image File Format, a codec-agnostic container standard rather than a single compression scheme. Where .heic specifically means HEVC-coded content, the .heif extension signals the general container, which can in principle wrap HEVC, AV1, or even JPEG payloads along with sequences and derived images.
An .svg file is a Scalable Vector Graphics document: an XML text file describing shapes, paths, text, and gradients mathematically rather than as pixels. Because the geometry is resolution-independent, one .svg renders razor-sharp at any size, from a 16-pixel favicon to a billboard. For this route the practical draw is infinite scalability with no quality loss at any zoom or resolution and tiny file sizes for geometric artwork compared with high-resolution rasters — balanced against utterly unsuited to photographs, which have no economical vector representation, which is worth knowing before you commit a large batch.
Tracing is what you reach for when a .heif file is the only copy of a logo, badge, or line drawing you have, and you now need it sharp at any size — a large print, a vinyl or laser cut, or the vector outline an embroidery digitizer starts from. Flat-colour artwork traces cleanly; photographs do not, because there are no crisp colour boundaries for the tracer to follow. Expect to tidy the result in a vector editor for production work.
| Aspect | HEIF image (.heif) | SVG vector (.svg) |
|---|---|---|
| Format type | Lossy — discards detail it judges invisible to shrink files | Vector — resolution-independent geometry instead of pixels |
| How it stores data | iSO BMFF box structure: items, item properties, and item references describe images declaratively | plain XML: elements like <path>, <rect>, <circle>, and <text> with a d-attribute path language for arbitrary curves |
| Strongest at | container-level workflows that need bursts, brackets, or multi-resolution imagery in one file | logos and brand marks that must stay crisp at every display density |
| Weak spot | the extension alone does not reveal the codec inside, so a given .heif file may or may not decode on a given device | utterly unsuited to photographs, which have no economical vector representation |
| Metadata | eXIF and XMP are first-class metadata items in the container, with ICC profiles or CICP parameters describing color; what survives conversion depends on the tool, not the format | metadata travels as XML: <title> and <desc> elements aid accessibility, a <metadata> element can hold RDF or XMP, and Creative Commons licensing blocks are common in Inkscape output; EXIF does not apply |
Drop one or more .heif files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .svg in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if SVG is selectable, the route is real and validated.
Press Convert. An image tracer running in local JavaScript groups the pixels into flat colour regions and fits outline paths around them, entirely inside your browser.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid SVG file. Outputs keep the original filename with the .svg extension.
Tracing is an interpretation, not a lossless conversion: the .heif pixels are grouped into a limited set of flat colours and redrawn as outlines, so gradients band, soft edges harden, and fine texture disappears. The quality slider controls how many colours and how much detail survive. The payoff is that the .svg result then scales to any size without ever pixelating.
Yes — the .heif file is processed inside your browser tab and never uploaded. An image tracer running in local JavaScript groups the pixels into flat colour regions and fits outline paths around them, entirely inside your browser. Close the tab and the file is gone from memory.
Every modern browser renders SVG natively, inline in HTML or as an image source, and design tools from Illustrator and Figma to Inkscape treat it as a first-class format. Gaps appear in contexts expecting rasters — email clients, older office software, some CMS uploaders — which is when rasterizing to PNG at a chosen resolution becomes necessary.
It depends entirely on the artwork. A flat logo or line drawing traces to a handful of paths and often lands far smaller than the .heif source. A photograph produces thousands of paths and can be many times larger — if that happens, lower the quality to trace fewer colours, or accept that the image is not a good tracing candidate.
In .heif, eXIF and XMP are first-class metadata items in the container, with ICC profiles or CICP parameters describing color; what survives conversion depends on the tool, not the format. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.