format

MP4

MP4 is the default video container, normally holding H.264 video and AAC audio.

Also known as MPEG-4 Part 14.

Convert a file now

What is a MP4 file?

The most widely supported video container, wrapping compressed video, audio, subtitle and chapter streams.

MP4 is a wrapper, not a compression method. What determines whether a given MP4 plays on an old TV is the codec inside it: H.264 plays essentially everywhere, while HEVC or AV1 may not decode at all.

Technical characteristics

Representation
binary
Compression
H.264, HEVC, AV1
Lossy
Yes
Open specification
Yes

History and origin

Introduced
2003
Organisation
ISO/IEC MPEG

Compatibility

  • Windowsfull
  • macOSfull
  • Linuxfull
  • Androidfull
  • iOSfull

Browsers: Chrome, Firefox, Safari, Edge.

Advantages of MP4

  • Plays on virtually every device
  • Efficient streaming with faststart
  • Supports subtitles and chapters

Limitations to know about

  • Patent licensing on H.264 and HEVC
  • Editing requires re-encoding

When to use MP4

  • Web video
  • Social media
  • Camera recordings

Convert MP4 files

MP4 scores

Deterministic scores calculated from the structured facts above. Identical facts always produce identical scores.

Overall score

75/100

  • Openness score

    100
    • the specification is published openly
    • an openly specified format can be implemented without a licence negotiation

    Confidence 63% · evidence coverage 100%

  • Web score

    94
    • browsers render it natively, so no conversion step is needed at request time
    • every major browser engine renders it natively
    • smaller payloads mean less I/O and faster first paint
    • it compresses lossily, which produces much smaller files than lossless coding

    Confidence 77% · evidence coverage 92%

  • Streaming score

    92
    • lossy compression keeps the bitrate low enough to stream reliably
    • smaller payloads mean less I/O and faster first paint
    • it compresses lossily, which produces much smaller files than lossless coding
    • every major browser engine renders it natively

    Confidence 80% · evidence coverage 100%

  • Archiving score

    88
    • the specification is public, so a decoder can always be rebuilt
    • the specification is published openly
    • it is actively maintained and current
    • an openly specified format can be implemented without a licence negotiation

    Confidence 78% · evidence coverage 89%

  • Performance score

    88
    • smaller payloads mean less I/O and faster first paint
    • it compresses lossily, which produces much smaller files than lossless coding

    Confidence 72% · evidence coverage 100%

  • Longevity score

    86
    • it is actively maintained and current
    • the specification is published openly
    • the specification is public, so a decoder can always be rebuilt
    • it sits at the centre of the format ecosystem, with many documented relationships

    Confidence 78% · evidence coverage 100%

  • Compatibility score

    83
    • every major browser engine renders it natively
    • Windows, macOS, Linux, Android and iOS all open it without extra software
    • an open specification means cloud SDKs can implement it without licensing friction
    • it opens by double-clicking on every mainstream device
    • only a narrow set of applications handles it

    Confidence 82% · evidence coverage 100%

  • AI score

    66
    • the specification is published openly
    • smaller payloads mean less I/O and faster first paint
    • only a narrow set of applications handles it
    • lossy artefacts add noise that models can learn by mistake

    Confidence 60% · evidence coverage 100%

  • Photography score

    42
    • it opens by double-clicking on every mainstream device
    • it compresses lossily, which produces much smaller files than lossless coding
    • each edit-and-save cycle compounds compression damage

    Confidence 66% · evidence coverage 44%

  • Editing score

    13
    • each edit-and-save cycle compounds compression damage
    • only a narrow set of applications handles it

    Confidence 55% · evidence coverage 63%

  • Printing score

    8
    • lossy artefacts become visible when the image is enlarged for print
    • only a narrow set of applications handles it

    Confidence 64% · evidence coverage 50%

Every conclusion below is derived from the structured facts on this page — nothing is written by hand.

  • Browser compatibility100/100

    • Because every major browser engine renders it natively.
    • Because at least one shipping browser renders it.
  • Operating system compatibility100/100

    • Because Windows, macOS, Linux, Android and iOS all open it without extra software.
    • Because most platforms handle it natively.
  • Web suitability100/100

    • Because browsers render it natively, so no conversion step is needed at request time.
    • Because lossy compression keeps transfer sizes and Core Web Vitals in check.
    • Because the specification is open, so tooling and CDNs implement it freely.
  • Cloud compatibility100/100

    • Because an open specification means cloud SDKs can implement it without licensing friction.
    • Because it converts into many other formats, which suits automated pipelines.
  • Streaming100/100

    • Because lossy compression keeps the bitrate low enough to stream reliably.
    • Because browsers decode it natively, so it plays without a plugin.
    • Because open specifications avoid per-stream licensing complications.
  • Everyday consumer usage100/100

    • Because it opens by double-clicking on every mainstream device.
    • Because small files are easy to email, message and upload.
    • Because it is a current format that people and services still expect.
  • Open standards100/100

    • Because the specification is published openly.
  • Licensing100/100

    • Because an openly specified format can be implemented without a licence negotiation.
    • Because the core patents are old enough to have expired.
  • Decode performance100/100

    • Because smaller payloads mean less I/O and faster first paint.
    • Because mature formats benefit from hardware and SIMD-optimised decoders.
  • Future-proofing88/100

    • Because it is actively maintained and current.
    • Because open specifications outlive the companies that create them.
    • Because nothing in the graph supersedes it yet.
  • Long-term archiving76/100

    • Because the specification is public, so a decoder can always be rebuilt.
    • Because it is a current, actively maintained format.
    • Because it has a decade or more of proven, stable implementations.
  • Popularity71/100

    • Because it sits at the centre of the format ecosystem, with many documented relationships.
    • Because every mainstream operating system handles it.
    • Because it is still current rather than being phased out.
  • Compression efficiency69/100

    • Because it compresses lossily, which produces much smaller files than lossless coding.
    • Because it defines a documented compression scheme.
  • Printing suitability0/100

    • Because lossy artefacts become visible when the image is enlarged for print.
    • Because it does not satisfy: it is a page-description format built around fixed layout.
  • Professional editing0/100

    • Because each edit-and-save cycle compounds compression damage.
    • Because it does not satisfy: professional applications read and write it.
  • Software compatibility33/100

    • Because only a narrow set of applications handles it.

Migration paths

  • MP4GIF

    Professional editing improves by 100 points because lossless data survives repeated open-edit-save cycles without degrading.

    Trade-off: Future-proofing drops by 63 points because it is marked legacy or deprecated in the knowledge graph.

    Convert MP4 to GIF

Frequently asked questions

Why won't my MP4 play on this device?

Almost always the codec, not the container. Re-encode to H.264 with AAC audio for maximum compatibility.

Data quality

Every claim on this page is classified as a verified fact, a derived fact or an assumption.

Overall confidence
95%
Verification status
verified
Last reviewed
2026-08-03
Verified facts
2

2 classified claims backed by 2 sources.

Sources and review status

Review status: verified · confidence 95%

Last reviewed 2026-08-03 (revision 1).