Initializing... drag & drop files here
Supports: MTS
If you have pulled .mts files off a Sony, Panasonic, Canon, or JVC handycam and something in your workflow is asking for .m4v, the short answer is this: .m4v is Apple's extension for what is otherwise an MP4 file, so converting gets you a normal H.264-in-MP4 movie wearing a name that Apple software and Apple-centric workflows expect. Convert if a specific app, library, or hand-off asks for .m4v. If nothing does, MTS to MP4 gives you the same container under the extension every upload form, TV, and phone recognises.
The change that actually matters here is not the extension but the container underneath it. AVCHD stores H.264 inside an MPEG-2 transport stream — a format built for broadcast and disc, not for random-access editing — and this conversion rewraps the picture into the ISO base media container that every modern player treats as native, re-encoding as it goes.
| Property | MTS (AVCHD source) | M4V (output) | MP4 |
|---|---|---|---|
| Container | MPEG-2 transport stream | MPEG-4 Part 14 (ISO base media) | MPEG-4 Part 14 (ISO base media) |
| Origin | AVCHD, co-promoted by Sony and Panasonic | Apple's extension for MP4 content | ISO/IEC |
| Video codec | H.264/AVC, as recorded by the camera | H.264 by default; MPEG-4 or Xvid also offered | H.264 by default |
| Audio codec | Dolby Digital (AC-3) or Linear PCM | AAC by default; AC3 also offered | AAC by default |
| Bitrate ceiling | 24 Mbps, or 28 Mbps for stereoscopic modes | None imposed by the container | None imposed by the container |
| Optional DRM | None | Apple's FairPlay, on iTunes Store purchases only — never applied by this tool | None |
| Accepted by upload forms | Rarely | Sometimes rejected purely on the extension | Almost always |
| Random-access seeking | Poor; built for streaming and disc playback | Good | Good |
| Best at | Recording to a camera card | Apple-centric libraries and apps that ask for .m4v |
Everything else |
.m4v files and ignores anything else..m4v files and want a consistent set rather than a mix of extensions..mp4 and .m4v differently for sorting, metadata, or "movie versus home video" categorisation..m4v; MPEG-4 and Xvid are there for old hardware. Audio Codec opens on AAC, with AC3 available if something downstream specifically wants Dolby Digital..m4v. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically a few hours later — no sign-up, no watermark, never shared or made public.With H.264 selected, Quality Preset is a friendly front end for CRF — the constant-quality target that decides how hard the encoder squeezes each frame. These are the values it uses at a 1080p output, nudged slightly up or down when you scale to a different resolution, because compression artifacts are easier to hide in more pixels:
| Quality Preset | H.264 CRF at 1080p | What you get |
|---|---|---|
| Highest | 17 | Visually lossless; the largest files |
| Very High (opens selected) | 18 | Near-lossless — the sensible default for camcorder masters |
| High | 20 | Transparent: nothing you would spot in normal viewing |
| Medium | 23 | Standard web quality |
| Low | 26 | Artifacts visible on close inspection |
| Very Low | 28 | Noticeably compressed |
| Lowest | 32 | Heavy artifacts, smallest file |
If you would rather set the number yourself, Constant Quality takes a CRF on the 16-51 H.264 scale where lower means better. Around 18 is near-lossless, 23 is the codec's own default, and past 28 the softness becomes obvious on 1080p material.
For the file this tool produces, effectively yes: both use the MPEG-4 Part 14 (ISO base media) container, and the H.264 video and AAC audio inside are laid out identically. Apple uses the .m4v extension for video content in its own ecosystem, and some video sold through the iTunes Store under that extension carries Apple's FairPlay copy protection. Files converted here are ordinary, unprotected MP4 content. If a player refuses a .m4v, renaming it to .mp4 almost always fixes it and changes nothing inside.
No. FairPlay is applied by Apple's own distribution systems to content sold or rented through the iTunes Store; it is not a property of the .m4v extension and nothing in this conversion adds it. What you download is a plain, unencrypted file you can play, copy, and re-encode freely. The reverse is also worth knowing: if you have a purchased .m4v that is FairPlay-protected, no converter can decode it, and this one will not either.
A little, and it is unavoidable, because the video is re-encoded rather than copied — there is no stream passthrough in this pipeline. Both sides are H.264, so the second encode is working from an already-compressed picture and can only match or lose ground, never improve. At the Very High preset (CRF 18 at 1080p) the difference from the source is invisible in normal viewing while the file lands somewhere near the original's size. Choose Medium or a Constant Quality of 22-23 if you want a clearly smaller file and can accept web-grade quality.
It is decoded and re-encoded to AAC, which is the default and the right choice for an Apple-facing file: AAC is decoded natively by every current Apple app and device, whereas AC-3 support in consumer players has always been patchier. If something downstream genuinely wants Dolby Digital — a receiver or a disc-authoring step, say — the Audio Codec dropdown offers AC3. AVCHD recordings that used Linear PCM instead are likewise re-encoded to whichever of the two you pick.
Because nothing in this pipeline deinterlaces, and converting to MP4 or M4V does not fix interlacing as a side effect — that is a persistent myth. A 1080i frame contains two fields captured a fraction of a second apart, and if the source has them woven together, the encoder faithfully preserves that woven picture in the output. No Quality Preset, resolution setting, or container change removes it. Removing combing needs a deinterlacing filter, which means a desktop tool such as a non-linear editor or a FFmpeg command with yadif or bwdif.
Some AVCHD modes record 1440x1080 with non-square (anamorphic) pixels that players stretch to a 1920-wide 16:9 image at display time. When the video is rescaled here the pixel aspect is normalised to square, so the stored 1440-wide shape becomes the real shape and the picture looks narrow. Set Video resolution to Width x Height and enter 1920 by 1080 in pixels to restore the intended proportions. Leaving the resolution on Keep original avoids the rescale entirely.
Only for genuinely old hardware — both are MPEG-4 Part 2 codecs from the generation before H.264, so at any given file size they look worse. There is a practical catch too: neither supports CRF, so selecting one changes the Constant Quality box from H.264's 16-51 CRF scale to a 1-31 quantiser scale, and the box does not re-open at a sensible value for that scale. If you use it, set it deliberately — roughly 2 to 5 is high quality on a 1-31 quantiser, and higher numbers get worse fast. For anything modern, leave Video Codec on H.264.
The accepted-extension list here is .mts only. AVCHD is written under two extensions in practice: cameras use .mts on the card, while Windows, Blu-ray tooling, and several import utilities produce .m2ts containing what is usually the identical transport stream. Rename the file to .mts, or use M2TS to M4V, which accepts the other spelling.
There is no fixed per-file cap; the real constraint is upload size and connection speed, and AVCHD is heavy — the format allows up to 24 Mbps, so a long recording is several gigabytes before you start. Cutting the section you need first with Video Cutter is usually faster than uploading the whole reel. Whatever you upload travels over an encrypted connection, is processed on our servers, and is deleted automatically a few hours after the job completes. Files are never shared or made public, and there is no sign-up and no watermark.