Skip to main content

Local Network Support for Shared LaunchBox Libraries (NAT/LAN Awareness)

šŸ“‹ Summary

Introduce built-in support for managing shared LaunchBox libraries across multiple devices on a local network—enabling central management of games, ROMs, media, and metadata for families or multi-device households.


ā— Problem

Families with multiple devices and users currently need to manually copy files, manage separate LaunchBox installations, and individually curate libraries per device. This leads to:

  • Redundant storage across machines

  • Manual syncing overhead

  • Difficulty controlling age-appropriate content per user

  • No simple way to enforce access rules or apply updates centrally


🧠 Assessment

While copying shared folders or using cloud drives is possible, these solutions are limited, prone to errors, and don’t scale well in households with many devices. A centralized, local-only sharing solution within LaunchBox would provide the benefits of multi-user Steam-style sharing, but LAN-based.


āœ… Proposed Solution

Implement a LaunchBox Server Mode that allows:

  • A central LaunchBox instance to host ROMs, media, metadata, and playlists

  • Other LaunchBox or Big Box clients on the same network (Windows/Android) to connect and fetch content

  • User-level access control, enabling per-device or per-user content filtering (e.g. ā€œParent Onlyā€, ā€œKidsā€, ā€œAll Agesā€)

  • Support for syncing saved games and play progress across clients

  • Optional read-only client mode to prevent accidental edits


šŸŽ® Use Case Example

  • Parent curates the main library from a PC

  • Kids’ devices connect to the central library and display only the age-appropriate subset

  • Updates, metadata fixes, and content changes happen once and propagate across all devices

  • Media and ROM storage is centralized, saving disk space


🚫 Scope Note

  • This request focuses on LAN-only functionality (no cloud sync or remote streaming)

  • It would support Windows and Android clients

Status: Open To Community4 comments

Log in to comment and vote

Comments4

  • AstroBob changed status to Open To Community
    Team•

    Jul 1, 2025

    Pinned

    Hi there!

    Thanks so much for submitting this request and for taking the time to explain your use case — that context is always super helpful.

    I’ve gone ahead and fleshed out the main idea using the info you provided, and I’m opening it up to the community for further discussion and feedback. Please let me know if this fleshed-out version doesn’t match your original intended request.

    Feel free to let me know if you have any extra thoughts, examples, or edge cases you think might be relevant!

    Cheers,
    The LaunchBox team

  • khersis

    •

    Apr 19

    I have a similar use case where I have an SMB / CIFS share already with all my games, and that I’d like to have metadata and media stored at as well. Since in my case it’s unlikely that multiple instances of Launch/Bigbox would be running, I thought I would just put the whole installation on the share. This did not work, however, because of the use of sqlite.

    So I’m in favor of the concept of making Launchbox LAN-aware, or for there to be something like a client-server model. But, perhaps as a starting point, supporting the use of a database server like postgresql would be a good start. I think it would go a long way for me, at least.

  • Anatrok

    •

    Mar 20

    I am very interested in some of this functionality. currently I mount platform folders located on my NAS to computers and devices (i have some description in my last couple of posts here

    https://forums.launchbox-app.com/topic/74986-romm-rom-manager-support/#comment-466778)

    this allows local installed instances of launchbox to all share a library, however each one has a duplicate of metadata and media. I personally don’t care much about the parental controls (i’m the main user and my only usecase for multi-user is to separate saves, playlists, etc). Currently mounting folders is a very manual process; i’ve taken a look at the ā€œPlatforms.xmlā€ and considered how i could automate some of this, but the few times i tried were impacted by the lack of client side caching (archive cache manager handles the roms, but i have not solved for media which can cause hitches on large libraries).

    As an aside I have been very happy with launchbox as a client front end but as the number of devices i use have grown (mini-pc, SBC handhelds, Mister, etc) i am spending more and more time reconciling differences between launchbox and RomM. There are several efforts on the RomM side to pull in metadata and media from launchbox libraries (the 4.8 alpha just introduced this), but currently no way to pull that back into launchbox. I would personally benefit from deeper integration with RomM, however i do acknowledge this is beyond the scope of the request. I only mention it here as RomM is opensource and it could provide a possible solution for the ā€œCentral Launchbox Instanceā€.

    Edit; looks like there was a recent release of a plugin that offers some of the functionality I am personally looking for;

    https://github.com/phscezario/launchbox-romm-plugin

  • Skyhoshi

    •

    Jul 1, 2025

    NAT / local LAN Awareness and support

    I’m a family 5 soon to be 7 and I have multiple computers around the house in various forms from laptops to desktops and tablets (*Windows and Android)

    I’m looking to have / provide launch box as a networked server/data center with instances that then talk back to the server for game information.

    I would compare this request to what ā€œFamily Shareā€ (Features now migrated to ā€œFamily Managementā€) on steam is like and but in this case provides a Local Network (LAN Only) Family style sharing of games, roms and data.

    My PAS (Problem, Assessment, Solution) Analysis of this issue is this.

    Problem:

    With multiple family computers and attempting to managing various ranges of age appropriate and content appropriate games and data for my family. iā€m attempting to manage 5 different libraries on various different computers.
    If I’m updating my 6 year olds content that content should also be available my 10 year old. but not to my 3 year old.

    if iā€m updating my 3 year old’s content that should be avalable to everyone.

    if I’m updating Parent only content that should be available to no one but me.

    Assessment:

    There are various ways to address the problem and currently the simplest way is to Copy data files between computers but only update for the most restrictive. (3 year old) then externally make available requested games for the elder kids.