Initializing... drag & drop files here
Supports: RAF
Most people converting a Fujifilm RAF reach for HEIC because they want an Apple-friendly file that is smaller than a JPEG. That is a reasonable goal, but the trade is not the one most pages describe. Convert to HEIC when the destination is Apple's Photos library and storage matters. Convert to JPG when the file has to open anywhere else, or when colour fidelity matters more than size — because at this site's default preset the JPEG actually keeps more colour resolution than the HEIC does.
| Property | HEIC output | JPEG output |
|---|---|---|
| Underlying codec | HEVC (H.265) intra frame | JPEG DCT |
| Bit depth produced here | 8-bit | 8-bit |
| Chroma sampling at the default preset | 4:2:0 (colour halved) | 4:4:4 (colour at full resolution) |
| Chroma sampling at any preset | Always 4:2:0 | 4:4:4 down to quality 90, then 4:2:0 |
| Native browser rendering | Safari 17+ only, about 15% of users | Universal |
| Opens on Windows / Android without extra software | Not reliably | Yes |
| Typical size at matched visual quality | Smaller | Larger |
| Best for | Apple Photos, phone storage, AirDrop | Sharing, uploading, printing, archiving a render |
The size advantage is real — HEVC intra coding is a far newer design than JPEG's — but how large it is depends entirely on the image and the preset, so treat any fixed "half the size" figure with suspicion.
.raf masters..raf files onto the page or click "+ Add Files". Only .raf inputs are accepted, and every queued file is converted separately with the same settings.We encoded the same frame at every rung through the encoder this page uses. Two results are worth knowing before you touch the dropdown:
| Quality Preset | Encoder quality | Bit depth | Chroma | Effect versus the default |
|---|---|---|---|---|
| Highest | 100 | 8-bit | 4:2:0 | None — pixel-identical to Very High |
| Very High (default) | 95 | 8-bit | 4:2:0 | Baseline |
| High | 90 | 8-bit | 4:2:0 | First rung that actually changes the image |
| Medium | 80 | 8-bit | 4:2:0 | Noticeably smaller, mild detail loss |
| Low | 70 | 8-bit | 4:2:0 | Visible softening |
| Very Low | 60 | 8-bit | 4:2:0 | Artefacts on gradients |
| Lowest | 50 | 8-bit | 4:2:0 | Obvious blocking |
Comparing the Highest and Very High outputs of the same source gave an absolute pixel difference of zero and the same file size, so moving the dropdown up from the default buys nothing. If you want a better-looking file than the default, the lever is resolution, not the top preset.
No. HEIC as a format can store 10-bit and higher, but the raw decoder in this pipeline develops RAF at 8 bits per channel by default and the converter does not override it, so the pixels are already 8-bit before the HEIC encoder sees them. If you need more than 8 bits from a Fujifilm raw, use in-camera raw conversion to 16-bit TIFF or a desktop raw editor.
No. We compared the two outputs from the same source: identical file size and an absolute pixel difference of zero. "High" (quality 90) is the first rung below the default that changes anything at all. Treat Very High as the ceiling on this page.
Because of chroma subsampling. Our HEIC output is 4:2:0 at every preset — the two colour channels are stored at half resolution horizontally and vertically. Our JPEG output stays at 4:4:4 (full colour resolution) for the top three presets. On luminance detail HEIC generally wins; on saturated colour edges a Very High JPEG can look cleaner despite being larger.
Apple platforms handle it natively in Photos, Preview and Quick Look. On the web, Safari 17 and later is the only major browser that renders HEIC, which caniuse currently puts at roughly 15% of users; Chrome, Firefox and Edge do not. Windows needs a codec extension installed, and support on Android varies by version and gallery app. If you are not certain about the recipient, send a JPEG.
Only the filename. HEIC is Apple's name for a HEIF container carrying HEVC-coded image data, which is exactly what both pages produce — the bytes from RAF to HEIF and from this page are the same file under a different extension. Use .heic if the destination is Apple software, .heif if a tool specifically asks for it.
The rear preview is a camera-rendered JPEG with a Film Simulation and Fujifilm's own colour science applied. A general-purpose raw render produces a neutral baseline instead, and Fujifilm's X-Trans colour filter array — which is not the 2×2 Bayer grid most demosaic algorithms assume — means different converters resolve micro-detail slightly differently. Neither rendering is wrong; they are different interpretations of the same sensor data.
Standard shooting metadata — camera body, lens, shutter, aperture, ISO, date — travels with the image. What does not survive is anything that only means something to a raw file: the un-demosaiced sensor data, the ability to change white balance non-destructively, and the option to re-render with a different Film Simulation later. Keep the .raf if any of that matters.
Yes — queue as many .raf files as you like and each becomes its own HEIC with the settings you chose; nothing is merged. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public. If the results are still too large, run them through compress HEIC, and the RAF converter hub lists every other target this format can reach.