Initializing... drag & drop files here
Supports: MP4, M4V
M4V is Apple's iTunes flavour of MP4 — an ISO base-media container that normally holds H.264 video and an AAC soundtrack — and FLV is Adobe's Flash Video container from the RTMP era. This guide walks the conversion and is straight with you about the three things that actually decide whether the result is usable: which video codec you pick (the default is not H.264), why the Quality Preset dropdown does nothing on this particular output, and why a FairPlay-protected iTunes purchase will never convert on any web tool. If you only want a file that plays on phones, browsers and TVs, FLV is the wrong target and the last section points you at the right one.
.m4v onto the drop area or click "Add Files". DRM-free sources — your own iPhone and iPad exports, iMovie and Final Cut renders, screen recordings, HandBrake output — work. .mp4 files are accepted on the same page, and you can queue several clips and run them as one batch..flv. Your file is uploaded over an encrypted connection, converted on our servers and deleted automatically a few hours later. No sign-up, no watermark.The Video Codec list looks like four flavours of the same thing. It is not — two of those entries are lossless screen-capture codecs that ignore every bitrate control you set, which is how people end up with a 2 GB FLV from a 40 MB M4V.
| Video Codec option | What it really is | Rate control | Sensible for |
|---|---|---|---|
| FLV (starts selected) | Sorenson Spark, FourCC FLV1 — a Flash-specific H.263 derivative, the codec FLV shipped with in 2002 |
Bitrate or a fixed quality scale | Legacy Flash players, RTMP-era servers, old e-learning ingest |
| H.264 | The same AVC family your M4V already uses, muxed into FLV | Full CRF-style quality control | Late-era Flash pipelines and FLV-only tools that were built after 2008 |
| Flash Video | Flash Screen Video 1 — a lossless screen-capture codec | None; ignores bitrate settings entirely | Screencasts of static UI, where lossless matters more than size |
| Flash Video (v2) | Flash Screen Video 2 — the improved lossless screen codec | None; ignores bitrate settings entirely | The same screencast case, smaller than v1 |
Camera footage, gameplay and anything with grain or motion should never go through the two Flash Screen Video entries: they are designed for flat, repetitive screen pixels, so a live-action M4V balloons. If your player is modern enough to accept it, H.264 is the best-quality choice, because it avoids a cross-codec generation loss the Sorenson Spark path cannot avoid. Adobe added H.264 playback to Flash Player 9 Update 3 in December 2007, so anything older than that needs the default FLV codec.
Quality Preset is a CRF control. It only reaches the encoder on codecs that actually implement constant-rate-factor encoding — H.264, H.265, VP8, VP9, AV1. Sorenson Spark is not one of them, so with the default codec the preset silently falls through to a bitrate calculation and the whole dropdown becomes decorative. In our testing, every setting from Highest to Lowest produced the same very low-bitrate FLV, well under what any of those labels implies.
| File Compression mode | Effect with the default FLV codec | Use it when |
|---|---|---|
| Quality Preset | No useful effect — all seven presets behave the same | Never, on this output, unless you switched the codec to H.264 |
| Constant Bitrate | Real control; the value you type is the encode bitrate | You know the bitrate the target player or server expects |
| Variable Bitrate | Real control, with min and max bitrate fields | You want a size ceiling but variable scene quality |
| Specific file size | Real control; the encoder aims at a byte budget | You have a hard upload or storage limit |
| Constant Quality | Applies a fixed quality scale to the encoder, but exposes no number to tune | You want "just encode it" and don't care about the exact size |
| Constraint Quality | Quality-targeted with a max-bitrate ceiling you set | You need a bitrate cap the stream must never exceed |
The practical recipe: keep the codec on FLV, switch File Compression to Constant Bitrate, and set something in the region of the source's own bitrate. Sorenson Spark is far less efficient than H.264, so matching the source bitrate roughly matches the source's look — and it is entirely normal for the FLV to come out larger than the M4V it came from.
FLV is a legacy target with two remaining honest use cases: feeding an RTMP-era Flash streaming server that is still running somewhere on an intranet, and satisfying an old e-learning or LMS pipeline whose ingest step only accepts .flv. Everything else has moved on — Adobe ended Flash Player support on 31 December 2020, and browsers removed the plugin. If your goal is a file that plays on phones, browsers, TVs and editors, convert M4V to MP4 instead; if you want an open container with wide codec choice, M4V to MKV is the better home. Already holding FLV files you need to modernise? FLV to MP4 goes the other way.
Only for a specific legacy consumer. Adobe ended Flash Player support on 31 December 2020, browsers dropped the plugin, and FLV is not a delivery format anyone should be choosing today. The realistic reasons left are an RTMP-era streaming server or an old learning-management system whose upload step validates the .flv extension. If neither applies, target MP4 — the H.264 in your M4V goes there with far less quality loss.
No. Films and TV episodes bought or rented from the iTunes Store can carry Apple's FairPlay protection, which encrypts the video so it only decodes on a device authorised with the purchasing Apple ID. No web converter can read that stream, so the job fails. Everything DRM-free converts normally: your own iPhone and iPad exports, iMovie and Final Cut renders, screen recordings, and HandBrake output that happens to carry an .m4v extension.
Leave it on FLV (Sorenson Spark) if the consumer is a genuine Flash-era player or server — it is the codec those systems were written against. Choose H.264 if the target is newer than late 2007 and simply demands the .flv container, because it keeps the AVC family your M4V already uses and avoids a cross-codec quality drop. Avoid Flash Video and Flash Video (v2) unless your source is a screen recording: they are lossless screen-capture codecs and produce very large files from camera footage.
Because Quality Preset drives a CRF value, and CRF only exists on codecs that implement it — H.264, H.265, VP8, VP9, AV1. The default FLV codec is a Sorenson Spark encoder with no CRF mode, so the preset falls through to a bitrate calculation and every setting lands in the same place. Switch File Compression to Constant Bitrate or Specific file size for real control, or change the Video Codec to H.264, where the preset does work as labelled.
Often the opposite. Your M4V is H.264, which is a much more efficient codec than Sorenson Spark, so re-encoding at a comparable visual quality usually needs more bits, not fewer. If you need the output under a specific size, use Specific file size and accept the softness, or drop the resolution with a Preset Resolution first — fewer pixels is the cheapest way to buy quality back at a fixed byte budget.
It is re-encoded, not copied. Audio Codec starts on AAC; MP3 and ADPCM_SWF are the alternatives. MP3 is the safer choice for genuinely old Flash targets, since MP3 was FLV's original audio codec and AAC-in-FLV only arrived with Flash Player 9. If you only want the soundtrack and not the picture at all, M4V to MP3 skips the video entirely.
No. FLV has no chapter or subtitle model comparable to MP4's, and the iTunes-specific atoms an M4V can carry — artwork, episode and season fields, media kind — have no FLV equivalent. What survives is video and audio. If you need the chapter and subtitle structure preserved, M4V to MKV is the container built to hold it.
Files are uploaded over an encrypted connection, converted on our servers, and deleted automatically a few hours afterwards — no sign-up, no watermark, never shared or made public. There is no fixed clip-length cap; the real constraint on a multi-gigabyte HD source is upload time and connection stability, so trimming to just the segment you need with the Trim control is usually faster than converting the whole file.