Official
Taken from the publisher or platform holder, such as a posted system requirement or a confirmed release detail. This is the strongest label FrameReady uses.
Methodology
FrameReady estimates whether a game will run on your hardware, converts sensitivity between shooters, sizes Minecraft and server settings, and tracks live game server status. This page explains how those answers are produced, what each data label means, and where the estimates stop being reliable.
The Can I Run check compares your GPU and CPU against a game's requirement profile. Every part in the FrameReady catalog has a numeric tier on a shared scale, so a GTX 1060 and an RTX 4070 can be compared against the same target. A game stores a minimum profile and a recommended profile, each with a GPU tier, a CPU tier, and a RAM figure.
The verdict is a starting point for a decision, not a frame-rate promise. Two PCs with the same GPU can perform differently depending on drivers, thermals, resolution, and settings.
Taken from the publisher or platform holder, such as a posted system requirement or a confirmed release detail. This is the strongest label FrameReady uses.
An estimate made before official data exists, based on comparable games and hardware. Predictions stay labeled and are replaced when official or measured data arrives.
Based on a measured result, either from the in-browser benchmark or from a comparable tested configuration. Benchmarks describe one setup, not every setup.
Aggregated from anonymous player reports, such as server-status reports. Useful as a signal, but it reflects who reported, not a complete census.
A reasonable deduction from related facts, not a direct source. Inferred data is treated as weaker than official and is labeled so you can weigh it yourself.
Rumor marks unconfirmed reports. Unknown marks a gap FrameReady has not filled yet. Neither is presented as a fact.
You can always pick your GPU, CPU, and RAM manually from the catalog. Browser-assisted detection is optional and only reads what the browser exposes, which is limited and sometimes generic. When detection is uncertain, FrameReady asks you to confirm the part rather than guessing. Manual selection stays available even after detection runs.
When official data replaces a prediction, or a page turns out to be wrong, FrameReady updates the page and the evidence label rather than leaving a stale claim in place. If you find an error, see the corrections page for how to report it. For the full picture of sources, see sources and methodology.
No. Predicted readiness is an estimate based on your parts and comparable hardware. Real performance depends on the game version, drivers, background apps, resolution, and settings. FrameReady labels predictions as predictions and does not present them as measured results.
Requirement data comes from official publisher pages when available. When a game has no official requirements yet, FrameReady uses a predicted estimate and labels it clearly. Hardware tiers use a shared internal scale so parts can be compared across games.
No. Every public tool works in the browser without a login. Optional saves and reports are anonymous. Browser-assisted hardware detection is optional and you can always pick parts manually.
The result stays labeled as predicted until the publisher confirms real requirements or until enough benchmark data exists to replace the estimate. FrameReady does not turn a rumor into a confirmed spec.