rommapp/rommPublic

What is romm?

A self-hosted ROM manager and modern web-based retro game player with rich metadata integration.

What does romm do?

Romm is a comprehensive self-hosted platform designed for managing and playing extensive retro video game collections. It scans local directories for ROM files and automatically fetches rich metadata, high-quality cover art, and release information via integrations with databases like IGDB and Screenscraper. The application provides a modern, responsive web interface for organizing, tagging, and browsing the library seamlessly across multiple devices. Crucially, it includes an integrated web-based emulator layer that allows users to play their classic games directly in the browser without installing any local standalone emulators.

Who is romm for?

Retro gaming enthusiasts, emulation fans, and home lab owners who want a centralized, visually appealing way to manage and play their ROM collections.

How do I get started with romm?

Please refer to the official documentation for Docker installation instructions.

How popular is romm on GitHub?

rommapp/romm has 13,230 stars and 744 forks on GitHub, and gained 68 stars in the last 7 days.

What license does romm use?

rommapp/romm is released under the AGPL-3.0 license.

• Widely adopted

  13,230 stars

• Very active

  7,974 commits in 52 weeks

• Community-driven

  ~163 contributors

• Well documented

  High community health score

• Continuous integration

  Automated checks passing

Romm is a comprehensive self-hosted platform designed for managing and playing extensive retro video game collections. It scans local directories for ROM files and automatically fetches rich metadata, high-quality cover art, and release information via integrations with databases like IGDB and Screenscraper. The application provides a modern, responsive web interface for organizing, tagging, and browsing the library seamlessly across multiple devices. Crucially, it includes an integrated web-based emulator layer that allows users to play their classic games directly in the browser without installing any local standalone emulators.

Retro gaming enthusiasts, emulation fans, and home lab owners who want a centralized, visually appealing way to manage and play their ROM collections.

• Automated metadata scraping: Fetches high-quality box art, screenshots, and detailed game descriptions from external sources like IGDB.
• Integrated web player: Plays classic console games directly within modern web browsers using integrated WebAssembly-based emulator technologies.
• Cross-device synchronization: Syncs game save states and play history across desktop computers, tablets, and mobile devices effortlessly.
• Modern web interface: Offers a beautiful, responsive, and highly customizable user interface for organizing and browsing large game libraries.
• Multi-system support: Manages ROMs, ISOs, and patches for dozens of retro consoles and handhelds within a single, unified platform.

Getting started: Please refer to the official documentation for Docker installation instructions.

1. 5.3.15.3.1Sep 23, 2026

   ## Minor changes * feat(v2): shorten the changelog's pull request links to #nnnn by @zurdi15 in https://github.com/rommapp/romm/pull/4705 ## Fixes * fix(config): show folder mappings whose folder name is not lowercase by @sdornan in https://github.com/rommapp/romm/pull/4676 * fix(router): re-read the rom on every entry to the details route by @sdornan in https://github.com/rommapp/romm/pull/4685 * fix(streaming): put every container in a pool, and reach later pools by key by @LoneAngelFayt in https://github.com/rommapp/romm/pull/4596 * fix(security): patch OS packages in the published image and scope workflow permissions by @gantoine in https://github.com/rommapp/romm/pull/4592 * fix(docker): move the bases to Alpine 3.24 and nginx 1.30.5 by @sdornan in https://github.com/rommapp/romm/pull/4602 * fix(frontend): eliminate import cycles and gate them with eslint by @andest01 in https://github.com/rommapp/romm/pull/4643 * fix(security): revoke the target account's sessions on a credential change by @sdornan in https://github.com/rommapp/romm/pull/4653 * fix(v2): declare color-scheme with the v2 theme palettes by @sdornan in https://github.com/rommapp/romm/pull/4701 * fix(

2. 5.3.05.3.0Sep 21, 2026

   > [!CAUTION] > ## Breaking changes > ### Filesystem structure must be explicitly declared > We no longer detect the filesystem layout by default, and an instance will **refuses to start** until explicitly declared in your `config.yml`. This is the equivalent of **structure A**: > > ```yaml > filesystem: > structure: > default: "roms/{platform}/{game}" > firmware: "bios/{platform}" > ``` > > And the equivalent of **structure B**: > > ```yaml > filesystem: > structure: > default: "{platform}/roms/{game}" > firmware: "{platform}/bios" > ``` > > `filesystem.roms_folder` and `filesystem.firmware_folder` have also been removed. An instance that still sets either will refuse to start and print the equivalent template. > > See [Custom library structure](https://docs.romm.app/5.3.0-beta/getting-started/folder-structure/#custom-library-structure) and the [`filesystem.structure`](https://docs.romm.app/5.3.0-beta/reference/configuration-file/#filesystemstructure) schema. > [!WARNING] > **Emulator streaming config is now one entry per container, not one per emulator.** > A container's host, protocol and label become the defaults for every platform

