212 GB on the page, 230 on the sleeve

The first storage figure printed on a physical Grand Theft Auto VI package reads 230 GB minimum. It was photographed on the back of a sealed German PlayStation 5 case on 7 November, twelve days before launch, and within a day the number had been set against the 212 GB Rockstar published on 3 November and reported, in English and in Chinese, as a gap of about 18 GB. Some of that coverage attributed the surplus to space reserved for an online mode. None of it put the figure beside the second Sony document that issues the same instruction.

Sony’s own product page carries a storage line, and it is the smaller number. Read today, the US listing for the game says: “Get ready by clearing a minimum of 212GB of storage space on your PlayStation 5.” That sentence and the line on the sleeve are the same kind of statement — free space a buyer must have, not a file size — and they differ by 18 GB. The German version of the same page carries no storage line at all, in the rendered text or the page data, which is a small inconsistency of its own: the market whose shops received the 230 GB sleeve is the market whose store page prints nothing.

The 18 GB is almost certainly not a second build, and the arithmetic that dissolves it went into this site’s 7 November piece. 212 GiB, the binary unit a console displays, is 227.63 decimal GB, so a package line rounded to the next round number becomes 230 — a difference of 1 per cent. Run the conversion the other way and 230 decimal GB is 214.16 GiB, which is 2.2 GiB above 212. Both readings leave about 2 GB of headroom, which is what a minimum printed on packaging is for: saves, a patch, the system’s own reserve. Neither leaves 18 GB of content. The reading the coverage chose would require an install 8.5 per cent larger than the one Rockstar described, and the only package anyone has counted in bytes — the Xbox Series X|S build at 225,336,918,016 bytes — sits under 230 in either unit.

So the instruction that is actually useful is the dull one, and no outlet we read printed it: budget 230 GB. When a printed minimum and a web sentence disagree, resolve upwards. The cost of over-clearing is one more deleted game; the cost of under-clearing is a failed install on the evening of 18 November, with the shops shut and four hours left in the pre-load window. The two purchase routes carry different clocks for exactly this reason. Digital buyers open pre-load on 10 November and have nine days; boxed buyers redeem a code from 12 November and have seven, which is the window the physical release was scheduled around.

Where the gap bites is not the console the box is for. A launch PS5 has about 667 GB usable, so 230 GB takes 34.5 per cent of the drive and 212 GB takes 31.8 per cent; either way you keep 437 or 455 GB, and nothing about a purchase changes. A 1 TB Slim leaves roughly 618 GB afterwards, a 2 TB Pro about 1.66 TB. Apply the same printed minimum to the console with the least room and the arithmetic gets sharp: 230 GB is 63 per cent of the 364 GB usable on a Series S, and that is the machine where the choice is between this game and the next three. The figure comes from a PlayStation sleeve and Rockstar splits nothing by platform, so take that last number as the shape of the problem rather than a specification.

Three things stay open. Whether the 230 GB already includes a day-one patch, which nobody has sized. Whether the PlayStation build has a byte count anywhere at all — the sleeve’s line is the closest thing to one, and it is a space figure rather than a file size. And whether the sleeve is genuine: the photographs are unattributed, the Reddit post and its author were deleted within a day, and Rockstar and Take-Two have said nothing about them. Two dates will settle the number regardless of all three. When pre-load opens on 10 November the console will report a size, and from 12 November people redeeming boxed codes will report another. If those come back near 209 to 212 GiB, the sleeve was rounding and the 18 GB was never there. If they come back at 230 GiB, the coverage was right and this article is wrong — and we will write that.