Initializing... drag & drop files here
Supports: PEF
PEF is Pentax's proprietary camera raw format — a TIFF-based file holding 12 or 14 bits per channel of largely unprocessed sensor data — and GIF is a 1980s indexed-colour bitmap capped at 256 colours per image. Converting one to the other is a very large step down in colour fidelity, and it is worth understanding exactly what the format is doing before you decide it is what you need. The two honest reasons to be on this page are a legacy system that accepts nothing but .gif, and building an animation out of several Pentax frames. For a picture you actually want to look at, PEF to JPG or PEF to PNG is the right target.
| Property | Value |
|---|---|
| Full name | Pentax Electronic File |
| Standard | Proprietary to Pentax (Ricoh Imaging); no public specification |
| Underlying structure | TIFF-based raw container, identified by a PENTAX maker string |
| Payload | Largely unprocessed sensor readout plus EXIF, white balance and tone metadata |
| Bit depth | 12 or 14 bits per channel, depending on the camera body |
| Colour model | Bayer-filtered mosaic, demosaiced at render time |
| Animation | None — one frame per file |
| Open alternative | Pentax bodies can write Adobe DNG instead, holding the same sensor data |
| Best for | Archiving and full-latitude editing |
| Property | Value |
|---|---|
| Full name | Graphics Interchange Format |
| Standard | CompuServe; the GIF89a specification document is dated 31 July 1990, superseding GIF87a |
| Compression | Variable-length-code LZW, lossless within the palette |
| Colour | Indexed palette, a maximum of 256 entries per colour table |
| Transparency | Single fully transparent palette index — no partial alpha |
| Animation | Yes — multiple frames stored sequentially in one file |
| Bit depth | 8 bits per pixel of palette index |
| Native support | Universal; every browser and image viewer since the 1990s |
| Best for | Short loops, flat graphics and legacy compatibility |
.pef files onto the page or use the file picker. One file gives you a single-frame GIF; several files can be merged into one animation.The page shares one option panel across the still and the animated routes, so some controls render even when they cannot change a one-frame result. This is what each one does when you upload exactly one .pef:
| Control | Effect on a single PEF | Effect on several merged PEFs |
|---|---|---|
| Colors (File Compression → Custom) | Applied — sets the palette size passed to the encoder | Applied |
| Dither checkbox (File Compression → Custom) | No effect — Floyd–Steinberg error diffusion is applied regardless | No effect |
| Image quality (%) (File Compression → Custom) | No effect on the single-still route | Applied on the animated route |
| Framerate | No effect — one frame has no rate | Applied — sets the animation speed |
| Image resolution (File Compression → Custom) | Applied | Applied |
| Combine? | No effect with one file | Chooses one animation versus separate files |
Two mechanisms stack. GIF stores at most 256 colours, so millions of distinct tones from the sensor are quantised down to a tiny palette — that produces the visible steps across skies and skin known as banding. The converter then applies Floyd–Steinberg error diffusion, which scatters palette colours in a fine pattern to fake the tones that are missing, and that shows up as grain. Both are inherent to indexed colour, not faults in the conversion.
Not on this page. The dither toggle renders as part of the colour-reduction group, but the single-image route hard-codes Floyd–Steinberg error diffusion, so switching it makes no difference to the output. If flat, undithered colour is what you want, reduce the palette hard with the Colors option — at 16 or 8 colours the posterisation becomes a deliberate look rather than an accident — or use PEF to PNG, which keeps full colour without a palette.
Because dithering destroys the redundancy GIF's compressor depends on. LZW works by finding repeated byte sequences, and error diffusion deliberately makes neighbouring pixels differ so the eye blends them — which is close to the worst case for that algorithm. A dithered, full-resolution photographic GIF can easily end up several times the size of a JPEG that also looks better. Scaling the image down first is the single most effective fix.
No. On a single still the conversion goes through the palette-based image path, which reads the resolution and the colour count and nothing else — GIF has no JPEG-style quality dial to turn. That slider becomes meaningful only when several images are merged into an animation, where it feeds the animated encoder. For one frame, use Colors and resolution to control the result.
Yes, and it is the most useful thing this page does. Upload several .pef files, leave "Combine?" on "Single animation", and pick a rate from the Framerate list — the entries run from 1 FPS as a slideshow through 10 FPS, which is preselected, up to 50 FPS. Each raw is rendered, the frames are normalised to a shared canvas, and they are assembled into one animated GIF. Reduce the resolution first unless you want a very large file.
Entirely. A PEF is an unprocessed negative: white balance, exposure and highlight recovery all remain adjustable while the file stays raw, because it holds 12 or 14 bits per channel. Rendering to GIF commits to one interpretation and then throws away all but 256 of the resulting colours. Keep the original .pef as your master and treat any GIF as a disposable export.
Not the result. Pentax bodies can write either their own PEF or an Adobe DNG holding the same sensor readout, so the rendered picture is effectively identical; the practical differences are metadata layout, slightly larger DNG files, and DNG's better odds with software that has not been updated for a new camera. For those files use DNG to GIF.
Only crudely. GIF can mark exactly one palette entry as fully transparent, so a pixel is either completely opaque or completely invisible — there is no partial alpha, which is why GIF cut-outs show hard, jagged edges against a coloured background. PNG supports a full 8-bit alpha channel and is the correct choice if you need soft edges.
Your .pef 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 real constraint on large batches is upload size and time, since Pentax raw frames often run tens of megabytes each.