Detect Magazine logo Detect MagazineFind what others miss
Tech Notes

Why Game Download Sizes Keep Getting Bigger Each Year

A reader wrote to me last month because a single shooter had eaten 237 GB of his 1 TB drive, which left him room for roughly two other games. He had bought the console in 2020 expecting that number to be plenty.

A console storage screen showing a nearly full drive with one enormous game install beside an external hard drive on a shelf

A reader wrote to me last month because a single shooter had eaten 237 GB of his 1 TB drive, which left him room for roughly two other games. He had bought the console in 2020 expecting that number to be plenty. The uncomfortable part of my reply was that nothing had gone wrong on his machine. That is simply what the game weighs.

The usual explanation offered in comment threads is that developers have stopped bothering to compress anything. It is a satisfying story and it is mostly wrong. The gigabytes are going somewhere specific, and once you know the order of the list, the growth stops looking like carelessness and starts looking like a series of deliberate trades, a few of which I think are bad ones.

Where the gigabytes actually sit

Install sizes are not dominated by code. The executable for a huge modern game is typically in the tens of megabytes. What fills a drive is data meant to be read quickly, and it breaks down in a fairly predictable way.

ComponentRough share of a big releaseWhy it is that large
Textures40 to 60 percent4K source art, multiple maps per surface, and mip chains kept on disk rather than generated
Audio15 to 35 percentDialogue in every shipped language, often at light compression so the CPU does not decode it
Video5 to 20 percentPrerendered cutscenes and attract loops, sometimes duplicated per resolution
Geometry and animation5 to 15 percentHigher polygon budgets and motion capture libraries with thousands of clips
Code and shadersUnder 2 percentTiny by comparison, which is why patching logic is cheap and patching art is not

Textures lead, which supports the popular theory up to a point. The part that surprises people is audio. A twenty hour script recorded in twelve languages is twelve separate performances of the same content, and localisation does not compress away. On PC this is why selective language installs can cut 20 or 30 GB off an install in one tick box, and why that option is buried three menus deep when it exists at all.

Duplication on purpose

Here is the mechanism almost nobody outside development knows about, and it is the reason the lazy coding theory falls apart.

Games built in the hard drive era could not afford to seek. A mechanical drive takes somewhere around 10 to 15 milliseconds to move its head to a new position, so a level that needed forty assets scattered across the disk would stall. The solution was to pack each level's assets together in one contiguous block, in the order they would be needed. If a crate model appears in eight levels, it is stored eight times.

That is deliberate waste traded for load time, and it worked. It also means a game can be 40 percent larger than the sum of its unique assets. The practice should have faded with solid state storage, where random reads cost almost nothing, and it has started to, but slowly, because PC versions still have to run acceptably on spinning drives that users bought in 2016.

Compression complicates it further. Modern packers reach roughly 1.5 to 2 times reduction on game data, and consoles since 2020 have dedicated hardware to decompress it at several gigabytes per second. Textures already stored in GPU formats like BC7 compress poorly on top of that, because they are compressed once already. So the headline figure you see is usually a compressed number, and the uncompressed data behind it is considerably larger again.

The patch problem is worse than the install

Install size is a one off annoyance. Patch size is a recurring one, and it is where the real frustration lives.

If a developer changes one texture inside a 2 GB packed archive, the naive patch replaces the whole archive. Good build pipelines produce binary deltas instead, shipping only the changed bytes, but the delta only works if the surrounding data stays byte identical. Recompressing an archive shifts everything after the edit, so a trivial art fix can turn into a multi gigabyte download. This is why you sometimes download 48 GB for a patch note that lists four bug fixes.

Some platforms then require the console to rebuild the install while patching, which needs free space roughly equal to the patch plus the affected archives. That is the origin of the error message telling you a 15 GB update needs 60 GB free. Nothing is broken. The system is writing a new copy before it deletes the old one.

Day one patches add to this because certification submission happens weeks before release, so the disc or the preload is already frozen while development continues. The preload gets you the bulk, and the patch gets you six weeks of fixes. It also means the first run of a new PC game does a pile of local work before it is playable, which is a separate irritation covered in our piece on shader compilation stutter on PC launches.

Why I think two of these trades are bad

I am sympathetic to most of the above. Two choices I am not.

The first is shipping every language by default on console. Storage on a console is finite and expensive, the user already told the system which language they speak, and the platform holders have had the metadata to handle this for a decade. A few publishers do split language packs properly. Most do not, and that is a straightforward failure of effort rather than a technical limit.

The second is prerendered video for content the engine could produce live. A six minute cutscene at high bitrate can occupy more space than an entire level, and it looks worse than the real time rendering around it on a current machine, because it was encoded for the lowest target platform. The usual defence is determinism, meaning the sequence looks identical for everyone. That argument made sense when hardware varied wildly. It makes less sense when the same engine is already rendering the rest of the game.

What I would not blame developers for is texture resolution. Asking a 2026 release to look like 2016 to save a drive is not a serious position, and the alternative, streaming more aggressively from the network, trades disk space for a dependency on your connection that most players would hate more.

What you can actually do about it

Three things help, in descending order of effect. Install optional language packs only where the game offers them, which is most often on PC storefronts under the properties or DLC tab for the title. Delete high resolution texture packs on a 1080p display, since the difference is invisible at that output and the pack is routinely 10 to 25 GB. And on consoles, move finished games to an external drive rather than deleting them, because reinstalling later means downloading the whole thing plus every patch since.

What does not help is any utility promising to shrink an installed game. The data is already compressed, and the ones that genuinely repack it break the integrity check and trigger a full redownload. I have watched that happen to someone twice in the same month, which is also the kind of thing dataminers working inside patch files run into for different reasons.

One last number worth keeping in mind before you buy a drive. Big releases have grown roughly tenfold in fifteen years, from around 8 GB on a dual layer DVD in 2010 to the 150 to 240 GB range at the top end now. If that continues at even half the rate, a 2 TB drive holds a dozen games in 2031, and the install picker becomes a feature people choose consoles over.

FAQ

Why is a game bigger on PC than on console?

Usually because the PC build ships assets for more hardware targets and more languages, and because console versions can rely on guaranteed hardware decompression. The same game can differ by 20 or 30 GB between platforms for those reasons alone.

Does deleting a game and reinstalling it make it smaller?

Occasionally, and only because a fresh install pulls the current packed build rather than years of stacked patch data. If a game has had a dozen large updates, a clean reinstall can reclaim a few gigabytes of accumulated overhead.

Why does an update need more free space than its size?

Because the system writes the new archives before removing the old ones, so for a while both versions exist. Budget roughly double the patch size, plus a little, and the warnings stop appearing.

Will faster storage reduce install sizes?

Not directly, though it removes the reason for duplicating assets, which is one of the largest avoidable chunks. Expect that saving to arrive slowly, since PC builds still support drives that punish random reads. Graphics settings behave the same way, as our look at what ray tracing actually changes on screen explains.

RQ
Rosamund Quist

Rosamund spent years writing about game culture for print magazines before moving online. She edits Detect Magazine's features and has a soft spot for games that hide their best ideas in plain sight.

More posts by Rosamund

More in Tech Notes

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto