RAW to RAF Converter
Convert RAW to RAF in your browser. You download a Linear DNG (.dng), not a .raf: only a Fujifilm camera can create a genuine RAF, and every editor that opens RAF also opens DNG. Nothing is uploaded.
- Processed locally
- No upload, no wait
- No sign-up
- No watermark
Drop images here
or choose files · paste with Ctrl/⌘ V
RAW expected · other image formats also work
How to use RAW to RAF
- 1
Add your RAW files: drop them here, choose them, or paste from the clipboard.
- 2
There is nothing to tune: the DNG is written uncompressed. Resizing and rotating are under More options if you need them.
- 3
Click Convert. Each file is decoded and encoded in a background thread on this device.
- 4
Download the .dng files one at a time or together as a ZIP.
Why use Aback Images for raw to raf
Where a RAF would go
RAF files are opened by Fujifilm X RAW Studio, Lightroom, Photoshop Camera Raw, Capture One and darktable, and every one of them opens the DNG too.
DNG next to RAW
The DNG stores the camera preview's pixels uncompressed, so it can be as large as the 20 to 80 MB raw file, or larger, depending on the preview's resolution.
No new artefacts
The preview inside the RAW is a camera JPEG; the DNG stores its decoded pixels uncompressed, so this step adds no compression damage of its own.
Processed on your device
Your images are decoded, edited and encoded inside this browser tab by Web Workers. Nothing is uploaded to a server.
RAW vs RAF
What changes from RAW to RAF
Encoding: the RAW uses uncompressed, lossless JPEG or vendor-specific coding of the sensor data, depending on the maker; RAF uses uncompressed or lossless compressed sensor data in Fujifilm's own container, and the download is a Linear DNG: demosaiced 8-bit RGB with the colour matrices raw editors need.
Bit depth: 12 to 16 bits per channel in the RAW; RAF allows 12 to 16 bits per channel depending on the camera, and the DNG written here has 8 bits per channel, linearised. The sensor's 12 to 16 bits are not used: the camera's 8-bit preview is converted.
Colour: camera-native RGB from a colour filter mosaic in the RAW; RAF supports camera RGB from an X-Trans 6×6 or Bayer 2×2 mosaic, written here as 8-bit sRGB.
Metadata: the RAW can carry EXIF and vendor maker notes, almost always with an embedded JPEG preview; RAF can carry EXIF and Fujifilm maker notes, including the Film Simulation, but nothing is copied across.
About RAW
Camera RAW files (CR2, CR3, NEF, ARW, DNG, ORF, RW2, RAF and others) hold the unprocessed sensor data from a camera along with an embedded full-size JPEG preview rendered by the camera.
.RAW is an extension rather than one format. Panasonic and Leica compacts wrote TIFF-like .RAW files before Panasonic moved to RW2, and scanners and scientific cameras use .raw for headerless dumps with no width, height or layout recorded, which nothing can read without being told those values.
RAW files usually come from older Panasonic and Leica compacts that saved .RAW, and scanners or scientific cameras that use the extension for pixel dumps.
About RAF
RAF is the raw format of Fujifilm cameras, from the X series to the medium-format GFX. Most X-series bodies use an X-Trans sensor with a 6×6 colour filter pattern instead of the usual Bayer 2×2.
RAF is not TIFF at the top level: it opens with the text 'FUJIFILMCCD-RAW', then a header with the camera model and offsets to three blocks: a JPEG preview near the start of the file, a header describing the sensor layout, and the sensor data.
RAF files come from Fujifilm X-T, X-H, X-S, X-E, X100 and GFX cameras.
When converting RAW to RAF makes sense
Forms and workflows that ask for RAF usually feed a raw editor, and each of those opens DNG as well, so the DNG can take the RAF's place. Keep the RAW if you only need to view or share the picture.
What RAF offers when it comes straight from the camera: Film Simulation baked into the embedded JPEG; Lossless compressed option on recent bodies; Large medium-format files from GFX cameras. Its drawbacks: Fujifilm's own container rather than TIFF; X-Trans demosaicing differs between raw editors; Film Simulations need camera-matching profiles in third-party editors.
Limitations
- The camera's embedded JPEG preview is what gets converted, not the sensor data; it matches what the camera showed on its screen.
- A headerless .raw pixel dump has no preview and no size information, so it cannot be converted here.
- The DNG holds the decoded 8-bit pixels, so it adds no dynamic range or detail beyond the RAW.
More conversions
Related tools
Convert RAF to RAW in your browser, saved as a Linear DNG, the raw file every RAW editor also opens. Batch, private, no uploads.
Convert RAW to JPG in your browser, made from the full-size preview your camera camera stored in the file. Batch, private, no uploads.
Shrink JPG, PNG, WebP, AVIF and GIF files with MozJPEG, OxiPNG and modern codecs, with a live before/after preview.
Resize to exact pixels, a percentage or a longest side, with Lanczos3 and Magic Kernel resampling. Batch ready.
Strip EXIF, GPS, XMP, IPTC and comments losslessly. Pixels are never re-encoded for JPG, PNG and WebP.
Convert between 34 image formats in bulk: HEIC, WebP, AVIF, JPEG XL, PNG, JPG, GIF, TIFF, SVG, ICO, PSD, RAW and more.
Frequently asked questions
Why do I get a .dng file instead of a .raf?
A real RAF is written by Fujifilm cameras and holds the sensor's own readings (12 to 16 bits per channel depending on the camera, stored as uncompressed or lossless compressed sensor data in Fujifilm's own container) along with EXIF and Fujifilm maker notes, including the Film Simulation. This converter reads the JPEG preview inside the RAW, not its sensor data, so it cannot make one either. The Linear DNG you get instead is Adobe's open raw format, and every editor that opens RAF files opens it with the same raw controls. It holds decoded pixels, so it adds no quality or dynamic range.
Does this process the RAW sensor data?
No. Camera RAW files carry a JPEG rendered by the camera when the picture was taken, and that is what gets converted, so the result matches what you saw on the camera screen. For full development (white balance, highlight recovery, lens corrections) use a RAW editor.
Are my images uploaded anywhere?
No. Processing happens inside your browser with WebAssembly and Web Workers. The site only downloads the app code and codecs; your files never leave your device. You can confirm this with the live upload counter on the tool, or in your browser's network panel.
Can I process many files at once?
Yes. Drop a whole selection or folder. Files are processed in parallel on several worker threads, each result can be downloaded on its own, and everything can be saved as one ZIP.
Is it free? Is there a file limit or watermark?
It is free with no account, no watermark and no daily limit. The only limit is your device's memory: very large images (over roughly 100 megapixels) may be refused to keep the tab from crashing.