Adding games to RPCS3 starts with the game files themselves
RPCS3 is an emulator that runs PlayStation 3 games on your PC. To play a game, you need the actual game files — either dumped from a disc you own or obtained legally through other means — and you need to tell RPCS3 where to find them. The emulator does not come with games built in. You add them by pointing RPCS3 to a folder containing the game data, then configuring settings so the emulator can run that specific title.
The process has three main steps: getting the game files onto your computer, adding them to RPCS3's game library, and adjusting emulator settings if the game does not run smoothly out of the box. Most games work with default settings, but some need tweaks to graphics, CPU behavior, or audio to perform well on your hardware.
Key Takeaways
- Game files go into a folder on your PC, and RPCS3 scans that folder to find and list available games.
- You can organize games in subfolders by title or region, and RPCS3 will find them all during a library scan.
- Most games run with RPCS3's default settings, but some require adjustments to the GPU renderer, CPU threads, or audio settings for stable performance.
- RPCS3 stores per-game configuration files so you can have different settings for different titles without affecting the emulator globally.
- Game compatibility varies widely — check the RPCS3 compatibility database before spending time configuring a title that may not work on your hardware.
Where to store game files and how RPCS3 finds them
RPCS3 looks for games in a specific folder structure on your hard drive. By default, this is a folder called dev_hdd0 inside your RPCS3 installation directory. Inside that folder, games go into a subfolder called game. Each individual game gets its own subfolder with a folder name that matches the game's title ID — a unique code like BLUS12345 that identifies that specific release.
You do not have to memorize title IDs. When you dump a game from a disc you own, the dumping tool creates the correct folder structure automatically. If you are organizing games manually, you can look up the title ID on the RPCS3 compatibility database or on sites like PSXDataCenter. Once the game folder is in the right place, RPCS3 will find it during a library scan.
You can also create subfolders inside the game folder to organize by region or genre — for example, dev_hdd0/game/NTSC-U or dev_hdd0/game/RPGs — and RPCS3 will scan all of them. This makes managing a large library easier without affecting how the emulator finds or runs individual titles.
Scanning your library and adding games to the emulator
Once your game files are in the correct folder, open RPCS3 and go to File > Boot > Add Games. RPCS3 will scan the dev_hdd0/game folder and all subfolders, then display every game it finds. This scan reads the game's metadata — title, release date, region — from the game files themselves, so the list populates automatically.
Games appear in RPCS3's main window as a grid or list, depending on your view preference. You can switch between grid and list view using the buttons in the toolbar. Each game entry shows a cover image (if available), the title, and the title ID. From here, you can right-click any game to see options like Configure, Run, or Remove from Library. Removing a game from the library does not delete the files — it just hides the entry from RPCS3's interface.
If you add new games to your dev_hdd0/game folder later, you can rescan the library by going to File > Boot > Add Games again. RPCS3 will find the new titles and add them to the list without removing the ones already there.
Configuring settings for individual games
Right-click any game and select Configure to open that game's settings panel. These settings explore only to that specific title and override RPCS3's global defaults. The most common adjustments are in the GPU and CPU tabs.
In the GPU tab, you can choose between OpenGL and Vulkan renderers. Vulkan is generally faster and more stable on modern hardware, but some older games run better with OpenGL. You can also enable or disable features like Resolution Scale (to render at higher than 1080p) or Anisotropic Filtering (which improves texture quality at angles). If a game has graphical glitches or crashes, try switching renderers or disabling advanced features one at a time to find the culprit.
In the CPU tab, you can set the number of SPU Threads — the emulator's way of using your PC's processor cores to simulate the PlayStation 3's processor. More threads usually means better performance, but some games have bugs that only appear with certain thread counts. If a game stutters or crashes, try lowering the thread count from the default.
The Audio tab lets you choose between audio backends like XAudio2 (Windows) or PulseAudio (Linux). Most games work with the default, but if you hear crackling or no sound at all, switching backends can help. You can also enable Downmix to Stereo if your speakers do not support surround sound.
Checking game compatibility before you configure
Not every PlayStation 3 game runs well on RPCS3, and some do not run at all. Before you spend time configuring a title, check the RPCS3 Compatibility Database at rpcs3.net/compatibility. This database lists thousands of games with their current status: Playable, Ingame, Loadable, or Not Bootable.
Playable means the game runs from start to finish with few or no issues. Ingame means you can play the game but may hit bugs, crashes, or performance problems. Loadable means the game starts but has serious problems that make it unplayable. Not Bootable means RPCS3 cannot run it at all. The database also shows which settings other users have found to work best for each title, so you can copy their configuration instead of guessing.
Compatibility depends partly on your hardware. A game marked Playable on a high-end GPU might run poorly on an older graphics card. The database notes include hardware details, so you can see what others with similar setups have achieved. If your hardware is significantly weaker, a game's performance may be worse than the database suggests.
Troubleshooting games that do not start or crash
If a game does not boot, check RPCS3's log window at the bottom of the screen. The log shows error messages that can point you toward the problem. Common issues include missing system files, incompatible CPU settings, or graphics driver problems. If the log mentions missing firmware, you may need to install PlayStation 3 firmware files in RPCS3 — a separate step that involves downloading firmware from Sony and importing it into the emulator.
If a game crashes after loading, try the configuration steps above: switch GPU renderers, lower SPU thread count, or disable advanced graphics features. Make small changes one at a time and test after each one so you know which setting fixed the problem. Save your working configuration — RPCS3 stores it automatically in a file named after the game's title ID, so you do not have to reconfigure the same game twice.
If a game runs but has audio problems, crackling, or visual glitches, the compatibility database entry for that title often lists known issues and workarounds. Check there before adjusting settings randomly. Some games have bugs in RPCS3 that no configuration can fix — in those cases, the database will say so, and you can decide whether the game is playable enough for your purposes.
Organizing a large game library
If you plan to add many games, create a folder structure that makes sense to you. For example, you might organize by region (NTSC-U for North America, PAL for Europe, NTSC-J for Japan) or by genre (RPGs, Action, Sports). Place these folders inside dev_hdd0/game, and RPCS3 will scan all of them during library updates.
You can also use RPCS3's built-in search and filter features to find games quickly. The search bar at the top of the game list filters by title name, and you can sort by title, region, or date. If you have hundreds of games, these tools help you navigate without scrolling endlessly.
Keep in mind that RPCS3 stores game data separately from the emulator itself. If you move your dev_hdd0 folder to a different drive or computer, RPCS3 will not find your games unless you update the folder path in File > Settings > System > HDD. This flexibility means you can store games on an external drive or network location if your main drive is full.
Frequently Asked Questions
Can I add games from different regions to the same library?
Yes. RPCS3 handles games from any region — North American, European, Japanese, and others. You can mix them in the same library folder, and RPCS3 will display them all. Some games may have region-specific bugs or performance differences, but the emulator itself does not restrict which regions you can play.
What if a game folder has the wrong name or title ID?
Rename the folder to match the correct title ID, which you can find on the RPCS3 compatibility database or PSXDataCenter. RPCS3 reads the game's internal metadata to display the correct title in the library, so the folder name does not have to match perfectly — but using the correct title ID keeps your files organized and makes troubleshooting easier.
Do I need to install games, or can I run them directly from the folder?
You run them directly from the folder. RPCS3 does not require installation or copying files to a special location beyond placing them in the dev_hdd0/game folder. Once they are there and RPCS3 has scanned the library, you can launch any game by double-clicking it in the list.
Can I back up my game configurations if I reinstall RPCS3?
Yes. RPCS3 stores per-game settings in a folder called config inside your RPCS3 installation directory. If you reinstall RPCS3, copy the config folder from your old installation to the new one, and all your game-specific settings will transfer. Your game files themselves are separate and do not need to be backed up this way.
Why does RPCS3 not find a game I added to the folder?
Make sure the game folder is inside dev_hdd0/game and that the folder name matches the game's title ID. Then go to File > Boot > Add Games to rescan. If RPCS3 still does not find it, check that the game files are not corrupted and that you have read permissions for the folder. The RPCS3 log may also show why the scan failed.