DNG to SVG Converter

Convert DNG to SVG: What This Tutorial Covers

A DNG is a camera RAW photograph — one high-bit-depth frame of unprocessed sensor data. SVG is a vector format made of paths, curves and fills. Nothing inside a DNG is a path, so this conversion cannot re-wrap your file; it has to trace the picture and rebuild it as flat vector shapes. This page walks through the one setting the tracer exposes, shows why rendering the RAW to PNG yourself first gives you a better trace, and is blunt about the cases where you should convert to PNG or JPG instead and stop.

How to Convert DNG to SVG

1. Upload Your DNG File: Drag and drop your .dng onto the page or click "Add Files" to browse. Several files can be queued and traced with the same setting.
2. Set Number Precision: Open Advanced Options and move the "Number precision" slider, which runs from 1 to 10 and sits at 6 by default. It is the only tracing control on this page, and it changes two things at once — see the walk-through below.
3. Consider Rendering to PNG First: A tracer works on decoded pixels, and a RAW is a sensor mosaic that has to be demosaiced, white-balanced and tone-curved before it is one. Rendering it yourself with DNG to PNG and then tracing that PNG with PNG to SVG means you choose the exposure, crop and size the tracer sees — same tracer, same slider, a much better-controlled input.
4. Convert and Download: Click Convert and save the .svg. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark.

Walk-through: What "Number Precision" Really Does

Most write-ups describe this slider as a file-size control for path coordinates. That is only half of it. In our pipeline the single value you pick is handed to the tracer twice — once as colour precision and once as path precision — so one slider governs two unrelated parts of the trace:

• Colour precision is the number of significant bits kept in each RGB channel. At 6, every channel is quantised to 6 bits before the tracer groups pixels into regions. Lower values merge more shades into one region, so you get fewer, larger, flatter shapes.
• Path precision is the number of decimal places written into each path's coordinate string. Lower values round coordinates harder, which shortens the XML but can visibly nudge edges on small shapes.

Raising the slider never adds detail the trace did not find. On a photograph it mostly multiplies the number of shapes, which inflates the file without making it look like the photo.

Which Sources Trace Well

Common Errors and How to Fix Them

• "The run stopped and no SVG came back" — Check Number precision first: positions 9 and 10 stop the trace outright, because the same value is sent as both the path precision and the colour precision and colour precision only accepts 1 to 8. Drop it to 8 or below. Failing that, render the RAW yourself with DNG to PNG and trace the PNG — a plain lossless raster is the most predictable input a tracer can be given.
• "The SVG looks posterized and nothing like my photo" — You traced continuous-tone content. Flattening gradients into solid shapes is what tracing does; it is not a settings problem. Use a raster target instead.
• "The SVG is far bigger than the original DNG" — A busy image forces one path per colour region, and thousands of paths cost more bytes than a compressed raster. Lower Number precision, simplify the source, or accept that this image is not a vectorisation candidate.
• "Thin lines and small details vanished" — Small features fall below the tracer's speckle threshold and are discarded. Start from a higher-contrast, sharper source so thin strokes survive.
• "My editor opens the SVG but the photo is not editable" — Correct. The SVG contains freshly generated paths, not your photograph. There is no route back to the original pixels from it.

When This Doesn't Work

Vectorisation is the wrong tool for almost every DNG, because almost every DNG is a real photograph. It earns its place only when the RAW frame happens to hold a simple, high-contrast graphic — a logo shot off a wall, a stencil, a scanned diagram. For everything else the question is not which precision to pick but which raster format to use: PNG for lossless quality, JPG for a small shareable photo, TIFF for editing at full bit depth. And if you have already made the SVG and it looks wrong, no slider position will rescue it — go back to the source and pick a raster target.

Frequently Asked Questions

Does this embed my DNG inside an SVG, or actually vectorize it?

It vectorizes. The tracer detects colour regions and rebuilds them as real SVG paths and curves — it does not base64-encode the photo into an <image> element. That is why the output is genuinely resolution-independent for suitable artwork, and equally why a photograph comes back reinterpreted as flat shapes rather than preserved pixel-for-pixel.

Why does a PNG trace better than the RAW it came from?

Because tracing engines work on decoded pixels, and a DNG is not decoded pixels — it is a TIFF-structured container of unprocessed sensor data that still needs demosaicing, white balance and a tone curve before it is a viewable image at all. Somebody has to make those calls. Rendering the file yourself with DNG to PNG means you make them, and you get to check the result: a correctly exposed frame keeps its shadow tones separated instead of clipping them into one flat black region, and a sensibly downscaled frame gives the tracer real edges instead of sensor grain. A RAW developed on defaults gets none of that attention, and the difference lands straight in the path count.

What value should I set Number precision to?

For flat artwork, 4 to 6 covers nearly every case — crisp paths at a sensible file size. Drop to 1–3 when the image is genuinely two-tone and you want the smallest possible output. Go above 7 only when near-identical shades must stay separate, and expect the file to grow quickly, because the value raises colour precision and path precision together.

Will tracing preserve my camera's EXIF, lens or white balance data?

No. SVG has no equivalent of a RAW metadata block, and tracing discards everything that is not shape and fill. Capture date, camera model, lens, ISO, shutter speed and the RAW white-balance values are all gone from the output. Keep the original .dng, or convert to TIFF if you need an image file that still carries capture metadata.

Can I get my photo back from the SVG afterwards?

Not meaningfully. The SVG holds generated paths that approximate what the tracer saw, so rendering it back to a raster gives you the posterised approximation, not the original frame. Tracing is a one-way transformation. Always keep the DNG.

Do browsers and design apps open the resulting SVG?

Yes. SVG is a W3C standard written in XML, rendered natively by Chrome, Firefox, Safari and Edge, and imported by Illustrator, Inkscape, Figma, Affinity Designer and most other vector editors. A traced logo will open identically in a browser and in a vector editor; a traced photograph will open just as reliably and simply look wrong in both.

Why is my traced file slow to open in an editor?

Because path count, not file size, is what makes a vector editor struggle. A photographic trace can emit tens of thousands of individual paths, and editors have to build an object for each one. Lowering Number precision merges colour regions and cuts the path count directly, which helps far more than any other change you can make on this page.

Is my file kept private during conversion?

Your DNG is uploaded over an encrypted connection, traced on our servers, and deleted automatically after a few hours. There is no sign-up, no watermark, and nothing is ever shared or made public.