You discover a promising new game, then see a storage requirement that runs into tens of gigabytes—or well past 100GB. The inconvenience goes beyond a single download. Installation size determines which titles stay in your library, how often you reinstall them, how much of a limited data plan you spend and whether your SSD has room for another game. 'It's all the graphics' captures only part of the story. Textures, recorded voices, cinematics, multiple modes, packaging decisions, compression and streaming all play a role, and some are choices rather than inevitable laws. The useful question is what occupies space on your particular platform and whether the developer gives you control over it.
100GB is not a universal requirement for modern games
Not every modern release needs an enormous install. Small games with stylized assets can offer extensive playtime using modest storage, while a project with dense maps, detailed textures and multiple language tracks may be far larger. There is no technical rule that great games need 100GB. The useful number is the current installed footprint for your platform and selected modes, not a screenshot of another edition's requirements from years ago. Size by itself is neither a review score nor a measure of how much fun a game contains.
Download size is not the same as installed size
- Downloaded package
- Installed game data
- On-demand streaming
Stores and launchers may show the data transferred over the network, while installation can unpack or reorganize it on disk. Some asset types compress better than others, and there may also be working space for checking or replacing files during an update. The temporary requirement should not automatically be added to the permanent game size, nor should a compressed download be assumed to match the final installation. When comparing games, distinguish download traffic, steady-state occupied space and peak temporary space.
Why high-resolution textures consume storage
A game world may contain multiple data maps for a surface: color, roughness, normals and other material properties, as well as different quality levels. Thousands of characters, objects and environments increase the potential volume of those assets. Modern texture formats can compress data, but quality, decode cost and hardware compatibility impose trade-offs. File size is not a direct proxy for visual excellence; repeated resources, efficient asset authoring and the way packages are assembled also matter. A large library of unique materials can cost much more space than a cleverly reused set.
Voice acting, audio and localization matter
Hundreds of recorded conversations, sports commentary, sound effects, music and cinematic dialogue take storage. Supporting several spoken languages can add substantial audio files, although translated menu text typically requires much less space than voice recordings. Some games offer downloadable language packs, while others bundle multiple tracks. It would be misleading to claim that ten text translations multiply an installation tenfold. Where voice packs are separately selectable, a player who uses one language gains a practical storage choice without losing the underlying game.
Cinematics, maps and content diversity
Pre-rendered scenes may use large video files; real-time cutscenes instead reuse in-game assets but place different demands on hardware. Campaign environments, multiplayer maps, enemy types and optional activities can each introduce unique content. A big footprint is not proof of a large or high-quality game, however. One developer may reuse assets intelligently while another duplicates data across packages. The honest comparison is between the content a player can access, the footprint of the selected modes and how the package changes with time.
Live-service modes can accumulate assets
A product that combines a campaign, competitive multiplayer, zombies, battle-royale areas or seasonal events may distribute resources that no individual player uses together. New seasons can add or replace content, and the total size may move in either direction as older assets are retired. Not every increase is lazy optimization; neither is 'live service' an excuse to deny useful options. The practical question is whether the store or launcher lets you install only the modes and content you intend to play.
Compression saves bytes but makes trade-offs
Compression reduces transferred or stored bytes at the cost of processing and design complexity; the result depends on how compressible the data already is. Precompressed videos and audio often cannot be squeezed like raw assets. Developers also need to think about decoding overhead, load-time behavior and the difficulty of updating tightly packed files. 'Just compress the game' ignores those constraints, but those constraints do not remove the obligation to communicate the actual storage footprint and available download choices.
What SteamPipe's documentation actually says
Valve's SteamPipe documentation describes how game content is organized into depots, packaged into chunks and delivered through build and update tooling. It includes advice about arranging asset packages to avoid unnecessarily expensive update behavior. This does not mean every Steam game is a modular install, or that the player can always choose individual content depots. The developer's packaging decisions influence both the game footprint and future patching behavior. SteamPipe is evidence of engineering options—not a universal promise of small installations.
Call of Duty's documented plan to reduce its footprint
In August 2024, Activision published a roadmap for reducing aspects of Call of Duty's installation burden ahead of Black Ops 6. It described separating Warzone from some other downloads and using on-demand texture streaming to reduce local requirements in certain cases. Those statements are dated plans, not a guarantee that every 2026 Call of Duty configuration uses one fixed number of gigabytes. They do show that an enormous package need not be treated as untouchable: content can sometimes be reorganized to give players fewer required components.
Streaming textures shifts costs from SSD to internet
With on-demand streaming, selected high-quality texture data can be requested across the network and cached rather than permanently bundled. This can reduce occupied local space for some configurations. The trade-off is additional network traffic and potentially more dependence on connectivity or cache behavior. Someone with reliable uncapped broadband may find the bargain attractive; a player with slow or metered internet may prefer a larger offline package. A 'storage-saving' option should disclose the possible data and connection cost rather than present the saved gigabytes as free.
A fast SSD does not create more capacity
An SSD can help a supported system read and stream game assets efficiently, but faster storage does not give the drive extra gigabytes. When capacity runs short, players uninstall titles and later pay for them again in download time and, sometimes, metered traffic. The same listed game size can be trivial for someone with several terabytes and a genuine access barrier for someone on a smaller drive. Transfer performance and storage capacity are different buying decisions, even when marketing sometimes blends them together.
Temporary patching space is a different problem
Some patch workflows need scratch space to prepare, verify or replace large data packages. This is different from the final steady-state size of the game. The behavior varies with the update mechanism and how the assets are packed, rather than following one rule for every game or launcher. We separately analyzed surprising Steam update disk activity and SteamPipe patch behavior in an earlier original article. Here the concern is the size of the base content and how it can be distributed, not diagnosing a specific download stuck at a percentage.
Why PC and console package sizes can differ
A PC package and a console package may differ due to content variants, packaging and the optional quality or language files each distribution offers. You should not assume that a PC store listing predicts an identical PS5 footprint. Nor should the install options of one popular game be assumed standard everywhere. Before committing to a large release, check the current size on your platform, whether optional high-resolution assets and language tracks exist, and how much headroom future updates may need.
What PS5 storage choices really allow
Sony explains that PS5 offers console storage, compatible M.2 SSD expansion and USB extended storage with different abilities. PS5 games can be stored on supported USB drives, but must be moved to console storage or a supported M.2 SSD to play; eligible PS4 games can run from suitable USB extended storage. Sony separately specifies installation and compatibility requirements for M.2 SSD expansion. A bigger drive can solve a personal capacity shortage but is an additional expense, not proof that a large game is well packaged.
What publishers should disclose before purchase
Publishers could state download size and expected installed footprint separately, identify removable modes or voice packs, and explain whether texture streaming consumes more network data. Estimates for unusually large temporary update space can also prevent surprises. Such disclosure need not reveal proprietary asset technology. It would simply allow players with smaller SSDs, shared consoles or metered connections to make informed decisions about buying and keeping games installed instead of discovering the real cost after purchase.
Conclusion and sources: give players a meaningful choice
Large installs have understandable technical causes: detailed assets, substantial audio, many environments and packaging constraints. But organization, optional packages and transparent trade-offs can make those costs fairer. This editorial analysis uses Valve's SteamPipe documentation, Activision's August 2024 Call of Duty size roadmap and Sony's official PS5 storage and M.2 SSD support information. Individual download sizes and platform policies can change, so always confirm the current details for your chosen version. The primary sources are linked below.