- Top Pick: Samsung T7 Portable SSD 1TB
- Runner-up: WD Elements Desktop 14TB External Hard Drive
- Also consider: SanDisk 256GB High Endurance microSDXC Card
Before you spend an evening dumping a disc you own, one page decides whether the effort is worth it: the emulator’s compatibility list. Every major project keeps a per-game database where testers record how far a title gets, on which build, and with what problems. Those databases are the most honest documents in emulation, because they are built from individual test reports rather than marketing claims.
As an Amazon Associate, we earn from qualifying purchases.
The catch is that each project grades differently, and the labels only look interchangeable. One list’s Playable demands a full completion run; another’s green tag can rest on a single tester’s afternoon. Ratings also age as emulators change, and the entry for one region of a game says nothing about another. This guide maps the five databases that matter, translates their labels, and shows how to read a single game’s page before you commit.
This article contains affiliate links, and we may earn a commission if you buy through them, at no extra cost to you.
Quick Answer
Emulator compatibility lists are per-game databases maintained by each emulator project, grading titles from Broken or Nothing up to Playable and Perfect. Check the official list for your emulator, match your game’s exact region and serial, read the newest test entry instead of the headline label, and treat Playable as finishable on the tester’s build and hardware, not a guarantee for yours.
The Five Databases at a Glance
| Database | Who maintains it | Label scale | Where reports live |
|---|---|---|---|
| PCSX2 list and wiki | PCSX2 team and wiki contributors | Unknown, Nothing, Intro, Menu, Ingame, Playable, Perfect | Per-game wiki pages with test tables; ratings also feed the built-in GameDB |
| Dolphin list and wiki | Dolphin team and wiki testers | Unknown, Broken, Intro/Menu, Starts, Playable, Perfect | Per-game wiki pages with dated testing entries |
| RPCS3 compatibility database | RPCS3 team, from forum test reports | Nothing, Loadable, Intro, Ingame, Playable | Entries keyed by game ID, each linked to a forum thread |
| Xemu compatibility list | Volunteer reporters | Graded labels running from Broken up to Perfect | Reports sent in through the project’s community channels |
| PPSSPP reports | PPSSPP team and reporters | States such as Playable, In-Game and Blackscreen attached to reports | GitHub issues and forum threads, each tied to a specific build |
What the Labels Actually Mean
The vocabulary converges at the top. Perfect is the ceiling everywhere it exists: Dolphin’s own list defines it as no issues at all, and PCSX2 reserves the top of its GameDB scale for games that behave like the original hardware. Playable sits one step down and is the label most readers hunt for. Dolphin defines it as running well with only minor graphical or audio glitches, completable all the way through. RPCS3’s definition is stricter in wording: games that can be completed with playable performance and no game-breaking glitches.
Ingame is where projects agree least. On RPCS3’s list it covers games that cannot be finished, have serious glitches, or perform too poorly. The middle of every scale is a warning, not an invitation. Below that, the early labels describe how far a game gets: Intro and Menu grades mean the opening screens appear but play does not start, Dolphin’s Starts means it may even play briefly before crashes or major glitches, RPCS3’s Loadable means a black screen with a framerate counter, and Nothing or Broken means the game does not initialise or crashes on boot.
Why a Green Label Is Not a Promise
A status is a report about one copy of a game, on one build, on one computer. Region is the first trap: lists key entries by serial, so the North American, European and Japanese releases of the same title can carry different grades, and the entry you found may not describe the disc on your shelf. Build age is the second. Emulators change weekly, a fix can lift a game a whole grade, and a regression can quietly break one that used to work; an entry last updated years ago describes a program that no longer exists.
Hardware is the third variable. A tester with a fast desktop CPU may honestly report Playable while a laptop with the same build crawls, because several lists fold performance into the grade itself. Settings are the fourth: some entries only hold with specific options, per-game fixes or patches applied, which is exactly the detail a headline label hides. Xemu states the principle openly on its own site: a status is what a volunteer reporter experienced in the current version on their computer at the time of reporting, and reports may need updating as the project evolves.
How to Read One Game’s Page
Start with identity, not the grade. Confirm the serial and region on the entry match your disc, then look for the newest test report rather than the oldest. On the PCSX2 and Dolphin wikis, each game’s page collects testing entries that name the emulator version, operating system and hardware used, alongside a problems section describing known issues in plain language. That problems section is the most valuable text on the page: it tells you whether the flaws are cosmetic, like a broken effect in one cutscene, or structural, like a crash at a fixed story point.
Follow any settings guidance the page offers. Wiki entries and database threads routinely record the renderer, accuracy options or game fixes a tester needed, and PCSX2’s GameDB applies many per-game fixes automatically when it recognises a serial. Finally, check the date. A recent entry on a current build outweighs three older ones, and an entry marked untested or unknown means nobody has reported yet, not that the game fails.
Checking a Game Before You Dump It
Work in this order and you will rarely waste an evening. Find the official list, never a search-result summary. Search it by the game’s serial if you know it, since serials cut through translated and re-release titles. Read the newest report for your region and note the build it used, then compare that build with the one you plan to run. Read the known-issues notes for anything that would ruin the game for you specifically, such as broken multiplayer, missing audio in cutscenes, or a crash late in the story. If the entry is old, untested or missing entirely, that is information too: budget time for experimenting or pick a different game first.
Reporting Your Own Results
These lists only stay useful because players file reports, and a good report is a small, complete document. Record the emulator’s exact build number, your operating system, CPU and graphics card, the game’s serial and region, and the settings you changed from default. Describe how far you actually played; an honest hour of gameplay is worth more than a completion claim based on the first level. RPCS3 routes reports through its forums, where each database entry links back to a discussion thread, PPSSPP tracks reports as GitHub issues and forum threads tagged with a state, and Xemu invites updated reports through its community channels because old ones go stale. If a game regresses on a newer build, report that too: a downgrade is as valuable as an upgrade.
Red Flags: Stale Copies and Summary Blogs
The official lists are frequently scraped and republished by third-party sites that freeze them in time. Treat any compatibility page with suspicion when it never names a build number, shows no dates on its entries, or quotes a single library-wide score without defining the labels underneath it. Another tell is a page that lists statuses for games the official database still marks untested. Work from the project’s own list, wiki or tracker; use summaries only as signposts.
Kit for Checking, Storing and Testing Your Own Games
Samsung T7 Portable SSD 1TB
A fast portable drive keeps your dump library beside whichever PC you test on, so every build reads the same verified image.
Specs:
- Capacity: 1TB
- Interface: USB 3.2 Gen 2, up to 1,050 MB/s read and 1,000 MB/s write as published by Samsung
- Security: AES 256-bit hardware encryption
- Model: MU-PC1T0T/AM
WD Elements Desktop 14TB External Hard Drive
A large desktop drive is the cheap seat for a sprawling library of disc images, including titles still waiting for a first test report.
Specs:
- Capacity: 14TB
- Interface: USB 3.0
- Format: desktop external drive, preformatted for Windows as listed
- Model: WDBWLG0140HBK-NESN
SanDisk 256GB High Endurance microSDXC Card
A high-endurance card tolerates the constant rewriting that save files, shader caches and test builds generate on handheld PCs and single-board systems.
Specs:
- Capacity: 256GB
- Speed class: Class 10, U3, V30 as listed
- Read speed: up to 100 MB/s as published by SanDisk
- Model: SDSQQNR-256G-GN6IA
Sony DualSense Wireless Controller
A consistent controller removes one variable from your own testing: if a game misbehaves, you know the input path is not the cause.
Specs:
- Connectivity: Bluetooth and USB-C
- Features: haptic feedback and adaptive triggers as published by Sony
- Battery: built-in rechargeable
- Model: CFI-ZCT1W
Keychron K3 Version 2 Wireless Mechanical Keyboard
Filing reports, editing wiki test entries and renaming dump files is keyboard work, and this low-profile board suits a testing desk.
Specs:
- Layout: 84 keys
- Connectivity: Bluetooth 5.1 and USB-C wired
- Battery: 1,550 mAh as published by Keychron
- Model: K3A3
How to Choose
Choose which list to trust by proximity to the source: the project’s own database first, its wiki second, and anything else only as a signpost. Choose which entry to believe by recency and detail, preferring a dated report on a recent build with named hardware over an undated grade. Choose whether to dump a game by the worst detail in its known-issues section rather than the best word in its label, and by whether your hardware resembles the tester’s. If two entries conflict, the newer one describes the emulator you will actually run.
Who Should Skip
Skip the lists entirely if you only play systems whose emulation is effectively complete and you never chase problem titles; you will learn nothing you need. Skip them, too, if you are looking for permission to download games: the lists assume you already own the disc or cartridge and say nothing about where games come from. And skip third-party compatibility blogs as a primary source.
FAQ
Does Playable mean a game runs perfectly?
No. Playable means completable, usually with minor glitches, on the tester’s build and hardware. Perfect is the label that claims no issues at all, and even it reflects one reporter’s machine and settings.
Why does the same game show different grades on different sites?
Usually because one site copied an old snapshot, or because the entries describe different regions, serials or builds. The official list, read with its dates, settles the question.
A game I own is not listed at all. What does that mean?
It means nobody has filed a report, which the lists record as Unknown or untested. It is not a failure grade. Your own run, reported back with build and hardware details, is how the entry gets created.
How often do compatibility ratings change?
Whenever a new report is accepted or a build fixes or breaks something, which is why an undated copy of a list drifts out of date quickly.
Final Verdict
Compatibility lists are the hobby’s lab notebooks: imperfect, volunteer-written, and still the best evidence available before you invest time in a game. Read them at the source, match the serial and region, weigh the newest report over the headline grade, and remember what every label quietly assumes: one build, one machine, one tester. Do that, and a Playable tag becomes what it should be, a well-informed expectation rather than a promise.










