Initializing... drag & drop files here
Supports: NEF
This tool turns a Nikon NEF raw photo into a true SVG — it renders the raw sensor data into a viewable image, then traces that image into real vector paths and Bézier curves. It does not base64-encode your photo inside an <image> wrapper; it genuinely vectorizes. The catch worth knowing up front: tracing a photograph produces a posterized, stylized illustration — flat color regions with the fine detail collapsed away — not a scalable copy of your photo. That is exactly what you want for poster art, stencils, or laser-cutting from a shot, and exactly what you don't want if you need the picture to stay a picture. For that, use NEF to JPG or NEF to TIFF instead.
.nef onto the page, or click "+ Add Files" to browse. You can queue several Nikon raw files and trace them with the same setting.| Property | NEF (input) | SVG (output) |
|---|---|---|
| Type | Nikon raw still — TIFF-based container, one photo per file | XML-based vector graphic, W3C-developed since 1999 (per MDN) |
| Color data | 12-bit or 14-bit sensor data (per Nikon) | 8-bit sRGB, quantized into a handful of flat color regions |
| Photographic detail | Full sensor resolution, continuous tone | Posterized — gradients band, fine texture flattens |
| Scalability | Fixed pixel grid | Resolution-independent for the shapes the trace found |
| Editing latitude | White balance, tone, Picture Control kept as instruction sets | Baked in before tracing — gone in the output |
| Best use | The editable master of a shot | Logo-izing a photo, poster art, stencils, laser/CNC input |
It traces. After rendering the raw file to RGB, the converter runs an open-source vector tracer that groups neighbouring pixels into solid 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 detail is lost during tracing, before any scaling happens. A NEF holds millions of subtly different pixels, and the tracer must quantize them into a small set 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 with NEF to JPG.
For most images, 4–6 is the sweet spot — reasonably crisp paths at a sensible file size — and matches the converter's on-screen guidance. 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. In our testing, a NEF of a high-contrast sign traced at precision 5 produced a clean, compact SVG, while a NEF portrait at the same setting came out visibly posterized — a good illustration of which sources suit this tool.
No. A NEF stores roughly 12-bit or 14-bit raw sensor data with white balance, tone and Picture Control held as editable instruction sets rather than baked into the pixels, as Nikon describes. The conversion develops that raw 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 .nef if you may want to re-develop the exposure later, and treat the SVG as a stylized derivative.
Your NEF 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.