Initializing... drag & drop files here
Supports: 3FR
A .3fr is Hasselblad's camera raw: a 16-bit medium-format negative meant to be developed in Phocus, Lightroom, or Capture One. AVIF is the opposite end of the pipeline — AV1-coded image data in a HEIF container, built to deliver a finished photograph to a browser in as few bytes as possible. The short answer for most people: keep every 3FR as the master and convert a copy to AVIF when the destination is a web page, a portfolio, or anywhere page weight matters. Convert to AVIF only after the look is locked, because the render is one-way.
| Property | 3FR (Hasselblad raw) | AVIF |
|---|---|---|
| What it is | Unrendered sensor data | A finished, encoded image |
| Standard | Hasselblad's own raw layout, built on TIFF | AV1 image coding in a HEIF container |
| Bit depth | 16 bits per channel | 8, 10, or 12 bits per channel |
| Colour | Natural Color Solution profile matched to the camera | sRGB through wide gamut and HDR (PQ/HLG Rec. 2020, P3) |
| Transparency | Not applicable | Full alpha channel |
| Compression | Lossless, but raw — huge | Lossy or lossless; lossy AVIF runs about 50% smaller than JPEG at similar quality |
| Typical size, one 100 MP capture | Frequently past 150 MB | Comfortably under a megabyte at web display sizes |
| Editing latitude | Full — white balance, exposure, highlight recovery still adjustable | None; tone and white balance are baked in |
| Progressive loading | Not applicable | Not supported — an AVIF must download fully before it draws |
| Opens in | Phocus, Lightroom, Camera Raw, Capture One | Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+ (about 95% of browsers) |
| Best for | Editing, grading, archival masters | Web delivery, portfolios, anything measured in page weight |
| Target | Size vs. JPEG at matched quality | Bit depth | Transparency | Reach |
|---|---|---|---|---|
| AVIF | About 50% smaller | 8/10/12-bit | Yes | ~95% of browsers; no progressive rendering |
| WebP | About 30% smaller | 8-bit | Yes | ~96% of browsers |
| JPG | Baseline | 8-bit | No | Everything, everywhere, including old software |
| PNG | Larger than JPEG for photographs | 8 or 16-bit | Yes | Universal; lossless render |
| TIFF | Far larger | 16-bit | Yes | Desktop and print tools, not browsers |
For web delivery, yes, and the gap widens on exactly the images a Hasselblad produces. MDN puts lossy AVIF at around 50% smaller than JPEG for visually similar quality, and AVIF holds smooth gradients — skies, studio sweeps, defocused backgrounds — without the blocking and banding JPEG shows at the same weight. AVIF also carries 10- and 12-bit colour, HDR and alpha, none of which baseline JPEG can hold. JPEG's one remaining advantage is that literally everything opens it.
Completely, and that is inherent to any render rather than a limitation of this tool. A .3fr holds 16-bit sensor data with white balance, exposure and tone still open; producing an AVIF means demosaicing that data, baking in the current interpretation, and encoding the result with AV1. Afterwards you are editing a finished photograph, exactly as you would be with a JPEG. Keep the 3FR and convert a copy.
It can, but it usually should not. Leave Image resolution on "Keep original" and every pixel of a 39-to-100+ megapixel frame goes into the file, which defeats the point of choosing an efficient format. Web layouts rarely need more than a couple of thousand pixels on the long edge, so downscaling is where most of the size win actually comes from — the codec choice is the second-largest lever, not the first. For full detail, keep the raw or a TIFF.
Switch Image Compression from "Quality Preset" to "Specific file size" and enter the ceiling — the unit dropdown takes bytes, kilobytes or megabytes — and the encoder aims at that target instead of a fixed quality level. This is the right control when a CMS, a client brief, or an email cap gives you a hard number. When there is no hard number, leave it on "Very High (Recommended)" and set the size with resolution instead; quality-targeted encoding gives more predictable results across a batch of different photographs.
Because AVIF does not support progressive rendering: unlike a progressive JPEG, which paints a rough version early and refines it, an AVIF has to finish downloading before it draws anything. On a fast connection this is invisible; on a slow one a large AVIF can feel later than a JPEG of the same weight even though it transfers less data. The fix is size, not format — downscale the image and the problem disappears.
The format can; this conversion does not aim for it. AVIF supports 10- and 12-bit coding, HDR transfer functions such as PQ and HLG, and wide-gamut spaces including Rec. 2020 and Display P3 — that capability is a real advantage over JPEG. What arrives here, though, is a raw file rendered with our defaults, so expect an ordinary standard-dynamic-range image rather than an HDR master. If HDR delivery is the goal, grade the shot in Phocus or Lightroom, export an HDR-tagged file, and encode from that.
Not necessarily. A 3FR carries a Hasselblad Natural Color Solution profile tied to the individual camera, and Phocus applies it as part of its own render. This converter develops the raw with its own defaults, so colours can drift — usually slightly, sometimes visibly under mixed lighting. AVIF is capable of carrying an ICC profile and wide-gamut data, but that does not undo a different render. For colour-critical work, finish the file in Phocus, export it, and convert the export.
Some older content management systems, email clients and design tools still refuse the format. When that happens, 3FR to JPG is the safe universal answer, and 3FR to WebP is the middle ground — about 30% smaller than JPEG with near-universal browser support. If you already have the AVIF and just need a compatible copy, AVIF to JPG re-encodes it without going back to the raw.