Hobbyists Push No-Intro and Redump Standards for ROM Preservation
Preservation-minded hobbyists are coalescing around No-Intro and Redump datlists, and Launchbox guides insist: "leave it there" — don't move ROMs after importing.

Preservation-minded hobbyists and archivists are pushing concrete standards for ROM collections, favoring No-Intro for console ROMs and Redump for disc images as canonical datlists for preservation-grade sets. The Original Report on evergreen ROM management explicitly recommends "Prefer No-Intro (console ROMs) and Redump (disc images) datlists as canonical collections for preservation-grade ROMs," a position that anchors community workflow discussions.
The technical rationale is blunt: ROM media degrades. Retrobroker frames the problem plainly: "ROM chips, like any physical medium, degrade over time. Exposure to heat, humidity, and general wear and tear can corrupt the data stored on them, potentially leading to game glitches, save file corruption, or even the complete inability to play the game." That reporting links preservation directly to practical dumping and archiving work, arguing that "ROM dumping and archiving are vital to the future of retro gaming."
Operational guidance from Launchbox forums supplies the nuts-and-bolts for hobbyists wishing to follow those standards. The community step-by-step starts with the procedural mandate: "STEP 1 - obtain the up-to-date DAT file for the platform being added, and load it into a ROM manager." Forum contributors insist collections must be DAT-based, noting "To have a full ROM set (based on a DAT) for the platform with all ROMs present and correctly named" and to ensure front-end and manager agree, "To have the game count shown for a platform in Launchbox be the same as the ROM count for the platform in the ROM manager."
Folder layout and import behavior are treated as non-negotiable. The Launchbox guidance warns: "once you have the ROM set and have placed it in the folder where it is going to live, leave it there rather than moving ROMs into any sub-folders. The ROM manager will need to have the ROM set all in the same folder, and Launchbox won't work if you move ROMs around after importing them." That precise workflow detail is driving how many collectors reorganize existing libraries ahead of any front-end import.

Practical trade-offs are part of the conversation. The forum notes a split between guide versions: some prefer the more exacting version 1, while version 2 accepts maintenance shortcuts. As explained in the forum, "we will sacrifice having the correct artwork for both regions of a dual-region rom. This makes a number of things a bit easier, is a lot less work all round and makes things much easier to keep up to date." For platform-specific collections, one contributor recommends eXoDOS for DOS work, calling it "in my opinion the way to go as it's pretty complete, contains lots of media and extras and has all game pre-configured to work properly. It has a shaders option too," while noting that Gamebase collections are "set up to run in the Gamebase app and not Launchbox."
The community framing also carries an ethics check. Retrobroker states that "Responsible and ethical practices are key to ensuring this preservation effort continues legally and effectively," and closes with the appeal, "So, join the effort to preserve gaming history, one ROM at a time!" For practitioners that means following verified datlists, loading up-to-date DATs into ROM managers, keeping files in fixed folders after import, and accepting explicit maintenance trade-offs where necessary to keep collections consistent and accessible.
Know something we missed? Have a correction or additional information?
Submit a Tip

