Methodology

How FrameReady works

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.

How a readiness score is calculated

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.

  • Your GPU tier and CPU tier are checked against the game's minimum and recommended profiles.
  • The weaker of your two parts sets the ceiling, because one bottleneck caps the whole result.
  • RAM and storage are checked as pass or fail against the stated figure, not scored on a curve.
  • The result is a readiness verdict plus the specific part that holds you back, if any.

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.

What each data label means

official

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.

predicted

Predicted

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.

benchmarked

Benchmarked

Based on a measured result, either from the in-browser benchmark or from a comparable tested configuration. Benchmarks describe one setup, not every setup.

community

Community

Aggregated from anonymous player reports, such as server-status reports. Useful as a signal, but it reflects who reported, not a complete census.

inferred

Inferred

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 / unknown

Rumor and unknown

Rumor marks unconfirmed reports. Unknown marks a gap FrameReady has not filled yet. Neither is presented as a fact.

How hardware is detected or entered

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.

Where the estimates stop

  • Predicted requirements can be wrong until a publisher confirms the real numbers.
  • Sensitivity conversions match cm/360 or eDPI, but non-linear games are a starting point, not an exact feel.
  • Server-status pages reflect player reports and official status pages, not a private feed from the publisher.
  • Benchmark scores describe the tested run and vary with drivers, thermals, and background load.
  • FrameReady does not model every setting, mod, or resolution combination.

Corrections and updates

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.

Common questions

Does FrameReady guarantee my exact FPS?

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.

Where do the numbers come from?

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.

Do I need an account or to install anything?

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.

How do you handle games with no confirmed requirements?

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.

Try the tools