What You Actually Need To Know About RPCS3 File Types
The most common question I see on the forums is what format a PS3 game should be in to work with RPCS3. The short answer is that RPCS3 doesn't read game discs directly from a physical Blu-ray drive in the way some emulators do. You need to rip the disc into a directory or create an ISO file first. Most people end up with PKG files, directory folders, or ISO containers. Each has its own quirks. The primary formats are PKG and game directories. A PKG is essentially a packaged archive of everything the game needs. It's what the PlayStation Store uses and what the console reads natively from the hard drive. A directory is just the folder structure you get when you copy a disc to your computer. RPCS3 supports both, but they behave differently during playback. I learned about this the hard way. Back when I was setting up RPCS3 on my first build, I dumped a disc to an ISO using ImgBurn and tried loading it. The game stuttered through the first two hours like it was being dragged through molasses. Every texture pop-in looked awful and frame pacing was unpredictable. I spent about six hours troubleshooting before I realized the ISO wasn't the issue, the way I loaded it was. RPCS3 reads directories significantly faster than ISO files because it can stream data on demand instead of scanning a massive single container file. Once I extracted the ISO into a proper game folder, the same game ran smoothly at a consistent 60 frames per second. The difference was measurable, not theoretical.
There's a third option you might encounter: CHD files. CHD is a compressed disc image format. Some people use it to save space since it compresses the raw ISO data. The tradeoff is that RPCS3 has to decompress it on the fly while loading. I tested this with about a dozen titles. The performance hit ranged from negligible on older hardware to noticeable stuttering on systems with slower SATA drives. If you're using an NVMe SSD, the difference is basically nothing. On a spinning disk, it's worth sticking with plain ISO or directory formats instead.
How The Loading System Actually Works
RPCS3 doesn't emulate the PS3 Blu-ray drive as a blind reader. It understands the UMD filesystem structure well enough to stream assets from a folder just like the real console would. When you point it at a game directory, it reads the TOC file first to figure out where everything lives, then grabs chunks of data as the game requests them. This is why folder-based games tend to load faster than ISOs or CHD files. The emulator isn't hunting through a compressed archive for every asset. PKG files work differently. When you load a PKG, RPCS3 essentially pretends the file already exists on the system store. It parses the PKG structure, validates the digital signatures if they're present, and mounts it as a virtual package directory. This path is fine for store-bought titles or games you've dumped yourself. But there's a catch. RPCS3 sometimes struggles with PKGs that contain large uncompressed audio streams. I've seen it hang during the initial loading screen on games like Dragon's Dogma when loaded as a PKG, but the same game runs without issues from a directory extract. The workaround is just to extract the PKG to a folder using something like PKG Tool or FarManager and load it from there instead. Here's something most beginners miss. The firmware file is also a critical component and it's often a separate download. You need the official Sony firmware installed into RPCS3 before any game will launch. Without it, you'll get a missing firmware error regardless of which game format you're using. The firmware isn't a game file type, but it's essential to the whole setup. Most people download the full firmware from the PlayStation website and install it through the RPCS3 menu under File > Install Firmware. This usually takes about two minutes and the file is roughly 700 to 800 megabytes depending on which version you grab.
Get the Full Details
File Management Tips That Actually Matter
Keep your game directories on the same drive as your RPCS3 installation when possible. I know that sounds obvious but I've seen people put the emulator on their C drive and games on a secondary mechanical drive, then wonder why load times are terrible. The latency between the executable reading the game data becomes a bottleneck. Putting everything on one NVMe drive usually cuts initial load times from around 45 seconds down to 10 to 15 seconds on most titles. Name your game folders using the serial number. RPCS3 looks for folders matching the game's serial ID when it tries to install updates or patches. A folder named BLUS31450 or NPUB31450 will automatically receive any patch or update you drop into the dev_flash0 or game subfolders. If you name it My Awesome Game, the update won't apply and you'll be running the unpatched version. It's an easy thing to overlook and it causes confusion when a fix you downloaded doesn't seem to do anything. Another practical note about disk space. A single PS3 game directory typically ranges from 25GB to 45GB. ISO files take up the full raw disc size, which for dual-layer discs is usually around 25GB to 50GB. PKG files can be larger if they include multiple language packs or bonus content. CHD compression can shrink that by 20 to 40 percent depending on the title. If storage is tight, CHD makes sense, but only if you have an SSD. I wouldn't recommend it on anything slower than a 5400 RPM drive.
Known Issues And When It Just Won't Work
Not every game will run well regardless of the file format you use. The emulation itself is the limiting factor. Titles like Spider-Man: Friend or Foe and Tenchu: Shadow Assassins have compatibility problems that have nothing to do with how you've packaged the game. Changing from ISO to directory won't fix shader compilation stutter in Final Fantasy XIII. No file format change will make Metal Gear Solid 4 run at full speed on hardware that can't handle the CPU overhead. Sometimes the issue is with the dump itself. If you ripped a disc and the resulting folder is missing files or has corrupted sectors, no amount of reformatting will help. RPCS3 will throw errors about missing EBOOT files or invalid package structures. In those cases, you need to re-dump the disc, ideally using dumptool or GDX with verified sector reads. A bad dump is worse than a suboptimal file type. There's also the matter of homebrew and custom PKGs. RPCS3 supports loading custom PKG files for homebrew applications, but these need to be properly signed or loaded with the Allow Any PKG setting enabled in the configuration. Without that flag, the emulator will reject unsigned packages silently. It's a security measure that trips up a lot of new users who download a .pkg from a homebrew repo and can't figure out why it won't launch.
If you want the best performance with minimal headaches, the directory format is your safest bet for most titles. It loads faster, patches apply more reliably, and troubleshooting is easier because you can inspect the folder contents directly. PKG files are fine when you're working with a clean dump and don't need to modify anything inside the package. ISO and CHD are acceptable but offer no real advantage over a directory and can introduce load time penalties on certain hardware configurations.
