3FR to SVG Converter

Tracing a Hasselblad 3FR to SVG: What This Tutorial Covers

A .3fr is Hasselblad's 3F RAW — undeveloped medium-format sensor data — and SVG is an XML vector language standardised by the W3C, where a picture is described as shapes and paths rather than pixels. There is no way to "convert" one into the other losslessly. Getting from a RAW to an SVG always means two things happening in order: the sensor data is rendered into ordinary pixels, and those pixels are then traced into flat colour regions written out as vector paths. The trace can only ever be as good as the render it is given, which is why the source matters far more than any setting on this page. This tutorial covers when that produces something usable, how to set the one control that matters, and what to expect if you feed it an ordinary photograph.

How to Convert 3FR to SVG

1. Upload Your 3FR File: Drag and drop the .3fr onto the page or click "+ Add Files" to browse. Several captures can be queued and traced with the same setting.
2. Set the Number Precision: Open Advanced Options and move the "Number precision" slider, which runs from 1 to 10 and starts at 6. Positions 9 and 10 abort the conversion and return no file, because the slider sends the same value as the colour precision, which is only defined for 1 to 8. Lower values simplify the trace into fewer, smoother paths and a smaller file; higher values chase finer detail at the cost of size.
3. Match the Setting to the Subject: Flat art, logos, and packshots on plain backgrounds want a low-to-middle precision; a busy photographic frame needs the slider pulled down or the SVG will balloon.
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: Choosing the Number Precision

The slider is the whole tuning surface here, and the page's own guidance — "a number between 4 and 6 is recommended for most use cases" — is a reasonable default rather than a rule. What it controls is how faithfully each traced path follows the rendered pixels:

• Precision 1–3 — poster mode. Big, smooth shapes, very few nodes, tiny file. Use it for logos, silhouettes, and anything you intend to recolour by hand afterwards. Fine texture disappears entirely.
• Precision 4–6 — the recommended band, and where the default sits. Shapes stay recognisable, edges stay reasonably crisp, and the file size stays manageable for a medium-format source.
• Precision 7–8 — detail chasing. Every subtle tonal step gets its own path. On a 100 MP Hasselblad frame this is how you end up with an SVG that is slower to open than the RAW was, for a picture that still is not photorealistic.
• Precision 9–10 — not usable. The same slider value is sent as the colour precision as well as the path precision, and colour precision is only defined for 1 to 8 bits per channel. The top two positions stop the run with an out-of-range error rather than producing a finer trace, so treat 8 as the real maximum.
• If in doubt, trace twice. Run the file once at 3 and once at 6 and compare. Tracing is cheap; guessing which precision suits a given subject from the thumbnail alone is not.

What Traces Well, and What Doesn't

Common Errors and How to Fix Them

• "The SVG is enormous — bigger than the photo." You traced a continuous-tone image at high precision. Every gradient step becomes its own path. Drop "Number precision" toward 3–4, or accept that this subject wants a raster format.
• "It opens slowly, or my editor stalls." Same cause: path count. A vector file with hundreds of thousands of nodes is heavy for any renderer, including browsers. Re-trace lower.
• "The colours are banded and posterised." That is what tracing does — continuous tone is quantised into flat fills. There is no setting that makes a traced photograph look photographic; that is a property of vector graphics, not a bug in the converter.
• "Fine detail vanished." Precision is too low for the subject, or the detail was below the trace threshold to begin with. Raise the slider a step or two, and expect diminishing returns.
• "My 3FR will not load." It may come from a body newer than the RAW decoder recognises, or the copy may be truncated. Re-save it to DNG or TIFF in Hasselblad Phocus and convert that interim file, or re-copy the original from the card.

When This Doesn't Work

