Setting Up an Emulator Manually

Manually add an installed emulator, connect it to LaunchBox platforms, configure parameter precedence, cores, extraction, dependencies, and safe per-game overrides.

Written By launchbox

Last updated 6 days ago

An emulator is the program that runs a console or computer game file. LaunchBox organizes your library and builds the launch command, but the emulator still needs a working executable, the correct platform association, and sometimes a core, BIOS or firmware file, or command-line option.

This guide is for an emulator you have already downloaded or installed. When LaunchBox offers its automatic download-and-configure workflow for a supported emulator, that is normally the easiest beginner route: an official emulator integration can install the program and create a LaunchBox-ready profile with tested defaults. For supported integrations and their individual capabilities, see Emulator Plugins.

Before you add it

  1. Get the emulator from its official project source.

  2. Extract or install it in a stable location. A folder under LaunchBox\Emulators is convenient for a portable setup, but it is not required.

  3. Open the emulator directly and complete any first-run setup.

  4. Configure the emulator's graphics, audio, input, region, and BIOS or firmware requirements.

  5. Load one of your own game files directly inside the emulator.

If that game does not work inside the emulator by itself, adding it to LaunchBox will not fix the underlying emulator or game-file problem.

Add the emulator to LaunchBox

  1. Open Tools > Manage > Emulators....

  2. Select Add.

  3. On Details, choose or enter the Emulator Name. Selecting a recognized emulator name can prepopulate LaunchBox's known defaults; review them instead of assuming every version uses identical settings.

  4. Set Application Path to the emulator executable, not to a ROM, core, BIOS file, or game folder.

  5. Use Browse... to reduce path-entry mistakes.

  6. Leave the advanced checkboxes at their defaults unless the emulator's documentation or a dedicated LaunchBox guide requires a change.

If the executable is inside the LaunchBox folder, LaunchBox can store a relative path, which helps when moving the complete LaunchBox folder. This does not guarantee that the emulator itself is portable: some emulators keep settings, saves, or caches under the Windows user profile unless their own portable mode is enabled.

Understand the three parameter levels

LaunchBox normally sends the selected game's path to the emulator automatically. Command-line parameters are evaluated in this order:

  1. Per-game custom parameters, when Use Custom Command-line Parameters is enabled for that game.

  2. The matching row under the emulator's Associated Platforms.

  3. Default Command-Line Parameters on the emulator's Details page.

The first non-empty level wins. A per-game custom value replaces the associated-platform and emulator defaults; it is not appended to them. Likewise, a non-empty associated-platform value replaces the emulator-level default. Use the emulator-level field for settings shared by every platform, an associated-platform row when a system needs different settings, and a per-game override only for a genuine exception.

  • Do not type a literal ROM path into a shared parameter field. By default, LaunchBox appends the current game's path.

  • Use %romfile% when the emulator requires the file path at a particular position in the command. If it is absent, LaunchBox normally places the ROM path at the end.

  • Use %noromfile% only for a command that must not receive a ROM path.

  • Preserve the quoting and spacing required by the emulator. The Sample Command on Details previews the resulting structure.

For the available placeholders, see LaunchBox Built-in Command Line Variables.

Configure Associated Platforms

Open Associated Platforms in the Add/Edit Emulator window. Each row connects one LaunchBox library platform to this emulator and stores the settings used for that platform.

For each platform this emulator should run:

  1. Choose the Associated Platform. Use the same platform name assigned to the games in your library, such as Nintendo Entertainment System.

  2. Set platform-specific parameters only when they are required.

  3. For RetroArch, select the appropriate installed Core.

  4. Enable Extract ROMs only when the emulator cannot load the archive format directly.

  5. Optionally enable Use M3U Playlists for Multiple Discs only for an emulator or core that supports that workflow.

  6. Enable Default Emulator if this should be LaunchBox's normal emulator for that library platform.

A platform's Scrape As value controls metadata matching; it does not substitute for the platform name in this table.

What Default Emulator changes

Several emulators can be associated with the same platform, but LaunchBox keeps one default choice for that platform. Setting a row as Default Emulator removes the default designation from another emulator for the same platform. LaunchBox also assigns the default to games or emulated Additional Apps that currently have no emulator, and it may ask whether you want to switch existing assignments from a different emulator. Read that confirmation carefully, choosing a default does not have to mean replacing intentional per-game choices.

