Initializing... drag & drop files here
Supports: PEF
A Pentax .pef is one photograph; MKV is Matroska, a container designed to hold an arbitrary number of independently typed streams. Putting a still inside it produces a legitimate but unusual file: one video track holding a single motionless frame, no audio track at all, and a duration you choose. That is genuinely useful if your editor, media server or archive tool prefers Matroska — and needlessly awkward if what you wanted was a picture. This page compares the realistic targets so you pick once and stop.
| MKV (this page) | MP4 | A still image | |
|---|---|---|---|
| What it is | Matroska, an open multi-track container | ISO base media container | JPG, PNG or TIFF |
| Result from one PEF | One frame held for a set duration | Same | The picture itself |
| Playback on phones and TVs | Patchy on stock players | Near universal | Universal |
| Playback in editors and media servers | Excellent — Matroska is a favourite of both | Excellent | N/A |
| Codec freedom | Very wide — 21 video codecs render on this page | Narrower, tuned for compatibility | N/A |
| Audio from a photo | None; the audio controls are hidden | None | N/A |
| Streaming to a browser | Not directly | Yes | Yes |
| File size from one photo | Small — repeats compress to almost nothing | Small | Smallest |
| Right when | Your Matroska-based pipeline asked for it | You need it to just play | You wanted a photo all along |
.mkv at all..pef files onto the page or use the file picker. "Merge strategy" opens on "Merge images", which concatenates several photos into one MKV; "Video per image" writes a separate file for each.| Codec | Quality control from a still | Sensible use |
|---|---|---|
| H.264 (default) | Constant Quality slider on a 16–51 CRF scale | The safe answer; decodes everywhere |
| H.265 | 0–51 CRF | Smaller than H.264 at the same look; heavier to decode |
| VP9 and AV1 | 0–63 CRF | Best compression; slowest encode |
| MPEG-4, Xvid, DivX, WMV 1/2, MS MPEG-4, MPEG-1, FLV | Constant Quality re-scales to a 1–31 quantiser, where lower is better; the Quality Preset has no source bitrate to work from | Legacy compatibility only |
| MPEG-2 | Treat resolution as the only reliable control | Legacy authoring workflows |
| MJPEG | 2–31 quantiser scale | Frame-accurate scrubbing in old tools |
| HuffYUV | Quality controls render but have nothing to act on — the codec is mathematically lossless | Intermediate for further editing; very large files |
Neither, from a single photograph. The converter renders the raw and shows that one frame steadily for the duration you set — no pan, no zoom, no transition — and writes no audio track. Matroska treats every stream as an independent typed track, so a file with video and nothing else is completely well-formed rather than damaged. Upload several photos and choose "Merge images" and they will cut from one to the next, but each still remains motionless.
H.264, and usually no. It is decoded by essentially every current player, editor and phone, and for a single unchanging frame the compression differences between codecs barely matter — there is almost nothing to compress after frame one. Change it only for a specific downstream reason: HuffYUV if you want a lossless intermediate, VP9 or AV1 if the file is heading somewhere that prefers them, MPEG-2 for legacy authoring.
Because the preset works by scaling a source bitrate, and a photograph does not have one. On CRF-based codecs — H.264, H.265, VP9, AV1 — the preset maps onto a quality value and behaves normally. On the older quantiser-based codecs in the list there is no bitrate to scale from, so the preset has nothing to act on. On those, use Constraint Quality with an explicit Max bitrate, or simply set the resolution, which always works.
Because the input is an image. On image-to-video conversions the entire audio group is hidden rather than shown and ignored, so you are never offered a codec that could not be applied. If you need a soundtrack, produce the MKV here and add audio in a video editor, which is also where any motion would come from.
If it is very large, yes. Each image is re-rendered to a clean PNG before encoding and clamped so its long edge does not exceed 4096 pixels, because that is what the video pipeline's image input handles reliably. A 6000 × 4000 frame therefore reaches the encoder at roughly 4096 × 2730. Set an explicit width and height, a percentage or a height preset under "Video resolution" if you want a specific size instead.
Yes. A PEF holds 12 or 14 bits per channel of largely unprocessed sensor data, which is what keeps white balance, exposure and highlight recovery adjustable. Rendering it into a video frame demosaics that data and commits to one interpretation in 8-bit pixels. Adjust the raw first if the look matters, and keep the .pef as the master.
Your picture's aspect ratio does not match the chosen output frame, and the leftover area is filled with the Background Color, which defaults to White for image sources. Either pick a "Video resolution" whose proportions match the photograph — the height presets keep your source aspect ratio, so they avoid bars entirely — or choose a different fill colour from the list.
No. Pentax bodies can write either their own PEF or an in-camera Adobe DNG carrying the same sensor readout, so the rendered frame is effectively identical; the differences are in metadata layout and file size. For those files use DNG to MKV.
They are uploaded over an encrypted connection, rendered and packaged on our servers, and deleted automatically after a few hours. 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 files commonly run tens of megabytes each.