Every install size, system requirement, age rating, price and play-time figure on this site is pulled from a source we can name, and every figure is stamped with the date we checked it. This page explains where each type of number comes from, how we handle the ones that move, and what to do when you spot something that has gone stale.
Why we bother
Game data rots fast. A day-one patch can add 20 GB to an install. A publisher can quietly raise the recommended GPU after launch. A rating board can reclassify a game once DLC lands. If you read a figure on this site, you should be able to see where it came from and how old it is, then decide for yourself whether it still holds.
We are a new, independent site. Nobody pays us to list a game, and no publisher reviews our pages before they go live.
Where each number comes from
| Data type | Primary source | What we cross-check against |
|---|---|---|
| Release dates | Publisher and developer announcements, official store listings | Platform press releases, developer social accounts |
| Install size (download and on-disk) | Steam, PlayStation Store, Microsoft Store, Nintendo eShop product pages | Official patch notes, our own installs where we own the game |
| PC system requirements (minimum and recommended) | Steam store page as published by the developer, official game site | Patch notes that revise specs, developer FAQs |
| Platform availability | Each platform’s store listing | Publisher announcements |
| Age ratings and content descriptors | ESRB (North America) and PEGI (Europe) rating entries | The rating label on the store page itself |
| Prices and editions | The relevant store page at the time of checking | Publisher announcements for pre-order and edition contents |
| Patch and version numbers | Official patch notes from the developer or publisher | In-game version string on our copy |
| Online requirements, players, co-op | Store listing feature tags, official game site | Patch notes, our own testing |
| Game length | Player-reported completion times plus our own playthroughs, stated as an average | See the dedicated section below |
| Accessibility options | In-game settings on our copy, official accessibility pages | Developer blog posts |
If a figure on a page does not fit one of these rows, we say where it came from inline on that page.
How we treat store listings
Store pages are the most reliable public record of what a game currently requires, but they are not identical across platforms and they are not always current. A few rules we follow:
- We quote the platform, not “the console.” PlayStation Store and Microsoft Store sizes for the same game routinely differ by several gigabytes because of platform-specific assets and compression. We list each separately.
- Download size and installed size are different numbers. Where a store shows only one, we label which one it is. Where we have installed the game ourselves, we report the on-disk figure and say so.
- Steam requirements are written by the developer. We reproduce them as published. If they look wrong (a GPU that does not exist, a RAM figure that contradicts the minimum), we flag it rather than silently correct it.
- Regional stores differ. Prices and sometimes editions vary by region. We state which regional store we checked.
How we calculate game length
Play-time numbers are the softest data on the site, so we are strict about how we present them.
Every length figure is an average, never a promise. We combine player-reported completion times from community tracking with our own playthroughs when we have completed the game. We split lengths into three brackets where the data supports it: main story only, main story plus side content, and completionist. If we only have enough data for one bracket, we show only that one.
We do not round a thin sample into a confident number. A game with a handful of reported times gets a “limited data” note next to the figure. If we have not played it and the community sample is small, we would rather say “not enough data” than print a guess.
Our own playthroughs are listed with the difficulty setting and platform, because both change the clock.
Every figure has an “as of” date
Each data point on a game page carries the date we last verified it against the source in the table above. That date is for the specific figure, not the page as a whole. An install size checked last week can sit next to a system requirement checked three months ago, and the dates will show that.
When you see a figure with an older date, treat it as “this was true then.” If the game has shipped a major patch since, the number may have moved. We try to catch those; we do not always catch them on the same day.
What “not confirmed” means
“Not confirmed” is a deliberate label, not a placeholder. It means one of the following:
- The publisher or developer has not published the figure at all.
- The figure exists only in a leak, a retailer listing, or a third-party report we could not match to an official source.
- The figure has been announced but the platform store page has not yet been updated to show it.
In every case, we keep the field empty rather than filling it with a rumoured number. When the official figure appears, the “not confirmed” label is replaced and the “as of” date is set to the day we verified it.
A related label is “pre-release.” This marks figures that are official but come from announcements made before launch. Launch-day patches change install sizes and sometimes requirements, so pre-release figures get rechecked once the game is actually out.
How we update after patches and launches
Our refresh schedule is driven by events, not a calendar:
- At launch: every pre-release figure for the game is rechecked against the live store pages within the first few days. Day-one patch sizes are added from the patch notes or our own install.
- After a major patch: when official patch notes mention install size, performance targets, new platforms or changed requirements, the affected fields are updated and re-dated. Minor hotfixes that do not touch those fields do not trigger a full recheck.
- After a rating change: if ESRB or PEGI updates an entry, we update the rating and descriptors.
- Periodic sweeps: games with older “as of” dates are rechecked in batches so that no figure drifts indefinitely without a look.
We do not rewrite the page history. If a figure changes, the old value is replaced and the new date is shown. Where the change is significant (a 30 GB jump, a dropped platform, a revised minimum spec), we note the previous value so you can see what moved.
What we do not do
- We do not estimate install sizes from file counts, trailer resolution or any other proxy.
- We do not copy figures from other databases without checking the original source ourselves.
- We do not convert “around 40 hours” from a developer interview into a hard number. Quotes like that are shown as quotes.
- We do not accept data corrections from publishers that we cannot verify on a public source.
Reporting outdated or wrong data
If a figure on any page looks wrong, out of date, or does not match what you see on your platform, tell us through the contact page. The most useful reports include:
- The game and platform
- The field in question (for example, “PS5 install size”)
- What you are seeing and where (a store page, patch notes, your own console’s storage screen)
- The date you checked
We verify every report against the sources in the table above before changing anything, so a screenshot or a pointer to the official patch notes speeds things up considerably. Reports that check out are applied and re-dated. We do not publish reporter names.
