Initializing... drag & drop files here
Supports: DNG
A DNG is a camera RAW photograph — a single high-bit-depth image straight off the sensor. SVG is a vector format built for shapes and paths. This converter does not wrap your photo inside an SVG; it traces the image and rebuilds it as flat vector shapes. Tracing a detailed photo almost always looks wrong: the result posterizes into blobs of flat color, loses fine detail, and the file can balloon past the original. If you just want a normal, usable image, convert your DNG to PNG, JPG, or TIFF instead. Use SVG tracing only when your DNG is a simple, high-contrast graphic — a logo shot, a scanned line drawing, a flat-color sign.
.dng file onto the page, or click "+ Add Files" to browse. You can queue several files and trace them with the same setting.DNG was designed by Adobe (launched September 27, 2004) as an open, TIFF/EP-based container for raw sensor data — high bit depth, millions of colors, 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.
The Number precision slider does not fix this. Precision only sets how exactly each found path coordinate is written down:
Precision cannot add detail the trace did not find. If the output looks blobby, the source is the problem, not the slider.
Vectorization is the wrong tool for almost every DNG, because almost every DNG is a real photograph. It shines only on flat-color graphics — logos, icons, stencils, silhouettes, and line drawings — that happen to have been captured or stored as RAW. If your goal is simply to view, share, or edit the photo, a raster conversion is what you want: DNG to PNG for lossless quality, DNG to JPG for small shareable files, or DNG to TIFF for editing at full bit depth. Reserve SVG only for the rare DNG that is genuinely a simple graphic.
It vectorizes. The converter traces shapes and edges and rebuilds the image as real SVG paths and 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 DNG is reinterpreted as flat shapes rather than preserved pixel-for-pixel.
No. A DNG holds continuous-tone, high-bit-depth sensor data with millions of colors, so tracing approximates it as many flat color shapes — the result looks posterized and the file is often larger than the original. Tracing is built for logos, icons, and line art. For an actual photo, keep a raster format such as DNG to PNG.
For most artwork, 4–6 is the sweet spot — crisp paths at a reasonable file size. 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.
For viewing and sharing, convert to JPG — small and universally supported. For lossless quality, use PNG. For editing at the camera's full bit depth, use TIFF. Reach for SVG only when the DNG is actually a flat, high-contrast graphic.
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 traced at precision 5 produced a compact SVG that opened identically in the browser and in Inkscape, while the same setting on a real DNG photo produced a heavy, posterized file.
Yes. Your DNG 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.