Extension NavigatorFILE EXTENSION LIBRARY
日本語
Home›Games & Saves›.rom
THE FILE FIELD GUIDE
.rom

ROM Image

Games & Saves

ROM names hardware/game/firmware images without identifying the platform by suffix alone. Game images need the matching emulator/core and any required BIOS. Firmware images require exact device/model guidance. Do not flash hardware before establishing compatibility.

What it is used for
Hardware/game/firmware image
What the file contains
Producer-dependent
All sections, questions and sources

Content reviewed： · Editor：Kai

Opening steps

Choose your environment or purpose to see its steps.

Identify the target system

The suffix does not determine the system.

  1. Identify authorized provenance and target system.
  2. Distinguish game content from firmware.
  3. Inspect model, region and BIOS requirements.
Load in a compatible environment

Use game data you are authorized to use.

  1. Identify the correct core/emulator.
  2. Load a copy as content.
  3. Inspect display, audio, controls and save behavior.
Diagnose load failures

Do not assume hardware flashing is required.

  1. Compare core support with actual content format.
  2. Inspect BIOS, multipart content and integrity conditions.
  3. Test a separate configuration through official guidance.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Emulator fails: check core platform and actual supported format.
  • BIOS required: inspect authorized matching BIOS and configuration.
  • Name/content mismatch: compare provider identifiers/checksums.
  • Save missing: distinguish in-game and state saves.
  • Audio/speed differs: inspect core/system configuration.
  • Not in playlist: distinguish loading support from scan criteria.

Process images with platform-specific tools

  1. Identify platform/format and preserve the file plus validation information.
  2. Use a compatible tool only when needed and verify output/core compatibility.
  3. Use officially supported target formats and retain the original.

Renaming to ISO/BIN does not change image layout; never flash incompatible firmware.

Game content versus firmware

Firmware requires device-specific official procedures, separate from game loading.

Example: direct loading and automatic playlist scanning have different requirements.

Source for these steps：Libretro · Playlists and Thumbnails / Libretro Project · Core List

Retain reproducibility settings

Record system, core, BIOS and save requirements and retain separate backups.

Source for these steps：Libretro · Playlists and Thumbnails / Libretro Project · Core List

Related-format differences

Related-format differences
Format / methodRoleWhat to verify
Game ROMSystem contentCompatible core
FirmwareDevice firmwareModel-specific procedure
Save stateRuntime stateCore/version

Handling and security

Use authorized data, avoid unknown executables/providers and follow official firmware instructions.

Questions and answers

Does one emulator run all ROM files?

No; platform/core support must match.

Only games?

No; firmware/other memory images also use the name.

Can I flash it directly?

Establish exact model/purpose and official procedure first.

Are save states portable between emulators?

They can depend on core/version; inspect compatibility separately from in-game saves.

Does every checksum difference mean corruption?

Regions/headers can differ; inspect the exact expected source/variant.

Format facts: name, steward and MIME type
Formal name
ROM/memory image (platform- and purpose-dependent)
Steward / specification
Individual hardware/software producers
MIME type
Depends on the producer or server; an extension alone does not establish a MIME type.

Primary and official sources

  • Project documentationPlaylists and Thumbnails

    Documents matching emulator cores and content.

    Libretro · Link checked：
  • Official documentationCore List

    Cores and requirements for different systems.

    Libretro Project · Link checked：