Initializing... drag & drop files here
Supports: ERF
ERF is Epson's RAW File format — the "digital negative" written by the Epson R-D1, the world's first digital rangefinder camera (2004), and its R-D1s successor. Those bodies were rare and short-lived, so a stray .erf is usually an orphaned shot from a discontinued camera line that ordinary photo apps refuse to open. This converter renders the raw and writes it as a flat TIF (TIFF) — the long-standing standard for print labs and archival masters. One thing to set going in: pick a lossless Compression Type, because the default here is JPEG, which is lossy. Keep the original .erf as your editable master, since the render bakes in white balance and exposure.
| Property | Value |
|---|---|
| Full name | Epson RAW File |
| Camera line | Epson R-D1 / R-D1s rangefinders (R-D1 launched 2004) |
| Container | TIFF/EP-based (per libopenraw) |
| Sensor data | Color-filter-array mosaic, compressed and bit-packed — not uncompressed |
| Resolution class | About 6-megapixel APS-C |
| Editing latitude | Full — white balance and exposure recoverable from the raw |
| Native browser support | None — needs a raw-aware decoder |
| Still readable in | Adobe Camera Raw, Lightroom, RawTherapee, dcraw |
| Property | Value |
|---|---|
| Full name | Tagged Image File Format (.tif / .tiff) |
| Released | 1986 (Aldus); TIFF 6.0 in 1992, now maintained by Adobe |
| Type | Rendered raster image (RGB) |
| Compression | LZW, DEFLATE, PACKBITS, NONE (lossless) or JPEG (lossy) |
| Bit handling | Tagged container; carries the rendered image plus metadata |
| Native browser support | Safari only — not a web delivery format (per MDN) |
| Best for | Print, layered editing, long-term archival masters |
.erf files onto the page or click "+ Add Files" to browse — straight off an R-D1 or R-D1s. You can queue several frames and convert them with the same settings..tif or .tiff spelling under "File extension" to match your workflow.No, and this is a common myth — several converter sites, including CloudConvert, still describe ERF as "uncompressed." In reality the R-D1's color-filter-array sensor data is stored compressed and bit-packed inside a TIFF/EP structure (per libopenraw, which documents the CFA data as bit-packed with a compression tag of 32769). For your conversion this matters in one way: the decoder has to understand Epson's specific packing to unpack the frame, which is why some generic tools that treat an .erf as a plain TIFF return a corrupt or empty image. xconvert decodes the R-D1 layout, then renders and re-encodes it as TIF.
Not at the encode step, if you choose the right setting. Set "Compression Type" to LZW or DEFLATE and the TIF is mathematically lossless — no pixel data is discarded. Leave it on the JPEG default, though, and the TIF becomes lossy, so switch away from JPEG for archival masters. The real change is upstream of compression: to write any TIF the converter must demosaic the raw and bake in a white balance, exposure, and tone curve. The pixels are then preserved exactly, but the finished look is locked in.
Yes, and it is the one trade worth understanding before you archive. The raw mosaic in an ERF is what lets you recover blown highlights, lift shadows, and reset white balance long after the shot. To make a TIF, the converter renders that data into ordinary RGB pixels with the current interpretation baked in, so the TIF holds a finished picture, not a negative. Because these files came from a camera line Epson discontinued and may be the only copy you have, render a copy to TIF and keep the original .erf as your master. If you want control over the look, develop the ERF in a raw editor first, then convert the result.
The R-D1 and R-D1s were a tiny, discontinued line, so the pool of software that reads ERF is slowly thinning — Adobe Camera Raw, current Lightroom, RawTherapee, and dcraw still open it, but rendering archival TIF masters while those decoders exist is a sensible preservation move for 20-year-old files. On resolution, set expectations honestly: the R-D1 is about a 6-megapixel camera, so a TIF preserves that detail exactly but cannot add resolution the sensor never captured. "Keep original" under "Image resolution" holds the full frame; only scale down if you specifically need a smaller image.
It depends on the copy's job. TIF is the right target for a preservation or print master: with LZW or DEFLATE it is losslessly compressed and reads in every professional imaging and print tool. The downside is that TIFF is not a web format — only Safari displays it natively (per MDN) — so for sharing or the web, render an ERF to JPG copy for universal compatibility or an ERF to AVIF copy for small, current-browser delivery. Many people keep a TIF master plus a JPG or AVIF copy. If your workflow wants the four-letter spelling, ERF to TIFF produces an identical file with the .tiff extension.
Your ERF is uploaded over an encrypted connection, rendered and encoded into TIF on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, and your photos are never shared or made public. The main practical limit on a big upload is its size and the time it takes to send. In our testing, a rendered R-D1 frame written to an LZW TIF came out several times larger than the ERF it started from, because the TIF stores fully rendered RGB across three color planes rather than a single sensor mosaic — so if size matters more than print fidelity, convert to JPG or downscale with the "Image resolution" control. For irreplaceable originals, keep the .erf archived alongside the TIF.