bronze
Main Archive
One row per player per tick, plus every game event of the match, parsed but not interpreted.
Closest to what the game recorded. Wide and long; this is where the volume is.
Checking your access…
Catalog
What is in the dataset
Each match is published whole — every table derived from it, and a recording of every player's point of view in every round. This page explains how those parts fit together and lists every table.
Scale
— Matches
— Tables per match
— Rounds
— POV recordings
— Total size
— Map
These figures measure what is offered for download, not everything the company holds.
These figures are read from the dataset itself and could not be loaded just now. Everything else on this page still holds; reload to try again.
How a demo package is shaped
Everything derived from one Counter-Strike 2 match is published together as a demo package, named by its demo id. A package divides into three layers. The first two travel in the main archive; the third has an archive of its own.
silver
Main Archive
Per-match tables derived from the bronze layer.
Narrower, already joined and cleaned. Usually where an analysis starts.
video
Video Archive
Per-round, per-player point-of-view recordings, each with a frame table mapping its frames back to the game clock.
One folder per round. Tens of gigabytes per match.
How the parts link
Four keys hold a demo package together. Between them they cover every join the dataset supports, so what an analysis can ask is decidable before anything is downloaded.
- demo id The single join key across the whole package
- A uuid identifying a demo package and every file in it — the tables and the video both carry it. No other correlation key is needed to tie one match's parts together, and it is what tells two matches apart once you have loaded both.
- tick The shared time axis, 64 Hz
- The game's simulation step, and the clock every table is stamped with. Any two tables join on (demo id, tick); a second of match time is 64 of them.
- steamid The per-player key
- Where a table is per-player, it carries the player's steamid, so per-player tables join on (demo id, tick, steamid). In the wide per-slot tables the same identity appears as a column family across the ten player slots rather than as ten rows.
- frame table The bridge from a video moment to a table row
- Beside every point-of-view recording sits a frame table: one row per rendered frame, mapping the frame's index and its timestamp in the video to a tick. That is what lets a moment you can see resolve to the rows that describe it, and a row resolve back to the frame it happened on.
Frame tables ship in the video archive only, alongside the recordings they describe.
Every table in the dataset
Every demo package holds the same set of tables, so this describes the dataset rather than any one match. Row counts and sizes are totals across the packages that carry the table.
— Tables
— Rows in total
— Table data
Loading the table index…
| Table | Alias | Layer | Rows | Columns | Size | Packages |
|---|
A table's own page carries its schema, what each field means, and a preview of real rows.