A technical breakdown of the .bin, .nvm, .erom, and other files that make up a complete PS2 BIOS dump.
Most PS2 emulation guides tell you to download "a BIOS file" — as if there is just one. In reality, a proper PS2 BIOS package contains five or six different files, each with a specific job. Understanding what each one does helps you troubleshoot problems and set up new devices faster.
A verified BIOS dump from ps2 bios files contains these files:
| File | Required? | Purpose |
|---|---|---|
.bin | Yes | Main firmware file |
.nvm | Yes | Non-volatile memory — stores settings |
.erom | Yes | Extended ROM (DVD player firmware) |
.rom1 | Yes | Secondary ROM data |
.rom2 | Sometimes | Regional data (varies by model) |
.mec | Sometimes | Machine-specific encrypted config |
Many users copy only the .bin file and wonder why the emulator behaves strangely. The .bin file contains the boot firmware — the code that runs first. But it depends on the other files to complete common tasks.
The .nvm file stores system settings like language, time zone, and parental controls. Without it, the emulator resets your preferences every launch. The .erom file contains DVD player firmware. Without it, older DVD-Video PS2 games may fail to play. The .rom1 file holds secondary data needed for full game compatibility. Skipping any of these files causes hard-to-diagnose issues.
Every file in a proper BIOS dump comes from a real PlayStation 2 console. When someone "dumps" their PS2, they use a homebrew tool like ps2dumper to read the firmware chip and extract every component. This means the file authenticity ties directly to a specific physical console. A file from a fat model SCPH-39001 is not the same as one from a slim SCPH-90001, even though both are USA region.
The verification process on any trusted site checks that the extracted files match known reference hashes. If you have never come across the concept before, the beginner explainer covers what a BIOS actually is and why emulators cannot include it.
Emulators like PCSX2 and AetherSX2 look for exact filenames. If you rename scph70012.bin to ps2_bios.bin, PCSX2 will refuse to detect it — even if the file is in the correct folder. The BIOS list stays empty and you get "no BIOS selected" errors.
The same BIOS file structure appears in every region — but the contents differ. USA (NTSC-U) dumps behave differently from Europe (PAL) dumps. This matters because a PAL BIOS drives video output at 50Hz while an NTSC BIOS runs at 60Hz. This timing difference is baked into the firmware itself. The PAL technical guide covers the 50Hz timing in detail and explains when you actually need a PAL BIOS versus when you can get by with NTSC.
PCSX2 scans a single folder for all BIOS files. You set this folder in Settings > BIOS. Default locations are:
C:\Users\[name]\Documents\PCSX2\bios~/Library/Application Support/PCSX2/bios~/.config/PCSX2/bios~/.var/app/net.pcsx2.PCSX2/config/PCSX2/biosYou can use any folder you like — just point PCSX2 at it after copying the files in.