Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
.jpg, .jpeg, and .jfif files, and you can add several at once.Wrapping a JPG into WebM gives you a short video that holds your single image on screen for a set number of seconds — it does not animate the photo or add motion, it just plays the same frame for the duration you pick. People reach for it when a site, ad slot, or chat app accepts video uploads but not still images, or when a looping video reads better than a static picture in a feed.
The duration is the one setting that defines a still-to-video conversion, so it is worth a closer look.
When you add more than one image and keep Merge strategy on "Merge images", every photo uses this same duration and they play back to back as a slideshow; the total length is the per-frame duration times the number of images.
A few situations fall outside a simple JPG-to-WebM wrap. If you actually want movement — a pan, zoom, or transition — this tool won't create it; it only holds the static frame, so you'd need a video editor for animation. If your goal is the most universally playable file (older phones, smart TVs, embedded players), WebM is the wrong target because its Apple-device support is recent; use JPG to MP4 for that. And if you have a folder of frames meant to become a true animation, an animated GIF or a higher frame-rate video export is usually the better fit than a slideshow of multi-second stills.
No. The output is a video that displays your single still frame for the duration you set — it is the same image held on screen, not an animation. Any "motion" would have to come from a video editor; this converter only wraps the static picture into a playable WebM clip.
The Image Duration control runs from sub-second presets (down to a single frame at 60fps) up to 10 seconds per frame. If you merge several JPGs into one clip, the total length is the per-frame duration multiplied by the number of images, so ten photos at 5 seconds each gives a 50-second slideshow.
By default the clip is encoded with VP9 inside the Matroska-based WebM container. You can switch the codec to VP8 (older but very widely supported) or AV1 (newer, more efficient) in Advanced Options if a specific destination requires one.
Almost — WebM is supported by roughly 96% of browsers tracked by caniuse, including Chrome 25+, Firefox 28+, and Edge 79+. The gap is Apple's older releases: Safari only plays WebM from version 16.0 on macOS and 17.4 on iOS. For older iPhones, iPads, or Macs, convert to MP4 instead.
The common reason is a platform that accepts video uploads but not still images, or one where a video autoplays and loops while a static image just sits there. A few ad networks and chat-sticker slots also specifically want a WebM rather than a JPG or PNG, so wrapping the still into a short clip satisfies the uploader.
In our testing, a single 1920 x 1080 JPG held for 5 seconds and encoded at VP9 "Very High" produced a WebM of roughly 60–120 KB, because a static frame compresses to almost nothing after the first keyframe. Dropping the Quality Preset or shortening the duration shrinks it further; raising the resolution or merging many images grows it.