Compatibility

Know before you launch.

A public compatibility database aggregates community reports into status buckets; separate community wikis often hold per-game articles, hacks, and known issues. Always match the serial (e.g. SLUS/SLES) to your exact disc or image region.

Numbers on this page are broad snapshots for orientation only; your CPU, GPU, and PCSX2 version still decide smooth play. When something is “Playable” but stutters, check the wiki for recommended clamps, patches, or renderer notes before filing a bug.

~1%

Issues

5000+

Wiki

~1%

Perfect

~98%

Playable

Search the web for a public PCSX2 compatibility database and match your game’s serial—this site does not embed an external database.

How to read statuses

Perfect means no known issues in tested scenarios—not a promise for every hardware combo. Playable is the broad “works well” band most people target. In-game or lower tiers mean you can expect blockers, heavy glitches, or heavy performance cost.

Treat the DB as a living average: new builds can improve old entries, and niche bugs may not be reflected yet.

Practical workflow

  1. Search the database by title or serial.
  2. Open the wiki page for the same game (if it exists) for renderer and hack guidance.
  3. Test with default-ish settings first, then apply only what the article recommends.
  4. If you hit a regression, note your exact version—stable vs nightly matters for maintainers.

More context: Features · Setup · FAQ

Serials, regions, and “same game, different disc”

Two boxes can share a title while using different code paths: NTSC-U, NTSC-J, and PAL builds often differ in timing, language files, and bug surface. Always match the serial printed on your disc (or embedded in a verified dump) to the database row you read.

A “Playable” entry for SLUS-12345 does not automatically guarantee the same for every regional variant—check the row that matches your rip.

Performance ≠ compatibility label

A game can be marked playable yet still demand a strong CPU at native resolution, or fall apart when you stack 4× IR and aggressive texture filtering. If the label says “fine” but your machine struggles, lower internal resolution, try the other mainstream renderer, and read the wiki for known bottlenecks.

When the database and the wiki disagree

Aggregated status can lag behind nightlies; a wiki note might already describe a fix in a build newer than the last voter average. Prefer repro steps + version strings over anonymous star ratings when you decide what to trust.

Common false alarms

  • Black screen on first boot — test software renderer once, verify BIOS region, then re-check the rip before assuming “incompatible.”
  • Audio-only or frozen FMV — often renderer- or dump-related; swap backend and read per-game notes about mpeg/video quirks.
  • Random hangs after hours of play — overheating, unstable RAM overclocks, or a dying storage device can mimic emulation bugs—note whether the emulog shows a GPU driver reset.

Step A

Find your serial; open the public compatibility database row.

Step B

Open the matching wiki article (if any) for renderer and hack guidance.

Step C

Test defaults first; apply only recommended toggles one at a time.