Why Are Games So Big Now? From Floppy Disks to 100 GB Downloads
Short answer: old games were small because they had to be: a 1980s home computer had a few kilobytes of memory and a floppy disk held 1.44 MB at most, so games were built from reusable tiles, recoloured graphics and formulas. Today's games are big because of their art and sound, not their code: 4K textures, hours of recorded voice in several languages and pre-rendered video easily add up to 100 GB or more. The rules of a game take very little space; what grew is everything we look at and listen to.
How small were old games?
The numbers from the early decades of gaming look almost impossible now. The Atari 2600 console (1977) had 128 bytes of working memory, about two lines of text, and its first cartridges held 2 or 4 KB. The ZX81 home computer (1981) came with 1 KB of memory, and a chess program, 1K ZX Chess (1983), was written to fit inside it. Super Mario Bros. (1985) is about 40 KB, the size of a small photo thumbnail today.
| Medium or machine | Capacity | What that means |
|---|---|---|
| Atari 2600 memory (1977) | 128 bytes | about two lines of text |
| ZX81 memory (1981) | 1 KB | a short e-mail |
| BBC Micro Model B memory (1981) | 32 KB | enough for Elite, a whole space game |
| 5.25-inch floppy disk (double density) | 360 KB | one low-quality photo |
| 3.5-inch floppy disk (high density) | 1.44 MB | about 8 seconds of CD-quality sound |
| CD-ROM | about 650–700 MB | roughly 450–490 floppy disks |
| DVD (single layer) | 4.7 GB | about 7 CDs |
| Blu-ray (single / dual layer) | 25 / 50 GB | still not enough for some current games |
The biggest releases of the 2020s often ask for 100 GB of disk space or more, which is the capacity of roughly 70,000 floppy disks.
The tricks that made tiny games possible
Developers of the 1970s and 1980s could not simply store more. They had to store less and compute the rest.
- Tiles instead of pictures. Levels on consoles like the NES were built from small 8×8 pixel tiles placed on a grid. A whole castle could be drawn from a few dozen tiles used over and over, so the level itself was just a list of tile numbers.
- The same graphic in a different colour. In Super Mario Bros., the bushes on the ground use the same shape as the clouds in the sky, only in green. Changing a palette costs a few bytes; a new drawing costs hundreds.
- Formulas instead of data. Elite (1984) offered eight galaxies of 256 star systems each on a computer with 32 KB of memory. The systems were never stored: a short number sequence generated every name, position and economy the same way each time the game ran.
- Hand-written machine code. Many games were written in assembly language, instruction by instruction, so that no byte was wasted. Programmers knew exactly where in memory every value lived.
- Simple sound. Music was a list of notes played by a sound chip in real time, not a recording. A whole soundtrack could fit in a few kilobytes.
The same idea survives in the demoscene. The first-person shooter .kkrieger (2004) fits in 96 KB because its textures, models and music are all generated by code when the game starts.
Where today's 100 GB actually goes
Open a large modern game's folder and the program files are a small fraction of it. Almost everything else is content: what you see and what you hear.
Textures and resolution
A screen in VGA mode, the standard for PC games around 1990, was 320×200 pixels with 256 colours: 64,000 bytes for a whole frame. A single 4K texture, 4096×4096 pixels, has 16.8 million pixels. Stored as raw colour (4 bytes per pixel) that is 64 MB; with the compression graphics cards use (about 1 byte per pixel) it is still 16 MB, and the smaller copies the game keeps for distant objects add about a third. A detailed character may use several such textures for colour, surface bumps, shine and wear, and a game has thousands of objects.
Sound and voice
Uncompressed CD-quality audio takes about 10 MB per minute. Modern games are fully voiced, often in five to ten languages, and their music is a real recording rather than notes for a sound chip. Even compressed, hours of dialogue multiplied by every language add many gigabytes.
Video
Cutscenes and trailers inside games are often pre-rendered video in high resolution. A few minutes of high-quality 4K video can take more space than every game released in the 1980s put together.
Copies, engines and updates
Some games store the same data more than once so that it loads faster from a slow drive, ship with large general-purpose engines and tools they use only in part, and grow with every patch. Storage became cheap, so developers spend their limited time on what players see rather than on squeezing files.
Was it better back then?
Not simply. A small game is not automatically good, and a big one is not automatically wasteful: the extra gigabytes buy faces you can read emotions on, cities you can walk through and voices in your own language. But the limits of old machines forced a discipline that is worth admiring. When every byte counted, designers kept only what made the game fun. That is why many of the games still played every day, like Tetris, Snake, Minesweeper and solitaire, need almost no space at all: their fun lives in the rules, and rules are tiny.
How big are our browser games?
We measured the games on this site, file by file. The code of all 47 browser games takes about 650 KB together; the median game is 13 KB. Add everything the site needs to run them (menus, scores, the game page itself) and the total code is about 800 KB, so the whole collection would fit on a single 1.44 MB floppy disk with room to spare.
| Game | Code size | What is inside |
|---|---|---|
| 2048 | about 7 KB | the 4×4 board, the sliding and merging rules and the score |
| Snake | about 7 KB | a 20×20 grid, the snake, the food and a speed-up every 5 pieces of food |
| Space Rocks | about 19 KB | ship physics, splitting asteroids and on-screen controls |
| Chess | about 25 KB | all the rules plus a computer opponent that searches ahead with alpha-beta pruning |
They are small for the same reasons old games were. They draw their shapes with code instead of loading pictures, their rules are short, and they lean on something already installed: your web browser, which does the job a game engine does elsewhere. To be fair, the browser itself is a large program; the games stay small because they share it instead of each bringing their own. You can see the difference in practice: a game here opens in a second, with no download and nothing left behind on your device. We wrote more about that in browser games vs app downloads.
For more of the history behind these games, read about the first video games and the arcade golden age.
Frequently asked questions
Why are modern games so big?
Mostly because of art and sound, not code. High-resolution textures, many hours of recorded voice in several languages, pre-rendered video and detailed 3D models take up almost all of a modern game's size. The program itself is usually a small part.
How big was a floppy disk?
The common 3.5-inch high-density floppy disk held 1.44 MB. The older 5.25-inch double-density disks used by early PCs held 360 KB.
How could old games be so small?
They drew the world from small reusable tiles, reused the same graphics with different colours, generated content with formulas instead of storing it, and were written very compactly, often in assembly language, because the machines had only kilobytes of memory.
Is a bigger game a better game?
No. Size mostly measures how much recorded art, sound and video a game ships. Many classic games that are still played today, such as Tetris, Snake or chess programs, are tiny.
How big are the games on Extensive Harmony?
Very small. The code of all 47 browser games is about 650 KB together; Snake is about 7 KB and Chess, with its computer opponent, about 25 KB. The site's whole code would fit on one 1.44 MB floppy disk.
