Can I Run It?

Can I Run It settles the most practical question in PC gaming: will this game actually play well on my machine? Choose a title, your processor, and your graphics card above, and the tool returns a verdict grounded in measured performance rather than publisher optimism, which resolutions stay above 60 FPS, which graphics preset is the right one, and which component in your system becomes the limiting factor first. The database behind it holds more than two million recorded frame rate results across 53 games and over 190,000 hardware combinations, so in most cases the answer comes from a machine functionally identical to yours, tested at 1080p, 1440p, and 4K on every preset from Low to Ultra.

Why not just read the system requirements?

Because official system requirements answer a different question than the one you are asking. Minimum specifications describe hardware that launches the game, often at 30 frames per second at the lowest settings, a technical pass rather than an enjoyable one. Recommended specifications drift in the other direction, sometimes conservative, sometimes aspirational, and almost never define the resolution or frame rate they are recommending for. Neither tells you what happens on your exact hardware, because they cannot: the interaction between a specific CPU and GPU changes the answer. A game that leans on single-thread performance will stutter on an old quad-core even when paired with a flagship graphics card, and a VRAM-hungry open world will choke an 8 GB card behind the strongest processor money buys. Only measured data from the actual combination captures that, and measured data is what this tool is built on.

Reading the verdict

The result page opens with the headline answer and then earns it. The compatibility score weighs both components against the game's demands, because a strong GPU cannot rescue a CPU below the floor and vice versa. Below it sits the useful part: per-resolution, per-preset frame rates showing exactly where your hardware lands. As a reading guide, 30 FPS is the floor of playability, 60 FPS is smooth for most players and most genres, and 120 FPS or more is the territory of high-refresh competitive monitors. The settings recommendation translates those numbers into a choice you can act on, if your hardware holds 1440p Medium comfortably but falls short at High, you know your preset before the game finishes downloading, not after an hour of menu-tweaking.

When the answer is "barely", and what to do about it

A borderline verdict is not a dead end; it is a settings guide. The measured data shows precisely how much each preset costs, and the gaps are large: dropping from Ultra to High typically recovers twenty to forty percent of frame rate, and Medium often doubles Ultra's figure in exchange for differences that are hard to spot in motion. Resolution scaling is the second lever, rendering at 1440p instead of 4K, or using your GPU's upscaling feature, transforms marginal results into comfortable ones. DLSS, FSR, and XeSS each reconstruct a sharp image from a lower internal resolution and routinely add forty percent or more performance in supported titles; the verdict pages note where these apply. Only when every lever is exhausted does the verdict point at hardware, and in that case it identifies which component to upgrade, the part an informed purchase actually fixes.

Laptops get their own answer

Checking a laptop against a game requires different data than checking a desktop, and this tool keeps them separate. Mobile processors and graphics cards run at a fraction of desktop power budgets, so the same component name can conceal a thirty percent performance swing between a thin ultrabook and a thick gaming laptop. Wherever our testing includes mobile parts, the verdict draws on mobile-specific measurements, and the database treats laptop and desktop variants as the different products they are. That matters most for integrated graphics: the latest Core Ultra and Ryzen AI processors now run many popular titles at 1080p without any discrete GPU, and the tool knows which games and at what settings, genuinely useful knowledge for a student laptop or a work machine doing double duty.

Different games, different demands

The 53 titles in the library span the full range of hardware behavior, which is why the verdict is always game-specific. Competitive shooters like Counter-Strike 2, Valorant, and Call of Duty: Warzone are engine-limited and cache-hungry, they reward fast processors and high frame rates, since anything above your monitor's refresh rate still lowers input latency. Open-world epics like Cyberpunk 2077 and Red Dead Redemption 2 shift the load onto the graphics card, especially with ray tracing enabled. Survival and simulation titles keep the CPU busy in ways short benchmarks rarely show. The browse-games grid below links every title to its hardware-combination tables, so you can also work the question in reverse: for any game, see exactly which systems run it well, and for any system, see the whole library it can handle.

What the verdict accounts for

Every verdict draws on the full measured record for the pairing you enter: where your exact processor and graphics card have been tested together in a game, the tool starts from those recorded frame rates, at your chosen resolution, across Low, Medium, High, and Ultra settings. Where the exact pairing has not been tested, the verdict scales the game's measured results across other systems by your hardware's benchmark percentiles, and the page says plainly which kind of number you are looking at. That honesty matters at the boundary cases, the pairings that hover near 60 frames per second, where the difference between a recorded result and an estimate changes the recommended settings.

Working the question in reverse

The check runs both directions. Forward: pick your hardware, get the library. Backward: pick a game, and its page lists the hardware combinations measured running it, ranked by frame rate, so a purchase decision can start from the games you must play and work back to the machine that runs them. Both directions draw on the same measured library, and both end on pages that show the actual numbers rather than a pass or fail. For builders comparing two candidate machines, run the check for each and compare the same game at the same settings; the delta between the two verdicts is the honest measure of what the more expensive machine is buying.

When the answer is close

Pairings near the boundary deserve special care, and the tool is built for them. A verdict that lands between 30 and 60 frames per second at your chosen settings is not a no; it is an instruction to look one row down, at the next-lower preset or the next-lower resolution, where the measured numbers typically recover the smooth experience. The settings advice on each verdict comes from exactly that measured data, showing which preset holds the line and where the frame rate climbs back above the threshold. In the other direction, a verdict far above your monitor's refresh rate is a signal to raise settings rather than celebrate, since unused frames are free visual quality waiting to be claimed.