Initializing... drag & drop files here
Supports: CR2
This converter does two things in sequence: it renders your Canon CR2 raw file into a viewable image (demosaicing the sensor data and baking in white balance), then traces that image into a true SVG — real vector paths and Bézier curves, not the photo base64-encoded inside an <image> wrapper. That distinction decides whether the result is useful to you. Tracing a photograph does not give you a scalable copy of the photo; it gives you a posterized, stylized vector illustration — flat color regions with the fine detail collapsed away. This page walks through the conversion, the one setting that matters, and — most importantly — when CR2 to SVG is the wrong choice and you should convert to JPG or TIFF instead.
.cr2 file onto the page, or click "+ Add Files" to browse. You can queue several raw files and trace them with the same setting.A CR2 file is raw sensor data — it has to be developed (demosaiced, white-balanced) into RGB pixels before anything can display it. That part is faithful. The second step is where photos and vectors collide: the vtracer engine groups neighbouring pixels into solid color regions and draws a path around each one. A logo has a handful of regions, so it traces cleanly. A photograph has millions of subtly different pixels, so the tracer is forced to quantize them into a small number of flat colors — the same effect as a poster print or a screen-print stencil.
What that means in practice:
Raising Number precision does not add detail the trace never found — it only decides how exactly the found shapes are written down. If the output looks blobby, the cause is the photographic source, not a low precision value.
.cr2 file.Vectorization is the wrong tool for any photograph you want to keep looking like a photograph — portraits, landscapes, product shots, anything with smooth tone and fine texture will trace to a stylized, lower-fidelity graphic, and the file may be larger than the source. CR2 to SVG earns its place only in the deliberate-stylization niche: turning a photo into poster art, a flat-color illustration, a stencil, or artwork destined for laser cutting and CNC tools (Glowforge, Cricut, LightBurn) that require vector input. For everything else, the right move is a raster format — CR2 to JPG for web-ready photos or CR2 to TIF for an archival master — and you can trace one of those later if you change your mind. Note also that CR2 carries no transparency and no editable layers, so the SVG is a single flattened rendering, not your camera's raw data in a new container.
It traces. After rendering the raw file to RGB, the converter runs the open-source vtracer engine, which groups pixels into color regions and rebuilds the image as real SVG paths and Bézier curves — it does not base64-encode the photo into an <image> tag. The output is genuinely resolution-independent for the shapes it found, but for a photograph those shapes are a posterized approximation of the original, not a faithful copy.
No. Scalability is real — the traced shapes have no pixels, so they stay crisp at any size — but the detail is lost during tracing, before any scaling happens. A photo has millions of subtly different pixels, and the tracer must quantize them into a handful of flat colors, which looks posterized. SVG is built for logos, icons, and line art with solid color regions; a photographic raw file is the opposite of that. If preserving the photo matters, keep it as a raster.
Because a detailed photo forces the tracer to create one path per color patch, and a busy image can produce thousands of them. All that path data adds up — often past the size of a compressed JPG of the same shot. True file-size savings from vectorizing come from simple artwork (a two-color logo), not from photographs. Lower the Number precision slider to trim some bytes, or keep the image as a raster.
For most images, 4–6 is the sweet spot — reasonably crisp paths at a sensible file size. Drop toward 1–3 when you need the smallest possible file and can accept slightly rounded coordinates; only push toward 8–10 if you genuinely need sub-pixel edge accuracy, since beyond 6 the extra decimals usually add bytes without a visible change. Precision never recovers detail the trace did not capture.
No. CR2 stores roughly 14-bit-per-channel raw sensor data plus full EXIF (lens, exposure, autofocus, camera calibration). The conversion bakes white balance into a rendered image, traces it as 8-bit sRGB, and writes plain SVG markup — none of the raw latitude or the EXIF block survives. Keep the original CR2 if you may want to re-develop the exposure later, and treat the SVG purely as a stylized derivative.
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 CR2 of a high-contrast logo sign traced at precision 5 produced a clean, compact SVG, while a CR2 portrait at the same setting came out visibly posterized — a good illustration of which sources suit this tool.
Your CR2 is uploaded over an encrypted connection, rendered and traced on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, and nothing is shared or made public.