Language
English English Vietnamese (Tiếng Việt) Vietnamese (Tiếng Việt) Chinese (简体中文) Chinese (简体中文) Portuguese (Brazil) (Português do Brasil) Portuguese (Brazil) (Português do Brasil) Spanish (Español) Spanish (Español) Indonesian (Bahasa Indonesia) Indonesian (Bahasa Indonesia)
Gigabytes to Megabytes

Gigabytes to Megabytes

Put a game's install size and its patch queue on the same scale: gigabyte listings become megabytes, so downloads and free space can be compared directly.

Reading Game Install Sizes When Everything Is Quoted in Gigabytes

Store pages advertise a download in whole gigabytes. Patch notes, shader-cache warnings and console storage screens drop back to megabytes. When a 1 TB drive is already 80% full and the next title wants "about 90 GB", the difference between the two units decides whether you delete something tonight or not.

Restating an install footprint in megabytes puts it on the same scale as the update queue: a 4.7 GB seasonal patch and a 700 MB hotfix stop looking like unrelated numbers once both are counted the same way.

Storefronts and consoles count in decimal megabytes: MB = GB × 1,000. Worked example: a 110 GB install is 110,000 MB, so a 4,700 MB season patch adds a further 4.7 GB on top of it.

Why the Number You Download Is Not the Number on Disk

Downloads arrive compressed

Textures, audio banks and models ship packed and are expanded during installation. The store lists the transfer size; the disk pays the unpacked size, and the two can differ by tens of gigabytes on a texture-heavy title.

Working space during install

While an installer or patcher runs, the packed source and the expanded output exist side by side, plus verification data. That temporary peak — not the final footprint — is what triggers an out-of-space error at 94%.

Everything the game writes later

Compiled shader caches, downloaded high-resolution texture packs, replays and screenshots all land after installation. A folder that measured 90,000 MB on day one can quietly drift past 100,000 MB by the second season.

Checking a Download Against the Space You Have Left

1

Type the size from the store page

Put the advertised figure in the left field, which is already set to GB. Decimal sizes like 72.4 are fine, and a comma works as well as a dot if that is how your region writes it.

2

Compare it with the megabyte figures on screen

The result appears immediately on the right, with a space between thousands so a six-digit megabyte total stays readable. That is the number to line up against a launcher that reports the download queue in MB.

3

Add the patches before you decide

Convert the base install, then the day-one patch, then any high-resolution texture pack, and add them up in megabytes. Each field's copy button gives you the plain number without units so it pastes cleanly into a notes app or a spreadsheet.

4

Work backwards from a patch size

Both boxes accept input, so you can type a megabyte figure on the right — that 8,400 MB update the console is downloading — and read the gigabyte equivalent on the left. The swap button reverses the pair, and the searchable dropdowns reach TB when you are sizing the whole library rather than one title.

What Modern Install Footprints Look Like in Megabytes

Install sizes fan out far more widely than they used to. A polished 2D indie game can still fit in the space a single high-resolution texture pack occupies, while a live-service shooter carrying several years of seasonal content sits near the top of any drive. These bands cover what current PC and console libraries actually look like.

Type of title Typical install Same size in MB Titles per 1 TB drive
2D indie or pixel-art game0.5 GB500 MB~2,000
Retro or emulated collection2 GB2,000 MB~500
Mid-size 3D indie title8 GB8,000 MB~125
Cross-generation action game30 GB30,000 MB~33
Open-world RPG60 GB60,000 MB~16
Current-gen AAA with 4K textures100 GB100,000 MB~10
Live-service shooter, all seasons installed150 GB150,000 MB~6

The right-hand column is deliberately blunt: three of the biggest titles in a library can eat half a terabyte between them, which is why console owners end up rotating installs rather than keeping everything resident.

Patch queue and store page on one scale

Type in whichever unit is in front of you — the two fields convert in both directions live, so a launcher's MB queue and a store's GB listing become directly comparable.

Numbers you can total up

Each field copies the bare value with no unit attached, so base install, day-one patch and texture pack can be added together in a notes app without cleaning up the text first.

Reaches the whole storage range

The searchable unit list on both sides goes from bytes up to terabytes, so the same page handles a 400 MB hotfix and a 2 TB expansion card without switching tools.

Works on the couch or at the desk

Everything runs in the browser after the page loads, so checking a size on a phone while the console downloads is no slower than doing it on the PC.

Questions from the Download Queue

Why does the store list a smaller size than the game actually takes on my drive?

The store quotes what has to come down the wire, and that data is compressed. Installation expands textures, audio and models into the formats the engine can stream at speed, which is routinely larger than the packed archive. Some launchers show a separate "space required" figure that includes the expansion and the working files; when only one number is shown, treat it as the download and assume the disk will want more.

What exactly is a day-one patch, and does it stack on top of the install?

Discs and store builds are locked weeks before release, so fixes finished after that date ship as an update you download at launch — sometimes tens of gigabytes, occasionally larger than the base game when a whole mode was held back. It partly replaces files rather than purely adding to them, so the final footprint is usually less than base plus patch, but the peak during installation can briefly exceed both.

Why does a PC game keep growing after installation with shader caches?

PC hardware is too varied to ship pre-compiled shaders for every GPU and driver, so the game compiles them on your machine and stores the results to avoid stuttering later. That cache can reach several gigabytes on a large title, and it is usually rebuilt after a driver update. It lives outside the install folder on most launchers, which is why the folder size and the space actually consumed drift apart over a season.

If an update is a delta patch, do I still need the full amount of free space?

You need more than the download suggests. A differential update sends only the changed blocks, but rebuilding a large packed archive means writing a new copy while the old one is still in place, so the temporary requirement can be several times the patch size. This is the usual reason a 3 GB update refuses to start on a drive showing 10 GB free — the patcher is reserving room for the reconstructed files, not just the incoming data.

Do expansion cards and external drives change how sizes are reported?

The reported sizes stay the same — a 90 GB title is 90,000 MB wherever it lives. What changes is which titles are allowed to sit there. Current-generation consoles require their newest games to run from internal or certified expansion storage, while an ordinary USB drive is fine as cold storage for older titles and for anything you are not playing this week. Moving a game back from external storage is still far quicker than downloading it again.

GB
MB

Install Footprints in Megabytes

0.5 GB=500 MB
8 GB=8,000 MB
30 GB=30,000 MB
60 GB=60,000 MB
100 GB=100,000 MB
150 GB=150,000 MB

Gigabyte (GB)

The unit a store page and a console storage screen use. Current AAA titles land between 30 GB and 150 GB, so a 1 TB drive holds fewer of them than most owners expect.

Megabyte (MB)

The unit patch notes, hotfixes and download queues fall back to. A 4,700 MB seasonal update is 4.7 GB — small next to the install, but they accumulate every season.

Store pages and consoles count in decimal megabytes: 1 GB = 1,000 MB
Type a patch size in MB on the right and read its gigabyte equivalent on the left — both fields are live
Copy gives you the plain number, so base install plus patches can be totalled in a notes app
The searchable unit lists reach bytes through terabytes, from a hotfix to a whole expansion card
Want to learn more? Read documentation →
1/5
Start typing to search...
Searching...
No results found
Try searching with different keywords