Initializing... drag & drop files here
Supports: DNG
A DNG is a still photo — a camera RAW file — while OGV is an Ogg video container. Converting one to the other does not "play" the photo; it wraps your single DNG frame into a short, silent video clip that shows that one image for a set duration. This is useful when a slideshow tool, web player, or upload form only accepts video, but for a normal photo you almost always want DNG to JPG or DNG to TIFF instead.
| Property | Value |
|---|---|
| Full name | Adobe Digital Negative |
| Type | Still image (camera RAW) |
| Based on | TIFF 6.0 / TIFF-EP container |
| Published | 2004 by Adobe; openly documented (current spec 1.6, Dec 2021) |
| Bit depth | Typically 12–14 bits per channel of linear sensor data |
| Contains | Unprocessed sensor data plus EXIF, white-balance, and lens metadata |
| Best for | Archiving RAW captures, non-destructive editing |
| Property | Value |
|---|---|
| Full name | Ogg Video |
| Type | Video container (Xiph.org Ogg) |
| Video codec here | VP8 by default (Theora and VP8 are both selectable) |
| Audio | None — a DNG has no sound, so the clip is silent |
| Bit depth | 8 bits per channel (the RAW's wide latitude is baked down) |
| Browser support | None by default — Chrome disabled Theora at v120 and Chromium removed it at v123 (March 2024), Firefox disabled it at v126; Safari never shipped it |
| Best for | Legacy Ogg pipelines; otherwise prefer MP4 or WebM |
No. A DNG is a still photo with no audio track, so the resulting OGV is a silent video showing your single frame for the duration you set. The audio codec option is hidden for image-to-video conversions because there is nothing to encode.
By default our OGV output uses VP8 video inside the Ogg container, and you can switch to Theora under the video codec advanced option. We default to VP8 because Theora is effectively obsolete — Chrome disabled Theora by default in version 120 and Chromium dropped the built-in decoder in 123 (March 2024), Firefox disabled it by default in 126, and Safari never supported it.
The only practical reason is a destination that accepts video but not photos — some slideshow makers, web players, social uploaders, or kiosk displays. If you just want a viewable or shareable picture, convert to DNG to JPG, DNG to PNG, or DNG to TIFF instead; those keep the image as an image.
Yes. DNG stores 12–14 bits per channel of unprocessed sensor data so you can recover highlights and shadows in an editor. Any video, OGV included, is 8 bits per channel with the white balance and tone curve already baked in, so the wide latitude that makes RAW useful does not survive the conversion. Edit the DNG first if you need to.
Yes. Upload all the DNGs, choose "Merge images," and set "Image Duration" to control how long each photo holds on screen. The files are stitched into a single Ogg clip in upload order. In our testing, a single 24-megapixel DNG set to 5 seconds at the "Very High" preset produced a roughly 2–4 MB silent OGV, depending on image detail.
Often not. Because modern browsers dropped Theora and have only patchy Ogg support, an .ogv can fail to play for many viewers. If your goal is a clip that plays everywhere, convert your DNG to MP4 (H.264, near-universal) or WebM (VP9, native in Chrome, Firefox, and Edge) instead of OGV.
No. The Ogg video container has no place for photographic EXIF, so the camera model, lens, exposure, white balance, and any GPS coordinates stored in the DNG are dropped when the frame is baked into video.
If you need that metadata to survive, convert to a still image such as DNG to JPG or DNG to TIFF instead — both carry EXIF, whereas a video wrapper discards it.
Desktop players like VLC and mpv still open Ogg video, so an .ogv is not unplayable — just inconvenient. Because Chrome disabled Theora at version 120 and Chromium removed the decoder at 123, Firefox disabled it at 126, and Safari never shipped one, handing an .ogv to a general audience is risky; MP4 or WebM is the safer share.