Initializing... drag & drop files here
Supports: 3FR, ARW, AVIF, BMP, CR2, CR3 +30 more
WebM is the open, royalty-free video container Google built for the HTML5 <video> tag. It's the right output any time the destination is the open web — a marketing site hero loop, a blog post embed, a Wikipedia article, an HTML5 game asset, a Matrix or Discord inline preview, or a banner ad on a network that prefers VP9/AV1. Wrapping still images into WebM turns a photo set into a streamable video file browsers play without a plugin and without licensing fees flowing to MPEG-LA.
<video> tag embeds with no licensing concerns — WebM (VP8/VP9/AV1 + Opus/Vorbis) is fully royalty-free, unlike H.264 / H.265 in MP4. Open-source projects, government sites, Wikipedia / Wikimedia Commons, and Mozilla all standardize on WebM for that reason. A 1080P slideshow encoded as WebM drops into <video src="...webm"> on any page with no plugin and no patent footnote.<video> directly. Image-sequence intros from a numbered PNG export at 24 or 30 fps as WebM are a standard pipeline step.| Property | WebM | MP4 |
|---|---|---|
| Container origin | Google / WebM Project (2010) | ISO Base Media (2003) |
| Typical video codec | VP9 / VP8 / AV1 | H.264 / H.265 / VP9 / AV1 |
| Typical audio codec | Opus / Vorbis | AAC / MP3 / AC-3 / Opus |
| Royalty-free | Yes (no patent licensing) | No (H.264 / H.265 require MPEG-LA license) |
HTML5 <video> native |
Yes (Chrome, Firefox, Edge, Opera; Safari since Big Sur / iOS 14.5) | Yes (universal) |
| File size at equal quality | Smaller than H.264 MP4; AV1 smallest | H.264 medium; H.265 ~half of H.264 |
| Wikimedia Commons accepts | Yes | No |
| Best fit | Open web, Wikimedia, HTML5 games, Discord previews | Social platforms, smart TVs, mobile devices |
| Codec | Best for | File size | Encode speed | Decoder availability |
|---|---|---|---|---|
| VP9 (default) | General-purpose web embeds, Discord, blog posts | Small (~half H.264) | Medium | Chrome, Firefox, Edge, Opera; Safari (macOS 11+, iOS 14.5+) |
| AV1 | Highest compression, modern ad networks, AVIF-era pipelines | Smallest (~30% under VP9) | Slow | Chrome 70+, Firefox 67+, Safari 17+, Edge |
| VP8 | Legacy WebM 1.0, oldest Android browsers, embedded HTML5 players | Medium (similar to H.264) | Fast | Universal on WebM-aware players since 2010 |
VP9 is the default and the right pick for almost every modern use — every desktop browser plays it, Safari has supported it since macOS Big Sur and iOS 14.5, and file sizes are roughly half of H.264 MP4 at the same visual quality. Pick AV1 when bandwidth or storage is the priority and you can afford a slower encode (it's roughly 30% smaller than VP9 again, and modern Chrome / Firefox / Safari 17+ all decode it). Stick with VP8 only if you're targeting very old Android stock browsers or an embedded HTML5 player from the early 2010s that hasn't been updated.
You're publishing to the open web, a Wikimedia/Wikipedia article, an HTML5 game, or any platform that won't accept patent-encumbered codecs. WebM is fully royalty-free (the VP8/VP9/AV1 + Opus/Vorbis stack), and Wikimedia Commons explicitly rejects MP4 for that reason. WebM is also typically smaller than H.264 MP4 at the same quality. If your destination is a smart TV, an iPhone Photos roll, Instagram Reels, or a hardware DVD player, pick MP4 instead via Image to MP4.
Yes. Drop in iPhone HEIC, DSLR RAW (CR2, CR3, NEF, ARW, DNG, RAF, ORF), Android JPG, and PNG screenshots together — every input decodes into a single WebM. Each frame scales to fit the chosen output resolution while preserving its source aspect ratio; empty space is filled with the background color you pick.
Output duration = number of images × image duration. 50 photos at 4 seconds each = 200 seconds (~3 minutes 20 seconds). 1,800 timelapse frames at 1/30 second = a 60-second clip. The duration setting is per-image, applied uniformly across the batch — there's no separate timeline for variable-length slides on the upload screen.
<video>?Browsers autoplay muted video by default and block sound until user interaction. Since image-to-WebM conversion produces a silent track (no audio source), the output autoplays cleanly with <video src="..." autoplay loop muted playsinline>. That's the standard pattern for hero loops, background ambience, and looping product shots.
WebM uses lossy compression by default (VP9 / AV1 / VP8), and a 24 MP DSLR photo or 48 MP iPhone shot is being downscaled to whatever resolution preset you picked — often 1080P (~2 megapixels), a ~12× reduction. For sharper output, pick a higher resolution preset (1440P, 2160P, or 4320P) and increase the Quality preset toward Highest, or set a custom CRF in the lower range (VP9 / AV1 use 0-63, lower = higher quality; 18-28 is visually very strong).
This converter produces silent WebM by default — the source images have no audio. The Audio Codec setting (Opus or Vorbis) controls what audio track gets written into the container for downstream compatibility, but to actually layer music in, convert here first and then merge it with a video editor (DaVinci Resolve, Shotcut, CapCut, Adobe Premiere) with an MP3 or WAV soundtrack.
Yes — files appear in the WebM in the order shown on the upload screen (typically alphabetical by filename). Numbered sequences like frame_0001.png through frame_0500.png sort correctly, which is what makes this page useful for stop-motion, timelapse, and HTML5-game intro sequences. Drag to reorder before clicking Convert if you need a custom sequence.
Yes — Video Trim sets a start time and duration on the output, and Image Drop Frames takes every 2nd / 3rd / 4th / up to every 10th frame from a long sequence to shorten a timelapse or interval shoot without re-shooting. To go the other direction (extract stills from a finished WebM), see WebM to JPG.