How this site works out whether a game runs on your computer
One ladder, two numbers, and the cases where the honest answer is nothing.
Steam tells you a game needs a "GeForce GTX 1060 or AMD Radeon RX 580". Your machine has something else. Answering whether that is enough means putting both on the same scale, and the store does not give you one.
So this site keeps one. It is a hand-maintained ladder of 181 graphics cards, each with a rank from 0 to 100, anchored so that a GTX 1060 6GB sits at 53. The rank is ordinal and nothing more. A card at 80 is stronger than a card at 40; it is not twice as fast, and the number is not a benchmark score. It exists to be compared against another number on the same ladder, and for nothing else.
Two numbers, one scale
When the pipeline reads a game's requirements, it tries to resolve the graphics line to a rank on that ladder. When your browser reports your card, the same resolver runs on the same ladder in your browser. Then the comparison is arithmetic instead of judgement: your rank against the game's rank.
That symmetry is the whole design, and it is fragile in an obvious way. If the two resolvers ever disagree, the answer is wrong in the direction nobody notices. So the ladder is one file, the browser copy is generated from it, and a check fails the build if the generated copy drifts from the source.
Three confidences, and one of them is "no"
Most requirement lines do not name a card cleanly. The resolver has three ways to answer and one way to decline.
A card it recognises. "GeForce GTX 1060" resolves directly. This is the strongest answer and covers about 40 percent of the catalog.
A memory floor. "2 GB VRAM" names no card, but it puts a floor under one. The rank comes from the memory figure. Looser, and labelled as such.
A capability floor. "DirectX 11 compatible" is a generation, not a part. A DirectX 11 card can be a Radeon HD 5450, which is why that floor sits low rather than somewhere flattering.
Nothing readable. About a third of the catalog states a graphics requirement this site cannot rank. Those games are left out of a "runs here" list rather than guessed into it, because a false yes costs you money and a false no costs you a game you can find another way.
There is a specific trap inside that last case, and it shipped. A requirements line reading "SM2.0 (or later) Graphics Card" is a DirectX 9-era shader model. For a while the resolver matched the "M2" inside "SM2" against Apple's M2 chip and ranked a 2004-era requirement as Apple silicon, with the highest confidence label on it. The same bug read "AMD Radeon R5 M430" as an Apple M4. Every pattern in the ladder is now anchored so it cannot match inside an unrelated part number, and a set of real hardware the ladder does not contain is tested on every build to confirm the resolver still says nothing about it.
What your browser will actually tell us
Less than you would expect, and the gap matters.
The operating system is reliable, and it is the one that decides most cases outright. A 64 GB Mac cannot run a Windows-only game, and no amount of hardware changes that.
Memory comes from a browser API that reports in rounded steps, caps what it will admit to, and does not exist at all in Firefox or Safari. Treat it as a floor on what you have, never a measurement.
The graphics card comes from a WebGL extension. Chrome reports the actual model. Firefox restricts it. Safari returns something generic. When your browser will not say, the graphics half of the comparison is skipped rather than assumed.
The processor is not available. There is no browser API that reports a CPU model, only a logical core count, which tells you nothing about speed. Anyone claiming a web page read your processor is reading a core count and guessing. So this site does not compare processors automatically, and says so where the comparison would otherwise appear complete.
Nothing above is sent anywhere. The detection runs in your browser, the result stays in your browser, and the filter reaches the server as ordinary query parameters you can read in the address bar.
Read it as "should run"
Every layer of this is an approximation stacked on a developer's own estimate, and developers write requirements the way people write resolutions. A rank comparison says the hardware is in the right class. It does not know about your drivers, your background processes, the resolution you play at, or a game that ships badly optimised and runs worse than its own minimum suggests.
Where the answer is genuinely unknown, this site says so rather than filling the gap. That is the part worth trusting.