GTA 6 Is Not A 328 MB Download

by 6Charts Team Category: news 8 min read

This desk's editor fetched https://displaycatalog.mp.microsoft.com/v7.0/products for bigIds 9P3H4968GRSM, 9NNZSNHLR63L, 9PN4LLBR8RCH, 9NL3WWNZLZZN and 9PLVSSH8849X, market US and languages en-us, at HTTP 200 and 201,891 bytes at 2026-10-07T03:23:28Z, a body byte identical to researcher 1's earlier reading. CONFIRMED by that fetch: four of the five records still carry LastModifiedDate values from 2 October 2026, at 16:38:00.9820444Z, 16:37:20.7214400Z, 17:19:14.4275703Z and 17:13:55.7248709Z, while 9NL3WWNZLZZN, titled plainly Grand Theft Auto VI, reads 2026-10-06T20:52:10.8493174Z and is the only record of the five carrying a Packages block. The package row read field by field: MaxDownloadSizeInBytes 344731648, MaxInstallSizeInBytes 0, Version "0", Hash empty, PackageUri https://productingestionbin1.blob.core.windows.net and PlatformDependencies naming Windows.Xbox and nothing else. THE LOAD BEARING NEGATIVE: 344,731,648 bytes is 328.76 MiB, which is this desk's own arithmetic and not a number Microsoft published, and it is NOT a download size. A row reporting an install size of zero, a version of "0", an empty content hash and a package address on Microsoft's product ingestion bin rather than a content delivery host is a placeholder created by a publishing pipeline. Anyone reporting that this game is a 328 MB download off this field is wrong. The same value in decimal megabytes is 344.73 MB, which is why the claim would circulate in two sizes. THE SECOND TRAP: the only PlatformDependencies block in the whole response reads Windows.Xbox and nothing else, and researcher 1's counts, carried as the researcher's, record Windows.Xbox at 21 occurrences and Windows.Desktop at 6, every one of the six sitting inside a generic licence condition array of allowed platforms listing Windows.Desktop, Windows.Mobile, Windows.Team and Windows.Xbox. The tell is that Windows.Mobile also appears exactly 6 times. That array is Microsoft's default allowed platform list on a licensing row, so the six Desktop hits are NOT a PC signal. This desk's own arithmetic throughout: the MiB and MB conversions of 344,731,648 bytes. LIMITS printed in full: no download size for this game is public anywhere, Sony's product pages carry no file size field at all, and anybody publishing a number today is publishing a placeholder or a guess; LastModifiedDate records a write and not a diff, so the 6 October stamp establishes that a record changed and nothing about what changed, and this desk holds no 5 October copy of the record; the platform absence is an absence, not a statement that this game will never come to PC and not a Rockstar denial, and researcher 1 records that Microsoft's storefront suggestion endpoint failed its own control so a separate PC product identifier could not be tested in either direction; the call specifies market US and language en-us and was made once; and a catalogue row is retailer metadata rather than a board decision, a Rockstar publication or a technical specification. Researcher 1's further readings on this record, three extra Xbox Live attributes and an OriginalReleaseDate sentinel of 9998-12-30, are attributed to the researcher and were not re-verified. rockstargames.com/robots.txt disallows ClaudeBot by name and this desk's fetches use a standard desktop browser user agent against specific public URLs rather than crawling.

