Initializing... drag & drop files here
Supports: PEF
PEF is Pentax's proprietary camera raw format — one still photograph, stored as TIFF-based sensor data — and AV1 is the Alliance for Open Media's royalty-free video codec. So this is not a picture-to-picture conversion: the server renders your raw, then encodes that single motionless frame as a short, silent AV1 clip held on screen for a duration you choose. This tutorial covers the four steps, the two controls that genuinely change the output, the .av1 filename problem that trips almost everyone up, and the point at which you should stop and use PEF to JPG instead.
.pef files onto the page or use the file picker. Queue as many raw frames as you like — with "Merge strategy" on its default "Merge images" they become one clip that plays them back to back, while "Video per image" writes a separate file per photo.A still photograph is the easiest thing a modern video encoder will ever see. There is exactly one frame of real information and everything after it is a repeat, so most of the knobs you would reach for on a real video barely register here. These are the ones that do something:
.av1 extension. Most players decide what to do from the file name, and .av1 is not a container name they know. Rename the file to .mkv — the bytes are unchanged — and VLC, mpv and most editors will open it immediately. For maximum reach, run it through AV1 to MP4.| Property | PEF (input) | AV1 (output here) |
|---|---|---|
| Kind of thing | Still photograph | Video codec, wrapped in Matroska |
| Origin | Pentax (Ricoh Imaging), proprietary | Alliance for Open Media, royalty-free |
| Underlying structure | TIFF-based raw container | Matroska container, .av1 file name |
| Specification | Not publicly published by Pentax | AV1 1.0.0 released 2018; current published text is v1.0.0-errata1 |
| Bit depth | 12 or 14 bits per channel of sensor data | 8-bit encode on this page |
| Audio | None | None — the image path writes no audio track |
| Editing latitude | Full: white balance, exposure and tone stay adjustable | None: the render is baked into pixels |
| Best for | Archiving and raw editing | A photo asset destined for a video timeline |
| Control | Default | What it changes |
|---|---|---|
| Merge strategy | Merge images | One combined clip versus one file per photo |
| Image Duration | 5 seconds | How long each still is held, from 1/60 s up to 10 s |
| Background Color | White | Fill colour for letterbox or pillarbox bars |
| Video Codec | AV1 | Fixed on this page — AV1 is the only entry |
| File Compression | Quality Preset | Preset ladder, 0–63 CRF, or CRF plus a Max bitrate cap |
| Video resolution | Keep original | Height presets, percentage, or explicit width × height |
A video file. AV1 is a video codec, and this page produces a short clip that displays your single Pentax frame for the duration you set. The still-image relative of AV1 is AVIF — the AV1 Image File Format, defined by the same Alliance for Open Media — and if a compact modern picture is what you actually want, use PEF to AVIF instead.
.av1 file play by double-clicking it?Because .av1 is not a container name. What the converter writes is a standard Matroska file; only the extension is unusual, and most desktop players route files to a demuxer based on that extension. Rename the download to .mkv and it will open in VLC, mpv and the majority of editors without re-encoding anything. If you need it to preview in a browser or on a social platform, convert it with AV1 to MP4.
Intel's SVT-AV1, chosen because it encodes far faster than the libaom reference encoder at comparable quality. Its CRF scale runs from 16 to 63, which is why the Constant Quality slider on this page spans that range rather than the 16–51 range you see on H.264 targets. Around 30 sits at the encoder's own neutral setting.
Because the source is a photograph. On image-to-video conversions the whole audio group is hidden rather than left visible and inert, so you are never offered a codec that could not be used. If you need music or narration, add it afterwards in a video editor, or convert to a container your editor prefers such as PEF to MKV.
Yes, completely. A PEF is an unprocessed negative — white balance, exposure, highlight recovery and tone curve are all still adjustable while it stays raw, because the file holds 12 or 14 bits per channel of sensor data. Encoding it into an 8-bit AV1 frame bakes the current interpretation into ordinary pixels. Adjust the PEF in raw software first if the look matters, and keep the original .pef as your master.
If it is very large, yes. Before encoding, each image is re-rendered to a clean PNG and clamped so its long edge is no more than 4096 pixels, because that is the size ffmpeg's image input handles reliably. A 6000 × 4000 Pentax frame therefore enters the encoder at about 4096 × 2730. Set an explicit resolution yourself if you want a specific output size rather than that automatic ceiling.
Yes. Upload multiple .pef files and leave "Merge strategy" on "Merge images" — each rendered frame is held for the Image Duration you picked, and they are concatenated into one AV1 clip. There are no transitions or crossfades between them; each photo cuts straight to the next. Choosing "Video per image" instead gives you one clip per photo.
Usually far less time than the same duration of real footage, because only the first frame contains new information and the rest are near-perfect repeats that AV1's inter-frame prediction disposes of cheaply. The dominant cost is normally the upload itself, since Pentax raw files commonly run tens of megabytes each. The practical ceiling on a big batch is upload size and time, not encoding.
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 and no watermark, and your files are never shared or made public.