retrobar.dev
v1.22.122

Tool

RetroBar Settings Builder

Set RetroBar up the way you want, then take it with you: as a settings.json to drop in place, or as a PowerShell script that closes RetroBar, applies your settings and starts it again. RetroBar itself has no command-line options, so the script is also the way to switch themes from a shortcut or a schedule. Everything runs in your browser.

Checked against RetroBar 1.22.122Updated

Explain my settings.json

Paste the contents of your %LOCALAPPDATA%\RetroBar\settings.json. Each value is explained, mistakes are flagged (RetroBar silently ignores a number outside an option's list, and an unknown name), and your values load into the builder above.

How it works, and what we tested

RetroBar reads settings.json only when it starts, and writes the whole file back whenever a setting changes while it runs (SettingsManager.cs). Editing the file under a running RetroBar therefore does nothing, and is undone the next time RetroBar saves. Both scripts get around that the same way: close RetroBar, change the file, start RetroBar.

Tested on Windows 11 (Arm64) (build 26200.9711) with RetroBar 1.22.122: Set-RetroBarTheme.ps1 -Theme 'Windows XP Silver' restarted RetroBar and settings.json then read "Theme": "Windows XP Silver".

  • Option lists are numbers. “Location: Top” is stored as "Edge": 1, because RetroBar saves the position in its list. The builder shows both.
  • Out-of-range numbers are ignored. RetroBar checks that a stored number is a defined option before using it, so "Edge": 7 leaves the taskbar where the default puts it.
  • Theme names must match a file. The theme is the file name without .xaml, from RetroBar's own Themes folder or %LOCALAPPDATA%\RetroBar\Themes. Set-RetroBarTheme.ps1 -List prints the names it can find.
  • Two things are not in settings.json: autostart (a RetroBar value under the Run key in the registry) and the Quick Launch shortcuts themselves (files in the Quick Launch folder).

Keep going

Found something out of date or wrong? Tell us at hello@retrobar.dev and we will fix it.