What the GIFvideo → gif, the way creatives need it
history of mp4

Every Video You Watched Today Probably Rode the Same 2003 Standard

MP4 is not one invention. It's a container descended from QuickTime carrying a codec finished in 2003, and the story of how that pair beat every rival explains most of how video works on the internet, including in this converter.

Drop a video, get a GIF free · frame-perfect · nothing leaves your browser Open the converter →

First, the fact that untangles everything: container versus codec

MP4 is not a compression method. It is a container, a filing system that holds video and audio streams, timing data, and metadata in labeled boxes. The compression lives in the codec inside, and in the overwhelming majority of MP4 files that codec is H.264. Confusing the two is the most common video misconception there is, and once you separate them, format history stops being acronym soup.

It also explains everyday mysteries: why one .mp4 plays and another will not (same box, different codec inside), and why a .mov often converts instantly (it is nearly the same box). When a MOV lands in this converter, the browser is usually reading the identical structure under a different extension.

MP4 is QuickTime with an ISO stamp

The container's family tree runs straight through Apple. QuickTime's file format, with its nested-box architecture, was contributed to the MPEG standards effort in the late 1990s, and the MP4 specification was built directly on the published QuickTime format. The first MP4 file format arrived in 2001 inside MPEG-4 Part 1, and in 2003 it was reissued as its own standard, ISO/IEC 14496-14, the document that makes .mp4 mean something on every device on earth.

That shared ancestry was later formalized as the ISO base media file format, the common skeleton under MP4, MOV, and their relatives. It is why the pair behave like siblings rather than rivals, and why this site's converter treats them identically on the way in.

May 2003: the codec that ate the world

The container needed a killer codec, and it arrived the same year. H.264, also called AVC, was finalized in May 2003 by the Joint Video Team, a rare joint effort between the ITU's video experts and MPEG. Unlike GIF's LZW, which just spots repeating byte patterns, H.264 predicts motion: it stores a frame, then describes how blocks of that frame move, spending bits only on what prediction gets wrong. Roughly double the efficiency of its predecessor, at the cost of enormous encoder complexity.

Then came the masterstroke: silicon. H.264 decoding was baked into phone chips, GPUs, cameras, and TVs, hundreds of millions of devices a year, until playing it cost almost no battery anywhere. Standards win on paper; formats win in hardware. That hardware moat is why a 2003 codec still carries most of the internet's video in 2026.

The codec wars, fought and mostly forgotten

H.264's weakness was money: a patent pool collects royalties from encoder and decoder makers, and the open web hated that. When HTML5 introduced the video element, browsers split, with Mozilla championing royalty-free alternatives and Google announcing in 2011 that Chrome would drop H.264 entirely. It never did. The stalemate softened in 2013 when Cisco open-sourced its H.264 module and covered the licensing for anyone shipping its binary, which gave Firefox royalty-free H.264 for real-time calls; for ordinary video playback, Firefox leaned on the operating system's own decoders instead of licensing its own.

The successors tell the same story from both sides. H.265 arrived in 2013 with better compression and a licensing situation so tangled it stalled web adoption. AV1, released in 2018 by an alliance of tech companies, is royalty-free by design and is genuinely growing. But check what your own browser records a screen capture in, or what a camera writes to its card: overwhelmingly still H.264, because the hardware is already everywhere and already paid for.

Find out what is really inside a video file

The container-versus-codec lesson, applied in under a minute:

  1. Ignore the extension. The .mp4 suffix names the box, not the compression. Two files with identical extensions can carry different codecs and behave completely differently.
  2. Drop it into the converter. The source info panel reads the file's actual properties in your browser: dimensions, frame rate, duration, and format, with nothing uploaded.
  3. Let the browser be the referee. If the preview plays, your browser decodes that codec and the file will convert. If a rare codec will not decode, re-export it as H.264 MP4 in any editor and it will play everywhere, which is the entire point of the history above.

Where this converter sits in that history

When you flip this tool's output switch to MP4, your browser's own built-in encoder produces the H.264, locally. That encoder exists in Chrome, Edge, and Safari precisely because of the hardware-and-licensing story above, and its absence in some Firefox builds is the last visible scar of the codec wars. The result is usually a fraction of the equivalent GIF's size, because motion prediction beats 1984-vintage pattern matching at video by an enormous margin. Our measured benchmarks put numbers on that gap, and GIF to MP4 is the page where a 39-year-old format hands its frames to a 23-year-old one.

And the reverse trip exists for a reason: MP4 wins physics, GIF wins deployment. An MP4 needs a video player and a tap; a GIF plays anywhere an image loads. Which is why MP4 to GIF remains this site's busiest road, and why both formats, born sixteen years apart, are still splitting the work in 2026.

Twenty years of standards, one drop zone

Bring the QuickTime grandchild, leave with the 1987 survivor, or go the other way. Either direction, the conversion happens in your browser and the file never leaves it.

Open the converter

Keep going

The GIF, a Historyhistory of the gif
GIF to MP4gif to mp4
MP4 to GIFmp4 to gif

Questions, answered

What is the difference between MP4 and H.264?
MP4 is the container, standardized as ISO/IEC 14496-14 in 2003: a box structure holding streams, timing, and metadata. H.264 is the video codec usually inside that box, finalized in May 2003, which does the actual compression. An MP4 can technically hold other codecs, which is why two .mp4 files can behave differently.
Where does the MP4 format come from?
From QuickTime. The MP4 specification was built directly on Apple's published QuickTime file format, first appearing in 2001 within MPEG-4 Part 1 and becoming its own ISO standard, 14496-14, in 2003. The shared skeleton was later formalized as the ISO base media file format, which is why MP4 and MOV are near-siblings.
Why did H.264 beat every rival codec?
Hardware. The codec was finalized in 2003 and then etched into phone chips, GPUs, cameras, and TVs for two decades, making playback nearly free in battery terms on essentially every device. Newer codecs compress better on paper, but H.264's silicon footprint is why it still carries most internet video.
Why does GIF still exist if MP4 is so much smaller?
Because they win different games. H.264's motion prediction crushes GIF's 1984-vintage LZW compression on file size, but an MP4 needs a video player while a GIF autoplays anywhere an image loads, loops by default, and asks no permission. Efficiency versus deployment: that tradeoff is the whole reason converters like this one exist.
Why can't Firefox always export MP4 from this tool?
Licensing history. H.264 carries patent royalties, which open-source Mozilla long resisted; Firefox plays ordinary H.264 files through the operating system's decoders, and Cisco's 2013 open-sourced module covers real-time calls, but a built-in H.264 encoder still is not guaranteed in every Firefox build. The MP4 switch here appears only when the browser has an encoder, and GIF and APNG export work everywhere regardless.
Will AV1 replace H.264?
Slowly, where it counts. AV1, released royalty-free in 2018 by a coalition of major tech companies, is growing in streaming because it saves real bandwidth at scale. But cameras, screen recorders, and hardware encoders still overwhelmingly write H.264, so files people actually hold and convert will stay H.264 for years yet.