Skip to content

SVG to NEF Converter

Convert SVG to NEF in your browser. You download a Linear DNG (.dng), not a .nef: only a Nikon camera can create a genuine NEF, and every editor that opens NEF also opens DNG. Nothing is uploaded.

  • Processed locally
  • No upload, no wait
  • No sign-up
  • No watermark

Drop images here

or choose files · paste with Ctrl/⌘ V

SVG expected · other image formats also work

Files are processed on this device. Nothing is uploaded.0 B uploaded

How to use SVG to NEF

  1. 1

    Add your SVG files: drop them here, choose them, or paste from the clipboard.

  2. 2

    Pick the colour that replaces transparent areas, since DNG has none.

  3. 3

    Click Convert. Each file is decoded and encoded in a background thread on this device.

  4. 4

    Download the .dng files one at a time or together as a ZIP.

Why use Aback Images for svg to nef

Where a NEF would go

NEF files are opened by Nikon NX Studio, Lightroom, Photoshop Camera Raw, Capture One and RawTherapee, and every one of them opens the DNG too.

DNG next to SVG

Rasterising turns a description of shapes into stored pixels, so the DNG is usually larger than a small SVG, and grows with the size you render at.

Written without a lossy pass

The DNG is written uncompressed, so the pixels decoded from the SVG arrive unchanged.

Processed on your device

Your images are decoded, edited and encoded inside this browser tab by Web Workers. Nothing is uploaded to a server.

SVG vs NEF

What changes from SVG to NEF

Encoding: the SVG uses XML text describing paths, shapes and text, sometimes gzipped as .svgz; NEF uses uncompressed, lossless compressed, lossy compressed, or High Efficiency on recent Z bodies, and the download is a Linear DNG: demosaiced 8-bit RGB with the colour matrices raw editors need.

Bit depth: not fixed: coordinates and colours are continuous values in the SVG; NEF allows 12 or 14 bits per channel, and the DNG written here has 8 bits per channel, linearised.

Colour: sRGB by default, other spaces through CSS colour functions in the SVG; NEF supports camera RGB from a Bayer mosaic, written here as 8-bit sRGB.

Transparency: the SVG stores it as opacity on any element, with anti-aliased edges; the DNG has none, so transparent areas are filled with the colour you choose.

Animation: SMIL or CSS animation described in the markup; a single still rendering is converted.

Metadata: the SVG can carry title, description and RDF metadata elements; NEF can carry EXIF and Nikon maker notes, partly encrypted, plus a thumbnail and a larger preview, but nothing is copied across.

About SVG

SVG describes shapes, paths and text as XML instead of pixels, so it stays crisp at any size. It is the standard for logos, icons and illustrations on the web.

An SVG is an XML document: a root <svg> element with a viewBox, then paths, shapes, text, gradients and filters. It can also embed raster images and, dangerously, scripts, which is why untrusted SVG is sanitized before rendering here.

SVG files usually come from icon sets, logos, design tools (Figma, Illustrator, Inkscape) and diagram exports.

About NEF

NEF is the raw format of Nikon cameras, from the D1 to the current Z series. It stores 12 or 14-bit sensor data, uncompressed or compressed, with a JPEG preview the camera renders using its Picture Control.

NEF is TIFF-based: the first directory usually holds a small thumbnail, and sub-directories hold the sensor data and, on current bodies, a full-size JPEG preview. Nikon's maker notes are a TIFF structure of their own, and since the D2X their white-balance block is encrypted with a key derived from the camera's serial number and shutter count.

NEF files come from Nikon DSLRs (D-series) and Z-series mirrorless cameras.

When converting SVG to NEF makes sense

Forms and workflows that ask for NEF usually feed a raw editor, and each of those opens DNG as well, so the DNG can take the NEF's place. Keep the SVG if you only need to view or share the picture.

What NEF offers when it comes straight from the camera: Lossless compressed mode with no data loss; Picture Control recorded so Nikon NX Studio can reapply it; 12 or 14-bit sensor data. Its drawbacks: Partly encrypted maker notes; The lossy compressed mode discards some sensor data; Large files on high-resolution Z bodies.

Limitations

  • Rasterising fixes the picture at one pixel size; set a larger size under More options if you need to print or zoom.
  • Text that was not converted to outlines is drawn with the fonts on this device, so lettering can look different from the designer's screen.
  • The DNG holds the decoded 8-bit pixels, so it adds no dynamic range or detail beyond the SVG.

Frequently asked questions

Why do I get a .dng file instead of a .nef?

A real NEF is written by Nikon cameras and holds the sensor's own readings (12 or 14 bits per channel, stored as uncompressed, lossless compressed, lossy compressed, or High Efficiency on recent Z bodies) along with EXIF and Nikon maker notes, partly encrypted, plus a thumbnail and a larger preview. An SVG holds no sensor data, so no software outside the camera can create a genuine NEF. The Linear DNG you get instead is Adobe's open raw format, and every editor that opens NEF files opens it with the same raw controls. It holds decoded pixels, so it adds no quality or dynamic range.

Does converting SVG to NEF lose quality?

DNG is written uncompressed, so the pixels are stored exactly as decoded.

What happens to transparency when converting SVG to NEF?

SVG stores transparency as opacity on any element, with anti-aliased edges. DNG has no alpha channel, so transparent pixels are composited onto a solid colour, white unless you pick another. To keep transparency, convert to PNG, WebP or AVIF instead.

What resolution will the output be?

SVG has no fixed pixel size, so it is rendered at its declared width and height. Use the resize options to render it larger: because it is vector, an SVG stays perfectly sharp at any size you choose here. Files are sanitized first, so scripts and external references never run.

Are my images uploaded anywhere?

No. Processing happens inside your browser with WebAssembly and Web Workers. The site only downloads the app code and codecs; your files never leave your device. You can confirm this with the live upload counter on the tool, or in your browser's network panel.

Can I process many files at once?

Yes. Drop a whole selection or folder. Files are processed in parallel on several worker threads, each result can be downloaded on its own, and everything can be saved as one ZIP.

Is it free? Is there a file limit or watermark?

It is free with no account, no watermark and no daily limit. The only limit is your device's memory: very large images (over roughly 100 megapixels) may be refused to keep the tab from crashing.