Hi all,
I originally built this to help explore a large adventure game backlog, but I'd like to see how well it works with other collections too. The kind of question it's meant to answer is "what's a good adventure game I own that I haven't played, that isn't too long, and is highly rated?" — and I'm looking for testers with libraries that look different from mine before I call it done.
What it does
It's a single HTML file. You open it in your browser, load a CSV export of your game library, and it turns it into a filterable, sortable table: quick filters for session length, rating, status, and whatever genre/category/tag columns your file has. Click multiple filters to combine them. No installation, no account, no internet connection required after downloading — it all runs locally in your browser, the file never leaves your computer.
There's a real-world example library pre-loaded (mine), so you can explore the interface immediately before trying your own export. The current example library contains around 1,400 games and was used to stress-test the dashboard against a large, real-world collection.
Currently tested with Playnite-based exports, plus representative Steam- and GOG-style CSV exports. The dashboard automatically maps common column names (playtime, rating, status, genres, tags, etc.). I'm still looking for compatibility testing with real-world exports from different tools, because actual libraries always contain edge cases that synthetic test data doesn't.
Expected CSV format
One row per game, with a header row. Only a name/title column is required — everything else is optional. The tool looks for column headers containing:
How to get a CSV in the first place
Why not just use SteamDB or Playnite?
Personal curation is the real difference. Unlike Steam categories, you can organize games the way you actually think about them — detective games, winter games, historical games, cozy games, short evening games — whatever makes sense for your own library, not just whatever genre tag a store assigned.
Beyond that, both are great tools that solve a different problem:
Right now it's intentionally simple and stateless (single file, no backend, nothing saved between sessions). If there's enough interest, I'd consider adding things like saved custom filter presets or persistent settings. For now, I'd rather get the basics right first.
Download
https://drive.google.com/file/d/1gsnM7ae...p=drivesdk
Thanks in advance to anyone willing to kick the tires — especially if your library is large, messy, or comes from somewhere other than Playnite. Bug reports and "this broke on my file" reports are exactly what I'm after.
I originally built this to help explore a large adventure game backlog, but I'd like to see how well it works with other collections too. The kind of question it's meant to answer is "what's a good adventure game I own that I haven't played, that isn't too long, and is highly rated?" — and I'm looking for testers with libraries that look different from mine before I call it done.
What it does
It's a single HTML file. You open it in your browser, load a CSV export of your game library, and it turns it into a filterable, sortable table: quick filters for session length, rating, status, and whatever genre/category/tag columns your file has. Click multiple filters to combine them. No installation, no account, no internet connection required after downloading — it all runs locally in your browser, the file never leaves your computer.
There's a real-world example library pre-loaded (mine), so you can explore the interface immediately before trying your own export. The current example library contains around 1,400 games and was used to stress-test the dashboard against a large, real-world collection.
Currently tested with Playnite-based exports, plus representative Steam- and GOG-style CSV exports. The dashboard automatically maps common column names (playtime, rating, status, genres, tags, etc.). I'm still looking for compatibility testing with real-world exports from different tools, because actual libraries always contain edge cases that synthetic test data doesn't.
Expected CSV format
One row per game, with a header row. Only a name/title column is required — everything else is optional. The tool looks for column headers containing:
- Name — name, title
- Platform / source — platform, source, store
- Genre / category / tags — genre, categor, tag
- Playtime — hour, playtime, time to beat, duration, time played
- Status — status, completed, finished, beaten, progress
- Rating — rating, score, metacritic
How to get a CSV in the first place
- Playnite has this built in: Library → Export Library. Straightforward.
- Steam has no built-in CSV export. You'll need a third-party tool — steam-library-exporter or steam2csv are two that work off a public profile.
- GOG also has no built-in CSV export, so a third-party tool or a manual spreadsheet is the way to go.
Why not just use SteamDB or Playnite?
Personal curation is the real difference. Unlike Steam categories, you can organize games the way you actually think about them — detective games, winter games, historical games, cozy games, short evening games — whatever makes sense for your own library, not just whatever genre tag a store assigned.
Beyond that, both are great tools that solve a different problem:
- SteamDB is fantastic for Steam itself. This tool focuses on unified libraries and personal categorization across multiple sources — if your backlog spans GOG, Epic, Amazon, Battle.net, or physical copies, that's outside what SteamDB covers.
- Playnite is an excellent launcher and library manager. This project focuses on exploratory filtering and personal curation on top of an existing library — think of it as a companion for a specific kind of question ("short, unplayed, highly rated, tagged Point & Click") rather than a replacement.
- Real-world exports from Steam, GOG, Playnite and other launchers
- Libraries with 500+ games
- Non-English titles
- Duplicate games across multiple stores
- Encoding / Unicode issues
- Unexpected column layouts or metadata
- Wrong or unexpected filter results
Right now it's intentionally simple and stateless (single file, no backend, nothing saved between sessions). If there's enough interest, I'd consider adding things like saved custom filter presets or persistent settings. For now, I'd rather get the basics right first.
Download
https://drive.google.com/file/d/1gsnM7ae...p=drivesdk
Thanks in advance to anyone willing to kick the tires — especially if your library is large, messy, or comes from somewhere other than Playnite. Bug reports and "this broke on my file" reports are exactly what I'm after.
This post was last modified: 9 hours ago by Wild Boar.