Initializing... drag & drop files here
Supports: 3FR
A .3fr file is a Hasselblad medium-format raw still, and AV1 is a video codec — so this is a still-to-video job, not a photo-to-photo one. The result is a short, silent AV1 clip that holds your rendered frame on screen for a length you choose, wrapped in a Matroska container that carries a .av1 name. This walk-through covers the three settings that decide what you get, the playback quirk that catches everyone out, and when you should be converting to a still format instead.
.3fr onto the page or click "Add Files". You can queue several Hasselblad frames and convert them under one set of settings..av1 File Actually Contains| Property | Value |
|---|---|
| Video codec | AV1, the royalty-free codec from the Alliance for Open Media |
| Container | Matroska |
| Extension written | .av1 — not a standard container name |
| Audio | None; a single photo has no audio track to carry |
| Length | Duration per frame (5 seconds by default) × number of images |
| Motion | None — one rendered still held on screen |
| Colour | Standard 8-bit video colour, rendered down from the raw's 16-bit data |
| Reliable players | VLC (AV1 decoding arrived in the 3.0.4 update), mpv, ffplay |
| Quickest compatibility fix | Rename to .mkv — same bytes — or re-encode to MP4 or WebM |
The surprise in this conversion is the file name, not the codec. The bytes we write are ordinary Matroska carrying an AV1 video track, but the .av1 extension is not a container name anyone standardised — AV1 is normally delivered inside MP4, WebM, or MKV, and most players and browsers decide what to do from the extension before they ever look inside the file.
.mkv — the bytes do not change — or convert it with AV1 to MP4 or AV1 to WebM, both of which re-encode rather than repackage..av1 extension is being rejected before the container is read. Rename it to .mkv and try again.| What you actually want | Best target | Why |
|---|---|---|
| A picture to keep editing or print | 3FR to TIFF | Holds detail and high bit depth for print work |
| A picture to email or post | 3FR to JPG | Opens literally everywhere |
| A small, sharp web still | 3FR to AVIF | AV1's still-image sibling; far smaller than JPEG at matched quality |
| The frame as an element in a video timeline | 3FR to AV1 (this page) | Royalty-free codec, efficient on held frames |
| A clip that plays on phones, TVs and browsers | 3FR to MP4 | H.264 in MP4 is the one video combination nothing rejects |
If all you ever wanted was a picture — to edit, print, email, or post — AV1 is the wrong target and hands you a playback problem you did not have. Convert to a still format instead. AV1 output earns its place only when the Hasselblad frame has to live inside a video timeline, an AV1 encoding pipeline, or a montage; and even then, plan to rename the result to .mkv or re-encode it before you hand it to anyone else.
Because a 3FR is one still photograph and carries no audio. On image-to-video conversions the Audio Codec control is hidden rather than set to "none", so the encode never even offers you a track to fill — the muxer writes video only. That is correct behaviour for this pairing, not a dropped stream. If the clip needs sound, add it afterwards in a video editor.
.av1 file play in my browser or in VLC?VLC and mpv open it; browsers generally do not. The file is AV1 video inside a Matroska container that we name .av1, and browsers expect AV1 delivered in MP4 or WebM. VLC gained AV1 decoding in the 3.0.4 update, so anything current handles the stream, and older builds report "codec not supported: av01". For dependable playback anywhere, rename to .mkv or convert with AV1 to MP4.
No. A 3FR stores 16-bit-per-channel sensor data, which is what gives Hasselblad files their highlight and shadow recovery headroom. The clip we write is standard 8-bit video, so that headroom is baked off the moment the frame is rendered — the same thing happens exporting a JPEG. Do exposure, white balance and highlight work in a raw editor before converting, and keep the .3fr as the master.
Duration alone. Each image is held for the Duration you set — 5 seconds per frame by default, adjustable from a fraction of a second to 10 seconds — so a single upload gives you a clip of exactly that length. Upload several 3FR files with Merge strategy on "Merge images" and you get one clip of duration times frame count; switch it to "Video per image" to get a separate file per raw instead.
For video in general AV1 wins on efficiency: MDN puts it at higher compression than VP9 and HEVC, and as much as 50% higher than H.264, with royalty-free licensing that HEVC does not offer. For one held frame that advantage largely evaporates — there is almost nothing to predict across time, so the codecs converge — while AV1's slower encoding and thinner player support remain. If the file is going to a person rather than a pipeline, MP4 is the more practical share.
Yes. Upload the set, leave Merge strategy on "Merge images", and each raw becomes one held frame in a single clip, in upload order, with Duration deciding how long each stays on screen. There are no transitions or motion — it is a hard cut between stills. If you want each capture as its own file instead, set Merge strategy to "Video per image" before converting.
Because a medium-format capture is usually 4:3 and the video resolution you picked is usually 16:9, so the encoder pads the sides. The Background Color control chooses the pad colour and starts on White. Two ways out: leave Video resolution on "Keep original" so the frame keeps its own shape, or choose a Fixed Resolution closer to 4:3, such as 1024 x 768 or 1280 x 1024.
It is uploaded over an encrypted connection, rendered and encoded on our servers, and deleted automatically a few hours later — no sign-up, no watermark, never shared or made public. Hasselblad raws are large, so the upload is normally the slowest part of the job; that transfer time, not anything on the encoding side, is what you are waiting on.