Initializing... drag & drop files here
Supports: PEF
PEF is Pentax's own raw format — sensor data in a TIFF-structured file, written by Pentax and Ricoh-era bodies alongside the DNG option the camera menu also offers. It is not a legacy format: Ricoh's published specification for the PENTAX K-3 Mark III lists its file formats as "RAW (PEF/DNG), JPEG (Exif 2.3)" and its raw depth as "RAW (14bit): PEF, DNG", so current bodies still write it.
JFIF is the other end of the same photograph's life. It stands for JPEG File Interchange Format — the 1992 document that told everyone how to actually put JPEG-compressed data in a file, formalised nearly twenty years later as ITU-T Recommendation T.871, approved on 14 May 2011, and published by ISO/IEC as 10918-5. In practice a .jfif file is a JPEG. Same compressed data, same decoders, different filename.
| PEF | JFIF | |
|---|---|---|
| What it holds | Undemosaiced sensor readings plus the camera's settings and Exif | JPEG-compressed 8-bit-per-channel RGB |
| Underlying structure | TIFF-based, like most camera raw formats | The JPEG bitstream of ITU-T T.81, in a file with marker segments around it |
| Standardised by | Nobody — it is a vendor format, reverse-engineered by the raw-decoding community | ITU-T T.871 (2011) and ISO/IEC 10918-5, formalising JFIF 1.02 from 1992 |
| Bit depth | 14 bits per channel on current Pentax bodies; fewer on early ones | 8 bits per channel |
| Compression | Lossless or uncompressed depending on the body | Lossy, discrete cosine transform |
| Colour and exposure decisions | Deferred — they live as instructions, not as pixels | Baked in permanently |
| Typical file size | 20-40 MB from a modern body | Under a tenth of that at high quality |
| Opens in a browser? | No | Yes, everywhere |
.jfif. Files are uploaded over an encrypted connection, developed and encoded on our servers, and deleted automatically after a few hours — no sign-up, no watermark.Converting raw to JPEG is a one-way development, and it is worth being explicit about what is spent.
| Held in the PEF | After conversion |
|---|---|
| 14 bits per channel of tonal range | 8 bits per channel — roughly four stops of highlight and shadow recovery gone |
| White balance as an adjustable setting | Fixed. The rendering uses the camera's recorded white balance and you cannot revisit it |
| Undemosaiced Bayer data | Demosaiced once, on our servers, with no chance to try a different algorithm |
| Full sensor area including any masked border | The visible frame only |
| Lens-correction and picture-mode instructions | Applied or ignored at development time; either way they are no longer parameters |
| Exif capture data | JPEG can carry Exif, so the shooting information generally survives the trip |
If any part of that list matters to you, develop the raw properly first. Free, open-source raw developers — RawTherapee, which describes itself as a cross-platform raw image processing program, and darktable, an open-source raw developer that edits non-destructively — let you set exposure, white balance and tone curve deliberately and then export. This page is the right tool when you want the picture out of the raw file quickly and correctly, not when you want to grade it.
For a still that keeps more of the raw file's range, PEF to TIFF writes an uncompressed or losslessly compressed image instead, and PEF to PNG is the lossless option when the destination is a screen rather than a print pipeline.
Not in any way that affects you. Both are JPEG: the same compressed image data, decoded by the same code in every browser, operating system and image editor. JFIF is the name of the specification that defined how to store a JPEG bitstream in a file, so .jfif is a perfectly correct extension for a JPEG — it is simply an uncommon one. You can rename the download to .jpg and nothing about the file changes. The reason people meet the extension at all is that some Windows applications have historically saved or downloaded JPEGs under it.
Because it is deciding what to do by extension rather than by content, and .jfif is rare enough that some applications never registered it. Renaming the file to .jpg fixes it immediately and losslessly. If you would rather not deal with it, PEF to JPG produces the identical conversion under the conventional extension.
Close, but not identical. The camera's own JPEG engine applies Pentax's picture modes, sharpening, noise reduction and lens corrections in a way that only Pentax's own software fully reproduces. A generic raw development renders the same exposure and white balance faithfully but makes its own choices about sharpening and colour rendition. If matching the in-camera look exactly is the goal, Ricoh's Digital Camera Utility is the tool that will do it.
Very High for anything you intend to keep, and Highest if the file is going to be printed or edited further. Raw conversions are unusually revealing of JPEG artefacts because the image has not already been through a camera's noise reduction and sharpening, so ringing around high-contrast edges and blocking in smooth gradients show up at quality levels that would look fine on a re-saved camera JPEG. Medium and below are for the web, and only when size genuinely matters more than the picture.
Not to the result here. Both hold the same sensor data from the same exposure — DNG is Adobe's openly documented raw container and PEF is Pentax's own, and Pentax bodies let you choose between them in the menu. Both are decoded the same way on our servers. DNG's advantage is longevity and universal software support; PEF's is that it is what the camera writes by default on many bodies. If you are choosing for the future, shoot DNG; if you already have PEFs, this page reads them fine.
Yes. Queue as many PEF files as you like and they convert with the same quality and resolution settings, which is normally what you want for a single shoot. Raw files are large, so the upload will be the slow part — a hundred frames from a current Pentax body is several gigabytes. If you are only after web-sized versions, setting a Preset Resolution before converting does not speed up the upload, but it does make the download far smaller.
Because almost everything that makes a raw file big is discarded. A PEF stores 14 bits per channel of undemosaiced sensor data losslessly, so it keeps information you cannot see and detail you have not yet decided how to render. A JPEG stores 8 bits per channel of a single rendered interpretation, compressed by throwing away the high-frequency detail the eye is least sensitive to. A tenth of the size is normal; a twentieth at moderate quality is not unusual.
Generally not. JPEG files carry Exif, so the capture data recorded by the camera — model, lens, exposure settings and any copyright field you set — normally travels across into the output. What does not survive is anything specific to the raw format itself: the Pentax maker-note blocks, the raw processing instructions and the sensor calibration data have nowhere to live in a JPEG. If a particular field matters legally, verify it in the output before deleting the original.
Your PEF files are uploaded over an encrypted connection, developed and encoded on our servers, and both the uploads and the resulting JPEGs are deleted automatically after a few hours. Nothing is shared or made public, and there is no sign-up, no watermark and no account required.