Initializing... drag & drop files here
Supports: HEIC
HEIC (High Efficiency Image Container) is Apple's default photo format since iOS 11, released September 19, 2017. It stores raster pixel data using HEVC-derived compression — roughly half the byte size of JPEG at similar SSIM quality. SVG is a completely different beast: an XML-based vector format defined by the W3C, where shapes are described as mathematical paths instead of a pixel grid. There is no lossless one-to-one mapping between the two; the conversion runs an image-tracing pass that approximates the HEIC's pixels as filled vector paths.
This conversion is genuinely useful in a narrow set of cases — and a poor fit for most photographs:
For ordinary iPhone photos — landscapes, portraits, food shots — SVG is the wrong target. The tracer has to approximate thousands of subtle color gradients with discrete paths, producing huge files (often 10-100x larger than the source HEIC) that look posterized and aren't practically editable. Use HEIC to JPG or HEIC to PNG for those cases instead.
| Property | HEIC | SVG |
|---|---|---|
| Data model | Raster (pixel grid) | Vector (XML paths) |
| Defined by | MPEG ISO/IEC 23008-12 (HEIF container) | W3C SVG 1.1 / 2 |
| Apple iOS default since | iOS 11 (Sept 19, 2017) | n/a (web standard) |
| Underlying compression | HEVC intra-frame (H.265) | gzip-compressible XML |
| Scaling | Blurs/pixelates when enlarged | Sharp at any zoom level |
| Color depth | Up to 16-bit per channel, wide gamut | Limited by tracing; flat fills + gradients |
| Best for | Photographs, screenshots, HDR captures | Logos, icons, line art, diagrams |
| Browser support | Safari 17+ only; Chrome/Firefox via JS decode | Universal (every modern browser since 2011) |
| Editable paths | No | Yes — open in Illustrator, Inkscape, Figma |
| Typical file size (simple graphic) | 80-200 KB | 5-50 KB after tracing |
| Typical file size (complex photo) | 1-5 MB | 5-100 MB after tracing (impractical) |
The "Number precision" slider controls how many decimal digits are kept in each path coordinate. Fewer digits make smaller files; more digits keep curves smoother.
| Precision | Behavior | Use when |
|---|---|---|
| 1-2 | Very rough paths, smallest file | You only need a silhouette or low-fidelity icon |
| 3 | Compact, slightly stair-stepped curves | Simple logos at small display sizes |
| 4-6 (default 6) | Recommended balance | Most use cases — readable paths, manageable size |
| 7-8 | Higher fidelity, larger file | Detailed line art, illustrations with tight curves |
| 9-10 | Maximum precision | Print or laser-cut workflows where geometry matters |
Only if the original image is graphically simple. A photo of a printed logo, a silhouette, or high-contrast line art traces into a handful of paths you can actually edit. A photo of a face, a landscape, or food traces into thousands of overlapping color regions that technically open in Illustrator but aren't practical to edit and produce files many times larger than the source HEIC.
HEIC compresses pixel data very efficiently using HEVC intra-frame compression. SVG describes shapes as text — every path coordinate, color, and curve handle is spelled out in XML. For a photograph, that XML can run to millions of characters. The fix is to either choose a simpler source image, lower the Number precision slider, or convert to HEIC to PNG instead if you wanted a raster.
Yes. The output is a standards-compliant SVG that opens in Adobe Illustrator, Inkscape (free), Affinity Designer, Figma, Sketch, and any browser. Path-level edits — recoloring fills, deleting paths, smoothing curves — work the same as any vector file.
Partially. SVG supports the sRGB color space natively and Display P3 via CSS color functions, but the tracer flattens HEIC's 10-bit-per-channel HDR data into discrete fill regions. Subtle color transitions become posterized bands. If color fidelity matters, keep the source in HEIC or convert to a 16-bit-capable raster like HEIC to TIFF.
True vectorization. The output uses <path> elements with traced geometry, not an embedded <image> reference to the original pixels. You can confirm by opening the SVG in a text editor — you will see d="M…" path strings, not a base64-encoded JPEG/PNG payload. Some other HEIC-to-SVG converters do take the wrapping shortcut; that produces a file that scales blurry just like the original raster.
The xconvert pipeline exposes one knob — Number precision — which controls path coordinate fidelity. If you need fine control over color count, edge threshold, or curve smoothing, run the converter at the default settings to get a starting SVG, then refine it in Inkscape's Path → Trace Bitmap dialog or Illustrator's Image Trace panel.
Only the still primary image is converted. A Live Photo's motion component (the embedded .mov) and burst sequences beyond the cover frame are not used — the tracer only operates on the single decoded still. To keep the motion, use HEIC to MP4 for the Live Photo's video portion instead.
Single-frame HEIC and the primary frame of multi-image HEIC containers. Animated HEIC sequences flatten to the cover image before tracing — there is no animated-SVG output. For animated outputs from HEIC, see HEIC to GIF or HEIC to WebP.
Yes, if the traced result is geometrically clean. Cricut Design Space, Silhouette Studio (Designer Edition+), and Glowforge all accept SVG uploads. For cutting, prefer Number precision 7-10 so corners and curves land where you expect, and clean up stray paths in Inkscape before sending the file to the cutter.