3. 5.3.0-beta.15.3.0-beta.1Sep 18, 2026pre-release

   > [!CAUTION] > ## Breaking changes > ### Filesystem structure must be explicitly declared > We no longer detect the filesystem layout by default, and an instance will **refuses to start** until explicitly declared in your `config.yml`. This is the equivalent of **structure A**: > > ```yaml > filesystem: > structure: > default: "roms/{platform}/{game}" > firmware: "bios/{platform}" > ``` > > And the equivalent of **structure B**: > > ```yaml > filesystem: > structure: > default: "{platform}/roms/{game}" > firmware: "{platform}/bios" > ``` > > `filesystem.roms_folder` and `filesystem.firmware_folder` have also been removed. An instance that still sets either will refuse to start and print the equivalent template. > > See [Custom library structure](https://docs.romm.app/5.3.0-beta/getting-started/folder-structure/#custom-library-structure) and the [`filesystem.structure`](https://docs.romm.app/5.3.0-beta/reference/configuration-file/#filesystemstructure) schema. > [!WARNING] > **Emulator streaming config is now one entry per container, not one per emulator.** > A container's host, protocol and label become the defaults for every platform

4. 5.3.0-alpha.35.3.0-alpha.3Sep 17, 2026pre-release

   ## What's Changed * chore(ci): drop the docs and website release triggers by @gantoine in https://github.com/rommapp/romm/pull/4491 * feat(v2): show a reading-progress bar in the manual and walkthrough viewers by @gantoine in https://github.com/rommapp/romm/pull/4470 * feat: offer Steam as a match provider for PC platforms by @sdornan in https://github.com/rommapp/romm/pull/4498 * perf(migrations): add the 5.3.0 roms columns in one table copy by @gantoine in https://github.com/rommapp/romm/pull/4501 * perf(docker): upgrade nginx to 1.29.8 and tune the serving layer by @sdornan in https://github.com/rommapp/romm/pull/4468 * docs: correct stale Vuetify claims in v2 skills and architecture doc by @sdornan in https://github.com/rommapp/romm/pull/4474 * Translate the remaining untranslated zh_CN strings by @wolfg1969 in https://github.com/rommapp/romm/pull/4489 * feat: offer Steam as a cover art provider by @zurdi15 in https://github.com/rommapp/romm/pull/4500 * fix(v2): dismiss tooltips when an overlay opens over them by @sdornan in https://github.com/rommapp/romm/pull/4482 * refactor(roms): give the ROM filters a single home, and match them against the facets mirror by @sdor

5. 5.3.0-alpha.25.3.0-alpha.2Sep 13, 2026pre-release

   > [!CAUTION] > ## Breaking changes > ### Filesystem structure must be explicitly declared > We no longer detect the filesystem layout by default, and an instance will **refuses to start** until explicitly declared in your `config.yml`. This is the equivalent of **structure A**: > > ```yaml > filesystem: > structure: > default: "roms/{platform}/{game}" > firmware: "bios/{platform}" > ``` > > And the equivalent of **structure B**: > > ```yaml > filesystem: > structure: > default: "{platform}/roms/{game}" > firmware: "{platform}/bios" > ``` > > `filesystem.roms_folder` and `filesystem.firmware_folder` have also been removed. An instance that still sets either will refuse to start and print the equivalent template. > > See [Custom library structure](https://docs.romm.app/5.3.0-alpha/getting-started/folder-structure/#custom-library-structure) and the [`filesystem.structure`](https://docs.romm.app/5.3.0-alpha/reference/configuration-file/#filesystemstructure) schema. > [!WARNING] > **Emulator streaming config is now one entry per container, not one per emulator.** > A container's host, protocol and label become the defaults for every platfo

• public-apis/public-apis

  A collective list of free APIs

  486.1K stars · Python

• donnemartin/system-design-primer

  Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards.

  373.2K stars · Python

• awesome-selfhosted/awesome-selfhosted

  A list of Free Software network services and web applications which can be hosted on your own servers

  323.8K stars

• practical-tutorials/project-based-learning

  Curated list of project-based tutorials

  285.8K stars · Python

• NousResearch/hermes-agent

  The agent that grows with you

  251.2K stars · Python

• n8n-io/n8n

  Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.

  206.7K stars · TypeScript