Initializing... drag & drop files here
Supports: NEF
A NEF is one still photograph — Nikon's raw sensor readout, with white balance and tone stored as instruction sets rather than baked pixels. WebM is a video container. So this conversion develops the raw file, then holds that single rendered frame on screen for a length you choose. The result is a silent, motionless clip: the right thing for a slate, a placeholder, a title card or a still you need to drop onto a WebM timeline, and the wrong thing if you expected the photo to move.
Unlike the older video targets on this site, WebM does not throw away resolution. VP9 and AV1 have no small-frame ceiling here, so a 45-megapixel Nikon frame comes through at up to 4096 pixels on its long edge. The codec you pick, though, decides whether the quality controls on the page do anything at all — that is the part worth reading below.
.nef onto the page or click "+ Add Files" to browse. Queue several photos if you like; "Merge strategy" then decides between one combined clip ("Merge images", preselected) and one file per photo ("Video per image")..webm. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark.| VP9 (preselected) | VP8 | AV1 | |
|---|---|---|---|
| Quality mode | True constant-quality encoding | None — quantiser bounds only | True constant-quality encoding |
| Quality Preset control | Works: maps to a real quality target | Does nothing useful on a still image | Works |
| Constant Quality slider | Works, 16-63 | Renders but is not applied | Works, 16-63 |
| Constraint Quality "Max bitrate" | Acts as a bitrate ceiling | The only control that bites on VP8 | Acts as a bitrate ceiling |
| Playback reach | Widest of the three inside WebM | Wide but obsolete | Narrower; Safari lists AV1 as partial from 17.0 |
| Verdict for a still photo | Use this | Avoid | Fine if your player handles it |
There is no reason to choose VP8 for a photograph. It predates constant-quality encoding, so with a still source — which has no bitrate for the encoder to scale from — every Quality Preset collapses to the same minimum-rate encode, and the Constant Quality slider that renders next to it is never passed through. If you select VP8 anyway, use Constraint Quality and set the Max bitrate explicitly; that is the one path that reaches the encoder.
On VP9 the preset is translated into a constant-quality target calibrated for a 1080p frame and then nudged for the size of your actual output — larger frames tolerate slightly more compression, so the value shifts by up to two steps in either direction.
| Quality Preset | VP9 quality target at 1080p | Practical description |
|---|---|---|
| Highest | 18 | Visually lossless; largest file |
| Very High (Recommended) | 20 | Near-lossless — the preselected setting |
| High | 25 | Transparent for most viewing |
| Medium | 33 | Standard web quality |
| Low | 40 | Visible softening |
| Very Low | 45 | Obvious artefacts |
| Lowest | 50 | Heavy artefacts, smallest file |
We traced these values out of the encoder configuration this page uses rather than guessing them, which is why they are specific: if you would rather set the number yourself, switch File Compression to "Constant Quality" and use the 16-63 slider directly. Lower is better on that scale, and it opens at 30 — roughly the "Medium" preset — so drag it toward 20 for a still you want to look sharp.
It is a still image, repeated. NEF is a single photograph with no timeline inside it, so the clip holds one rendered frame for however long you set. There is no pan, zoom, Ken Burns motion or transition, and no audio. Uploading several NEF files and choosing "Merge images" produces a slideshow-style clip, but each photo is still a static frame shown for its set duration.
VP9 by default. The WebM container also carries VP8 — the codec it launched with — and this page additionally offers AV1. VP9 is the right pick for a photograph: it supports true constant-quality encoding, which is what makes the Quality Preset meaningful, and any player that handles WebM at all handles it. AV1 compresses harder but decodes more slowly and reaches fewer players; Safari lists it as partial support from version 17.0 (per caniuse).
No. Nikon records 12-bit or 14-bit sensor data depending on the camera, but the render step here outputs 8 bits per channel and the encoders on this page are configured for standard 8-bit profiles. The wide tonal range is compressed down during the develop step, before the video encoder sees anything. If you need to preserve editing headroom, keep the .nef and work from it in a raw editor.
More than most video targets on this site allow. Before encoding, the raw file is rendered to an intermediate image capped at 4096 pixels on its long edge, and VP9 and AV1 impose no further ceiling — so a 45-megapixel frame arrives as roughly a 4K-wide clip rather than being squeezed into a standard video size. Leave Video resolution on "Keep original" to get that; the preset list sets height only and width follows the photo's own aspect ratio.
Because the encoder only has to describe one frame and then say "again" for the rest of the clip. Video codecs spend nearly all their bits on differences between frames, and here there are none, so a five-second clip costs very little more than a single compressed image. A tens-of-megabytes raw file routinely becomes a WebM of a small fraction of that size — which is exactly why WebM is a poor archival target for a photograph and a good delivery target for a slate.
Whatever Image Duration you pick, from a single frame up to 10 seconds, with 5 seconds preselected. Under the hood a still is encoded at one frame per second with B-frames turned off, since neither a higher frame rate nor bidirectional prediction buys anything when every frame is identical. For a longer hold, drop the clip onto a timeline in an editor and stretch it there.
WebM sits at roughly 96% global support (per caniuse), with Chrome from version 25, Firefox from 28 and Edge from 79. The gap is Apple: Safari is listed as partial from 12.1 and fully supported from 16, and Safari on iOS is partial from 12.2 and fully supported from 17.4. If you are sending the file to an unknown recipient, MP4 remains the safer container.
No. The audio section is hidden entirely on image-to-video pages, so the output has no audio track at all. WebM itself carries Vorbis or Opus audio, so you can add a track afterwards in any video editor without re-encoding the picture if your editor supports stream copy.
Your NEF is uploaded over an encrypted connection, developed and encoded on our servers, and deleted automatically after a few hours. Nothing is shared or made public, and there is no sign-up or watermark. With large raw files the practical constraint is upload size and time rather than the encode itself.