RAW to SVG Converter
Convert RAW to SVG in your browser. The camera's embedded JPEG preview is what gets converted, not the sensor data; it matches what the camera showed on its screen. No raw development happens here. You get an SVG traced into vector paths (or, if you prefer, the pixels embedded in an SVG wrapper). Nothing is uploaded.
- Processed locally
- No upload, no wait
- No sign-up
- No watermark
Drop images here
or choose files · paste with Ctrl/⌘ V
RAW expected · other image formats also work
How to use RAW to SVG
- 1
Add your RAW files: drop them here, choose them, or paste from the clipboard.
- 2
Choose how many colours to trace; fewer colours give simpler paths.
- 3
Click Convert. Each file is decoded and encoded in a background thread on this device.
- 4
Download the .svg files one at a time or together as a ZIP.
Why use Aback Images for raw to svg
Where the SVG goes next
SVG opens in every browser, Illustrator, Inkscape, Figma and most design tools.
SVG next to RAW
The SVG is made from the camera's 8-bit preview, so it is a small fraction of a 20 to 80 MB raw file.
A second JPEG generation
The pixels come from the JPEG preview the camera embedded in the RAW, so they have been compressed once already; keep the quality at or above the default.
Processed on your device
Your images are decoded, edited and encoded inside this browser tab by Web Workers. Nothing is uploaded to a server.
RAW vs SVG
What changes from RAW to SVG
Encoding: the RAW uses uncompressed, lossless JPEG or vendor-specific coding of the sensor data, depending on the maker; SVG uses XML text describing paths, shapes and text, sometimes gzipped as .svgz, and the download is an SVG traced into vector paths (or, if you prefer, the pixels embedded in an SVG wrapper).
Bit depth: 12 to 16 bits per channel in the RAW; SVG allows not fixed: coordinates and colours are continuous values, and the SVG written here has vector paths with flat colours. The sensor's 12 to 16 bits are not used: the camera's 8-bit preview is converted.
Colour: camera-native RGB from a colour filter mosaic in the RAW; SVG supports sRGB by default, other spaces through CSS colour functions, written here as flat colour regions.
Metadata: the RAW can carry EXIF and vendor maker notes, almost always with an embedded JPEG preview; SVG can carry title, description and RDF metadata elements, but nothing is copied across.
About RAW
Camera RAW files (CR2, CR3, NEF, ARW, DNG, ORF, RW2, RAF and others) hold the unprocessed sensor data from a camera along with an embedded full-size JPEG preview rendered by the camera.
.RAW is an extension rather than one format. Panasonic and Leica compacts wrote TIFF-like .RAW files before Panasonic moved to RW2, and scanners and scientific cameras use .raw for headerless dumps with no width, height or layout recorded, which nothing can read without being told those values.
RAW files usually come from older Panasonic and Leica compacts that saved .RAW, and scanners or scientific cameras that use the extension for pixel dumps.
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.
When converting RAW to SVG makes sense
SVG is the better choice for logos, icons and illustrations, while RAW suits editing in Lightroom, Capture One or darktable.
SVG strengths: Infinitely scalable and sharp; Tiny files for logos and icons; Editable as text and styleable with CSS. Drawbacks to weigh: Not suitable for photographs; Can contain scripts, so untrusted SVG must be sanitized; Many apps and social sites will not accept it.
Limitations
- A headerless .raw pixel dump has no preview and no size information, so it cannot be converted here.
- Tracing approximates the image with flat-colour shapes, so photographs become poster-like art rather than exact copies.
- Logos, icons and line art with clear edges trace best; raise the colour count for more detail.
More conversions
Related tools
Convert SVG to RAW in your browser, saved as a Linear DNG, the raw file every RAW editor also opens. Batch, private, no uploads.
Convert RAW to JPG in your browser, made from the full-size preview your camera camera stored in the file. Batch, private, no uploads.
Convert any image (HEIC, PNG, WebP, AVIF, RAW, PSD, SVG and 26 more) to SVG in bulk, right in your browser.
Convert JPG to SVG in your browser, traced into real vector paths. Batch, private, no uploads.
Shrink JPG, PNG, WebP, AVIF and GIF files with MozJPEG, OxiPNG and modern codecs, with a live before/after preview.
Resize to exact pixels, a percentage or a longest side, with Lanczos3 and Magic Kernel resampling. Batch ready.
Strip EXIF, GPS, XMP, IPTC and comments losslessly. Pixels are never re-encoded for JPG, PNG and WebP.
Convert between 34 image formats in bulk: HEIC, WebP, AVIF, JPEG XL, PNG, JPG, GIF, TIFF, SVG, ICO, PSD, RAW and more.
Frequently asked questions
Does converting RAW to SVG lose quality?
SVG is lossy, so detail the eye barely notices is discarded to save space. The RAW's preview is a camera JPEG already, so keep the quality high to avoid stacking artefacts. The sensor's 12 to 16 bits are not used: the camera's 8-bit preview is converted.
Does this process the RAW sensor data?
No. Camera RAW files carry a JPEG rendered by the camera when the picture was taken, and that is what gets converted, so the result matches what you saw on the camera screen. For full development (white balance, highlight recovery, lens corrections) use a RAW editor.
Is the SVG a real vector or just embedded pixels?
By default the image is traced into true vector paths, so it scales without pixelation and can be edited in Illustrator, Figma or Inkscape. You can switch to embedding the pixels inside an SVG wrapper if you need an exact copy.
Which apps open SVG files?
Every browser, Illustrator, Inkscape, Figma and most design tools.
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.