PNG to OGV Converter

How to Convert PNG to OGV Online

1. Upload Your PNG Files: Drag and drop or click "Add Files" to select one or many PNGs (ISO/IEC 15948). Screenshots, exported frames, slide exports, and rendered graphics all work. Batch is supported — drop in an entire folder for an image-sequence slideshow.
2. Pick a Merge Strategy: Choose "Merge images" to stitch every uploaded PNG into a single OGV video in upload order, or "Video per image" to emit one OGV per PNG. Merge is the right choice for slideshows, time-lapse stacks, and rendered animation frames.
3. Set Image Duration and Background Color: Use the Duration dropdown to control how long each frame is held — from 1/60s (a single frame at 60 fps) up to 10 seconds per image. Pick a Background Color (black by default) which fills any letterbox area when frames don't match the output aspect ratio.
4. Choose a Quality Preset and Resolution: Quality Preset offers Highest, Very High (Recommended), High, Medium, Low, Very Low, and Lowest. Keep Resolution on "Original," pick a preset (4320p down to 144p, plus social aspect ratios like 1080×1920 and 1080×1350), or enter exact width/height in pixels or percent. Click Convert. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared.

The default video codec for OGV output is VP8 with Vorbis audio. For maximum compatibility with Wikimedia Commons and other patent-strict pipelines, switch the Video Codec dropdown to Theora under Advanced Options — Theora in an Ogg container is the historically standard OGV stream.

Why Convert PNG to OGV?

OGV (Ogg Video) is the Xiph.Org Foundation container that pairs Theora video with Vorbis audio. Both codecs are royalty-free and patent-unencumbered, which is why Wikimedia Commons accepts OGV alongside WebM but rejects MP4, MOV, and anything carrying H.264 or H.265. Converting a stack of PNGs to OGV is the canonical way to publish a slideshow, time-lapse, or rendered animation into open-licensed environments.

• Wikimedia Commons and Wikipedia uploads — Commons explicitly states "the preferred video format is VP9 video in the WebM container, but Theora video in the ogv container and VP8 or AV1 video in the WebM container are also allowed." If your target is a Wikipedia article, OGV (Theora) is one of three accepted upload formats — and the only one inside the Ogg family.
• Rendered animation frames — Blender, Manim, and most ray tracers export numbered PNG sequences. Merging them into OGV at a chosen frame duration produces a self-contained patent-free preview clip without needing FFmpeg locally.
• Time-lapse from photo bursts — Convert a folder of timestamp-ordered PNGs into a single OGV at 1/24s or 1/30s per frame for cinematic time-lapse, or 1-2s per frame for slideshow pacing.
• Open-source documentation and FOSS demos — Linux distributions, GNU projects, and Wikipedia tutorials prefer Ogg/Theora to avoid MPEG-LA licensing footprints. Output OGV directly so your demo videos match the licensing posture of your project.
• Educational and lecture media — Slide PNG exports (from Keynote, PowerPoint, or LaTeX Beamer) can be merged with a fixed image duration to produce a low-bandwidth OGV lecture aid that plays in Firefox and on Linux desktops without proprietary codecs.
• Archival of static graphic series — When you need a single durable file that contains a numbered set of charts or scans, an OGV merge produces one Ogg-wrapped artefact rather than a folder of loose images.

OGV vs WebM vs MP4 — Open Format Comparison

Image Duration Guide — Frames per Image

Frequently Asked Questions

Why does Wikimedia Commons still accept OGV when most browsers dropped Theora?

Wikimedia's content policy is patent-driven, not browser-driven. Theora's source patents were irrevocably granted royalty-free by On2 in 2002 when it donated VP3 to Xiph.Org, so Commons can host Theora indefinitely without licensing exposure. Browser removal (Chrome 123 in March 2024, Firefox 126) is a security and footprint decision — Commons transcodes uploaded OGV/WebM into web-friendly derivatives for playback, so the upload format and the playback format don't have to match.

Should I pick VP8 or Theora for the OGV codec?

Pick Theora if your target is Wikimedia Commons or any open-source project that explicitly says "Ogg/Theora" — Ogg-with-Theora is the historically standard OGV stream. Pick VP8 for slightly better compression at the same bitrate when the destination is just "any open-format player" and the consumer is VLC, mpv, or a Linux desktop. xconvert defaults to VP8 for visual quality; switch to Theora under Video Codec → Theora in Advanced Options for Wikimedia compatibility.

How long should each PNG be displayed?

Match the source's frame rate. For numbered render outputs (frame_0001.png, frame_0002.png…) from Blender or a game engine, set 1/24s or 1/30s — the resulting OGV plays as cinematic motion. For slideshow PNGs (slides, photos), 2-5 seconds per frame matches most lecture and portfolio pacing. For time-lapse from a photo burst, 1/30s gives smooth 30 fps playback; 1/10s feels stuttery but covers long sequences quickly.

Will my OGV play in Chrome or Safari?

Probably not natively in 2026. Google removed Theora support from Chromium in version 123 (March 2024), and Firefox disabled it by default in version 126. Safari never supported Theora. The reliable players are VLC, mpv, the GNOME and KDE default video apps, and Firefox builds with media.theora.enabled flipped back on. If your audience is general web viewers, convert PNG to WebM or convert PNG to MP4 instead — both keep universal browser support.

Can I merge a thousand PNGs into one OGV?

Yes — Merge Strategy → "Merge images" stacks every uploaded PNG into a single OGV in filename order. Sort your files by name before uploading (frame_0001.png, frame_0002.png, …) so the merge order matches your intended sequence. There's no fixed cap, but very large stacks (tens of thousands of frames) are smoother done locally with FFmpeg; for a few hundred to a few thousand frames a browser conversion is fine.

What resolution should I pick for the output OGV?

For Wikimedia uploads, "strongly recommended to upload your video with the best quality (bit rate and frame size) possible" — keep Resolution on "Original" and let your source PNG dimensions drive output. For web playback or embed previews, 720p or 1080p is plenty. Vertical destinations (Wikimedia Commons mobile, social previews) benefit from the 1080×1920 or 720×1280 presets. Files on Commons must stay under 5 GiB.

Why is the OGV file so much larger than my PNG folder?

PNG is lossless per frame. OGV (Theora or VP8) re-encodes at a target bitrate, but a slideshow of 100 high-resolution photos held for 5 seconds each at the "Highest" preset can still produce a hundreds-of-MB file because every frame is being held for many displayed-frame copies. Drop the Quality Preset to "Very High" or "High," lower the resolution preset, or shorten the per-image duration to shrink output.

Will the OGV preserve transparency from my PNGs?

No. Both Theora and VP8 are opaque video codecs — they do not encode an alpha channel. Any transparent pixels in your PNGs are flattened against the Background Color you pick (default black). If you need transparency, convert PNG to GIF for an animated frame sequence with 1-bit transparency, or use APNG/WebP for full alpha.

Can I convert PNG to OGV with audio?

Not in a single step — image-to-OGV is silent by default (Vorbis stream with no audio). To attach narration or music, convert PNG → OGV here, then merge an audio track in a video editor like Kdenlive or OpenShot, both of which export Ogg/Theora natively. To go the other direction (extract still frames from an OGV), convert OGV to PNG.