What Is MP4? The Container Behind Every Video You Share

Every video you’ve ever sent, received, or recorded on a phone almost certainly ends in .mp4. Yet most people’s mental model of what MP4 is is wrong in a way that causes real confusion — like “I converted it to MP4 and it still won’t play.”

This guide explains what’s actually inside the file, and how that knowledge answers most video problems you’ll hit.

MP4 is a box, not a compressor

The single most important idea:

MP4 is a container. The compression is done by a codec living inside it.

A useful analogy: an MP4 file is like a box for shipping. The box tells you where the contents are, how they’re laid out, and where the label goes. It says nothing about what’s in the box — that’s the codec’s job.

So when a file is “an MP4,” all that’s guaranteed is the packaging. Inside, the box holds:

The file size, the visual quality, and whether it plays on a given device are all decided by the codec streams, not by the MP4-ness of the file.

Two files, same extension, different destinies

Concrete example of why this matters:

• File A: H.264 video inside an MP4 → plays on every phone, browser, TV, and game console made in the last 15 years.
• File B: HEVC video inside an MP4 → plays on modern iPhones and Android flagships, fails on many older Windows machines, older Androids, and Chrome/Firefox on some platforms.

Same .mp4 extension. Completely different compatibility. When someone says “MP4 doesn’t play on my TV,” they’re almost always holding File B — the container is fine; the codec inside it is the problem.

The family tree: MP4, MOV, MKV, WebM

Two details worth knowing:

• MP4 and MOV are siblings. MP4 is literally derived from QuickTime’s structure. A “MOV to MP4” conversion is often just repackaging the same streams in a different box — no quality loss, near-instant, and it fixes most compatibility issues.
• WebM is a codec-restricted MP4 rival. It can only hold Google’s codecs, which is why it lost the phone/social world to MP4 but lives in browsers.

Why every platform standardized on MP4

MP4 won because it hits every requirement at once:

• Streaming-friendly: MP4’s moov atom (the index) lets players start playing before the whole file arrives — critical for the web. (Fun fact: a file with its index at the end — common in raw camera files — won’t stream until the player downloads it all and fixes the layout.)
• Codec-flexible: MP4 supports new codecs via registration, so it didn’t age out when H.264 gave way to HEVC and AV1.
• Universal tooling: Every camera, phone, editor, browser, and messaging app reads and writes it.

That’s also why Kompress outputs MP4: an MP4 containing H.264 is the single most compatible video file that can exist — and when your device supports HEVC, an MP4 containing HEVC is the same compatibility with ~40% smaller files (codec trade-offs here).

“Converting to MP4” — what people usually mean, and what they should do

The phrase hides two very different operations:

1. Repackaging (remuxing). Streams are copied from one container into MP4 untouched. Instant, zero quality loss, no re-compression. This is the right fix for:

• a .mov or .mkv that won’t open in some app,
• a file that won’t stream because its index is misplaced.

2. Re-encoding. The video stream is actually decompressed and recompressed — this is where files get smaller, and where quality decisions happen. This is what a video compressor like Kompress does: it decodes your original (whatever the container), re-encodes the stream with a lower bitrate/resolution, and writes the result into a fresh MP4.

If your goal is smaller files, repackaging does nothing — a byte-copied stream weighs the same in any box. If your goal is plays somewhere new, re-encoding is usually overkill; remux is the tool. Know which problem you have.

Inside the box: what compression actually touches

When Kompress (or any encoder) writes a new MP4, the tracks get unequal treatment:

• Video stream: the overwhelming majority of bytes. This is where bitrate, resolution, frame rate, and codec choices bite — see our compression guide for how these interact.
• Audio stream: typically 5–10% of bytes. Compressing AAC further saves little; muting (for silent clips) is the one lever that matters.
• Metadata: kilobytes. Ignore it — unless it’s location metadata you don’t want to share, which some tools can strip. (Kompress preserves capture date and location on your device when saving — your gallery’s business, never ours. Nothing is uploaded, ever.)

The MP4 facts that answer real questions

• “My video is MP4 but won’t send.” → Size limits, not format. Email caps at ~25 MB; platforms re-encode everything anyway — see the platform limits guide.
• “MP4 is still huge after converting.” → You remuxed instead of re-encoding. Repackaging never shrinks; compression does.
• “Which format should I share?” → MP4 with H.264 inside, every time, unless you control every playback device and can use HEVC.
• “Is MP4 outdated? Should I use something newer?” → No. Containers don’t age like codecs do. MP4 happily carries AV1 — the newest widely-discussed codec — today.

Kompress writes standard MP4 output on both iOS and Android, with hardware H.264 or HEVC inside — first run free, compressed entirely on your device. Same video, smaller file, in the box everything already opens.