This PS5Xbox editorial policy explains how we make the evidence behind a claim visible. A version number, a console model and an observation matter more than a confident label. PS5Xbox.com has not performed its own console gameplay tests. The launch guides are based on review of public documentation.
How the PS5Xbox editorial policy labels evidence
| Label | What it means | What it does not mean |
|---|---|---|
| Unverified | A lead has not met our source checks | The claim is necessarily false, or the game cannot run |
| Third-party reported | An identifiable independent source describes or shows an observation | We reproduced it, or the observation covers the whole game |
| Author documented | The maintainer’s public material supports the stated claim | Every listed installation target has identical performance |
| Site tested | We performed and documented the test ourselves | Other builds, games or consoles inherit the same result |
Evidence identity and run status answer different questions. An author’s installation document can establish a documented procedure without establishing that a particular game is playable. Watching somebody else’s video is a review of their evidence, not a test performed by this site.
What running a game means
We distinguish unknown, does not boot, boots to menu, in game, playable with issues and playable. A record must say what was actually observed.
A title screen can support a menu observation. A short gameplay segment can support an in-game observation for the scene shown. Neither proves completion, stable performance throughout the game or the absence of later failures. A playable label requires a documented test scope, such as time observed, progression reached or completion evidence, along with the issues found.
We do not turn an instantaneous FPS display into an average benchmark. A meaningful performance result needs its source, measurement method, duration and context. If FPS was not measured or cannot be verified, we say so instead of filling the gap with zero or an estimate.
Test scope and console separation
A useful game record identifies the game and version, console model, emulator release, relevant settings, date, source and observed behavior. A future test by this site must also include the tester, reproduction steps and supporting evidence.
Series X and Series S records are kept separate. Desktop Windows, Linux and macOS results do not become Xbox results. A new release does not silently inherit an older version’s status. Native Xbox releases, cloud-streamed games and PS5 software running through a local translation layer are different subjects.
Unknown and conflicting results
Missing information is marked unknown. The absence of a recorded problem does not establish that there are no problems. If two credible reports disagree, we keep their different conditions visible and identify the conflict rather than selecting the more appealing outcome.
Unverified leads do not count as confirmed compatible titles. A game page is published only when its evidence and explanation serve a distinct reader need; a keyword alone is not enough to create one.
Sources and review dates
For project identity, release requirements and installation steps, we prefer the author’s repository and platform documentation. For performance, we need game-specific observations. A private research conversation, an AI-generated summary or a search-result snippet is not a substitute for the public source behind a claim.
We link version-sensitive instructions to a specific release or commit where practical. Last reviewed means the page’s sources were checked on that date. Released identifies the project’s publication date. Tested is reserved for an actual test date. These dates are not interchangeable and are not advanced just to make a page look fresh.
AI may assist with research organization, drafting and site production. Claims still require source checking, and generated descriptions cannot supply missing measurements, personal experience or game results.
Corrections and revision history
Send the affected URL, the disputed statement and a public supporting source through our contact page. We assess the evidence, update the explanation where warranted and record material corrections with their scope and date. A significant factual correction should remain understandable to a reader who saw the earlier claim.
Initial policy published: October 19, 2026. There are no site-tested console records in this launch edition. The About page explains the publisher’s independence; the installation guide shows how these rules apply to a practical task.