PCSX2 BIOS Setup: Add a PS2 Image File, Pick the Right One

First Launch: The Missing BIOS Prompt

Open a fresh install and the wizard stops on a page stating that the emulator requires a BIOS from a real unit in order to run. It also reminds you that, for legal reasons, the image must come from a PlayStation 2 that you own, and that borrowing doesn’t count. That is the whole reason no emulator can ship with one: the startup code, the system ROM of the console, belongs to Sony, and nobody has written a free replacement. Other emulators for the same hardware face the same rule.

The good news is that the app is not picky. It scans one place, lists every valid BIOS it finds and lets you switch between them at any moment. You need to add the file only once, and the system BIOS stays selected after every update and launch.

Before You Start: What to Gather

Gather these before you open anything:

• The parts your dumper made, kept together and with their original names: .rom0 (main), .rom1, .rom2, .erom and .nvm, depending on the model. The main BIOS part is the one that matters; it should be exactly 4,194,304 bytes.
• An unzipped copy. Nothing reads inside a zip or 7z archive, so extract it first.
• The emulator itself, installed from the official builds on our PCSX2 page. Minimum requirements: SSE4.1 support on a 64-bit processor, 8 GB of memory and graphics that handle OpenGL 3.3, Direct3D 11 or Vulkan 1.1.

Para usuarios en español: con descargar no alcanza. Copia la imagen sin comprimir en la carpeta y vuelve a abrir el programa.

Add the BIOS in the PCSX2 Wizard

The wizard has six pages: Language, BIOS Image, Game Directories, Controller Setup, RetroAchievements and Complete. Only the second one needs care.

1. Copy the BIOS parts into the default bios subfolder (paths below), or into any folder you like.
2. On the BIOS Image page, use Browse to pick another place if you did not use the default, then press Refresh List.
3. The table fills with each BIOS it found, showing its filename and the BIOS version read from inside the file. Click the one that matches your discs.
4. Press Next, add the folder holding your own disc backups, map a controller, and finish.

Start any game. If the PlayStation 2 logo appears and the disc loads, you are done. To reach the PlayStation 2 browser with no disc, use Start BIOS from the System menu instead; it is a quick test before you boot games.

BIOS Folder Location for Each Install Type

Each install type keeps its data in a different place, so a BIOS copied to the wrong one simply never appears. These come from the v2.8.2 source code, so they match the current stable BIOS file lookup:

On a Mac the Library folder is hidden, so press Cmd+Shift+G in Finder and paste the path. On Linux, show hidden folders with Ctrl+H. Tools, then Open Data Directory, jumps straight there on any OS.

Change the BIOS Selection Later

Open Settings and pick the BIOS page. The BIOS selection list is the same as in the wizard, plus a button that opens the folder and two options:

• Fast Boot skips the PlayStation 2 logo and the card check, so games load sooner. Leave it on unless a title misbehaves.
• Fast Forward Boot speeds through the startup animation without skipping it.

To use a different BIOS for a single title, right-click it in the game list and open Properties. That way a Japanese disc can keep its own BIOS while the rest use your US one, and you never touch the global choice.

Reading BIOS Versions and Regions

Every line in the list shows a market and a revision number taken from the BIOS, so BIOS versions are easy to compare. A string such as 0230A means revision 2.30 for America; older units show revisions such as 1.60 or 2.20. The letter tells you the market (J for Japan, E for Europe, C for China, H for Asia), and the region of the console has to match your discs more than the number does. A newer BIOS revision isn’t always the best one; a complete copy from a retail unit matters most, and Sony never offered BIOS updates for the console.

NTSC discs from the USA run best with an image from an xxx01 model, Japanese ones with a model ending in 00, and PAL discs with an xxx02, xxx03 or xxx04 model. The full model table, with every market code, is in our PS2 BIOS files overview, so we won’t repeat it here.

Old PCSX2 Builds and the Plugin Menu

Guides written before the 2.0 release in July 2024 show a different screen. In 1.6.0 and earlier stable releases (back to 1.4.0, 1.2.0, 1.2.1, 1.0.0 and the 0.9.6, 0.9.7 and 0.9.8 era), the BIOS was picked under Config, then Plugin/BIOS Selector, because graphics, sound and input were separate plugins. Odd-numbered lines like 1.1.0, 1.3.0, 1.5.0 and 1.7.0 were development builds; the 1.7.4 thousands were the last nightlies before 2.0. There is no 1.4.1 tag on GitHub, and people who type 1.40 or 140 usually mean 1.4.0.

From 2.0 and 2.2.0 onwards the plugins are gone and the menu lives in Settings. If a tutorial still mentions plugins, it predates the current interface. Install the latest stable from our PCSX2 download page (never download a random repack that bundles a BIOS pack) and follow the steps above.

PCSX2 Not Recognizing the BIOS? Fixes

• List is empty: the folder holds a zip, or only the .nvm and .rom1 parts. Extract the archive and make sure the main BIOS image is there.
• File not showing after copying: you copied it to the installer path while running the portable build, or the reverse. Browse to the folder that really holds it and press Refresh List.
• Flatpak cannot read the folder: keep the files inside the Flatpak path above, or grant the app access to your folder.
• Image is smaller than 4MB: the copy is broken. Copy it again from the console and compare its SHA1 or CRC with the Redump list.
• Black screen with a working BIOS: check the disc region against the BIOS region, turn Fast Boot off and look at the compatibility notes on the official wiki.

If none of that helps, the official forum and Discord are the right places to ask. Bring your emulog.txt from the logs folder.

Check the Image Before You Blame the Emulator

Most “not detected” reports come from a broken or altered BIOS file, not from the app. The official docs suggest hashing the main part and comparing the result with the Redump data file for your model:

• PowerShell: Get-FileHash followed by the path and -Algorithm SHA1.
• Mac Terminal: shasum followed by the path.
• Linux shell: sha1sum followed by the path.

If the hash matches a known retail BIOS, the image is fine and the problem is the folder, the disc or a setting. If it matches nothing, make a fresh dump on your PlayStation 2 with any modchip switched off, following our dumping guide, because an active chip can spoil the read. Keep the original BIOS file somewhere safe, away from the emulator folder, so a reinstall never costs you a second session with the console.

Memory Cards, the .nvm Part and Clock Settings

The small .nvm part stores the console language, the clock and a few display options. The app builds a new one when it is absent, so nothing breaks without it, but keeping your own means the system menu opens in your language. Saves live elsewhere: each virtual memory card is a separate 8 MB file in the memcards folder, and you can swap cards per game. Save states are not a substitute for in-game saves, and they can stop loading after an update.

The BIOS itself is never modified by the emulator, and its display options live in the .nvm part. You can copy the same BIOS file to a laptop, a Steam Deck and a desktop and use it on all three, as long as each one belongs to you.

Handheld Notes: Deck Flatpak vs EmuDeck

On a Steam Deck the Flatpak build from Discover keeps its images in the Flatpak path shown in the table. EmuDeck users can skip that: EmuDeck installs the emulator, creates an Emulation folder on the drive you picked and points every console at its bios subfolder. Copy the BIOS parts there in desktop mode, return to gaming mode and the BIOS appears in the list. The EmuDeck app also has a checker that flags a missing PlayStation 2 BIOS file before you start a game.

Performance on the Deck is good for most titles at native resolution. Raise the upscale only after one game runs cleanly, and use per-game properties for heavy titles rather than changing global options.