Why a tiny game patch can need gigabytes of free space
A patch’s download size tells you how much data comes over the internet—not how much room the installer needs to finish the job. Games often store code and assets in large packaged files, or in directory structures that the update tool handles as a unit. A change of only a few megabytes can therefore require the tool to build a fresh copy of a much larger package or folder.
The installer needs a safe place to work
Rather than overwrite the installed version piece by piece, an updater may create the replacement alongside it. It can apply the changes to that working copy, check that the result is usable, and then switch the game over. Keeping the original until the replacement is ready helps avoid leaving the game half-updated if something goes wrong—but temporarily means both versions occupy storage.
The exact space requirement depends on how the game’s files are packaged and how its updater applies changes. Some systems can modify files more selectively; others need room for a much larger temporary copy. The patch can be small while the install process is not.
Why personal files become part of the update
On a nearly full drive, the updater cannot reserve space for that temporary copy. The game may still have plenty of room after installation, but not enough room to complete the transition. If the same drive also holds photos or documents, deleting them can appear to be the only way to make a small patch fit.
The awkward detail is that the extra space may be temporary: once the update succeeds, the old files or staging copy can be removed. So the size shown for a download is a poor guide to whether an update will install; the updater’s peak workspace is what determines whether it can finish.
