Storage planner: fitting a library into a real drive
A plan is not a list of titles. It is a set of rules for deciding what stays, what waits and how much room is held back. This page sets out rules that stay useful as releases keep growing.
Rule one: reserve headroom before anything else
Take the stated capacity of a drive and subtract the operating system, the page file and the working space the system keeps for updates and caches. What remains is your true budget. Then hold back a further ten to fifteen percent as active headroom. That margin pays for patches, saved data, temporary working copies and the shader cache described elsewhere on this site.
Readers who skip this step tend to experience the same pattern: a drive works well for months, then a routine update fails because there is no space left to build a working copy. The failure feels sudden but it was predictable.
Rule two: separate the fast tier from the archive
Not every title needs to live on the quickest device at the same time. A practical arrangement has two tiers. The fast tier holds whatever is played this week. The archive tier, which may be a larger and calmer device, holds everything else. Moving a title between tiers is a normal housekeeping task, and it keeps the fast device well inside its budget.
Rule three: pressure-test the wish list
Write down the titles you actually intend to play in the next month. Add their indicative figures from our size index. Add the headroom. If the total exceeds the budget, the decision is already made for you: something moves to the archive tier. Being explicit about this early avoids the scramble later.
A worked example
| Item | Indicative need | Note |
|---|---|---|
| System and working space | 60 GB | Not available for titles |
| Fast-tier titles (three) | 240 GB | Played this month |
| Active headroom | 80 GB | Patches, caches, saves |
| Reserved total | 380 GB | Comfortable on a 500 GB device |
Read the example as a shape rather than a fixed plan. The important part is the third row. Headroom is a line item, not whatever is left over.
When to reach for reduction
If the archive tier is already full and the fast tier is close behind, reduction becomes worthwhile. Two of the levers are built into the operating system: a general-purpose compressor for directories you rarely touch, and a storage manager that shows what is actually consuming room. Our built-in tool guides cover both, platform by platform. A third lever is honest reduction at the source: choosing a smaller language set, skipping an optional high-resolution pack, or removing bonus material once it has been viewed.
Keeping the plan alive
A plan decays. New titles arrive, patches land, and preferences change. Two habits keep it healthy. The first is a short monthly review: confirm the headroom is still where you expect it. The second is a seasonal review, timed to the sales windows we describe elsewhere, when prices fall and libraries tend to grow. Between those two habits, a modest drive can stay comfortable for years.