To choose an exception for one game, right-click it and open Edit > Edit Metadata/Media..., then select Launching > Emulation. Enable Use an Emulator and choose the emulator you want. This changes that game, not the platform's default.

RetroArch cores

RetroArch is a frontend that loads separate emulation cores. LaunchBox shows the Core column when the emulator is recognized as RetroArch and reads available .dll cores from the cores folder beside the configured RetroArch executable.

  • Application Path points to RetroArch itself.

  • The Associated Platforms Core selects the library used for that platform.

  • The core must be installed, compatible with the content, and appropriate for the platform.

  • Core configuration, controller behavior, saves, and BIOS searches remain governed by RetroArch.

If RetroArch opens and immediately closes or returns to LaunchBox, verify the core is installed, the correct core is selected, the game format is supported, and required BIOS files are available. For the managed integration, see RetroArch LaunchBox Integration Plugin.

Compressed ROMs and extraction

Extract ROMs is a compatibility setting, not a general performance boost. When enabled and LaunchBox recognizes the game as a supported archive, it extracts the contents to LaunchBox's temporary 7-Zip area and gives the emulator a file from the extracted set. LaunchBox prioritizes common entry files such as .cue, .m3u, .gdi, .mds, eboot.bin, and default.xbe; otherwise it uses the first extracted file.

Do not enable extraction blindly. Arcade sets, multi-file disc images, and systems whose archives contain related files may need the archive or its internal structure left intact. Test representative games before applying one setting to an entire platform.

BIOS, firmware, and Dependency Files

Some systems require files that are neither the emulator nor the game: BIOS images, firmware, encryption keys, font files, or other dependencies. Their required names, contents, hashes, and destinations are emulator- and core-specific.

The Add/Edit Emulator window includes a Dependency Files page. When LaunchBox has integration data for the selected emulator, platform, and core, this page can list requirements, check file status, validate hashes where supported, and help place a supplied file in the expected location. If no integration data is available, the page may report that no dependency files are required; that message is not proof that the emulator itself has no external requirements. Consult the emulator or core documentation as the final authority.

Never rename an unrelated file merely to satisfy an expected filename. A correct name with the wrong contents or hash is still the wrong dependency.

Test one game through LaunchBox

  1. Select one game you already proved works directly in the emulator.

  2. Right-click it and choose Edit > Edit Metadata/Media....

  3. Open Launching > Emulation.

  4. Confirm Use an Emulator is enabled and the intended emulator is selected.

  5. Leave Use Custom Command-line Parameters off unless this game truly requires an override.

  6. Save, then launch the game from LaunchBox.

If the direct test succeeds but the LaunchBox test fails, the problem is usually in the saved game path, emulator Application Path, platform association, core, parameters, extraction choice, dependency files, or a game-level override.

Troubleshoot one layer at a time

  1. Game file: confirm the game's Launching > Application Path exists.

  2. Emulator executable: confirm the emulator's Details > Application Path exists and opens.

  3. Direct launch: load the same game inside the emulator outside LaunchBox.

  4. Association: confirm the game's platform matches an Associated Platforms row.

  5. Core and parameters: verify the correct platform row and remove unnecessary per-game overrides.

  6. Dependencies: check BIOS, firmware, keys, and other required files.

  7. Extraction: test the archive both with and without extraction when the emulator's supported formats are unclear.

For a more complete diagnostic sequence, see My Game Won't Play in LaunchBox - Step-by-Step Troubleshooting.

Keep the setup portable when practical

Keeping a portable emulator under LaunchBox\Emulators makes a full LaunchBox installation easier to move, but portability is controlled by the emulator. Before moving or updating one:

  • Back up its configuration and save data.

  • Check its documentation for a portable mode or marker file.

  • Transfer any BIOS, firmware, keys, saves, or settings stored outside its folder.

  • Update the LaunchBox Application Path if the executable moves.

  • Retest a game from every associated platform.

Beginner checklist

  • The emulator and one game work outside LaunchBox.

  • Details > Application Path points to the correct executable.

  • The library platform has a matching Associated Platforms row.

  • The intended emulator is marked as the platform default, or the game has an intentional override.

  • RetroArch has the correct installed core selected.

  • Extraction is enabled only when required.

  • Required BIOS, firmware, and other dependency files are present in the emulator's expected locations.

  • The same known-working game launches from LaunchBox.