RAF to WebM Converter

RAF to WebM Converter

RAF is Fujifilm's raw stills format — the unprocessed sensor readout from an X-series or GFX body, one photograph per file. WebM is an open, royalty-free web video format built on the Matroska container. Converting between them means developing the raw frame and then holding that single rendered picture on screen for a set duration, so the output is a silent, motionless clip in a web-native container: a title slate, a poster frame, a placeholder that drops onto a WebM timeline without a second re-encode.

This page documents what each format actually is, what the converter writes, and which of the three codec choices behave the way their controls suggest.

RAF Format at a Glance

WebM Format at a Glance

How to Convert RAF to WebM

1. Upload Your RAF File: Drag and drop your Fujifilm .RAF files onto the page or click "+ Add Files". "Merge strategy" opens on "Merge images", which plays every upload in sequence inside one clip; "Video per image" gives you a separate WebM for each.
2. Set the Image Duration: Choose how long the still is held. The dropdown runs from a single frame at 60 fps up to 10 seconds per frame and opens on 5 seconds.
3. Pick the Video Codec and Quality: "Video Codec" offers AV1, VP8 and VP9, and opens on VP9. Leave "Quality Preset" on "Very High (Recommended)" unless you have a reason to move it — and read the VP8 note below before choosing that codec.
4. Convert and Download: Click "Convert" and save your WebM. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours. No sign-up, no watermark.

Codec Notes for This Path

Three constants apply whatever you choose: the clip is written at 1 frame per second with B-frames disabled, because a still gains nothing from either; every bitrate and target-file-size mode is hidden on this path, so Quality Preset, Constant Quality and Constraint Quality are the only rate controls offered; and the frame is re-rendered as a clean PNG clamped to 4,096 px on the long edge, with both dimensions rounded down to an even number, before encoding starts.

Frequently Asked Questions

Which codec does the WebM come out as?

VP9, unless you change it. WebM's own specification covers VP8 and VP9, and VP9 is the better of the two at essentially every quality point, so it is the default here. AV1 is offered as well and will produce the smallest file of the three, at the cost of a slower encode and slightly narrower playback support — the WebM Project's format description does not list AV1 among the codecs it covers, so a strict parser is entitled to refuse it even though current Chrome, Firefox and Edge all play it.

Why do the quality controls seem to do nothing when I pick VP8?

Because on this path they genuinely do not reach the encoder. With VP8 selected, Constant Quality emits neither a CRF value nor a bitrate, and libvpx falls back to its own defaults — it logs that neither bitrate nor constrained quality was specified and that it is using a default CRF of 32 at 256 kbit/sec. What makes this worse rather than merely quiet is that a 16-63 slider renders on the .webm page and looks entirely functional while having no effect. If you must use VP8, use Constraint Quality, which is the one mode that does set a bitrate. Better still, stay on VP9, where all three modes work.

Does the clip have any motion or sound?

Neither. One RAF is one photograph, so the WebM shows that single picture for the duration you set — no pan, no zoom, no animation. There is no audio track at all: the audio codec control is hidden on the image-to-video path, so the file is silent rather than carrying a silent track. If you want a sequence, upload several RAF files and leave "Merge strategy" on "Merge images"; each photo is held for the Image Duration and they play back to back as hard cuts. Add a soundtrack afterwards in a video editor.

What resolution and frame rate will the WebM be?

The frame rate is 1 fps, always, on this path — a still held for five seconds is five identical pictures, so there is nothing for a higher rate to describe, and B-frames are switched off for the same reason. Playback duration is whatever you set under "Image Duration". Resolution starts from your photo: "Video resolution" opens on "Keep original", and the frame is clamped to 4,096 px on the long edge with both dimensions rounded down to even numbers. A 7728 x 5152 X-T5 frame therefore lands at exactly 4096 x 2730, and an 11648 x 8736 GFX100 II frame at 4096 x 3072. Set "Fixed Resolutions" or "Preset Resolutions" if you need a specific size — the presets set the height and let the width follow your photo's aspect ratio.

Why are there white bars around my photo?

Because a 3:2 Fujifilm frame does not fit a 16:9 output shape, and rather than stretch or crop it the converter pads the difference with the "Background Color", which opens on White for image sources. That same colour fills the letterbox bars. Change it to Black if the clip is going into a dark edit, or pick an output resolution with the same proportions as the photo so there is nothing to pad.

Where does a WebM file actually play?

Everywhere modern, and nowhere old. Per caniuse, WebM has full native support from Chrome 25, Firefox 28, Edge 79 and Opera 16, from Safari 16.0 on desktop, and from Safari 17.4 on iOS. That iOS number is the one that catches people out — WebM support on iPhones and iPads is recent enough that anything targeting a broad mobile audience is safer as MP4. If that describes your project, RAF to MP4 produces the same rendered frame in a container with no such caveat.

Do I lose my raw editing latitude converting RAF to WebM?

Completely, and irreversibly. A RAF stores what the sensor measured — 14 bits per photosite on X-series bodies, 14 or 16 on GFX — which is why exposure, white balance and highlight recovery are still adjustable while it is raw. Encoding to WebM demosaics that data, renders it to 8-bit, then discards chroma detail in the 4:2:0 conversion the encoder uses. Keep the original .RAF as the master. The in-camera Film Simulation will not carry over either, since Provia, Velvia, Classic Chrome and the rest are render-time instructions rather than pixels stored in the file — apply the look in a raw developer first if it matters.

How large will the WebM be, and what happens to my upload?

Small, usually surprisingly so: a picture that never changes gives an inter-frame codec almost nothing to encode after the first frame, so a few seconds of a full-resolution Fujifilm still typically lands well under a megabyte at VP9. The input is the heavy part — raw files routinely run 40-80 MB each, so upload time is the real constraint rather than anything about the conversion. Your file travels over an encrypted connection, is rendered and encoded on our servers, and is deleted automatically after a few hours. It is never shared or made public. If what you actually wanted was a picture rather than a clip, RAF to JPG is the conversion to use instead.