Game size index: indicative figures by genre and by cause
A storage requirement is not a single number. It is the sum of several very different kinds of data, and each of them grows for its own reason. This page groups typical figures by genre and then unpacks what sits behind them.
Indicative figures
The table below is a planning aid. Ranges reflect how a category behaves across its lifetime, from the first release to a mature state with several content updates. Read the middle column as the space a title may settle at once playback, updates and optional packs are all present.
| Category | Indicative footprint | Primary driver |
|---|---|---|
| Modern open-world release | 110 – 180 GB | Unique art across a continuous map |
| Competitive shooter | 40 – 90 GB | Frequent map and asset updates |
| Sports simulation | 35 – 70 GB | Broadcast audio and commentary packs |
| Racing title with licensed content | 60 – 120 GB | Vehicle detail and track geometry |
| Strategy or simulation epic | 25 – 60 GB | Long-tail data tables and art |
| Independently produced narrative title | 5 – 20 GB | Hand-built scenes and audio |
Why a category range is wider than a single release
Two titles in the same genre can differ by tens of gigabytes because of decisions made long before launch. One team may bake lighting into every surface, which raises the size of each texture. Another may compute lighting as the scene plays, which lowers the stored figure but asks more of the hardware. Neither choice is wrong; they simply land in different places on the scale.
Audio is the quietest contributor of all. A production that ships full voice work in eight languages stores eight separate sets of recordings. Each set is large, and each is duplicated across the chapters of a campaign. A player who needs one language still carries the rest unless the publisher splits the audio into a separate pack.
Reading a published requirement
A published requirement usually describes the smallest sensible setup the publisher is willing to support. It tends to exclude the growth that arrives later through updates, and it may exclude optional high-resolution data. In practice, a title listed at a comfortable figure can still push against a drive once two or three substantial patches have landed.
There is also the matter of temporary space. Many setup routines build a working copy while they assemble the final data, then remove the working copy afterwards. During that window the requirement can be close to double the final figure. A drive that is nearly full at the best of times can therefore fail at exactly the wrong moment.
Turning figures into a plan
Once you accept that sizes drift upward, the useful question changes. Instead of asking whether a title fits, ask how much headroom remains after it does. A comfortable margin of roughly ten to fifteen percent absorbs patches, saved data and the transient files described above. Our storage planner suggests a method for keeping that margin intact across a whole library.
The same figures feed the compression guides. If a title duplicates art for fast access, or ships language sets you never open, those are the first places where a built-in system tool can reclaim room without altering the material you actually play. The next sections explain how that reduction works and which of the tools already on your machine can perform it.