NEF to SVG Converter

Convert NEF to SVG: Read This First

Two things make this conversion different from every other target on the site, and you should know both before you upload anything.

First, the quality of the trace is decided by the raster you hand it. SVG output is produced by an open-source raster-to-vector tracer that works on decoded pixels — it clusters neighbouring pixels into flat colour regions and fits curves around them. A Nikon raw is not decoded pixels: it is a single-channel Bayer mosaic that has to be demosaiced, white-balanced and tone-mapped before there are any colour boundaries to find. Something has to make those development decisions, and if you do not make them, they get made for you on defaults. Rendering the .nef to PNG yourself first and tracing that PNG puts the exposure, colour and size back under your control, and that is the single biggest lever on how the trace comes out. The steps below walk through it.

Second, tracing a photograph does not give you a scalable copy of the photograph. A tracer groups neighbouring pixels into flat colour regions and rebuilds them as Bézier paths. On a logo or line art that is close to lossless. On a 24-megapixel Nikon frame it is a posterisation: gradients band, texture disappears, and the result is poster art rather than a picture. That is genuinely useful for stencils, screen printing, laser and CNC work — and useless if you wanted the photo to stay a photo.

How to Convert NEF to SVG

1. Render the NEF to PNG First: Run your Nikon raw file through NEF to PNG and download the result. Set that converter's Quality Preset to "Highest" so you hand the tracer a true-colour image instead of a 256-colour one. This is the step that decides what the tracer has to work with: a correctly exposed, low-noise PNG at a sensible size traces far better than a raw developed on defaults.
2. Upload the PNG to the SVG Tracer: Open PNG to SVG and drop the rendered file in. It accepts .png and .apng and writes plain SVG markup — real <path> elements, not a base64 photo wrapped in an <image> tag.
3. Set Number Precision Between 1 and 8: The slider runs to 10, but the tracer rejects values above 8 for colour precision and the job fails. Stay inside 1-8; the on-screen note recommends 4-6, which is where most images land.
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.

Number Precision Is Two Settings on One Slider

The single "Number precision" control is passed to the tracer twice — once as the colour precision (how many significant bits per RGB channel the clustering keeps) and once as the path precision (how many decimal places each coordinate carries). That is why it behaves less like a smooth quality dial and more like a threshold.

In our checks the jump between neighbouring values is not gentle: below the point where the clustering finds real edges the trace can reduce to a single flat shape, and a notch or two higher it can leap to thousands of paths and a multi-megabyte file. Start at 5, look at the result, and move one step at a time.

NEF vs SVG at a Glance

Frequently Asked Questions

Why render the NEF to PNG instead of sending the raw straight in?

Because a raw file is not an image yet, and the tracer's whole job is finding boundaries between regions of similar colour. A .nef holds a 12-bit or 14-bit Bayer mosaic — one filtered value per photosite, not red, green and blue per pixel — so it has to be demosaiced, white-balanced and tone-curved before there are any colours to cluster. Whoever performs that development chooses the exposure, the white balance and the noise handling, and defaults are rarely the choices you would make for a trace. Rendering it yourself with NEF to PNG at the "Highest" preset lets you look at the render before you commit to tracing it. Renaming the file is not a substitute: the bytes stay a sensor mosaic whatever extension you give them.

Does this embed my photo inside an SVG or actually vectorise it?

It genuinely vectorises. The tracer clusters neighbouring pixels into solid colour regions and writes them out as real SVG <path> elements with Bézier curve data — there is no base64-encoded raster hidden in an <image> tag. That also means there is no way to get the original photograph back out of the file: what the trace discarded is gone.

Will the SVG look like my Nikon photo?

Only in the way a screen-printed poster looks like the photo it was made from. Every subtle tonal transition in a raw file has to be quantised into a handful of flat fills, so skies band, skin goes blotchy and fine texture vanishes. Images with large areas of solid colour and hard edges — signage, silhouettes, high-contrast product shots on plain backgrounds — trace well. Portraits, foliage and anything with fine detail do not. If you want the picture to stay a picture, use NEF to JPG instead.

What Number precision value should I use?

Start at 5. The on-screen note recommends 4-6, and that range is where most images produce a recognisable result at a sensible file size. Push toward 7-8 only when you need finer edge fidelity and can accept a file with thousands of paths. Drop toward 1-3 only when you deliberately want a heavily simplified, few-colour poster look — and check the output, because a busy photo can flatten almost entirely at those settings.

Why do the 9 and 10 positions on the precision slider fail?

Because the slider's range is wider than the tracer's. The value is used as the colour precision, which the tracer restricts to 1-8 significant bits per RGB channel; asking for 9 or 10 makes it reject the value outright and the job errors instead of producing a file. This is a known mismatch between the control's range and the encoder's — until it is fixed, treat 8 as the ceiling.

Can I get transparency, layers or editable text out of the trace?

Transparency, no — a photograph is fully opaque, so there is nothing to carry into the output. Layers, sort of: the tracer stacks its colour regions as separate paths, so a vector editor will let you select and recolour individual shapes, which is exactly why people trace images for cutting and printing. Editable text, no — lettering in a photograph becomes outlined shapes, not text elements. If you need real text you have to retype it in a vector editor.

Does the SVG keep my NEF's colour depth, white balance or EXIF data?

None of it. Nikon stores 12-bit or 14-bit sensor data with white balance and tone as instruction sets rather than baked pixels; developing the raw fixes those choices, the trace then reduces the render to a small set of 8-bit sRGB fills, and the output is plain SVG markup with no metadata block. Keep the original .nef if you may want to re-develop the exposure, and treat the SVG as a stylised derivative.

Is SVG the right target at all, or do I want something else?

Ask what the file is for. For cutting, engraving, screen printing or a deliberately poster-like graphic, SVG is right and the posterisation is the point. For viewing, sharing or printing the photograph, it is the wrong format entirely — use NEF to PNG for a lossless render or NEF to JPG for something small enough to email. For an editing or print master, NEF to TIF with LZW compression is the usual choice.

How are my files handled during conversion?

Whatever you upload travels over an encrypted connection, is processed on our servers, and is deleted automatically after a few hours. Nothing is shared or made public, and there is no sign-up or watermark. Rendering and tracing are two separate conversions, so the intermediate PNG and the traced SVG each follow the same retention rule.