Initializing... drag & drop files here
Supports: ERF
If you have Epson R-D1 files sitting on a drive, you are really choosing between two different jobs. ERF is a negative: uncompressed 12-bit sensor data that can still be re-developed years later, but that almost nothing opens. AVIF is a delivery format: an AV1-coded still that current browsers display natively and that is far smaller than a JPEG of comparable quality. The short answer is that you want both — archive the .erf, publish the AVIF — and this page converts one into the other.
| Property | ERF | AVIF |
|---|---|---|
| Full name | Epson RAW Format | AV1 Image File Format |
| Defined by | Epson (proprietary, undocumented publicly) | Alliance for Open Media, spec v1.2.0 finalised 16 October 2025 |
| Built on | TIFF structure (ExifTool: "Epson RAW Format (TIFF-based)") | HEIF and ISOBMFF |
| Payload | Uncompressed, bit-packed 12-bit CFA sensor data | AV1-coded image items |
| Compression | None on the pixel data | Lossy or lossless AV1 intra coding |
| Bit depth | 12 bits per photosite, undemosaiced | 8, 10 and 12-bit, plus higher via sample transforms |
| Colour | Bayer mosaic, needs demosaicing | Full RGB, with HDR and wide-gamut support |
| Transparency | None (opaque camera frame) | Yes, via AV1 alpha image items |
| Editing latitude | Full — white balance, exposure and tone are still parameters | None — one interpretation is baked in |
| Opens in a browser | No | Yes — 94.67% of tracked users; Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+, Samsung Internet 14+ |
| Written by | Epson R-D1 (2004), R-D1s (2006), R-D1x / R-D1xG (2009) | Any AVIF encoder |
| Typical role | Archive master | Web, storage, sharing |
| Target | Compression | Browser reach | Pick it when |
|---|---|---|---|
| AVIF | Lossy or lossless AV1 | 94.67% of tracked users | You want the smallest good-looking file for the web |
| JPG | Lossy DCT, 8-bit only | Effectively universal | The file must open absolutely everywhere, including old software and upload forms |
| PNG | Lossless DEFLATE | Effectively universal | You need an exact copy of the rendered pixels with no codec artefacts |
| TIFF | Lossless options | Not a browser format | You want a non-raw archival master for a document or print workflow |
| WebP | Lossy or lossless VP8/VP8L | Very broad | You need better-than-JPEG compression but must support browsers that predate AVIF |
.erf files onto the page or click "+ Add Files". Several R-D1, R-D1s or R-D1x frames can be queued and converted with one set of settings.For anything shown on a screen, yes. AVIF applies AV1's intra-frame coding tools to the still image, which is a far more capable toolset than JPEG's DCT, so at a given visual quality the AVIF is smaller. It also carries 10- and 12-bit images, HDR and wide gamut, none of which 8-bit JPEG can do. The trade is reach: JPEG opens in literally everything, whereas AVIF needs Chrome 85+, Firefox 93+, Safari 16.4+ or Edge 121+. If the file is going into a web upload form or an old photo app, choose ERF to JPG instead.
Yes, and that is inherent rather than a limitation of this converter. An ERF holds undemosaiced 12-bit sensor readings, so white balance, exposure and tone are still adjustable parameters. Producing any viewable image — AVIF, JPEG, PNG or TIFF — requires demosaicing that data and committing to one interpretation. Keep the original .erf as your master and treat the AVIF as a copy you can always regenerate.
Yes, despite what several converter sites say. darktable's RawSpeed decodes ERF using its uncompressed decompressor, reading 12-bit samples MSB-first with a control byte inserted roughly every ten pixels. There is no Huffman stage and no lossy compression on the sensor data — which is exactly why the files are large for a 6-megapixel camera, and why converting to AVIF shrinks them so dramatically.
Because they are deliberately not part of the conversion flow. We checked the option surface for this page: on image conversion pages the compression group renders "Quality Preset" and "Specific file size" only, while the percentage-based quality and target-size sliders are reserved for the compression tools. Quality Preset is the control to reach for first; use "Specific file size" when you have a hard byte budget to hit.
No. AVIF is a delivery format — it bakes in one render and discards the raw latitude, so it cannot serve as a negative. For preservation, keep the original .erf files; if you also want a non-raw archival master that a document or print workflow can read, ERF to TIFF is the better companion. AVIF is what you publish, not what you keep.
There is no transparency to keep — an R-D1 photograph is fully opaque, and AVIF's alpha support (via AV1 alpha image items) simply goes unused. Metadata is a different story: an ERF carries EXIF, IPTC, XMP and ICC data plus Epson's own white-balance tag, and a rendered delivery file is not a reliable place to look for all of it. If the shooting data matters to you, keep the original file, which is the only copy guaranteed to hold everything.
AVIF is the AV1 Image File Format, maintained by the Alliance for Open Media; the current specification is version 1.2.0, finalised on 16 October 2025. It stores a subset of an AV1 bitstream inside a HEIF file, which in turn sits on the ISO Base Media File Format — so an AVIF is structurally a close cousin of HEIC, with AV1 in place of HEVC and no patent-licensing questions attached.
They are uploaded over an encrypted connection, rendered and re-encoded to AVIF 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 usually the longest part of the job rather than the encode. For every other output available from the same source, see the ERF converter hub.