What is the RDB file format?
Files with the .rdb extension belong to the category of N64 emulator data files. An .rdb file is a ROM database - a structured text file that maps Nintendo 64 game identifiers to per-game emulator settings - not a ROM image itself. The Nintendo 64 was first released in 1996, and although the hardware is long discontinued, fans of this platform can still be found, supported by an active emulation community.
The database works alongside emulators. When Project64 loads a .z64 or .v64 ROM image, it reads the ROM's two 32-bit CRC values and looks them up in the .rdb file. Each entry tells the emulator how to handle that specific game - which CPU core to use, what save type the cartridge expects (EEPROM, SRAM, or Flash), and whether any video or audio plugin workarounds are needed. Without an accurate .rdb, games that require special handling may run incorrectly or crash.
The format is a plain-text INI-like file. Section headers follow the pattern [CRC1-CRC2-C:Region]; beneath each header, key=value pairs define emulation parameters. A companion file Project64.rdx extends the database with game title, developer, genre, and release-year metadata. Both files ship with Project64 and are maintained on GitHub by the community. This allows games designed for Nintendo 64 to be played on PCs running Windows, Mac OS X, or Linux. .rdb files are an important resource in circles of vintage video game enthusiasts.
Security & safety
RISK: LOWPlain-text data file; cannot execute code. Editing Project64.rdb incorrectly can break per-game emulation settings, but the original file is available from the Project64 GitHub repository. Redis .rdb files contain database contents and may hold sensitive application data if from a production server.
Format details
in a nutshell- Netscape Communicator AIM Data - Legacy Netscape (1990s) stored AIM instant-messenger data in .rdb files; Netscape is EOL and this format is obsolete.
- Redis Database Snapshot - Redis (open-source in-memory database) uses .rdb as its binary dump/snapshot format - completely unrelated, high-traffic use.
- Various proprietary databases - Several commercial applications (Value Navigator, etc.) use .rdb for proprietary relational data tables.
Programs that open RDB files
Technical details
deep spec| File format | Plain text, INI-like sections (ASCII/UTF-8) |
| Section key format | [CRC1-CRC2-C:Region] - two 32-bit CRC values from the ROM header plus a single-character region code (U=USA, E=Europe, J=Japan) |
| ROM identification | CRC32 pair computed from the ROM image header; each unique pair maps to one database section |
| Stored parameters | CPU core type, save memory type (EEPROM/SRAM/Flash), video plugin override, memory size, per-game compatibility flags |
| Companion file | Project64.rdx - extends the database with game title, publisher, genre, and release year |
| Integrity check | CRC32 pair provides ROM identity; the .rdb database file itself carries no checksum |
| Typical file size | 100 KB - 2 MB (Project64.rdb covers several thousand ROM entries) |
| Encoding | ASCII/UTF-8 plain text; no binary structures |
| Platform | Windows, Linux, macOS (wherever Project64 or compatible N64 emulators run) |
| Maintained by | Project64 community; source hosted on GitHub at project64/project64 |
| Related ROM image formats | .z64, .v64, .n64 - the actual ROM images that the .rdb database describes and configures |
| Introduced | Circa 1999, bundled with early Project64 releases |
| Released | circa 1999 (with early N64 emulators) |
| Latest version | active as of 2026 (Project64 3.x) |
| Specification | github.com |
RDB conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about RDB files.