An archive of roughly 12TB, reportedly originating from Valve's old Steam2 content delivery infrastructure, has been under investigation by the game preservation community since August 29, 2026. The post that sparked the discovery described the data as spanning 2003 to 2013, citing early versions of Portal 2 and Left 4 Dead, a prototype of Counter-Strike: Global Offensive, and material from the unreleased project "F-Stop." What drew the most attention was a Weaponizer 3D model suspected of ties to Half-Life 2: Episode 3. However, public information only confirms a link at the level of a single asset—no complete, executable build of Episode 3 has been publicly verified.
Making sense of this archive requires separating three distinct things: "depots," the units Steam used to deliver games; "assets," development material repurposed for other projects along the way; and "builds," playable, executable versions of a game. Without this distinction, more than ten thousand distribution units can be mistaken for ten thousand unreleased games, and a single weapon model can balloon into a legendary lost sequel.
What 10,876 Depots Actually Tell Us About the 12TB
The published "Steam2 Depot Manager" catalog maps 10,876 depot IDs to their corresponding names. A depot is simply the unit Steam used to distribute files for a game or application. Beyond the core game itself, separate IDs exist for language-specific data, OS-specific executables, dedicated servers, and shared assets used across multiple titles. So the figure 10,876 represents neither a count of games nor a count of unreleased builds.
The catalog makes this distinction clear at a glance. Portal 2 alone spans multiple depots, IDs 621 through 628, with depot 629 assigned to an authoring tool. Half-Life 2 and Left 4 Dead likewise have both core content and shared data, split further by language version and server-side components. The archive extends well beyond Valve's own catalog, too, encompassing numerous third-party titles that were distributed through Steam at the time. Treating the roughly 12TB figure as "a warehouse containing nothing but Valve's unreleased games" is not accurate.
The archive's size and provenance also warrant caution. Gabe Follower, an account that tracks Valve-related information, stated that the archive was obtained from a publicly accessible endpoint and involved no unauthorized intrusion. Valve, meanwhile, had issued no statement as of August 31 regarding the archive's authenticity, total size, or public accessibility. Figures of both 12TB and 13TB have circulated, so at this stage the only confirmed fact is that the archive was reported to be roughly 12TB in scale.
A Snapshot of Distribution, Not an Internal Repository
The Steam2 Depot Manager tool mounts user-supplied .blob and .dat archive files without extracting them. It cross-checks the CRCs indicating parent-child relationships, the corresponding DAT file sizes, and the keys required for decryption, refusing to mark anything as ready if data is missing or duplicated. What's published on GitHub is this viewing tool and the catalog itself—it neither includes nor distributes the actual game files.
Distribution depots are file sets bundled at a given point in time to be delivered to customers or testers—a fundamentally different role from a full source control history. They don't necessarily contain commit records showing who changed what, internal emails, or design meeting notes. What they do tend to preserve are working executables and audio or models that were cut from the final release. Rather than documentation tracing developer intent, this data is closer to a frozen cross-section of builds as they existed at the time.
According to Valve's current documentation, the successor system SteamPipe splits files into roughly 1MB chunks, compresses and encrypts them, and delivers them over HTTP. It generates a 64-bit manifest ID for each depot version and, on update, transmits only the changed portions; inactive versions are said to be hidden from users. The explanation that data from the old Steam2 system cuts off around 2013 is consistent with this generational transition, but it doesn't prove anything about the state of the old endpoints based on current encryption specifications alone.
The Alternate Future Preserved in Portal 2 and F-Stop
Portal 2 offers a clear illustration of why this material could matter to game history. According to Valve developers speaking at the 2012 Game Developers Conference, the game's early concept shared almost nothing with its predecessor besides the Aperture Science research facility setting. The team had removed the portal gun and was building the sequel around a new mechanic called "F-Stop."
Material the community claims to have booted, dated to around 2009, shows GLaDOS staging and voice lines that differ from the final release, along with placeholder models from other titles. Assets related to F-Stop likewise capture a period when development was headed in a different direction from the Portal 2 that ultimately shipped. The released game and developer interviews alone make it difficult to verify precisely which concepts made it how far, or which pieces carried over into later projects. Working cross-sections of the game let researchers compare adopted ideas against abandoned ones under the same conditions.
That said, the volume of early-stage assets doesn't indicate how complete a game was. Even with a full set of models and textures, a title can't function as a playable game without maps, progression systems, and scripting. And when something can be booted up, its meaning differs depending on whether it represents an actual complete build from that era or a reconstruction pieced together from multiple depots after the fact. Verifying this requires records of depot parent-child relationships along with file hashes.
What the Weaponizer Confirms—and What It Doesn't
The public material surrounding the Weaponizer becomes much clearer when broken into four tiers of evidentiary strength.
| Evidence tier | What public material confirms | What it does not confirm |
|---|---|---|
| Distribution depot catalog | 10,876 IDs spanning both Valve and third-party titles | 10,876 actual games; full data integrity |
| Single development asset | A placeholder model for a Paint Gun in Portal 2's reslist is linked to the Weaponizer | Episode 3 maps, scripts, or campaign content |
| Valve's official prototype footage | 2024 official footage shows an Ice Gun, a blob-type enemy, and an unidentified weapon | That Episode 3 was ever completed |
| Complete executable build | No publicly verified evidence exists at this time | Any assessment that the game was close to release |
What this comparison shows is that reused models can trace a lineage of development without carrying proof of a finished game. The technical record confirms, at most, that a Weaponizer model was placed as a stand-in for Portal 2's Paint Gun.
On November 15, 2024, Valve itself released Episode 3 prototype footage as part of a 20th-anniversary Half-Life 2 documentary. The footage shows an Ice Gun capable of forming ice walls and platforms, a blob-type enemy that splits and merges, and another weapon whose function isn't identified. Valve's official page also explicitly states that "ideas and experiments" existed for Episode 3 that never came to fruition. The Weaponizer model discussed here gives concrete shape to the asset reuse that occurred between that known set of prototypes and Portal 2's early development—it is not new evidence of a discovered, finished version of the legendary game.
What It Would Take to Turn This Into Verified Game History
A large collection of files sitting on a server doesn't automatically become verifiable historical record. At minimum, what's needed is a catalog cross-referencing depot IDs, versions, acquisition dates, parent-child relationships, and file hashes. Only once multiple independent researchers can reconstruct the same build and confirm which files date to which era does comparison move beyond mere novelty footage.
Safety and rights considerations can't be set aside either. The Steam2 Depot Manager tool itself treats archive metadata and build definitions as untrusted input requiring inspection. Running old executables should reasonably be done in an isolated environment. And publishing a catalog or set of hashes is a fundamentally different act from redistributing copyrighted game files. The more researchers widen access to leaked material, the more they risk undermining the legitimacy of preservation efforts themselves.
What would move this assessment forward is clear: Valve explaining the acquisition path and scope of the archive; researchers publishing hash-verified manifests; and executables and maps bearing the Episode 3 name being confirmed within the same lineage. Only with all of that in place would this discovery advance from a single lost asset to a reproducible piece of development history. Until then, the Weaponizer remains a strong clue unearthed from Portal 2's development strata—not Episode 3 itself.