Game installs are large now because they hold far more data than the ones you grew up with: 4K and 8K texture sets, lossless audio stems, full voice recordings for every language, entire open worlds sitting ready to stream, plus the day-one patches that land before you ever press play. A 150 to 250GB install is normal for a big modern release, where a cartridge-era game shipped on a single 64MB chip.
That answer gets you the headline number. The interesting part is where those gigabytes actually sit, and which ones a developer could have avoided shipping.
The short version in one line: a modern game ships far more visual and audio detail than it used to, keeps all of it ready to load instantly, and adds to it with updates after launch. Nothing about an SSD or a console drive is forcing that. It is a content decision, and content decisions are made by people with deadlines.
If you have ever paused mid-install because your drive filled up, or deleted a finished game to make room for the next one, this is the explanation for why that keeps happening.
Table of Contents
- Why Are Game Installs So Large Now?
- What Takes Up the Most Space in a Modern Game?
- How High-Resolution Textures Increase File Sizes
- Why Geometry and Lighting Data Keep Growing
- Why Games Use So Much Audio and Video Space
- How Pre-Loading, Updates, and Reserved Space Add to Installs
- Why PC and Console Install Sizes Can Differ
- Does a Faster SSD Make Games Need More Storage?
- Why Do Some Games Keep Extra Space Unused?
- How Developers Can Reduce Game Install Sizes
- Frequently Asked Questions
- Is 4K textures the main reason game installs are so large?
- Does a faster SSD change how much storage a game needs?
- Why is my game bigger on PC than on console?
- Is it safe to delete optional game files and shader caches?
- How much free space should I keep for installs and updates?
- What Should You Do First?
Why Are Game Installs So Large Now?
Six things drive the growth, and they compound rather than replace each other.
- Resolution. Texture sets now ship at 4K and sometimes 8K, and every material carries extra maps — normal, roughness, metallic, ambient occlusion — alongside the color image.
- Audio fidelity. Music ships as uncompressed stems rather than a single mix, and effects use more channels than a 2010 title would have considered.
- Every language at once. Full voice acting means hours of dialogue recorded and stored per language, whether you plan to hear it or not.
- Preloaded open worlds. Seamless travel requires every region to be resident and ready, so nothing gets stripped out at install time.
- Day-one patches and DLC. The base download you pay for on disc or preload is a subset of what ends up on your drive.
- Engine and framework overhead. Modern engines ship their own bundled components, cached shader data and platform files alongside the game.
The scale change is worth putting in plain view.
| Era | Typical example | Rough install size |
|---|---|---|
| 1980s–1990s cartridge | 8-bit and 16-bit console titles | Under 1MB to 2MB |
| 1996 CD-ROM era | Early 3D console and PC releases | 500MB to 2GB |
| 2005–2010 | Console HD era, high-definition consoles | 5GB to 20GB |
| 2011 | The Elder Scrolls V: Skyrim | Roughly 12GB to 15GB |
| 2020s open world | God of War Ragnarok, The Last of Us Part II Remastered | Roughly 150GB to 190GB |
| Live service, several years in | Warzone and Fortnite combined | Around 300GB |
| Outlier territory | ARK: Survival Evolved after updates | Close to 400GB |
Small games prove the ceiling isn’t fixed. Hades sits around 15GB and Doom Eternal near 50GB, both dense, modern-looking titles. Nothing about high frame rates forces a specific number.
What Takes Up the Most Space in a Modern Game?
Textures dominate most installs, audio comes second, and a long tail of smaller systems eats the rest. Exact shares vary by title, so treat the ranges below as a guide rather than a promise.
| Category | What it holds | Typical share of a 150–250GB install |
|---|---|---|
| Textures and materials | Color, normal, roughness, metallic, AO maps at every quality tier | 40–60GB, sometimes far more |
| Character and world models | High-density geometry, skeletal rigs, animation clips | 20–50GB |
| Audio | Music stems, effects, ambience, voice per language | 10–30GB |
| Video | Pre-rendered cutscenes, trailers, intros | 2–20GB |
| Game data and scripts | Levels, physics, AI, save systems | 10–25GB |
| Engine and platform overhead | Shader caches, runtime files, framework components | 3–15GB |
How High-Resolution Textures Increase File Sizes
A texture resolution is simply the pixel dimensions of an image wrapped onto a surface. Here’s the arithmetic that matters: 1080p is about 2.07 million pixels, 4K is about 8.3 million, and 8K is about 33 million.
Move from 1080p to 4K and you quadruple the pixel count, so each texture becomes roughly four times larger. Go to 8K and you multiply by sixteen. One 1080p surface stored uncompressed at four bytes per pixel takes about 8MB; the same surface at 4K takes about 33MB.
Then the multiplier stacks. Mipmaps add a smaller copy at each step down the pyramid, roughly a third more on top. Normal maps store a direction per pixel rather than a color, and roughness and metallic maps add further passes over the same surface. A single wall or character costume can carry six or eight of these maps per quality tier.
That’s the core mechanism behind why game installs are so large now: a single surface can exist at low, medium, high, ultra and 4K settings, and if all of them ship together, one material costs more than a whole game did a decade ago. Good news is that most modern releases now let you install without the high-resolution tier. On a 1080p display, dropping it can reclaim tens of gigabytes.
Why Geometry and Lighting Data Keep Growing
Textures are the obvious culprit, but geometry has quietly grown too. A character model at the detail level a current-gen game targets carries far more vertices than the same character did fifteen years ago, and skeletal animation data scales with it. A crowded open-world scene may carry millions of individual pieces of geometry, each with its own materials and texture references, and none of it can be deleted without the scene looking wrong.
Lighting data is the newer addition. Ray tracing and path tracing need extra scene data describing light bounce and occlusion, and those materials and buffers are typically authored at high resolution too. That is one reason a modern game will offer a lower ray tracing setting that not only drops the visual effect but also trims assets, instead of only lowering frame rates.
Level of detail is what keeps this manageable at runtime: distant objects load simplified versions, so the drive holds the high-detail set while memory holds the cheap one. That means the files stay large even though the game never loads most of it at once. Install size measures what is available, not what is currently in use.
Why Games Use So Much Audio and Video Space
Audio bloat is usually an engineering choice rather than a creative one. Music used to be delivered as a compressed mix; now many titles ship layered stems so the score can rebalance as gameplay shifts, which multiplies storage even though you only ever hear the final result.
Voice is the bigger number. A modern role-playing game can run tens of thousands of lines of dialogue, and full localization means every one of those lines recorded, edited and stored again for each supported language. A game with 40,000 lines and ten fully voiced languages carries a serious chunk of audio you will never load.
Pre-rendered video is straightforward: it is a movie file, and movies are large. Cutscenes and trailers stored as high-bitrate video add up quickly, and they cannot be re-compressed at install time without visible quality loss. Add spatial or multichannel effects data and the audio side stops being a rounding error.
How Pre-Loading, Updates, and Reserved Space Add to Installs
The number in the store listing is rarely the number you’ll see on your drive a week later. Day-one patches are the biggest reason, and console owners hit it hardest: a physical disc install of 15GB to 25GB regularly expands to 80GB or 150GB once launch updates land.
| Title | Launch install | After updates and DLC |
|---|---|---|
| Large open-world action game, disc edition | 15GB to 25GB | 80GB to 150GB |
| Live-service shooter, several seasons in | Around 100GB at launch | Near 200GB |
| Base game plus optional content library | Base size only | Frequently doubles |
Shader caches are a separate, sneaky contributor. Modern engines compile lighting and material shaders the first time they meet your hardware, and that compiled output is written to disk so your second launch is fast. A first playthrough on an unfamiliar GPU can quietly add several gigabytes.
On a PC with a capable card that is new to you, this is where a chunk of your post-install folder size comes from. On console, the equivalent work is baked in at build time, which is one small reason console installs start smaller.
Preloads are the most irritating category. Some store pages ship a portion of the game ahead of launch so you can play the moment it unlocks, and many listings advertise the expected post-launch size rather than what is actually available at preload. That means the download can shrink once the patch goes live, leaving you with a preloaded folder that no longer matches the number you planned your drive around.
There is one more forum favourite: why does a game on your G drive also want space on your C drive? Usually because the launcher or the platform layer keeps its own files on the system drive, and some engines write crash logs or configuration there. And why do updates sometimes feel like a full reinstallation? Because a large patch often rewrites entire asset archives rather than a few files, and a patched archive plus the original can briefly coexist before the old one is removed.
Finally, installers need room to breathe. Downloading a compressed archive and unpacking it requires the compressed file and the extracted file to exist at the same time, which is why launchers typically ask for 20% headroom above the stated size. Forum threads on r/steamsupport and steamcommunity.com/discussions fill up with people who discovered this halfway through an install, right after downloading a finished 80GB archive.
Why PC and Console Install Sizes Can Differ
Console builds are often smaller on disk than PC builds of the same game, and the reason is mostly about how the data is packaged. Console titles are built to fixed hardware targets with assets pre-arranged for streaming from fast internal storage, while PC builds often carry every supported resolution tier, plus compatibility layers and platform files the console never needs.
Not every title follows this pattern. Some PC builds are smaller because of aggressive compression; some console builds are larger because a later revision shipped with better textures. Check the actual listing rather than assuming.
Console players also hit a different ceiling: fixed total capacity.
| Platform | Usable game storage out of the box | Expansion route |
|---|---|---|
| PlayStation 5 | About 667GB of the 825GB drive | Proprietary SSD expansion |
| Xbox Series X | Roughly 1TB of the 1TB drive | External USB drive |
| Xbox Series S | About 512GB of a smaller SSD | External USB drive, but slower |
| Gaming PC | Whatever you installed | Add drives, move libraries, use external storage |
On a 512GB console, two modern open-world games plus updates can fill the drive. That is why the delete-and-reinstall cycle is so common there, and why keeping older finished titles on an external drive is standard advice rather than a workaround.
Optional content packs complicate the picture on both platforms. A game that needs 120GB on disk might let you install only the multiplayer portion, or only the campaign, and store the rest on the drive until you want it. That choice is worth finding before you install, because it can be the difference between a game that fits and a game that does not.
The other asymmetry players notice is that console storage is a fixed ceiling while PC storage is a purchase. A console owner cannot solve the problem with better hardware without buying a licensed expansion card. A PC player can add a drive, or move the entire library somewhere cheaper, which is why install size bites harder in living rooms than it does at a desk.
Does a Faster SSD Make Games Need More Storage?
No, not directly. SSD speed changes how fast your game loads and how smoothly it streams, not how many bytes it occupies. A faster drive will not turn a 100GB game into a 60GB game.
The distinction worth keeping straight is between four separate numbers: the download size on the store page, the installed size on your drive, the space the installer needs while unpacking, and the RAM the game uses at runtime. Only the third one has a technical reason to shrink with a faster drive.
The indirect effect is real, though. A studio shipping to a known base of fast Gen4 and Gen5 NVMe drives has less reason to scale its asset quality back for older hardware, and developers targeting capable modern hardware can afford heavier assets. PC builds are also frequently built as the highest-fidelity version, which is part of why they often read larger than the console equivalent. What VRAM you have matters as much as how fast your SSD is.
There is a related confusion worth clearing up, because people build whole PCs around the wrong assumption. Buying a very fast NVMe drive will not stop a game from taking longer to load if the game itself is limited by its own streaming logic. What actually helps is having the game on an SSD rather than a hard drive, and having enough free space that the drive is not near capacity, because nearly full SSDs slow down as they fill.
RAM is the other number people conflate with storage. Your system memory holds what is loaded right now; your drive holds everything available. A game with a 200GB install might use 16GB of RAM at any moment, and closing it changes neither figure.
The economic pressure is real. A 1TB SSD that felt enormous a few years ago now holds four or five big titles, so buying a 2TB or 4TB drive becomes part of owning a modern gaming PC. Build advice on r/buildapc has settled on 2TB as the practical minimum, with a second slower drive for less frequently played games. That is a real cost that traces back directly to install sizes.
Why Do Some Games Keep Extra Space Unused?
Drives allocate space in fixed blocks rather than bytes. If a file needs 100KB and the block size is 4KB, a chunk goes unused; over hundreds of thousands of small assets, rounding adds up to a noticeable gap between the sum of your files and what the drive reports.
Some of that slack is deliberate. Patching needs somewhere to write new data before old blocks are reclaimed, and modern filesystems and launcher libraries keep a percentage of free space available precisely so that a patch doesn’t fail halfway through. Your launcher also reserves space for its own files, and estimates built before a patch is final are frequently conservative.
Compression is the other half of the puzzle. Many games ship already-compressed in a container the engine can read directly, which is why the same game can be 90GB on one launcher’s listing and 140GB on another’s. Different versions of the same title, different compression settings, different results.
There is one more effect most players don’t notice. Compression tools such as CompactGUI and Steam Cleaner repack installed game files into a form the game can still read, which reliably shrinks several games by meaningful amounts. Deleting a shader cache before you switch GPUs, or before a driver update, reclaims the same space again. And mobile is the extreme case: Call of Duty Mobile installs have been pushed past 100GB on devices that only carry 128GB of storage total.
It helps to separate bloat into two categories. Some of it is genuinely unavoidable given the design: a seamless open world with four quality tiers of every material has a floor. The rest is laziness or a commercial decision, usually duplicated assets that were never cleaned up, or a single artist shipping their own copy of a texture that three other people already shipped.
How Developers Can Reduce Game Install Sizes
Most of the bloat is a choice, and studios have tools that trade a little convenience for a lot of space.
- Optional high-resolution packs. Ship the 4K and 8K tiers as a separate download so 1080p players never download them.
- Streamed audio instead of stems. Loading a compressed mix on demand removes the need to store every layer.
- Separate language and voice packages. Shipping text-only localization for most languages and full voice as an opt-in download cuts audio dramatically.
- Better compression. Modern codecs and per-file compression are cheap, but only help where the source assets are not already tightly packed.
- Deduplicated shared files. Identical assets used by several levels or modes should exist once, not once per usage.
- Virtualized texture streaming. Technologies from the Unreal Engine 5 generation let engines keep only the portions of a texture that are actually visible in memory, which reduces runtime memory pressure but does not by itself shrink the download.
The interesting disagreement is over whether AI upscaling will help. The optimistic case is that if a 1080p image upscaled by a neural network looks like a native 4K image, studios can ship the lower-resolution texture and let the GPU fill in the rest, shrinking the largest category in every install. The catch is that today’s upscalers mostly reconstruct a single frame using information already in that frame, so they cannot recover genuine high-frequency detail that was never authored. Expect texture sizes to fall somewhat, not to collapse.
Engine technology gets blamed here more than it deserves. Nanite-style virtualized geometry and Lumen-style dynamic lighting are often cited as causes of bloat. Both make it possible to render far more detail than earlier approaches, but the streaming and deduplication work built around them is usually the reason a well-optimized title on the same engine stays a fraction of the size of a badly built one. Hades and Doom Eternal are both modern-looking games with no hardware excuse for their size.
There is also a business reason to leave things uncompressed. Compression takes time at build and test, and developers under deadline pressure skip it. Bigger files are also a mild upsell for premium editions, and a launch-day install failure on a filled drive generates support tickets nobody wants to read. None of that requires a technical justification.
Player-side measures do the same job without a developer’s cooperation. In a video settings menu, stepping from 4K down to high quality textures is usually the single biggest change. After that, removing voice packs for languages you will never select, clearing the shader cache before a driver change, moving older titles to a slower secondary drive, and running a compaction tool on formats that support it will get you most of the way back.
Frequently Asked Questions
Is 4K textures the main reason game installs are so large?
4K textures are the single biggest contributor in most modern titles, often accounting for 40GB or more on their own. But they are not the only driver. Uncompressed music stems, fully voiced dialogue for every supported language, pre-rendered cutscenes, dense geometry and accumulated day-one patches all add up. Switching to a medium or high texture setting instead of 4K often reclaims tens of gigabytes on its own.
Does a faster SSD change how much storage a game needs?
Not directly. SSD speed affects load times and how smoothly assets stream, not the number of bytes a game occupies. The one exception is install-time: a faster drive shortens the window where you need temporary space for unpacking. Faster hardware can indirectly encourage larger installs, though, since studios targeting capable systems have less reason to scale asset quality back.
Why is my game bigger on PC than on console?
PC builds are often the highest-fidelity version, carrying every resolution tier and optional content, plus compatibility layers and platform files a console never needs. Console titles are built to fixed hardware targets with assets arranged for streaming from fast internal storage. The pattern is common but not universal, so check the actual store listings for the specific game before assuming.
Is it safe to delete optional game files and shader caches?
It depends on what you delete. Language and voice packs are safe if you never switch to that language, and shader caches are always safe because the game recompiles them, though you pay a performance cost on the next launch. Never delete core game files manually. Tools like CompactGUI and Steam Cleaner work on the supported formats only and will decline anything they cannot repack safely.
How much free space should I keep for installs and updates?
Keep at least 20% more free space than the stated install size, because the installer needs room to unpack compressed archives alongside the downloaded files. Beyond that, live-service titles grow every season, so leaving 150GB free on a 1TB drive for a game that will expand is a reasonable habit. Preorders also install before launch patches land, so expect the folder to grow afterward.
What Should You Do First?
Check the publisher’s own storage requirement rather than the store listing, since those numbers usually include patches and optional content. Then reserve headroom above that figure, and treat 20% as the floor rather than the goal.
If space is genuinely tight, the highest-resolution texture tier is almost always the biggest single thing you can drop without hurting the game. Follow it with language and voice packs you will never use, finished titles moved to an external drive, and shader cache cleanup as a free one-time reclaim.
As for whether game installs are so large now because of any single cause, the honest answer is that no one factor does it. Resolution, audio, voice, preloaded worlds and patches each took a turn growing, and the total is the sum of all of them.
