Initializing... drag & drop files here
Supports: ERF
You have Epson R-D1 raw files and you want small, good-looking stills that behave properly in an Apple photo library. That is exactly what HEIC is for — and it is also HEIC's biggest catch, because outside Apple's ecosystem support is thin. This tutorial walks through the two compression controls that matter, what "developing" a raw actually costs you, the errors people hit when the HEIC lands on a Windows or Android device, and when a different output is the honest answer.
.erf files onto the page or click "+ Add Files". Several R-D1, R-D1s or R-D1x frames can be queued and converted with the same settings.These are two different ways of asking for the same thing, and picking the wrong one is the most common cause of a disappointing result.
Quality Preset tells the encoder how hard to try and lets the file size fall where it falls. It is the right default for photographs, because a detailed frame and a flat one genuinely need different numbers of bits, and a quality-driven encode gives both what they need. Start at "Very High (Recommended)" and only step down if the output is bigger than you want.
Specific file size works the other way round: you name a size and the encoder aims for it. Use it when something downstream imposes a hard cap — an upload form, a mail attachment, a CMS limit. Be aware that on a detailed 6-megapixel frame an aggressive target has to come out of image quality somewhere.
A few patterns worth knowing:
| Environment | HEIC support | Notes |
|---|---|---|
| Apple devices | Native | HEIC is the default capture format on modern iPhones and is handled system-wide across Apple's photo apps |
| Safari (desktop and iOS) | Safari 17 and later | The only browser engine with HEIF/HEIC support — 15.02% of tracked users |
| Chrome, Firefox, Edge, Opera | No | None of them decode HEIF/HEIC images |
| Windows | Usually needs an add-on | Microsoft publishes a free HEIF Image Extension in the Microsoft Store; without it many Windows apps show nothing |
| Android | Patchy | Handling varies by app and by device vendor rather than being a single system-wide answer |
| Web upload forms | Often rejected | Many still accept only JPEG and PNG |
| Target | Codec behind it | Reach | Pick it when |
|---|---|---|---|
| HEIC | HEVC (H.265) intra coding | Apple-first; Safari 17+ only in browsers | The photos live in an Apple photo library and size matters |
| AVIF | AV1 intra coding | 94.67% of tracked users | You want comparable efficiency but need it to display in browsers |
| JPG | JPEG DCT, 8-bit | Effectively universal | The file has to open absolutely everywhere |
| PNG | Lossless DEFLATE | Effectively universal | You want the rendered pixels with no codec artefacts |
| TIFF | Lossless options | Print and document workflows | You want a non-raw archival master |
If the people who need to see these photos are on Windows, Android or older software, HEIC is the wrong target — not because the file is bad, but because their software will not open it. Render to JPG for them, or to AVIF if the destination is a web page. HEIC also cannot give back what the raw render takes away: once the 12-bit sensor data has been demosaiced there is no recovering highlights or resetting white balance from the HEIC, so reopen the original .erf in a raw editor for that. And a truncated ERF copied off a failing card may not decode at all — copy the file from the card again before assuming the converter is at fault.
It is a HEIF file whose images are coded with HEVC. HEIF itself is ISO/IEC 23008-12, a container built on the ISO Base Media File Format that specifies how to store images and their metadata; the .heic extension marks the variant that uses HEVC (ISO/IEC 23008-2, also published as ITU-T H.265) as the image codec. The format can carry anything from 8-bit consumer photos up to 16 bits per sample for professional work.
Because they are doing entirely different jobs. An ERF stores the R-D1's sensor readout uncompressed and bit-packed at 12 bits per photosite — 6.1 million photosites works out to roughly 9 MB of pixel data by simple arithmetic, before metadata and the embedded preview. A HEIC stores a developed RGB image compressed with HEVC's intra coding, which was standardised in 2013 as a 25-50% improvement on H.264 at equal quality. You are comparing an uncompressed negative with a compressed print.
Yes. The whole value of the ERF is that white balance, exposure and tone are still open parameters rather than baked pixels. Producing a HEIC demosaics the Bayer data and commits to one interpretation. Keep the original .erf as your master — the R-D1 line is discontinued, so these files cannot be recreated.
On Windows, usually only after installing Microsoft's free HEIF Image Extension from the Microsoft Store; without it many apps will simply show nothing. On Android, support depends on the individual app and the device vendor rather than being a single system-wide answer. In browsers, only Safari 17 and later display HEIC — which works out to about 15% of tracked users. If broad compatibility matters more than file size, convert to JPG.
Match the format to the destination. HEIC wins inside Apple's ecosystem, where it is handled natively everywhere and integrates with the photo library. AVIF wins on the open web, because it reaches 94.67% of tracked browser users against HEIC's 15%, and it uses the royalty-free AV1 codec rather than patent-encumbered HEVC. Both are far more efficient than JPEG; the difference is who has to open the file.
No — several converter sites say otherwise, but the decoders disagree. darktable's RawSpeed handles ERF with its uncompressed decompressor, reading 12-bit samples MSB-first with a control byte inserted roughly every ten pixels. There is no entropy-coding stage on the sensor data at all, which explains both the file sizes and the dramatic shrink when you convert to any modern still format.
Only three bodies: the Epson R-D1, announced in March 2004 and described by Wikipedia as the first digital rangefinder ever commercially produced, the R-D1s (March 2006), and the Japan-only R-D1x / R-D1xG (April 2009). All used a 6.1-megapixel Sony ICX413AQ APS-C CCD behind a Leica M mount. The files remain readable — LibRaw's supported-camera list covers all three, and ExifTool reads and writes the format's EXIF, IPTC, XMP and ICC metadata.
They are uploaded over an encrypted connection, rendered and re-encoded to HEIC on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public. Because ERF stores its sensor data uncompressed, upload time is normally the longest part of the job. The ERF converter hub lists every other output available from the same source file.