Skip to content 
PS1 BIOS Download for DuckStation, RetroArch & ePSXe (All Regions)
A PS1 BIOS is the firmware file that helps PlayStation emulators start and behave more like the original console. Most users need the correct regional BIOS for their games, such as USA (NTSC-U), Europe (PAL), or Japan (NTSC-J). These files are commonly stored in .bin format and can be used with popular emulators such as DuckStation, RetroArch, and ePSXe.
The right BIOS depends mainly on the emulator and the region of the game you want to play. Below, you can compare the available regions, common SCPH file names, emulator compatibility, and setup requirements before choosing the correct file. For legal use, the safest option is to dump the BIOS from a PlayStation console that you own.
PS1 BIOS Files by Region
PlayStation firmware was released in different versions for different parts of the world. The main regions are USA (NTSC-U), Japan (NTSC-J), and Europe (PAL). Choosing the version that matches your game region is a simple way to avoid unnecessary compatibility problems.
The files are normally stored in .bin format, but the SCPH file name and region can be different depending on the console revision.
USA BIOS (NTSC-U)
The USA version is made for PlayStation consoles and games released in North America, including the United States and Canada. A commonly used file for this region is SCPH-5501, while older North American revisions such as SCPH-1001 may also be seen in emulator setups.
For most USA-region games, start with an NTSC-U firmware file and make sure your emulator recognizes it correctly before changing other settings.
Japan BIOS (NTSC-J)
The Japanese version is designed for NTSC-J PlayStation games. One of the common Japanese firmware files is SCPH-5500.
This version is useful when playing original Japanese releases or Japan-exclusive titles. If you have games from more than one region, keeping the Japanese firmware separate makes it easier to identify the correct file when configuring your emulator.
Europe BIOS (PAL)
European PlayStation releases use the PAL video standard. A commonly recognized PAL firmware file is SCPH-5502.
This region covers games released across areas such as the UK, Europe, and Australia. If you are using a PAL game, selecting the matching regional firmware is a good starting point for compatibility.
Other PS1 BIOS Revisions
SCPH-5500, SCPH-5501, and SCPH-5502 are not the only PlayStation firmware revisions. Sony released different console models over the life of the original PlayStation, so you may also come across older or later SCPH versions.
A higher model number does not automatically mean that the file is better for every emulator or game. What matters more is that the file is valid, supported by your emulator, and appropriate for the region you are trying to run.Later in this guide, we will compare common SCPH file names and explain how to identify the right version.
Full Regional BIOS Pack
If you use games from several regions, keeping your legally obtained regional firmware backups together can make setup easier. A complete collection may include separate files for USA, Japan, and Europe, allowing you to select the appropriate region when needed.
Keep each file clearly named instead of renaming everything to the same filename. This makes it easier to tell which region and revision you are selecting in DuckStation, RetroArch, or another emulator.
Note: PlayStation firmware is copyrighted software. The safest way to obtain it is by dumping it from a console you own and following the laws that apply in your country.
PS1 BIOS File Details
PlayStation BIOS files are usually identified by their SCPH model number, region, and firmware revision. Two files may look similar by name but still contain different firmware, so the file name alone is not always enough to confirm that you have the correct BIOS.
For emulator setup, the most commonly referenced regional files are SCPH-5500 for Japan, SCPH-5501 for the USA, and SCPH-5502 for Europe. RetroArch’s Beetle PSX documentation lists these three files as the standard regional BIOS options.
Common PS1 BIOS File Names
The SCPH number comes from Sony’s PlayStation hardware model and firmware revisions. You may find several different BIOS names depending on the console model that the firmware was dumped from.
Some of the names you will see most often are:
- SCPH1001 — associated with early North American PlayStation systems
- SCPH5500 — Japanese BIOS revision
- SCPH5501 — North American BIOS revision
- SCPH5502 — European PAL BIOS revision
DuckStation recognizes many more PlayStation BIOS revisions than these four. Its current BIOS database includes multiple early and later SCPH models, so a BIOS does not have to be named SCPH5501 to be a valid North American firmware image.
This is also why you should avoid renaming an unknown file to scph5501.bin and assuming it has become the correct USA BIOS. Changing a file name does not change the firmware inside the file.
SCPH1001 vs SCPH5500 vs SCPH5501 vs SCPH5502
These BIOS versions are not simply older-to-newer choices. Their biggest practical difference is the console revision and region they came from.
SCPH1001 is associated with earlier North American PlayStation firmware. DuckStation’s BIOS database shows that more than one firmware revision has appeared under the SCPH-1001 model family, which means the model name alone does not identify one exact BIOS image.
SCPH5500 is a Japanese NTSC-J BIOS. It is commonly used when emulating Japanese-region PlayStation games.
SCPH5501 is the North American NTSC-U version commonly referenced for USA games.
SCPH5502 is the PAL version used for European-region games.
For most users, the important question is not simply “Which SCPH number is newer?” Instead, check whether the BIOS is valid, supported by your emulator, and suitable for the region you want to emulate.
How to Verify a BIOS File With Its MD5 Hash
An MD5 hash works like a digital fingerprint for a file. If two BIOS files have the same verified MD5 value, their contents are identical even if someone has renamed the files.
RetroArch’s official Beetle PSX documentation lists these hashes for its standard regional BIOS files:
If the hash of your legally dumped BIOS matches the documented value, you can confirm exactly which firmware image you have.
Do not rely on the file name alone. For example, a file named scph5501.bin could have been renamed manually while containing completely different data. Checking its hash gives you a much more reliable way to identify the file.
DuckStation also identifies known BIOS images using their hashes and can warn when a BIOS region does not match the region being requested.
Important: SCPH1001 should not be given one universal MD5 value without specifying its exact firmware revision, because multiple SCPH-1001 BIOS revisions exist.
What Is PS1 BIOS and Why Is It Needed?
A PS1 BIOS is the system firmware built into the original PlayStation console. It runs before a game starts and provides the basic instructions the console needs to initialize its hardware, load system functions, and begin the game boot process.
When you use an emulator, the emulator recreates the PlayStation hardware in software. A BIOS image can provide the original firmware behavior that the emulator expects. This is why programs such as DuckStation require a compatible BIOS image before games can run. DuckStation also recommends using a BIOS dumped from a console you own.
The BIOS is separate from your game files. A game may be stored as BIN/CUE, CHD, or another supported disc-image format, while the BIOS contains the console firmware used during startup.
What Does the PlayStation BIOS Actually Do?
The PlayStation BIOS handles several important tasks before and during the startup process.
- Starts the console environment: It runs the initial boot routines when the system powers on.
- Initializes hardware: It prepares important parts of the original PlayStation hardware so the system can begin operating.
- Loads system functions: Games can rely on low-level functions provided by the console firmware.
- Supports memory card functions: The original system software includes routines used for memory card access and management.
- Handles regional system behavior: Different PlayStation BIOS revisions were released for regions such as Japan, North America, and Europe.
- Starts the game boot process: After the system is ready, control can pass to the inserted game.
A BIOS should not be treated as a performance upgrade. Using a different firmware file will not automatically give you higher FPS or better graphics. Those results depend much more on the emulator, device hardware, renderer, and game compatibility.
Do All PS1 Emulators Require a BIOS?
No. Not every PlayStation emulator requires you to provide an original Sony BIOS file.
DuckStation currently requires a PS1 or compatible PS2 BIOS image to start the emulator and play games. It can use BIOS images from different hardware versions and regions, although the developer notes that a region mismatch may cause compatibility issues.
RetroArch is different because its behavior depends on the core you use. For example, the Beetle PSX and Beetle PSX HW cores support user-supplied regional BIOS files, but their current documentation says they can fall back to OpenBIOS when no external BIOS is supplied.
So the simple rule is:
Check the requirements of your emulator or RetroArch core instead of assuming every PS1 emulator works the same way.
If an emulator supports an original BIOS, using a correctly identified firmware image can also help you reproduce behavior closer to the original console.
PS1 BIOS vs PSX BIOS: Are They the Same?
In PlayStation emulation, PS1 BIOS and PSX BIOS usually mean the same thing: the firmware used for the original Sony PlayStation.
The name can be confusing because people use several terms for the same console:
- PlayStation
- PS1
- PSOne
- PSX
DuckStation itself describes the system as PlayStation 1, also known as PSX, which reflects how common the PSX name remains in the emulation community.
So if you see searches or emulator instructions mentioning a PSX BIOS, they are normally referring to a PlayStation 1 BIOS file such as the regional SCPH firmware discussed in this guide.
The important thing is not whether a guide calls it “PS1” or “PSX.” Check the SCPH revision, region, file integrity, and emulator requirements to make sure you are using the correct firmware.
PS1 BIOS Regions
Original PlayStation consoles were released with different regional firmware versions. The three main groups are NTSC-U for North America, NTSC-J for Japan, and PAL for Europe and Australia. These regions are tied to different console releases and video standards, which is why emulators often identify BIOS files by region.
DuckStation recognizes these same three console regions and can warn when the selected BIOS does not match the region requested by a game.
NTSC-U — USA and Canada
NTSC-U refers mainly to North American PlayStation systems, including the United States and Canada.
Common North American firmware files include SCPH-1001 and SCPH-5501, although other Sony revisions were also released over the lifetime of the console.
For a USA or Canadian game, an NTSC-U BIOS is the natural regional match. DuckStation classifies North American BIOS revisions under its NTSC-U region.
NTSC-J — Japan
NTSC-J is the Japanese PlayStation region. It was used for consoles and games released for the Japanese market.
A commonly referenced Japanese BIOS is SCPH-5500. RetroArch’s Beetle PSX documentation also identifies scph5500.bin as its standard Japanese regional BIOS file.
If you mainly play original Japanese releases, start with a BIOS that your emulator identifies as NTSC-J.
PAL — Europe, UK and Australia
PAL covers many PlayStation releases sold in Europe, the UK, Australia, and other PAL territories.
A commonly used European BIOS is SCPH-5502. Beetle PSX identifies scph5502.bin as its European BIOS file, while DuckStation classifies PAL console revisions separately from NTSC-U and NTSC-J.
PAL games also use different video timing from NTSC releases, so choosing the correct region can matter for accurate emulation.
NTSC vs PAL: What Changes in PS1 Emulation?
The biggest practical difference between NTSC and PAL is not that one BIOS is automatically better than the other. They represent different regional standards used by the original PlayStation hardware and games.
The timing difference can affect how games were originally designed to display and run. For example, the current Beetle PSX core reports approximately 59.8 FPS for NTSC content and 49.8 FPS for PAL content, with interlaced timing close to 59.94 and 50 FPS respectively.
This does not mean that selecting an NTSC BIOS will turn a PAL game into a 60 FPS game. The game’s region, original timing, emulator behavior, and BIOS selection are separate parts of the setup.
For the simplest setup, identify the region of your game first and use a BIOS that your emulator recognizes for that region. DuckStation can load a mismatched BIOS, but its current code warns that a region mismatch may cause issues, so matching the region is the safer starting point.
Which PS1 BIOS Should You Use?
The right BIOS depends mostly on the region of the game you want to play. For a simple setup, match a North American game with an NTSC-U BIOS, a Japanese game with NTSC-J, and a European or Australian game with PAL.
You do not always need the newest SCPH revision. A valid firmware file that your emulator supports and that matches the game region is usually a better starting point than choosing a BIOS only because its model number is higher. DuckStation can use BIOS images from different PlayStation hardware revisions and regions, but its documentation warns that mixing BIOS and game regions may cause compatibility problems.
Best Choice for USA Games
For games released in the United States or Canada, an NTSC-U firmware file is the natural starting point.
SCPH-5501 is one of the most commonly recognized North American BIOS revisions. DuckStation identifies SCPH-5501 as NTSC-U, while RetroArch’s Beetle PSX documentation uses scph5501.bin as its standard US BIOS file.
Older North American revisions such as SCPH-1001 can also be valid. There is no need to replace a working compatible BIOS simply because SCPH-5501 has a higher model number.
Best Choice for European / PAL Games
For games released in the UK, Europe, Australia, and other PAL territories, start with a PAL BIOS.
SCPH-5502 is a common choice for this region. Both DuckStation’s known BIOS database and Beetle PSX documentation identify this revision as European/PAL firmware.
Matching the region is especially useful when you want the emulator setup to stay close to the original regional console environment.
Best Choice for Japanese Games
For original Japanese releases, use an NTSC-J BIOS.
A common example is SCPH-5500, which DuckStation recognizes as a Japanese BIOS revision. Beetle PSX also lists scph5500.bin for Japanese games.
This is the better starting point for Japanese imports and titles originally released for the Japanese PlayStation.
Is SCPH1001 Still a Good Choice?
Yes. SCPH-1001 is still a valid North American PlayStation BIOS family, and a properly dumped version can work with modern emulators that support it.
It is an older revision than SCPH-5501, but that does not make it useless. DuckStation’s current BIOS database recognizes more than one SCPH-1001 firmware revision as NTSC-U.
The main reason SCPH-5501 appears so often in guides is that it is a widely recognized later North American revision and is specifically listed by some emulator documentation. That does not mean every user needs to replace SCPH-1001.
Is a Newer SCPH Version Always Better?
No. A higher SCPH number does not automatically mean better emulation.
SCPH numbers identify different console models and firmware revisions rather than acting like a simple performance score. Different revisions can belong to different regions and different generations of PlayStation hardware.
For most users, focus on three things:
- Is the BIOS file valid?
- Does your emulator support it?
- Does its region match the game you are trying to run?
If those three things are correct and your games work normally, there is usually no reason to change BIOS versions just to get a higher SCPH number.
Is There a Universal or Worldwide PS1 BIOS?
There is no single standard Sony PlayStation BIOS that should automatically be treated as the best choice for every region and every emulator.
Original Sony firmware was released in regional versions such as NTSC-U, NTSC-J, and PAL. For traditional setups, matching the firmware region to the game remains the clearest approach.
However, some emulators and RetroArch cores support region-free alternatives.
For example, Beetle PSX currently supports PSXONPSP660.bin, ps1_rom.bin, and openbios.bin as alternatives to its normal regional files. Its documentation identifies these as region-free options and notes that the Override BIOS setting must be enabled for these alternatives to be recognized.
This does not mean that every emulator supports those files.
DuckStation follows a different approach. It requires a BIOS image and can use firmware from different PlayStation hardware versions or regions, but it warns that a BIOS and game region mismatch may create compatibility issues.
So if you see a file advertised as a “worldwide” or “universal PS1 BIOS,” check what it actually is and whether your emulator officially supports it. Do not assume that one renamed file is automatically region-free or better than the normal regional firmware.
For the easiest setup, use the BIOS option documented by your emulator and match the game region when regional firmware is being used.
PS1 BIOS for DuckStation
DuckStation requires a compatible BIOS image before it can start PlayStation games. It can work with firmware from different PlayStation hardware revisions and regions, but using a BIOS from a different region than the game may cause compatibility problems.
You do not need to rename every BIOS to the same file name. DuckStation can scan its BIOS folder and identify supported firmware based on the file itself.
How to Add BIOS to DuckStation
On the desktop version, DuckStation keeps BIOS files inside the BIOS folder of its user data directory. The easiest way to find it is:
- Open DuckStation
- Go to Tools
- Select Open Data Directory
- Open the bios folder
- Copy your legally dumped BIOS file into this folder
- Restart DuckStation if needed
- Open the BIOS settings and confirm the correct regional firmware is available
DuckStation documents its user data locations separately for Windows, Linux, and macOS, while the Tools → Open Data Directory option provides a simple way to reach the correct folder without finding it manually.
Do not leave the firmware inside a ZIP archive. Place the actual BIOS image in the BIOS folder.
How DuckStation Chooses a Regional BIOS
DuckStation can automatically search its BIOS directory when a specific firmware path has not been selected manually.
It separates PlayStation regions into:
- NTSC-J for Japan
- NTSC-U for North America
- PAL for Europe and other PAL territories
When several BIOS images are available, DuckStation looks for a suitable firmware image and gives preference to a recognized file that matches the requested console region.
For example, if you start a North American game, an NTSC-U firmware such as SCPH-5501 is a natural match. A Japanese title would normally use an NTSC-J firmware instead.
DuckStation can still load a BIOS whose region does not match the requested region, but it produces a warning because the mismatch may cause compatibility issues.
This is why keeping properly identified regional files is better than randomly selecting one firmware for every game.
How to Check if DuckStation Detected the BIOS
The easiest check is to open DuckStation’s BIOS settings. The desktop interface has a dedicated BIOS settings panel that controls which firmware is used.
You can also try starting a game. If DuckStation cannot find a suitable firmware image, it reports that no BIOS image was found for the requested region. Its current BIOS scanner also skips files with an unsupported size and can identify known firmware images by their contents.
If your BIOS is not being detected:
- Make sure it is in the correct BIOS folder
- Extract it from ZIP or RAR first
- Check that the file is a valid BIOS image
- Verify its MD5 hash if you are unsure which firmware you have
- Confirm that its region matches the game you are trying to run
If the file is recognized and the game starts normally, you usually do not need to make additional BIOS changes.
PS1 BIOS for RetroArch
RetroArch works differently from DuckStation because RetroArch itself is a frontend. PlayStation emulation is handled by a core, and each core can have its own firmware requirements.
For original PlayStation emulation, two well-known options are Beetle PSX and Beetle PSX HW. Their current Libretro documentation supports regional Sony BIOS files but can also use OpenBIOS when no user-supplied Sony firmware is provided.
Beetle PSX and Beetle PSX HW BIOS Requirements
For Beetle PSX and Beetle PSX HW, user-supplied firmware is supported but not strictly required in the current versions. If no external BIOS is available, the cores can fall back to OpenBIOS.
If you want to use your own dumped Sony firmware, the standard regional files documented by Libretro are:
Region | BIOS File |
Japan | scph5500.bin |
USA | scph5501.bin |
Europe | scph5502.bin |
Using the documented filename, correct location, and matching MD5 hash makes it easier to confirm that RetroArch is seeing the firmware you intended to use.
RetroArch BIOS File Names
For the standard regional setup, Beetle PSX documents these names:
- scph5500.bin — Japan
- scph5501.bin — USA
- scph5502.bin — Europe
RetroArch and Libretro documentation recommends checking three things when a BIOS is not detected: its location, its exact file name, and its MD5 hash. Some operating systems also treat uppercase and lowercase file names differently.
This means simply renaming an unknown file to scph5501.bin does not prove that it is the correct US firmware. The contents and hash still need to match.
Where to Put BIOS in RetroArch
RetroArch normally looks for firmware inside its System/BIOS directory. You can check the folder being used from:
Settings → Directory → System/BIOS
The Beetle PSX documentation also states that its required or optional firmware files belong in the frontend’s system directory.
If RetroArch does not recognize your firmware, first check that you have placed it in the exact System/BIOS folder currently configured inside RetroArch. Do not assume that a folder named “BIOS” somewhere else on your device is automatically being scanned.
Can RetroArch Run PS1 Games Without a Sony BIOS?
With Beetle PSX and Beetle PSX HW, yes. Their current versions can use OpenBIOS when a user-supplied Sony BIOS is not available.
These cores also support some region-free firmware alternatives, including PSXONPSP660.bin, ps1_rom.bin, and openbios.bin. Libretro notes that the Override BIOS option must be enabled for these alternatives to be recognized.
However, this does not mean every RetroArch PlayStation core works the same way. Firmware requirements are core-specific, so always check the documentation for the core you actually use rather than applying one BIOS rule to all of RetroArch.
PS1 BIOS for ePSXe
ePSXe is another PlayStation emulator that can use an original Sony firmware file. Its setup is more manual than DuckStation: you select the BIOS file yourself and tell the emulator which one to use.
The official ePSXe documentation recommends extracting the firmware first and keeping it in the emulator’s bios directory before selecting it from the configuration menu.
How to Select the BIOS File
On the desktop version of ePSXe:
- Extract your legally obtained BIOS file if it is inside a ZIP or other archive.
- Place the .bin file inside the ePSXe bios folder.
- Open ePSXe.
- Go to Config → BIOS.
- Click Select.
- Choose the BIOS file you want to use.
- Click OK to save the selection.
These steps follow the configuration process described in ePSXe’s official support guide.
Files such as SCPH1001.bin are commonly associated with ePSXe setups, but other supported PlayStation firmware revisions can also be used. The important part is selecting a valid BIOS rather than assuming a particular file name is required for every game.
How to Confirm It Is Loaded
After selecting the file, ePSXe lets you boot into the PlayStation BIOS screen. This gives you a simple way to confirm that the firmware has been selected and can be loaded by the emulator.
On Android, the official ePSXe setup guide includes a Run BIOS option. If the firmware is configured correctly, running it should open the PlayStation system screens instead of showing a missing-BIOS error.
If ePSXe cannot find the file, check:
- The archive has been extracted
- The correct .bin file is selected
- The file is in a location ePSXe can access
- The BIOS path in the emulator points to the correct file
A file name alone does not confirm that the firmware is valid, so use the file details and hash-checking methods explained earlier in this guide if you are unsure.
PS1 BIOS on Android
Android setup varies slightly between emulators because modern Android versions restrict how apps access files. DuckStation, RetroArch, and ePSXe therefore handle firmware selection differently.
DuckStation on Android
DuckStation’s Android version uses a first-run setup wizard. A BIOS image is required for DuckStation to start PlayStation games, so have your legally dumped firmware available when completing the initial configuration.
Unlike the desktop version, you should not rely on copying files into a Windows-style DuckStation folder. Android storage permissions are different, so use the file-selection options provided by the app.
RetroArch on Android
RetroArch normally looks for firmware in its configured System/BIOS directory.
You can see the exact folder RetroArch is currently using by opening:
Settings → Directory → System/BIOS
This is more reliable than copying the file into a random folder named bios, because RetroArch allows the System directory to be changed.
For PlayStation cores, also check the core documentation because the expected file names and firmware requirements can differ between cores.
ePSXe on Android
Modern versions of Android use stricter storage permissions. ePSXe’s official documentation explains that on Android 11 and newer, the app uses Android’s scoped-storage system and can work with a user-selected ePSXe base folder.
If you use shared storage, you can place your legally dumped firmware in the selected ePSXe folder, for example inside a bios subfolder. ePSXe can scan that location, or you can select the file manually from:
Preferences → BIOS Preferences → BIOS File.
The main lesson on Android is simple: use the emulator’s own file picker or configured BIOS directory instead of assuming every app uses the same folder.
PS1 BIOS on Windows, Linux, macOS & Steam Deck
Desktop platforms give you more direct control over emulator folders, but the correct location still depends on which emulator you use.
Windows
For DuckStation, the current default user data location on Windows is:
AppData\Local\DuckStation
BIOS images belong in its bios subfolder. Older DuckStation installations may instead use Documents\DuckStation. You can avoid searching for the location manually by opening Tools → Open Data Directory from inside DuckStation.
For ePSXe, the traditional setup is simpler: keep the extracted firmware in the emulator’s bios folder and select it from Config → BIOS.
RetroArch does not require one fixed Windows BIOS location. Check:
Settings → Directory → System/BIOS
to see the directory your installation is actually using.
Linux
DuckStation stores its user data under:
$XDG_DATA_HOME/duckstation
or, when that variable is not set:
~/.local/share/duckstation
The BIOS folder is therefore commonly:
~/.local/share/duckstation/bios
DuckStation’s current official Linux release is distributed as an AppImage, so the user data stays separate from the emulator executable unless you intentionally use portable mode.
For RetroArch on Linux, do not assume a hard-coded firmware path because packages can use different configurations. Check the System/BIOS directory shown inside RetroArch itself.
macOS
DuckStation’s default user data directory on macOS is:
~/Library/Application Support/DuckStation
The firmware goes inside the bios folder under that directory.
If you cannot find the Library folder manually, using Tools → Open Data Directory inside DuckStation is the easier option.
RetroArch users should again check Settings → Directory → System/BIOS, since the configured System directory is what matters to the cores.
Steam Deck
Steam Deck uses Linux, so the exact firmware location depends on how the emulator was installed.
For a native DuckStation setup using its Linux build, the normal Linux user-data structure applies, with firmware stored in the DuckStation bios directory. This follows DuckStation’s documented Linux directory layout.
If you use RetroArch instead, check RetroArch’s configured System/BIOS directory rather than copying the file into DuckStation’s folder.
Because different Steam Deck installation methods can use different application directories, the safest rule is to open the emulator and check the directory it is actually configured to use rather than copying BIOS files into several folders until one works.
PS1 BIOS vs PS1 Game Files
A PlayStation BIOS file and a PlayStation game file are two completely different things. The BIOS contains the console firmware used during startup, while the game file contains the actual data from a game disc.
You may therefore need both parts for an emulator setup: a compatible firmware image and a legally created backup of the game you want to play.
The important difference is simple: the BIOS starts the console environment; the game image contains the game itself.
BIOS vs BIN/CUE
The .bin extension can be confusing because it can describe both a BIOS image and part of a PlayStation disc backup.
A BIOS file such as scph5501.bin contains firmware. A game stored as BIN/CUE is different: the .bin file contains the disc data, while the .cue file describes the tracks and layout of that disc.
DuckStation officially supports BIN/CUE game images alongside formats such as CHD, CCD, MDS/MDF and PBP.
So a file ending in .bin is not automatically a BIOS. Check its name, size, hash and where it came from before adding it to your emulator’s BIOS directory.
BIOS vs ISO / CHD
ISO and CHD files are also game-image formats rather than firmware files.
CHD is commonly used to store disc-based games in a compressed format. DuckStation supports MAME CHD images directly, and RetroArch’s Beetle PSX cores also list .chd among their supported game formats.
For original PlayStation games, BIN/CUE or CHD is often more useful than thinking of every disc backup simply as an ISO, because many PlayStation discs contain multiple tracks or audio information. The emulator documentation for DuckStation and Beetle PSX specifically lists formats such as BIN/CUE and CHD among their supported PlayStation content formats.
None of these game formats replaces the firmware required by an emulator that expects a BIOS.
PS1 BIOS vs PS2 BIOS
A PS1 BIOS and a PS2 BIOS come from different generations of Sony hardware. The first contains firmware from the original PlayStation, while the second comes from the PlayStation 2.
For normal emulator setup, use firmware intended and supported for the console you are emulating.
There is one useful exception to know about: DuckStation currently supports either a PS1 or PS2 BIOS ROM image for PlayStation emulation. Its developer still notes that mixing game and BIOS regions may create compatibility issues.
That DuckStation feature does not mean PS1 and PS2 firmware are identical or interchangeable in every emulator.
If you are setting up PlayStation 2 emulation instead, see our complete PS2 BIOS download guide for the available PS2 regions, SCPH versions and emulator instructions.
How to Get a PS1 BIOS Legally
PlayStation firmware is copyrighted software, so the safest approach is to create a BIOS dump from a PlayStation console that you personally own.
Copyright and personal-backup rules can differ between countries, so this page is not a substitute for local legal advice. Avoid assuming that a BIOS is legal to download simply because it is available on a website.
DuckStation does not include Sony firmware with the emulator for legal reasons. Its official documentation tells users to dump a BIOS from their own console instead.
Dumping BIOS From a Console You Own
BIOS dumping means copying the firmware stored in your physical PlayStation into a file that can be used with an emulator.
At a high level, the process is:
- Use a PlayStation console that you own.
- Use a BIOS-dumping method supported by your emulator community.
- Save the resulting firmware image to your own storage.
- Copy that file to your PC, Android device or other emulator system.
- Verify the file using its expected size or MD5 hash.
- Add the verified firmware to your emulator’s BIOS directory.
DuckStation specifically mentions Caetla or another suitable dumping method for creating a BIOS image from your own console.
After dumping the firmware, keep your original file unchanged and make a backup before renaming or moving it. You can then compare its hash with a known firmware database to identify the exact revision and region.
The goal is simple: use your own console firmware rather than relying on an unknown copy from somewhere else.
Common PS1 BIOS Errors and Quick Fixes
Most BIOS problems come from a wrong file, incorrect folder, unsupported revision, or region mismatch rather than the emulator itself. Before changing graphics or performance settings, first confirm that the firmware file is valid and that your emulator can actually see it.
No BIOS Found
A No BIOS Found message usually means the emulator cannot locate a usable firmware image.
Quick fix:
- Make sure the BIOS has been extracted from ZIP or RAR.
- Confirm that the actual .bin file is available.
- Check the BIOS or System directory used by your emulator.
- Restart the emulator after adding the file if it does not refresh automatically.
For RetroArch, also confirm that you are checking the System/BIOS directory configured inside RetroArch, because the folder can be changed manually.
BIOS File Not Detected
Sometimes the file is present, but the emulator does not list or recognize it. This can happen when the file is stored in the wrong location or when its contents are not a supported PlayStation firmware image.
Quick fix: move the file to the correct firmware directory and check it again. If your emulator supports manual BIOS selection, browse to the file directly.
Do not assume that renaming an unknown file to something like scph5501.bin will fix detection. The emulator reads the actual contents of the file, not only its name.
Invalid or Wrong-Size BIOS
If the emulator reports an invalid BIOS, the file may be incomplete, damaged, or not a BIOS image at all.
This is especially easy to confuse with PlayStation game files because both firmware and disc images can sometimes use the .bin extension.
Quick fix:
- Check that the file came from your own valid BIOS dump.
- Compare its file details with the expected firmware revision.
- Verify its MD5 hash if a trusted emulator document provides one.
- Dump the firmware again if the file appears incomplete or corrupted.
Avoid trying to repair a suspicious file by simply changing its extension or name.
Wrong BIOS File Name
Some emulators and RetroArch cores expect specific firmware names.
For example, a core may look for names such as:
- scph5500.bin
- scph5501.bin
- scph5502.bin
If the firmware is valid but the core still does not detect it, compare the filename with the requirements for that specific emulator or core.
On some systems, uppercase and lowercase letters can also matter, so SCPH5501.BIN and scph5501.bin may not always be treated the same way.
Remember that the correct filename is only part of the check. The file contents should also match the firmware you expect.
BIOS Region Does Not Match the Game
A North American, Japanese, or PAL firmware image may behave differently when used with a game from another region.
A mismatch does not always stop a game from running, but it can create compatibility problems in some emulator setups.
For the simplest setup, use:
- NTSC-U for USA and Canadian games
- NTSC-J for Japanese games
- PAL for European, UK, and Australian games
If you keep several regional firmware files, label them clearly so you know which version is being selected.
Game Does Not Boot After BIOS Loads
If the BIOS screen appears correctly but the game still does not start, the BIOS may not be the actual problem.
Possible causes include:
- Damaged or incomplete game image
- Incorrect disc format or missing CUE file
- Emulator compatibility issue
- Wrong regional setup
- Unsupported game configuration
Quick fix: test another legally backed-up game and start with the emulator’s default settings. If the second game works, troubleshoot the original game image before replacing the BIOS.
This prevents you from repeatedly changing a firmware file that is already working correctly.
Memory Card Problems
If games start normally but saves do not work, the issue may be related to the emulator’s virtual memory card, file permissions, or storage path rather than the firmware itself.
Common signs include:
- Save file not appearing
- Memory card reported as missing
- Previously saved game not loading
- Memory card data disappearing after restarting the emulator
Quick fix: check that the emulator has a memory card configured and that it can write to the folder where save data is stored.
If you are using a BIOS replacement or fallback firmware in a RetroArch core, also check the core’s documentation because firmware choice can affect compatibility with some system functions.
The best troubleshooting order is simple: confirm the BIOS is detected first, then check the game file, region, and emulator settings one by one.
Conclusion
Choosing the right PS1 BIOS comes down to using a valid firmware file, matching the region when needed, and following the setup method required by your emulator. Whether you use DuckStation, RetroArch, or ePSXe, keep your BIOS files clearly identified, verify them when possible, and use firmware dumped from a console you own.
Once the correct BIOS is in place, the rest of the setup becomes much simpler and you can focus on loading your legally backed-up PlayStation games with fewer compatibility problems.
FAQs
Which PS1 BIOS should I use?
Use a BIOS that matches your game region: NTSC-U for USA/Canada, NTSC-J for Japan, and PAL for Europe/Australia.
Where do I put PS1 BIOS in DuckStation?
On desktop, place the firmware in DuckStation’s bios folder inside its user data directory, or use its BIOS settings to select it.
Can I use PS1 BIOS on Android?
Yes, PlayStation BIOS files can be used with supported Android emulators such as DuckStation, RetroArch, and ePSXe.
Is PSX BIOS the same as PS1 BIOS?
Yes, in emulation discussions PSX BIOS usually refers to the same original PlayStation firmware as PS1 BIOS.
Does every PS1 emulator require BIOS?
No, some emulators or RetroArch cores can use replacement firmware, while others such as DuckStation require a compatible BIOS image.
What size should a PS1 BIOS file be?
A standard original PlayStation BIOS dump is commonly 512 KB, although supported alternative firmware can differ.