ERF to TIFF Converter
Initializing... drag & drop files here
Supports: ERF
Advanced Options - Our defaults are optimized for the best results. We recommend you keeping the defaults unless you have a specific need.
Reset to defaults
Need help?Convert ERF to TIFF: What This Tutorial Covers
An Epson .erf is a digital negative from a discontinued rangefinder; a TIFF is the flat, lossless master that print labs, archives and professional imaging tools all read. This tutorial covers rendering one into the other without quietly degrading it — because the "Compression Type" dropdown on this page defaults to JPEG, which is lossy, and an archival TIFF built on a lossy codec defeats the entire point. It also covers what you permanently give up by rendering a RAW file, and when keeping the .erf is the better decision.
How to Convert ERF to TIFF
- Upload Your ERF File: Drag the
.erffiles onto the page or click "+ Add Files" to browse. Whole folders of R-D1 frames can be queued and rendered with identical settings. - Change Compression Type to LZW or Deflate: Open Advanced Options and move "Compression Type" off its JPEG default. LZW and Deflate are both mathematically lossless, and LZW is read by virtually every imaging application.
- Check Quality Preset, Resolution and Extension: Leave "Quality Preset" on "Very High (Recommended)" and "Image resolution" on "Keep original" to hold the full frame; use the "File extension" list if your workflow specifically needs
.tifrather than.tiff. - Convert and Download: Click Convert and save the TIFF. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark.
Walk-through: Picking the Right Compression Type
This single dropdown decides whether your archive is faithful or silently degraded, and its default is the one lossy option in the list. Change it before you convert and match it to the job.
| Compression Type | Lossless? | Reader support | Use it when |
|---|---|---|---|
| JPEG (the default) | No | Wide | You deliberately want a small, lossy TIFF and fidelity does not matter |
| LZW | Yes | Effectively universal | Default choice for a preservation or print master |
| Deflate (ZIP) | Yes | Very wide | Same as LZW; often smaller on smooth, low-noise frames |
| PACKBITS | Yes | Universal, including very old software | A reader chokes on LZW — simple run-length encoding is the safest fallback |
| NONE | Yes (uncompressed) | Universal | Maximum compatibility, largest file, no decode step at all |
| ZSTD / JP2K / WebP | Varies | Narrow | Only when you know the receiving application supports that flavour |
| CCITT Fax 4 | Yes, but bilevel | Fax and document tooling | Scanned 1-bit black-and-white documents — never photographs |
Everything else on the page is secondary to this choice. MDN's image guide confirms the split: PackBits and LZW are TIFF's lossless options, JPEG is its lossy one (per MDN).
What Changes When a RAW Becomes a TIFF
| Property | In the .erf |
In the rendered TIFF |
|---|---|---|
| Pixel data | Bit-packed sensor mosaic, one reading per photosite | Demosaiced RGB, three channels per pixel |
| White balance | A tag you can reinterpret freely | Baked into the pixels |
| Highlight and shadow recovery | Available from the unclipped sensor data | Gone; only what the render kept survives |
| Typical file size | Smaller — one value per photosite | Roughly three times the pixel payload before compression |
| Software that opens it | RAW-aware tools only (Camera Raw, Lightroom, RawTherapee, darktable, dcraw / LibRaw) | Effectively every imaging, print and layout application |
| Web display | None | Only Safari renders TIFF natively |
Common Errors and How to Fix Them
- "My TIFF looks soft, or has blocky artefacts." Compression Type was left on the JPEG default. Re-convert with LZW or Deflate.
- "A generic converter gave me a corrupt or empty image." Many tools treat an
.erfas a plain TIFF. The R-D1's sensor data is bit-packed inside the TIFF/EP wrapper with compression tag 32769 (documented by libopenraw), so a decoder that does not understand Epson's packing produces garbage. A RAW-aware converter demosaics it properly. - "The TIFF is several times larger than the ERF." Expected. The TIFF stores three fully rendered colour channels per pixel where the ERF stored a single sensor reading. Reduce "Image resolution", pick a lighter Compression Type, or keep a JPG copy for circulation.
- "Colours or exposure look wrong." Writing any TIFF requires the RAW to be demosaiced with a white balance and tone curve applied. If you want your own interpretation, develop the
.erfin a RAW editor first and convert the export. - "My application opens
.tifbut not.tiff." Some legacy software only registers the three-letter extension. Re-convert and pick TIF under "File extension" — the file is otherwise identical. - "The web page will not display my TIFF." Only Safari supports TIFF natively in web content. Render an ERF to JPG copy for universal display, or ERF to AVIF for a small modern-browser copy.
When This Doesn't Work
Some .erf files resist a clean one-pass render. A truncated or partially copied file — common with twenty-year-old card transfers — decodes to a corrupt frame, and the only fix is recopying from the original media. More importantly, if you need to recover blown highlights, lift deep shadows or reset white balance, that latitude lives in the RAW mosaic and disappears the moment any TIFF is written, so develop the .erf in Camera Raw, Lightroom, RawTherapee or darktable first and render the corrected result. And because the R-D1 line was discontinued and no camera has written ERF since, treat the original as irreplaceable: render a copy to TIFF and keep the .erf archived beside it rather than in its place.
Frequently Asked Questions
Is ERF really an uncompressed RAW format?
Yes. The R-D1's colour-filter-array data is stored bit-packed inside a TIFF/EP structure, with the compression value in the CFA sub-IFD set to 32769 (per libopenraw) — but that custom value marks Epson's packing, not real compression: darktable's RawSpeed reads the 12-bit samples with its uncompressed decompressor. The packing still matters in practice: a decoder has to understand Epson's specific packing to unpack the frame, which is exactly why tools that treat an .erf as an ordinary TIFF return a corrupt image.
Does LZW compression inside a TIFF cost any image quality?
None. LZW, Deflate, PackBits and NONE are all lossless within TIFF — they change how the pixels are stored, not what the pixels are, so the rendered image comes back bit-for-bit intact. The only lossy entry in the dropdown is its JPEG default, which is the whole reason this tutorial keeps steering you away from it.
Will I lose the RAW editing latitude by converting to TIFF?
Yes, and this is the trade worth understanding before you archive. The mosaic in an ERF is what lets you recover blown highlights, lift shadows and reset white balance long after the shot. Producing a TIFF demosaics that data into ordinary RGB with the current interpretation baked in, so you get a finished picture rather than a negative. The pixels are then preserved perfectly, but the look is locked.
Should I archive to TIFF or just keep the ERF?
Ideally both. The .erf is your negative and the only file that still holds unprocessed sensor data; a TIFF with LZW or Deflate is the lossless, print-ready copy that opens in every professional tool without a RAW decoder. The pool of software that reads ERF is slowly thinning now that Epson has left the camera business, so rendering masters while good decoders exist is a sensible preservation move.
How much detail can a TIFF actually preserve from an R-D1 file?
Exactly as much as the camera recorded and no more. The R-D1 and R-D1s use a 6.1-megapixel APS-C CCD measuring 23.7 x 15.6 mm behind a Leica M mount, so a TIFF holds that roughly 6-megapixel frame losslessly — it cannot add resolution the sensor never captured. Enlarging the output under "Image resolution" only interpolates.
Why is the TIFF so much bigger than the ERF it came from?
Because the two store fundamentally different things. The ERF holds one bit-packed reading per photosite; the TIFF holds three fully rendered colour channels per pixel, roughly tripling the payload before any compression is applied. LZW or Deflate claw some of that back on smooth frames, and very little on noisy or highly detailed ones.
Can I get a JPG or PNG from this page instead?
Yes — the "File extension" list on this page also offers JPEG, JPG, PNG and APNG, so you can change the output without starting over. For a dedicated page with the full option set, use ERF to JPG for a small shareable photo or ERF to PNG for a lossless raster with wide software support.
What happens to my files after the conversion?
Your ERF is uploaded over an encrypted connection, demosaiced and encoded on our servers, and deleted automatically after a few hours along with the TIFF it produced. Nothing is shared or made public, and there is no sign-up and no watermark. The practical constraint on a large batch is upload time rather than anything on your machine.