Initializing... drag & drop files here
Supports: WEBP
cwebp, or animated WebPs saved from Chrome, Telegram stickers, or design tools. Batch is supported — drop in a folder of stills and they'll merge into one M4V slideshow, or queue separate animated WebPs as individual video files.WebP is Google's modern image format, supporting both static and animated content. Lossy WebP is 25-35% smaller than equivalent JPEG; lossless WebP is roughly 26% smaller than PNG. Animated WebP uses a VP8 bitstream with ANIM / ANMF chunks for frame data. M4V is Apple's container format introduced in 2006 alongside the iTunes Store — it's nearly identical to MP4 but signals to macOS, iOS, tvOS, iTunes, and Apple TV that the content is a video file rather than a generic MP4 (which might also hold audio-only or app payloads). Apple Photos exports slideshows directly to.m4v. Common reasons to convert WebP to M4V:
AVPlayer (effectively every video player on the platform) without polyfills or third-party libraries..mp4 is for Android — guaranteed thumbnail preview in Messages and Mail.| Property | M4V | MP4 |
|---|---|---|
| Origin | Apple, introduced 2006 with iTunes Store | ISO/IEC 14496-14:2003 (derived from Apple's QuickTime spec) |
| Typical codecs | H.264 video, AAC audio, AC-3 / Dolby Digital optional | H.264, H.265 / HEVC, AV1, VP9, AAC, MP3 |
| DRM | Supports Apple FairPlay (iTunes Store purchases) | No DRM in the container spec |
| Native players | iTunes, QuickTime, TV app, iMovie, Final Cut Pro, Apple TV, QuickLook | Effectively every modern player on every OS |
| File extension cue | Signals "video" to macOS / iOS / tvOS | Generic MPEG-4 container; could be video, audio, or app payload |
| Best for | Apple-ecosystem playback and library import | Cross-platform sharing, web embed, streaming |
| XConvert output | DRM-free — no FairPlay added | DRM-free |
The two containers are technically very similar — many tools (including QuickTime and VLC) treat them as interchangeable, and renaming .mp4 to .m4v works for H.264 + AAC payloads. The reason to pick M4V is the Apple-ecosystem signaling, not a structural codec difference.
| Setting | What it does | Pick when |
|---|---|---|
| Quality Preset — Very High (default) | Constant Quality H.264, visually lossless | Default — sharing or library import |
| Quality Preset — High / Medium | Smaller H.264 file, mild compression visible on flat color | Email, iCloud, AirDrop to older devices |
| Quality Preset — Constraint Quality | VBR capped at a target ceiling | Streaming over fixed-bandwidth links |
| Image Duration — 1/24 sec | 24 fps cinematic frame rate | Stop-motion, time-lapse, animation |
| Image Duration — 1/30 or 1/60 sec | 30 or 60 fps smooth playback | Game capture stills, screen-recording frames |
| Image Duration — 3-5 sec | Standard slideshow timing | Photo slideshows, presentation reels |
| Image Duration — 10 sec | Long dwell per image | Gallery / kiosk loops, ambient displays |
| Merge images | Combines all uploads into one M4V | Slideshow / reel from a folder of stills |
| Video per image | One M4V per source WebP | Bulk conversion of separate animated WebPs |
Yes. The output uses H.264 video + AAC audio inside an.m4v container — the exact codec / container combination Apple's apps prefer. Drop the file into the TV app's library (or the legacy iTunes Movies folder) on macOS and it appears under Home Videos without any conversion or re-import step. With Home Sharing enabled, the same file streams to every Apple TV on your network.
Yes. Each frame in the animated WebP becomes a video frame in the M4V at the Image Duration you set. WebP animation uses a VP8 bitstream split into ANIM and ANMF chunks — the converter walks the chunk list and emits H.264 frames in order, preserving timing as closely as the chosen frame rate allows. If your WebP runs at 30 fps and you pick Image Duration = 1/30 second, the output matches the original cadence frame-for-frame.
Structurally yes, semantically no. M4V tells macOS, iOS, tvOS, iTunes, and the TV app "this is a video file" — Apple's apps auto-import, generate thumbnails, and handle chapters / AC-3 audio by default. An identical MP4 may be treated as a generic media file requiring manual import. M4V also accommodates AC-3 / Dolby Digital audio without the container quirks some MP4 players hit. For pure cross-platform sharing, see WebP to MP4; for the Apple ecosystem, M4V is the cleaner choice.
No. FairPlay protection is only applied by Apple to content purchased through the iTunes Store / TV app. The M4V xconvert generates is a plain, unencrypted container — playable on any player that handles H.264 + AAC (QuickTime, VLC, IINA, MPV, browsers, smart TVs, Plex). The.m4v extension itself does not imply DRM; only iTunes-store-issued.m4v files are protected.
Yes — that's the default behavior with Merge strategy = Merge images. Upload all your WebP files in the order you want them to appear (the file list is reorderable before you click Convert), set Image Duration to 3-5 seconds per frame, pick a Background Color for letterbox fill if your aspect ratios vary, and you'll get a single M4V slideshow. Compare to Apple Photos' built-in slideshow export, which is fixed to 480p / 720p / 1080p; xconvert lets you pick anything up to 4320p (8K).
WebP doesn't carry audio. The default output is a silent M4V (which the TV app and QuickTime handle without warning). If you want music, convert the WebPs to M4V first, then drop the result into iMovie or Final Cut Pro and add an audio track — both editors accept the M4V output directly. There's no in-converter audio add step.
Close to exact, with one caveat: WebP allows per-frame variable delays (each ANMF chunk carries its own millisecond duration), while video frame rates are fixed. The converter picks the closest fixed frame rate to your selected Image Duration. For uniform-cadence animations (most animated WebPs from design tools and Telegram stickers), the result is frame-accurate. For irregular cadences, individual frame durations are rounded to the nearest frame slot — visible only on side-by-side comparison.
The practical limit is upload size and connection speed. Files are processed on our servers — hundreds of WebP stills merging into a multi-minute 1080p M4V is handled comfortably. There's no fixed per-file cap and no count limit on batch jobs — much higher than typical online converters (ezgif's WebP-to-MP4 tool, for example, caps at 200 MB per file).
Yes — see M4V to WebP for extracting an animated WebP from a video, or M4V to MP4 to switch the container without re-encoding. For the more common JPG / PNG starting points, see JPG to M4V and PNG to M4V. To shrink the result further, follow up with Compress M4V.