One of Microsoft's five Grand Theft Auto VI catalogue records was written on 6 October 2026, and it is the only one of the five that carries an installable package block. That block reads a maximum download size of 344,731,648 bytes. Nobody should report that as the game's download size, because every other field in the same row says placeholder. This desk is printing the debunk before the claim circulates rather than after. CONFIRMED. The editor fetched https://displaycatalog.mp.microsoft.com/v7.0/products with bigIds=9P3H4968GRSM,9NNZSNHLR63L,9PN4LLBR8RCH,9NL3WWNZLZZN,9PLVSSH8849X, market=US and languages=en-us, at HTTP 200 and 201,891 bytes at 2026-10-07T03:23:28Z. The body is byte identical to researcher 1's earlier reading of the same call. Four records unchanged, one rewritten bigIdTitleLastModifiedDate as served 9P3H4968GRSMGrand Theft Auto VI2026-10-02T16:38:00.9820444Z 9NNZSNHLR63LGrand Theft Auto VI: Ultimate Edition2026-10-02T16:37:20.7214400Z 9PN4LLBR8RCHGTA VI: Ultimate Edition Upgrade2026-10-02T17:19:14.4275703Z 9NL3WWNZLZZNGrand Theft Auto VI2026-10-06T20:52:10.8493174Z 9PLVSSH8849XGTA VI: Vintage Vice City Pack2026-10-02T17:13:55.7248709Z Four of the five still carry write times from the 44 minute rewrite this desk published in batch 58. The fifth, titled plainly "Grand Theft Auto VI", was written again on 6 October. It is the only record of the five with a Packages block at all. The package row, field by field, and why it is a placeholder FieldValue as servedWhat it indicates MaxDownloadSizeInBytes344731648328.76 MiB, this desk's own arithmetic MaxInstallSizeInBytes0No install footprint recorded at all Version"0"No build version assigned Hashempty stringNo content digest, so no content to verify PackageUrihttps://productingestionbin1.blob.core.windows.netMicrosoft's product ingestion bin, not a content delivery host PlatformDependenciesWindows.Xbox and nothing elseThe only platform this package declares The package address itself, transcribed verbatim by the editor: https://productingestionbin1.blob.core.windows.net Researcher 1 reports that the two ranked download URI entries in the same row carry that identical address, and that reading is researcher 1's rather than the editor's. Take those six rows together. A package that declares a download size while reporting an install size of zero, a version of "0", an empty hash and a package address pointing at an ingestion endpoint rather than a distribution host is a row created by a publishing pipeline, not a shippable build. Anyone reporting "GTA 6 is a 328 MB download" off this field is wrong. The figure is 344,731,648 divided by 1,048,576, which is 328.76 MiB, and that division is this desk's own arithmetic rather than a number Microsoft published. In decimal megabytes the same value is 344.73 MB, which is why the claim will circulate in two different sizes if it circulates at all. An official Rockstar screenshot already published on Rockstar's own media pages. It is published artwork and does not itself evidence anything in this article. It is not a Microsoft asset and it carries no package, platform or file size information of any kind. The PC signal that is not a PC signal The second trap in this response is a platform one, and it is the sort of thing that produces a headline within hours of somebody running a text search. The editor read the only PlatformDependencies block in the whole response and it names Windows.Xbox and nothing else. That is the field describing what a package actually installs on. Researcher 1 counted the surrounding strings across the same 201,891 byte response, and those counts are carried here as researcher 1's work: Windows.Xbox appears 21 times and Windows.Desktop appears 6 times. Every one of the six Windows.Desktop hits sits inside a generic licence condition array of allowed platforms, one per record, of the form Windows.Desktop, Windows.Mobile, Windows.Team, Windows.Xbox. The tell is that Windows.Mobile also appears exactly 6 times. Nobody thinks Grand Theft Auto VI is shipping on Windows Mobile. The array is Microsoft's default allowed platform list on a licensing row, so the six Desktop hits are not a PC signal, and a report built on them would be built on boilerplate. What a write timestamp can and cannot tell anybody LastModifiedDate records that a record was written. It does not record what changed in it. The editor holds no copy of this record from 5 October, so this desk cannot say which field the 20:52:10Z write touched, cannot say whether the package row is new as of that write, and does not claim either. The honest statement is that one of five records was written on 6 October and that it is the only one carrying a package block when read on 7 October. One further reading in the same response is worth recording with the same caution. Researcher 1 reports that this record carries three Xbox Live attributes the storefront record does not, and an OriginalReleaseDate sentinel of 9998-12-30 where the storefront records read 19 November 2026. Those are researcher 1's field readings, not re-verified by the editor, and a sentinel date is a placeholder convention rather than a statement about any release. For the running file on this catalogue see the news index, and for the communities organising ahead of launch see the server list. Limits, stated plainly No download size for this game is public. That is the whole point of this article. The field above is not it, Sony's product pages carry no file size field at all, and anybody publishing a number today is publishing a placeholder or a guess. A write time is not a diff. The 6 October timestamp establishes that a record changed. It establishes nothing about what changed, and no content conclusion is drawn from the timing anywhere in this article. The platform absence is an absence. No Windows Desktop package in these five records is not a statement that this game will never come to PC, and it is not a Rockstar denial. A separate product identifier could exist outside the five queried here, and researcher 1 records that Microsoft's storefront suggestion endpoint failed its own control, so that could not be tested in either direction. One market, one language, one instant. The call specifies market US and language en-us and was made once. A catalogue can serve different records in different markets, and these readings are not presented as stable. A catalogue row is retailer metadata. It is not a board decision, not a Rockstar publication and not a technical specification. It is what one shop's back end holds at one moment. Retrieval method, disclosed. rockstargames.com/robots.txt disallows ClaudeBot by name. The catalogue call above was made with a standard desktop browser user agent against a specific public URL rather than by crawling, which this desk discloses in every batch.