PS2 BIOS Files Explained
A PS2 BIOS file is a copy of the program that ran inside a real PlayStation 2. The one file you must have is the main .bin. A full dump also brings small companion files named .mec, .nvm, and .erom.
Most people only ever touch the main file. The rest are extras that some dumps include. This page explains the PS2 BIOS files one by one: what each is, what the names mean, and how to check that your file is the genuine, complete BIOS before you trust it.
What a PS2 BIOS file actually is
It is the firmware from a real PS2, saved as a file. The emulator loads it so it can behave like the console.
Without it, an emulator like PCSX2 or NetherSX2 has nothing to start from, so games do not boot. The file does not contain any game. It is only the console's own startup program. If you want the full background on what the BIOS does, the PS2 BIOS download hub covers it.
The files in a BIOS set
The main file is the only one you truly need. The companions store extra console data and are optional for most emulators.
.binis the main BIOS. This is the file the emulator reads. It is required..nvmstores console settings such as region and language..mecand.eromhold extra data that some dumps include.
| File | What it holds | Required? |
|---|---|---|
.bin | The main BIOS the emulator reads | Yes |
.nvm | Console settings such as region and language | No |
.mec | Extra data from a full dump | No |
.erom | Extra data from a full dump | No |
Keep whatever files you have in the same bios folder. PCSX2 runs fine with just the main file, and keeping the companions alongside it does no harm.
A fresh dump straight from a console can look different. Instead of a single .bin, you may see rom0, rom1, rom2, nvm, and erom. These are the same data split into parts. Keep them together in one folder and the emulator will read them.
What the file names mean
The name usually includes the console model, like SCPH-70012.bin. The model tells you the region.
Do not rename these files. An emulator can use the name to identify the version, so a renamed file can confuse it. If you keep several BIOS files for different regions, leave each original name in place so you can tell them apart. To learn which model belongs to which region, see which PS2 BIOS to use.
File formats you will see
.bin is the standard format. Some packs use .img, which is the same data under a different extension.
One thing trips people up more than any format question. If the file is still inside a .zip or .7z archive, the emulator cannot read it. Extract it first, then point the emulator at the raw file. A still-zipped BIOS is the most common reason a file "will not load," which the BIOS not found fix page covers in full.
PS2 BIOS and PS1 games
You do not need a separate PS1 BIOS to play PS1 discs on a PS2 emulator. The PS2 BIOS handles them.
The PlayStation 2 could run most PlayStation 1 games, and it used its own BIOS to do it. So the same PS2 BIOS also covers PS1 discs when you emulate a PS2. A separate PS1 BIOS only matters if you emulate a PS1 on its own, which is a different setup with different files.
How to check your BIOS file is genuine
Compare the file's checksum to a known-good value. If the SHA-256 or MD5 matches, the file is the real, complete BIOS. If it does not match, do not use it.
A checksum is a fingerprint of the file. Run one of these commands on your file and read the result:
# Windows (Command Prompt)# macOS and Linux shasum -a 256 SCPH-70012.bin ```
Then compare the output to the known-good SHA-256 value for that model. Every file we host lists its SHA-256 so you can confirm it yourself. File size alone is not proof, because a corrupted file can still be the right size. The checksum is what actually settles it. SHA-256 and MD5 are two common checksum types, and SHA-256 is the stronger one, so prefer it when a known-good value is listed.
Does a PS2 BIOS file ever update?
No. A PS2 BIOS file is fixed. It was dumped once from real hardware and never changes.
There is no newer version to chase and no patch to apply. If a site offers you an "updated" or "latest" BIOS, treat it with suspicion and check the checksum. What keeps improving is the emulator, not the BIOS, so keep your emulator current instead. Our update guide explains this in full.
Do you need every file?
You need the main file for your region. The companions are optional for most emulators.
For a single-region library, one main file is enough. If a companion file is missing, most emulators still start using default settings, so a lone main file is usually all you need. For a mixed library, keep one main file per region and switch between them in the emulator. Which regions you need comes down to your games, and which PS2 BIOS to use walks through that choice.
Where these files come from
The only method that is legal everywhere is dumping them from a console you own.
Our dump guide walks through the whole process. If you use a ready-made file instead, verify its checksum before you trust it. Files pulled from random archives or forums are often incomplete or tampered with, which is exactly why the checksum check matters. Once your files are ready, the install guide shows where they go on each platform.
Frequently asked questions
What is the main PS2 BIOS file?
.bin file, or a rom0 set if it came straight from a fresh dump. This is the file the emulator reads to act like a real PS2.