Initializing... drag & drop files here
Supports: PEF
A .pef is a Pentax raw — the unprocessed sensor data from a K-series camera, stored in a TIFF-based container that few programs outside Pentax's own software open directly. TIFF is the opposite end of the same family: a fully rendered, lossless, tagged image that print shops, layout software, and archives have read for nearly forty years. This converter demosaics the raw and writes a flat RGB TIFF on our servers, so think of the result as a finished print or archival copy and keep the original .pef as your editable master. The tables below explain what each format actually is before the steps.
| Property | Value |
|---|---|
| Full name | Pentax Electronic File (Pentax Electronic Format) |
| Type | Camera raw — single still, undeveloped sensor data |
| Used by | Pentax K-series DSLRs (and earlier *ist bodies) |
| Container lineage | Built on TIFF — a specialized TIFF variant, like Adobe's DNG |
| Sensor data | Bayer mosaic, typically 12- or 14-bit per photosite |
| Rendering | Custom Image look and white balance stored as instructions, not baked pixels |
| Edits stored in | A separate XMP sidecar file (DNG embeds them instead) |
| Native browser support | None — needs a raw viewer or converter |
| Best for | Archiving the original capture and editing with full latitude |
| Property | Value |
|---|---|
| Full name | Tagged Image File Format |
| First released | Aldus Corporation, autumn 1986 |
| Current spec | TIFF 6.0, published 3 June 1992 |
| Maintained by | Adobe (which acquired Aldus in 1994) |
| Bit depth | 8-bit and higher per channel; the spec allows extended precision |
| Compression | Lossless (None, LZW, Deflate/ZIP, PackBits) or lossy (JPEG) — your choice |
| Native browser support | Limited — not a web format (Safari shows it; Chrome and Firefox do not) |
| Extension | .tiff and .tif are the same format |
| Best for | Print, prepress, layout, scanning, and long-term archival masters |
.pef files onto the page or click "+ Add Files" to browse. You can queue several raw frames from a K-series body and convert them together..tiff or .tif under "File extension" to match your software.Structurally, yes — PEF is a specialized TIFF variant, using the same tagged file layout that DNG also builds on, which is why people describe both Pentax raw formats as "TIFF-based." But shared structure does not mean the pixels copy across untouched. A PEF holds an undeveloped Bayer mosaic, and the converter has to demosaic and develop it into ordinary RGB pixels before writing the TIFF. Whether that output is lossless is decided by your "Compression Type" choice — LZW, Deflate, PackBits, or None — not by the common heritage.
Yes. A PEF is an undeveloped negative: white balance, exposure, highlight recovery, and the Pentax Custom Image look are all still adjustable in a raw editor because they are stored as instructions (often in an XMP sidecar), not baked into pixels. Writing a TIFF forces the converter to demosaic that sensor data and fix the current white balance, exposure, and tone as ordinary RGB. Once it is a TIFF you are editing a finished image, not the raw — so adjust the PEF first if you want control, then convert, and keep the original .pef as your master.
For a true lossless archive or print master, choose LZW, Deflate, or PackBits — all three discard nothing, so every rendered pixel survives, and they are read by Photoshop, Affinity, Lightroom, GIMP, and print RIPs. Deflate (zip-style) usually writes the smallest file; LZW is the most universally recognized by legacy software; PackBits is the simplest and most broadly compatible with very old TIFF readers; None writes the largest, fully uncompressed file. The page defaults to JPEG, which is lossy and is rejected by some prepress tools, so change it unless you specifically only need a smaller flat copy.
No — there is no bit-depth selector on this page. A Pentax sensor records roughly 12- or 14-bit data, and the TIFF specification can carry more than 8 bits per channel, but this converter renders to a standard high-fidelity TIFF rather than letting you hand-pick 8-bit versus 16-bit. For most print and archival uses the rendered TIFF here is plenty; if you specifically need a controlled 16-bit export for heavy grading, do that step from a raw editor that exposes the setting.
The PEF stores a single, compactly packed raw mosaic — one brightness value per photosite behind a color filter array. A TIFF stores fully rendered RGB pixels, three color planes for every pixel, so even with lossless LZW or Deflate the file is substantially larger, and an uncompressed (None) TIFF is larger still. In our testing, a 24-megapixel PEF around 25 MB rendered to a lossless LZW TIFF well over 100 MB, which is normal for a flat RGB image. If file size matters more than edit headroom, render to PEF to JPG or PEF to AVIF instead.
Nothing but the filename. .tiff and .tif are two extensions for the identical Tagged Image File Format; the three-letter .tif exists because some older Windows software expected eight-dot-three names. This page lets you pick either under "File extension," and the bytes are the same. If your workflow specifically wants the three-letter name, the PEF to TIF page produces the exact same file with a .tif extension.
Not reliably. TIFF is a professional and archival format, not a web one: Safari can display TIFFs, but Chrome and Firefox generally cannot, so a TIFF is the wrong choice for a web page or a quick share. Use it for print, layout, scanning, and archival masters, and when you need something that opens everywhere render PEF to JPG, or PEF to AVIF for a small modern web copy.
Your PEF is uploaded over an encrypted connection, rendered into a TIFF on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, and your photos are never shared or made public. The main practical limit on a big upload is its size and the time it takes to send, since Pentax raws often run tens of megabytes each. For privacy-sensitive originals, keep the .pef locally and convert only the copies you need.