Add your PEF file
Drop one or more .pef files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Developing a .pef camera file into .avif turns unprocessed sensor data into a finished image any app can open. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Developing a .pef camera file into .avif turns unprocessed sensor data into a finished image any app can open. A .pef file is a Pentax Electronic File, the proprietary RAW format of Pentax DSLRs now produced under Ricoh Imaging. Pentax is unusual in offering photographers an in-camera choice between .pef and Adobe's open DNG, making it one of the few brands to treat its native RAW as optional.
An .avif file stores a still image (or sequence) coded with the AV1 video codec inside a HEIF-derived container. It is currently among the most efficient image formats deployed on the web, routinely beating JPEG by half at similar quality while adding HDR, wide gamut, and alpha. For this route the practical draw is best-in-class compression among widely supported web formats and 10/12-bit HDR and wide-gamut color, which JPEG cannot represent — balanced against encoding is much slower than JPEG or WebP, especially at high effort settings, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .pef, smaller ecosystem than Canon/Nikon/Sony formats, so niche tools sometimes lag. Switching to .avif buys you best-in-class compression among widely supported web formats, which is why it is the better fit for serving hero images and photo galleries where bandwidth savings are significant. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | Pentax RAW (.pef) | AVIF image (.avif) |
|---|---|---|
| Format type | Lossless — every pixel or sample is preserved exactly | Lossy — discards detail it judges invisible to shrink files |
| How it stores data | tIFF-based structure holding 12- or 14-bit Bayer mosaic data depending on body generation | encodes AV1 intra frames; both lossy and a mathematically lossless mode are defined |
| Strongest at | raw development from Pentax K-mount DSLRs and the 645 medium-format line | serving hero images and photo galleries where bandwidth savings are significant |
| Weak spot | smaller ecosystem than Canon/Nikon/Sony formats, so niche tools sometimes lag | encoding is much slower than JPEG or WebP, especially at high effort settings |
| Metadata | full EXIF with Pentax MakerNotes covering lens ID, shake-reduction state, and drive modes; XMP edits are stored in sidecar files by mainstream editors | eXIF and XMP are stored as metadata items in the HEIF container alongside ICC profiles or CICP color signaling, and mainstream encoders preserve them on conversion |
Drop one or more .pef files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .avif in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if AVIF is selectable, the route is real and validated.
Press Convert. A LibRaw WebAssembly decoder demosaics the sensor data in your browser and renders a developed image ready for export.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid AVIF file. Outputs keep the original filename with the .avif extension.
Some. Since pef is lossless-oriented and avif is lossy-oriented, the encoder will discard detail it judges least visible; the quality slider controls how aggressive that is. Keep the original .pef if you may need a pristine master later.
Yes — the .pef file is processed inside your browser tab and never uploaded. A LibRaw WebAssembly decoder demosaics the sensor data in your browser and renders a developed image ready for export. Close the tab and the file is gone from memory.
Chrome 85+ (2020), Firefox 93+ (2021), and Safari 16+ (2022) render AVIF natively, covering the overwhelming majority of current browsers. On the desktop, macOS 13+ and Windows (via the AV1 Video Extension) preview it, but plenty of older editing and printing software cannot open it yet.
Smaller, usually dramatically so — that is the main reason this route exists. The quality slider trades size against fidelity; the default sits at the point where most people cannot spot the difference.
In .pef, full EXIF with Pentax MakerNotes covering lens ID, shake-reduction state, and drive modes; XMP edits are stored in sidecar files by mainstream editors. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.