Vectorising a photograph is a stylistic choice, not a quality upgrade — if you reached this page expecting the SVG to look like the original Hasselblad frame, it will not. The honest use cases are narrow: artwork, logos, and graphic elements that happened to be captured on a Hasselblad, or a deliberately poster-like treatment. For everything else, render the RAW to a raster format and stop there: 3FR to JPG for delivery, 3FR to PNG for a lossless proof, 3FR to TIFF for print. And if you genuinely need hand-drawn vector artwork traced from a photograph, an automatic tracer only gets you the first 60% — the rest is node editing in Illustrator, Inkscape, or Affinity Designer.

3FR and SVG at a Glance

Frequently Asked Questions

Will my Hasselblad photo really become a true vector, or just a picture in a wrapper?

A true vector. The output is XML containing real path geometry you can select, rescale, and reshape in a vector editor — not a raster image embedded in an SVG shell. What "true vector" does not mean is "identical to the photo": the tracer approximates the rendered image with flat colour regions, so a photographic 3FR comes out as a stylised illustration. Graphic and high-contrast subjects survive that translation far better than portraits or landscapes.

Why is my SVG larger than the JPG it was traced from?

Because the two formats store completely different things. A JPG stores one compressed pixel grid; a traced SVG stores the coordinates of every path the tracer needed to approximate that grid, as text. Photographs contain millions of subtle tonal transitions, and a medium-format Hasselblad frame — up to 11656 × 8742 pixels on a 100 MP back — gives the tracer an enormous amount of material to describe. Lower the "Number precision" slider to merge detail into fewer paths, or use a raster target.

What exactly does the Number precision slider change?

How closely each generated path is allowed to follow the source. At low precision the tracer smooths aggressively, producing fewer nodes, softer curves, and a much smaller file; at high precision it preserves finer inflections and adds nodes, which grows both file size and rendering cost. The slider runs 1–10, starts at 6, and the tool's own note recommends staying between 4 and 6 for most images.

Can I scale the traced SVG to poster or billboard size?

Yes — that is the one thing a traced SVG does better than any render of the RAW. Because the paths are mathematical, they stay crisp at any output size, so a logo or graphic traced from a 3FR can be blown up to vehicle-wrap scale with no pixelation. The caveat is that scaling does not add detail the trace never captured; enlarging a posterised photograph simply gives you larger flat regions.

Does the SVG keep the RAW's 16-bit colour or the EXIF data?

No to both. Tracing collapses the rendered image into flat fills expressed as ordinary colour values, so the wide tonal range a 14-bit or 16-bit Hasselblad capture records is spent at the render stage and cannot survive as vector fills. SVG also carries no EXIF block, so camera, lens, exposure, and GPS data do not travel with the file. If the metadata matters, render to 3FR to TIFF and keep the original .3fr.

Should I trace the 3FR directly, or render it to PNG first and trace that?

Render to PNG first if you care how the result looks. A RAW has to be developed into ordinary pixels before anything can trace it, so the only real question is whether you make the exposure, colour and sizing decisions or a default profile makes them for you. Going through 3FR to PNG is what lets you intervene between the two stages: crop to the graphic, boost contrast, knock the background out, and downscale a 100-megapixel frame so the tracer follows the subject rather than the grain. Tracers key off edges and colour separation, so a manually contrast-boosted PNG traces markedly cleaner than an untouched capture developed on defaults.

What software opens an SVG once it is converted?

Every current desktop browser renders SVG directly — Chrome, Firefox, Safari, and Edge — as does any modern vector editor: Adobe Illustrator, Inkscape, Affinity Designer, Figma, and Sketch. Because the file is plain XML text, you can also open it in a code editor to hand-edit fills, strip paths, or minify it. That universality is the practical reason to trace at all: a .3fr opens in roughly four programs, an .svg opens in hundreds.

How are my files handled, and how large a 3FR can I send?

Your capture is uploaded over an encrypted connection, rendered and traced on our servers, then deleted automatically after a few hours — no sign-up, no watermark, never shared or made public. We keep the precision default in the recommended 4–6 band rather than pushing it higher, because a maxed-out trace of a medium-format frame produces a file most editors struggle to open. The real-world constraint is upload time: Hasselblad puts an average 100 MP 3FR at 206 MB, so sending the file takes longer than tracing it.