3DO BIOS Files for Opera: panafz1.bin, panafz10.bin and the Rest

Last updated: September 2026

3DO emulation runs through one core, Opera, which is the RetroArch descendant of 4DO and FreeDO. It will not start without a BIOS, and unlike most systems there is not one BIOS but a family: Panasonic made two consoles with three regional variants each, Goldstar and Sanyo made their own, and the arcade board had another. Opera lists every one it finds and lets you pick.

This page is the full list with hashes, which one to choose, the font ROMs Japanese games need, where the folder is, and what the “norsa” builds are for. It is the 3DO entry in my RetroArch BIOS reference.

The BIOS Files

Opera scans the RetroArch system directory and lists any of these it recognises under its BIOS core option. Consumer console images are 1,048,576 bytes (1 MB); the arcade one is half that.

Which one to use

Any consumer BIOS runs the commercial library; the 3DO had no region lock, and the hardware differences between an FZ-1 and an FZ-10 are in the case, not the boot ROM. My default is panafz10.bin, the later US revision, because it is the one most people test against and it boots faster than the FZ-1’s. Use panafz1.bin if you want the original 1993 startup, panafz1j.bin or the FZ-10 Japanese image if you play Japanese releases and want the matching boot screen.

The arcade image is only for the Shootout at Old Tucson ROM. Retail discs will not boot on it.

The norsa builds

Every retail 3DO disc carries an RSA signature the BIOS verifies at boot. The -norsa files are the same BIOS with that check patched out, so unsigned software runs: homebrew, the arcade titles, and disc images that were dumped in a way that lost the signature data. If a commercial game refuses to boot on the stock BIOS and you are sure the image is good, try the norsa version of the same BIOS before anything else. For a normal library of retail dumps, the stock images are the correct choice.

The Font ROMs (rom2)

Some Japanese games draw kanji from a second ROM the console carried, and Opera exposes it as a separate Font (rom2) option, disabled by default.

If a Japanese game shows boxes or blanks where text should be, enable one of these. Otherwise leave the option disabled; it does nothing for Western releases.

Where the Files Go

The RetroArch system directory, at the root. Opera does not search subfolders, and a 3do/ folder inside system/ hides the files from it completely.

Then load the core, open Quick Menu > Core Options, and the BIOS (rom1) dropdown lists every recognised file. If it lists nothing, the file is misnamed, mis-sized, or in a subfolder. Opera builds the list by scanning the directory at load time, so a file it does not recognise never appears, with no error to point at it.

EmuDeck on Steam Deck puts panafz1.bin flat in Emulation/bios/ and its checker looks for that specific file. The Linux handheld firmwares that ship Opera (Knulli, ROCKNIX, muOS on the capable chips) use their standard BIOS folder: /userdata/bios/, roms/bios/ and MUOS/bios/ respectively, all at the root.

3DO is heavier than it looks. The console had an ARM60 and custom video hardware that Opera emulates in software, so an RK3566 device runs it at partial speed and the Android handhelds below are the floor for full speed.

How to Verify

Get-FileHash .\panafz10.bin -Algorithm MD5

md5sum panafz10.bin

Consumer images are 1,048,576 bytes; a file of any other size is not one, unless it is the arcade image at 524,288 or the FZ-1 US font ROM at 933,636. A dump from a Japanese FZ-10 produces a hash that is not in Opera’s list (20706f726c22d79d3c385e215d7428e2), and Opera will not show it, so that console is the one exception to “any 3DO works”.

Where the Dumps Come From

The 3DO BIOS is a mask ROM soldered to the board, in a SOP44 or SOP48 package depending on the model, and on Japanese FZ-1 units a single chip holds both the BIOS and the kanji font. There is no homebrew that dumps it from inside the console. The images in circulation were made by desoldering the chip and reading it in a programmer, which is also how the Shootout at Old Tucson arcade ROMs were preserved.

If you own a 3DO and want your own dump, that is the route: a hot-air station, a SOP adapter for a programmer such as the TL866 family, and the patience to reflow the chip back. It is a real board-level job. For most people the honest position is that the BIOS is Panasonic’s, Goldstar’s or Sanyo’s copyrighted code, the console has been out of production for thirty years, and the file you need is one that a chip reader produced.

Common Problems

Opera will not start, no message. No valid BIOS in the system root. Check size, name, and that it is not in a subfolder.

The BIOS dropdown is empty. Same cause. Opera only lists files it recognises.

A game boots to a black screen on the stock BIOS. Try the -norsa variant of the same BIOS. If it runs there, the disc image has a signature problem.

Japanese text is garbage. Enable a font ROM under Font (rom2).

Everything runs slowly. Not a BIOS issue. Opera is CPU-bound; lower the internal resolution or move to a faster device.

FAQ

Which 3DO BIOS is best?

panafz10.bin for a US library, panafz1.bin for the original 1993 boot. Any consumer image runs every retail game.

Does the 3DO have a region lock?

No. A US BIOS boots Japanese discs and vice versa. The font ROM is the only thing that changes for Japanese text.

What are the norsa BIOS files for?

They skip the disc signature check, so unsigned software and the arcade titles boot.

Where does panafz1.bin go?

The RetroArch system directory root, or Emulation/bios/ on EmuDeck. No subfolder.

Can I dump the 3DO BIOS myself?

Only by desoldering the ROM and reading it in a programmer. No software dumper exists.

Opera core docs | Opera on GitHub | 3DODev ROM list

Last verified: September 2026