Initializing... drag & drop files here
Supports: ERF
ERF is Epson's proprietary RAW format, written by the R-D1 family of digital rangefinder cameras — sensor data that almost no modern image viewer opens directly. WebP is a widely supported web image format that handles both lossy and lossless compression plus transparency. Converting renders the RAW into a finished WebP you can actually view, embed, and share, while keeping the file small.
| Property | Value |
|---|---|
| Full name | Epson RAW Format |
| Based on | TIFF/EP (TIFF for Electronic Photography) |
| MIME type | image/x-epson-erf |
| Cameras | Epson R-D1 (March 2004), R-D1s, R-D1x |
| Sensor | 6.1 MP APS-C CCD |
| Payload | Bit-packed CFA (Color Filter Array) sensor data, with an 8-bit RGB thumbnail |
| Type | Undeveloped RAW — not directly viewable |
| Best for | Maximum editing latitude straight off the sensor |
| Property | Value |
|---|---|
| Full name | WebP (developed by Google, derived from the VP8 codec) |
| Compression | Lossy and lossless, selectable |
| Transparency | Alpha channel supported in both lossy and lossless modes |
| Typical size | ~26% smaller than PNG (lossless); 25–34% smaller than JPEG at equal SSIM quality |
| Color depth | 8-bit RGB / RGBA |
| Browser support | Chrome 32+, Firefox 65+, Edge 18+, Safari 16+; not supported in Internet Explorer |
| Best for | Viewing, sharing, and embedding photos on the web |
.erf file onto the page, or click "+ Add Files" to browse. You can queue several at once and convert them with the same settings.Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — never shared or made public.
If you need a format every device and editor opens without question, use ERF to JPG instead. Already have a WebP that is larger than you want? Run it through the WebP compressor.
ERF is a niche, effectively discontinued RAW format — Epson left the camera business, so the R-D1 line is the only source of these files. Few current viewers, browsers, or phone galleries can display an ERF directly. Rendering it to WebP turns the raw sensor data into a standard image you can open anywhere, while staying smaller than the equivalent JPEG or PNG.
You lose editing latitude, not necessarily visible quality. A RAW ERF holds the unprocessed sensor data with room to adjust exposure and white balance after the fact. Once it is rendered to WebP (or any standard image), those adjustments are baked in. For viewing and sharing the photo as-is, lossy WebP at a high Quality Preset looks clean; if you plan to edit heavily, keep the original ERF.
For a photograph, lossy WebP is usually the better trade: Google measures lossy WebP at roughly 25–34% smaller than a comparable JPEG at the same SSIM quality, so you get a small file with little visible difference. Choose lossless (set the Lossless toggle to Yes) only when you want an exact pixel-for-pixel result — it is larger, and the benefit is hard to see on continuous-tone camera images.
Treat metadata as not guaranteed to survive. ERF stores Exif (shutter, aperture, ISO, timestamp) in its TIFF/EP structure, but rendering a RAW to a delivery format like WebP commonly drops or trims that block. If the capture details matter, note them before converting or keep the source ERF, which retains the full Exif record.
Because the two store completely different things. An ERF carries bit-packed, full-bit-depth CFA sensor data meant for editing, so it is large. WebP stores a finished, compressed 8-bit RGB image meant for delivery. The size drop is the expected result of developing a RAW into a web image — it is not a sign anything went wrong.
Effectively yes on anything current. Chrome 32+, Firefox 65+, Edge 18+, and Safari 16+ all display WebP, which covers the large majority of browsers in use today. The main exception is Internet Explorer, which never added WebP support. In our testing, a single 6.1 MP ERF rendered at Very High quality produced a WebP around 1–2 MB — small enough to email or post without further compression.