RetroArch History vs Favorites vs system playlists: choose the right list
Use History to revisit recently launched content, Favorites for entries you deliberately bookmark, and a system or custom playlist for a maintained library with core, database, and thumbnail identity. All three can launch content, but deleting History is not a library rescan, removing a Favorite does not delete the game, and a playlist entry does not prove that its core or ROM is compatible.
Do this in order
- 01
Identify whether the affected tab is History, Favorites, a system playlist, or a user-created playlist before editing anything.
- 02
Launch the same lawful file directly with the intended core to prove that content and core work independently of the list entry.
- 03
For History, reproduce one clean launch and safe exit; use it as a recent-activity check rather than a permanent inventory.
- 04
For Favorites, add and remove one test entry and confirm that the underlying content file remains untouched.
- 05
For a maintained playlist, inspect its core association, entry label, `db_name`, and content path before scanning or editing.
- 06
Back up the affected `.lpl` file, apply one narrow repair, relaunch RetroArch, and verify the entry, core, and thumbnail behavior separately.
Decision and diagnostic table
| List | How entries arrive | Use it for |
|---|---|---|
| History | Successful or attempted recent launches | Return to recent content |
| Favorites | Explicit user bookmark | Small cross-system shortlist |
| System playlist | Scan, import, utility, or manual entry | Maintained system library |
| Custom playlist | Curated or manually combined entries | Purpose-based cross-system collection |
History records use, not ownership
Libretro documents History and Favorites as launch surfaces alongside normal playlists. History is useful evidence that RetroArch attempted or completed a launch, but it is not a rights record, content audit, or permanent catalog.
A missing History row can follow a list limit, configuration change, or different profile. It does not mean the content file was deleted.
Favorites are intentional but still lightweight
A Favorite is a deliberate bookmark and can mix systems. It is valuable for a short public-device menu, but its display label and core association still need the same technical checking as any other launch entry.
Removing the bookmark should not be used as a file-deletion workflow. Verify the underlying authorized content separately.
Playlists carry library identity
Libretro's playlist format can store content path, label, core path and name, checksum or detection marker, and database name. Those fields influence launch and thumbnail matching without changing the bytes of the content.
Choose scanning, manual entry, or direct editing only after the target core and lawful file work together. Cosmetic labels should not drive ROM renaming or unlicensed artwork downloads.
A list entry is launch metadata, not proof of ownership or permission. Add only content you may possess and use, and do not share playlist backups that expose private storage paths or point to unauthorized ROM, BIOS, CHD, artwork, or music.