Initializing... drag & drop files here
Supports: PEF
PEF is Pentax's proprietary camera raw — one still frame stored as TIFF-based sensor data — and WebM is the open, royalty-free web video container built on Matroska. Converting between them renders your raw and holds that single motionless frame on screen inside a .webm file for a duration you choose, with no audio track. The realistic uses are narrow and specific: a title card or slate for a web-video timeline, a still that an HTML5 player or an upload form will only accept as video, or a short slideshow assembled from several Pentax frames. If you just want the picture, PEF to JPG is the right page.
| Property | Value |
|---|---|
| Full name | Pentax Electronic File |
| Standard | Proprietary to Pentax (Ricoh Imaging); no public specification |
| Underlying structure | TIFF-based raw container |
| Payload | Largely unprocessed sensor readout plus EXIF, white balance and tone metadata |
| Bit depth | 12 or 14 bits per channel, depending on the body |
| Motion / audio | Neither — a single silent frame |
| Native browser support | None; needs raw software |
| Open alternative | Pentax bodies can write Adobe DNG holding the same sensor data |
| Best for | Archiving and full-latitude raw editing |
| Property | Value |
|---|---|
| Full name | WebM, from The WebM Project |
| Standard | Open project, copyright 2010, released under a BSD-style licence |
| Container | A profile of Matroska |
| Video codecs | VP8 and VP9 are the project's own codecs; this page also offers AV1 |
| Audio codecs | Vorbis and Opus — neither applies to an image source |
| Licensing | Royalty-free |
| Native browser support | Chrome 25+, Firefox 28+, Safari 16+, Edge 79+, Opera 16+ — around 96% of tracked browser usage per caniuse |
| Alpha channel | Not written here; transparent areas are filled with the Background Color |
| Best for | Video delivered natively over the open web |
.pef files onto the page or use the file picker. "Merge strategy" opens on "Merge images", which plays several photos back to back in one WebM; "Video per image" writes a separate clip for each.The File Compression group offers three modes — Quality Preset, Constant Quality and Constraint Quality — and the same three render whatever codec you choose. They do not all arrive at the encoder.
| Codec | Quality Preset | Constant Quality (16–63 slider) | Constraint Quality (Max bitrate) |
|---|---|---|---|
| VP9 (default) | Works — maps onto the quality value | Works — drives the VP9 quantiser | Works |
| AV1 | Works | Works — SVT-AV1 accepts 0–63 | Works — quality-based with a rate ceiling |
| VP8 | No effect | No effect — the slider renders but nothing reaches libvpx | Works — this is the only rate control VP8 honours here |
VP8's quality controls are the trap. The encoder has no constant-quality mode of the kind the slider implies, so in that mode neither a quality value nor a bitrate is passed and libvpx falls back to its own internal defaults regardless of where you put the slider. If you specifically need VP8 output, drive it with Constraint Quality and a Max bitrate, or just set the resolution. Otherwise stay on VP9.
Neither. One Pentax raw is one moment, so the converter renders it and shows that frame steadily for the duration you set — no pan, zoom or transition. The audio controls are hidden entirely on image-to-video conversions rather than shown and ignored, so no empty audio track is written either. Upload several photos with "Merge images" selected and they cut from one to the next, but each remains a still.
VP9 unless you change it. The WebM Project's own definition of the format covers VP8 and VP9 with Vorbis or Opus audio; this page additionally offers AV1, which browsers with AV1 decoding will play from a WebM container. VP9 is the sensible default because it compresses well, is supported everywhere WebM is, and — unlike VP8 — its quality slider on this page actually reaches the encoder.
Because VP8 has no constant-quality mode of the sort the control models. On the Constant Quality setting neither a quality value nor a target bitrate is passed through, so libvpx applies its own internal fallback and the slider position makes no difference to the output. The control still renders because the option panel is shared across all three codecs. Use Constraint Quality with an explicit Max bitrate for VP8, or switch to VP9.
No, and a raw file has no transparency to preserve in the first place. VP8 and VP9 can carry alpha in WebM, but this conversion does not write an alpha channel — any area of the output frame not covered by your photograph is filled with the Background Color, which defaults to White for image sources. Pick a different fill colour from the list if white does not suit the project.
If it is large, yes. Each image is re-rendered to a clean PNG first and clamped so its long edge does not exceed 4096 pixels, which is what the video pipeline's image input handles reliably. A 6000 × 4000 Pentax frame therefore reaches the encoder at roughly 4096 × 2730. Set an explicit width and height, a percentage, or one of the height presets under "Video resolution" if you want a specific size instead of that automatic ceiling.
Yes, entirely. A PEF holds 12 or 14 bits per channel of largely unprocessed sensor data, which is exactly what keeps white balance, exposure and highlight recovery adjustable. Encoding it into a video frame demosaics that data and commits to one interpretation in ordinary 8-bit pixels. Make the raw adjustments first if the look matters, and keep the original .pef as your master.
Yes. Upload several .pef files and leave "Merge strategy" on "Merge images" — each rendered still is held for the Image Duration you picked and the frames are concatenated into one WebM. There are no transitions or crossfades; each photo cuts straight to the next. Choosing "Video per image" instead produces one clip per photograph.
WebM if the destination is the open web and you control the player, because it is royalty-free, plays natively in current Chrome, Firefox, Edge, Safari and Opera, and drops straight into an HTML5 video element. PEF to MP4 if the file is going to phones, messaging apps, social platforms or older hardware decoders, where MP4 is still the more reliably accepted container. For a Matroska-based editing or media-server workflow, PEF to MKV is the closer match.
Not to the result. A Pentax body can write either its own PEF or an in-camera Adobe DNG carrying the same sensor readout, so the rendered frame is effectively identical; the practical differences are metadata layout, slightly larger DNG files, and DNG's better odds with software that has not yet been updated for a new camera model.
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 a large batch is upload size and time, since Pentax raw frames commonly run tens of megabytes each.