RAF to JXL Converter
FileFlip converts RAF to JXL entirely inside your browser, using ImageMagick compiled to WebAssembly. The file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. That means no file-size limit, no queue and no account.
How do I convert an RAF file to JXL?#
- Drop your RAF file onto the converter at the top of this page, or click it to pick one from your computer. You can add as many as you like.
- Leave the target set to JXL and the conversion starts on its own. FileFlip downloads 14.1 MB of WebAssembly the first time and nothing after that, then runs ImageMagick on your own machine.
- Save the JXL file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting RAF to JXL lose quality?#
It depends on what is inside the file. RAF is a container rather than a codec, so whether the JXL conversion copies the streams across untouched or re-encodes them is decided by the codecs that particular file happens to use.
Is it safe to convert RAF files online?#
Yes, because nothing is uploaded. FileFlip converts RAF files inside the browser tab you already have open, using WebAssembly builds of the same engines a desktop converter would install. Your file is read from your own disk into the page's memory, and no request carrying it is ever made.
You do not have to take that on trust. Open your browser's network panel, run a conversion, and you will see the engine come down and your file go nowhere. There is no upload, no server-side copy, no retention window, and no account tied to what you converted.
How FileFlip works lists every engine, its version and its download size, and shows how to check for yourself that nothing leaves your machine.
What RAF to JXL actually does to the file#
Converting RAF to JXL runs on ImageMagick, downloads 14.1 MB of WebAssembly the first time and nothing after that, re-encodes or copies through depending on the codecs in the file.
| Engine | ImageMagick |
|---|---|
| Conversion path | One step: RAF → JXL |
| Downloaded to your browser | 14.1 MB, once, then cached by your browser |
| Quality | Decided by the codecs inside the file |
| You get back | One file |
| Where it runs | In a background worker, so the page stays responsive |
Worth knowing before you start:
- camera raw is demosaiced with ImageMagick's defaults, which will not match the camera's own rendering
- some cameras write lossily compressed raw, so the source is not always a complete sensor record
What is an RAF file?#
An RAF file holds the unprocessed sensor readout from a Fujifilm camera in a TIFF-based container alongside an embedded JPEG preview and a Fujifilm-specific metadata block, and the same extension covers both the X-Trans bodies and Fujifilm's Bayer-sensor models such as the X-A series, the X-T100 and the GFX medium format line.
RAF is what a Fujifilm camera writes when you set it to raw, so the only decision in the menu is uncompressed against compressed, not the format itself.
Convert RAF to JPEG when the picture has to be shared or printed, or to DNG when you want one raw format across cameras from several manufacturers.
What is a JXL file?#
A JXL file stores an image under the JPEG XL coding system, a format built to losslessly repackage an existing JPEG into a smaller file or to encode a new photo at higher quality per byte than JPEG, WebP or AVIF.
Use JPEG XL for archiving and photo libraries where you want smaller files than JPEG without giving up the option to reconstruct the original JPEG exactly, especially once Chrome and Firefox finish rolling out default decoding.
Convert JXL to JPEG or PNG for anything going on the web today, since most browsers still require a manual flag to display JPEG XL directly.
RAF to JXL questions people ask#
What software opens RAF files?
Fujifilm's own X RAW Studio opens RAF files, and so do Adobe Lightroom and Camera Raw, Adobe Photoshop, Capture One, and the open source darktable and RawTherapee. X RAW Studio is the odd one out because it does the conversion on the image processor inside a Fujifilm camera connected over USB rather than on the computer, which is why its output matches the camera's own JPEG engine exactly.
Why do RAF files look softer in Lightroom than in Fujifilm's own software?
RAF files from an X-Trans sensor carry a 6x6 color filter pattern instead of the 2x2 Bayer grid almost every other camera uses, and a raw converter has to demosaic that pattern with code written for it. Adobe's early X-Trans rendering was widely criticized for smearing fine detail such as foliage. Every current raw processor now ships X-Trans specific demosaicing, RawTherapee's Markesteijn one-pass and three-pass methods being the open source example, so the gap has narrowed a lot since 2012. What is left is mostly a matter of taste, and photographers who still want a different rendering run their RAF files through Iridient X-Transformer before Lightroom sees them.
Does converting RAF to DNG lose anything?
Converting an RAF file with Adobe DNG Converter keeps the sensor data as it was captured, X-Trans mosaic and all, so nothing about image quality changes and the demosaicing still happens later in whatever software opens the DNG. Some Fujifilm-specific fields such as film simulation settings may not survive into a form other software understands. A tool like Iridient X-Transformer works differently: it demosaics the RAF itself and writes an already-processed linear DNG, which fixes the interpretation of the X-Trans pattern in place and takes that choice away from the editor you open it in.
Why does Fujifilm use RAF instead of DNG?
Fujifilm keeps RAF as its own format, as Canon, Nikon, Sony and Panasonic keep theirs, so it can describe new sensors and store its own processing settings without waiting for Adobe to update the shared DNG specification. X-Trans makes that argument sharper, since the 6x6 filter layout needs its own demosaicing treatment. No Fujifilm camera writes DNG in-camera, so converting is always something you do after the fact.