Initializing... drag & drop files here
Supports: PEF
A Pentax .pef and an .avif are answers to two completely different questions. PEF is a negative: TIFF-based sensor data at 12 or 14 bits per channel, meant to be worked on. AVIF is a delivery print: an AV1-coded picture built to be small, sharp and fast to load. The short answer, if you are here for one, is keep the PEF as the master and convert a copy to AVIF whenever the file is going onto a page, into an app, or to someone who just needs to look at it.
| Property | PEF | AVIF |
|---|---|---|
| Full name | Pentax Electronic File — proprietary Pentax raw | AV1 Image File Format |
| Standard body | None published; Pentax proprietary | Alliance for Open Media (current spec version 1.2.0) |
| Underlying structure | TIFF-based raw container | ISO base media container carrying an AV1-coded image |
| Bit depth | 12 or 14 bits per channel of sensor readout | 8, 10 or 12 bit supported by the format |
| Compression | Lossless or near-lossless raw packing | Lossy or lossless AV1 |
| Transparency | Not applicable | Supported by the format |
| Editing latitude | Full — white balance, exposure and tone remain adjustable | None — the render is fixed in pixels |
| Native browser support | None; needs raw software | Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+, Opera 71+ — around 95% of tracked browser usage per caniuse |
| Typical size | Tens of megabytes per frame | AOMedia cites over 50% savings versus JPEG and over 30% versus WebP |
| Open alternative | Pentax bodies can write Adobe DNG instead | — |
.pef files onto the page or pick them with the file browser. Several raw frames can be queued and converted with identical settings.| Preset | Encoder quality value | Reasonable use |
|---|---|---|
| Highest | 100 | Near-transparent quality; largest AVIF |
| Very High (default) | 95 | Portfolio and hero images |
| High | 90 | General web delivery |
| Medium | 80 | Gallery thumbnails and grids |
| Low | 70 | Low-priority or below-the-fold imagery |
| Very Low | 60 | Bandwidth-constrained placeholders |
| Lowest | 50 | Preview-only; visible softening |
Completely, and that is the whole point of the trade. A PEF stores 12 or 14 bits per channel of largely unprocessed sensor readout, so exposure, white balance and highlight recovery are still live decisions. Writing an AVIF requires demosaicing that data and committing to one interpretation. Make your raw adjustments first, convert the result, and keep the original .pef as the master you can always go back to.
For the same perceived quality, generally yes — AOMedia's own specification page cites savings of over 50% against JPEG and over 30% against WebP. The gain is largest on the kind of content a Pentax sensor produces: broad gradients, out-of-focus backgrounds and fine natural texture. It is smallest on images that are already tiny or already heavily compressed, where there is little redundancy left to remove.
Per caniuse, AVIF is supported in Chrome from version 85, Firefox from 93, Safari from 16.4, Edge from 121 and Opera from 71, which adds up to roughly 95% of tracked browser usage. Desktop application support is patchier than browser support — recent macOS and Windows builds, GIMP and current Adobe releases handle it, but plenty of older viewers and utilities still do not. If the recipient's software is unknown, PEF to JPG removes the guesswork.
By re-encoding and measuring. The converter renders the raw, encodes it, compares the result against your target, and then binary-searches the quality value until it finds the highest setting that still fits. With "Auto Scale" enabled it is also allowed to reduce the pixel dimensions as part of that search. If even the lowest quality still exceeds your target, you get the smallest file the encoder could produce rather than a failure.
No. The AVIF format itself supports lossless mode, 10- and 12-bit colour and speed tuning, but this page exposes only the quality controls and the resolution controls — a quality preset, an exact target size, and the resize options. Treat the output as a standard-range delivery copy. If you need a raster master you can keep editing, render to PEF to TIFF and switch its Compression Type to LZW — the default there is JPEG, which is lossy.
AVIF usually wins on file size at equal quality, and it handles gradients and wide tonal range better, which suits landscape and portrait work from a Pentax body. WebP wins on reach and on encode speed, and it is understood by a longer tail of older software. A practical pattern is AVIF as the primary asset with a WebP or JPEG fallback; PEF to WebP produces the fallback from the same raw.
They share a codec but not a purpose. AV1 is the Alliance for Open Media's video codec; AVIF applies the same intra-frame coding tools to a single still image and stores it in an ISO base media container. That shared ancestry is why AVIF compresses so well. If you actually want a video clip out of a Pentax frame rather than a picture, PEF to AV1 is the page for that.
Do not count on it. AVIF can carry EXIF, but a raw-to-delivery render is a re-authoring step rather than a copy, and metadata handling varies with the settings applied. If shooting data matters for cataloguing, keep the .pef — it holds the original EXIF and Pentax maker notes intact — and treat the AVIF purely as an output.
It is uploaded over an encrypted connection, rendered and encoded on our servers, and deleted automatically after a few hours. There is no sign-up, no watermark, and nothing is shared or made public. The practical limit on large batches is upload size and time, since Pentax raw frames commonly run tens of megabytes each.