Initializing... drag & drop files here
Supports: NEF
Turning a Nikon RAW still into a Flash Video file is a legacy job: Adobe stopped supporting Flash Player on 31 December 2020 and began blocking Flash content from running on 12 January 2021, so an .flv today is almost always destined for an old CMS, an ingest pipeline, or a media server that still scans for the extension. The one decision that matters on this page is which of the four codecs goes inside the container — and the codec the dropdown opens on is not the one we would pick. Here is the comparison, with numbers we measured.
| Codec (label in the dropdown) | What it really is | Rate control | Suitable for a 24 MP photo? |
|---|---|---|---|
| FLV — selected by default | FLV1 / Sorenson Spark, the H.263-derived codec Flash used before AVC support arrived | Quantizer 1–31, where 1 is best | Works, but hits a hard quality ceiling |
| H.264 | The same AVC encoder our MP4 targets use, carried inside the FLV container | CRF 0–51, where 0 is best | Yes — the best choice here by a wide margin |
| Flash Video | Flash Screen Video, a screen-recording codec | None — lossless, rate control is ignored | No. Its encoder rejects inputs wider than 4095 pixels, and at that size the keyframe overruns the FLV container's 16 MB packet limit |
| Flash Video (v2) | Flash Screen Video 2, same purpose | None — lossless | Only after downscaling. Same 4095-pixel input limit |
The two Flash Screen Video entries deserve a warning rather than a recommendation. They exist for screencasts — long stretches of unchanging desktop — and they store photographic detail extremely inefficiently. There is also a mechanical trap: our pipeline normalises every uploaded image to a maximum of 4096 pixels on the long edge, which is exactly one pixel past what those encoders accept. Leave Video resolution on Keep original with a modern Nikon file and they cannot run at all; choose a resolution preset first and they will.
We encoded a 4096 × 2730 photographic test frame through this page's settings — 1 frame per second, five seconds, B-frames disabled — and measured output size and PSNR against the source:
| Setting | Output size | PSNR |
|---|---|---|
| Sorenson Spark, quality value 23 (where the slider opens) | 312,246 bytes | 39.66 dB |
| Sorenson Spark, quality value 8 | 316,474 bytes | 39.71 dB |
| Sorenson Spark, quality value 4 | 486,034 bytes | 40.21 dB |
| Sorenson Spark, quality value 2 (its practical best) | 1,879,366 bytes | 43.30 dB |
| H.264, CRF 33 — matched to Spark's best size | 1,877,502 bytes | 43.88 dB |
| H.264, CRF 18 | 7,453,894 bytes | 58.79 dB |
Two conclusions fall out of that. First, Sorenson Spark saturates: values between roughly 14 and 31 produced byte-identical output in our runs, so most of the slider's range does nothing, and no setting took it past about 43 dB. H.264 kept improving all the way to 58.79 dB. Second, at a matched file size H.264 was already ahead — and it has headroom Spark simply does not have.
.flv files will handle it..nef onto the page or click "+ Add Files". Nikon RAW is one of two RAW extensions with a dedicated preview path here, so the thumbnail normally appears.Because on Sorenson Spark that control is not a CRF at all — it is an H.263-style quantizer clamped to the range 1–31, and past a certain point the encoder is already discarding everything it can. In our measurements values from roughly 14 through 31 produced byte-identical files at 312,246 bytes and 39.66 dB. The useful part of the range is the low end: 2 gave 1.88 MB at 43.30 dB. Remember the direction is inverted compared with H.264's CRF — lower means better on both, but the scales are not comparable.
It is mislabelled rather than broken, and it opens at an unhelpful value. The Constant Quality field is shared across every codec we support, so it carries the CRF label everywhere; on Sorenson Spark, WMV, MPEG-4 and the H.26x family the value is passed through as a quantizer instead, restricted to 1–31. Because the shared default is 23, the slider starts near the worst end of that 31-point scale rather than in the middle. Type a low number and it behaves exactly as you would expect.
Constant Quality. Quality Preset works by scaling the source video's bitrate, and a NEF is a photograph — it has no bitrate to scale, so there is nothing for the preset to compute from. That is specific to still-image sources; on a video-to-video conversion the same preset works normally. On this page, choose Constant Quality (or Constraint Quality if you want to cap the peak rate) and set the value yourself. If a conversion ever fails to produce a file, switching away from Quality Preset is the first thing to try.
Yes. FLV is a container rather than a codec, and AVC-in-FLV became standard long before Flash itself was retired — every FLV player and library written after that point handles it. We confirmed our own output by probing a finished file: the container reports as flv with an h264 video stream inside. The only reason to stay on Sorenson Spark is if the receiving software genuinely predates AVC support.
A NEF is a single still photograph with no soundtrack and no timeline, so the Audio Codec panel does not render on this page at all and the file is written video-only rather than with a silent placeholder track. The output holds one developed frame for the length you set under Image Duration, encoded at 1 frame per second with B-frames disabled because every frame is identical. Add a soundtrack afterwards in a video editor.
Because of a size limit rather than anything to do with the photo. Flash Screen Video encoders accept inputs up to 4095 pixels, and our pipeline normalises every uploaded image to a clean PNG capped at 4096 pixels on the long edge — a modern Nikon file lands exactly on that boundary, one pixel too wide. Even at 4095 the first keyframe of a photograph exceeded the FLV container's 16 MB per-packet limit in our test. Choose a Video resolution preset first, or better, use H.264, which has neither problem.
Only for compatibility with something that already exists. Adobe stopped supporting Flash Player on 31 December 2020 and started blocking Flash content on 12 January 2021, so nothing new is being built on it. The remaining real uses are old media servers, archive ingest paths, and content-management systems whose upload validators still look for .flv. If the requirement is soft, NEF to MP4 gives you a file that plays on every phone, browser and editor.
No. Nikon keeps white balance, hue, tone and sharpening as instruction sets inside the NEF instead of applying them to the sensor data, which is what makes RAW re-editable. Encoding video forces the pipeline to demosaic and develop that data into ordinary 8-bit video pixels and then compress them, so the 12-bit or 14-bit latitude is gone from the output. Keep the .nef as your master; NEF to TIFF is the right target if you want a still you can keep editing.
Less than you might hope, and the clamp is the reason. Before encoding, every image is re-encoded to PNG and limited to 4096 pixels on the long edge, so a 6000 × 4000 Nikon frame becomes 4096 × 2730 regardless of what you choose under Video resolution — that ceiling is not adjustable. Below it you have full control through Keep original, a fixed width × height, or a height-only preset. For a still that keeps every original pixel, use NEF to PNG or browse the NEF converter hub for other targets.