Played Log vs Backlog: Two Lists Every Gamer Needs
Pedro Faiole·
Ask a gamer how many games are in their backlog and they'll probably answer with a laugh and a shrug. Ask how many games they've actually finished this year and you might get a blank stare. That gap tells you something.
The gaming community talks about backlogs constantly. The "pile of shame" is a cultural institution at this point. Forum threads, Discord servers, subreddits: endless conversations about what people haven't played yet. But the played log, the record of games you've already beaten, the gaming history you've already lived, barely gets mentioned. It's treated as the past, and the past is boring. The next game is always more exciting.
That's a mistake. And fixing it is as simple as keeping two lists instead of one.
What the Backlog Actually Is (and Isn't)
The term "backlog" comes from project management, where it means overdue work: tasks that should have been done but weren't. Applied to gaming, it's become shorthand for every game you own but haven't played, every title on your wishlist, every bundle purchase you made because the deal was too good to pass up.
According to data from Two Average Gamers, the median Steam player has 124 unplayed games in their library. Across the platform as a whole, roughly 51.5% of games in the median library have never been launched. About 24% of digital PC games are never opened even once. The math is brutal: adults with full-time jobs and kids average around 8-10 hours of gaming per week. With roughly 18,800 new games released on Steam in 2024 alone, and the average player actually finishing around four titles per year, the backlog is structurally infinite.
That infinite quality is part of why the backlog produces such a complicated emotional response. Kotaku's Luke Plunkett made the case that the pile of shame reflects something off about how we relate to games as consumers: we've become "more interested in the rituals involved in buying a game than we are in actually playing them." Seasonal sales, social pressure, the dopamine hit of getting a deal, all of this drives purchase behavior that outpaces playing behavior by a wide margin. The result is a backlog that grows faster than any person can play through it, and a low-level guilt that trails most gamers.
Managing that backlog matters. Having some system to prioritize what you play next, to cut the 200-game library down to the 15 or 20 games you'd genuinely play if you had unlimited time, is genuinely useful. But the backlog is only half the picture.
A warm illustration of a gamer settling into an armchair, picking up a controller with two glowing lists visible nearby: a messy tower of unplayed game boxes versus an open, handwritten journal of memories
The Other List Most Gamers Don't Keep
The played log is exactly what it sounds like: a record of games you've already played, beaten, or spent meaningful time with. Not what you want to play. What you've lived.
Why doesn't this get the same attention as the backlog? Partly because the gaming industry is built around what's coming next. New releases, trailers, hype cycles. Anticipation is the product. Once you've played something, it exits the news cycle almost immediately. There's no financial or cultural incentive to revisit what you've finished.
But there's a personal incentive, and it's a strong one.
The writer at How-To Geek described starting their tracking habit after realizing they "could barely remember the previous three games I'd played, let alone what was hot in January." Within a year, the log had become a personal archive: specific titles tied to specific life moments, patterns about what they actually enjoyed versus what they thought they'd enjoy, and an end-of-year snapshot that revealed things about their gaming life they never would have noticed otherwise.
That's the core value proposition. A played log turns a fuzzy sense of "yeah, I play games" into an actual record. Without it, everything collapses into a general impression. You remember that you liked it. You remember roughly when. You lose the specifics.
And the specifics are what make a memory worth keeping.
What You Lose Without a Record
Think back to the last few years of games you've played. Which ones can you place in a specific life context? The one you were playing when a big life change happened. The one you finished on a rainy weekend. The co-op session that became a running joke between you and a friend.
Those details exist in your head right now. In five years, without a record, most of them will be gone. What remains is an impression, not a memory. "I think I played that around 2022?" is not the same as actually knowing.
The HowToGeek writer made a point that hits harder the older you get: they specifically regretted not tracking earlier, lamenting childhood games from their Commodore Amiga era that are now completely lost to memory. They know those games existed. They know they mattered. They can't remember which ones. That's the default outcome for most gaming histories.
A played log changes that default. It becomes what your memory can't be: a reliable, persistent, detailed record that doesn't fade.
Two Lists Working Together
Here's the practical insight: the backlog and the played log serve completely different functions, and both are most useful when they exist alongside each other.
List
Purpose
Direction
Timeframe
Backlog
What to play next
Forward-looking
Future
Played log
What you've experienced
Backward-looking
Past and present
The backlog is a planning tool. It answers: "What should I pick up tonight?" It's functional in a fairly straightforward way: you look at it, you pick something, you play it.
The played log is a memory tool. It answers: "What has my gaming life actually looked like?" It gets more valuable over time, not less, because it compounds. A played log with one year of entries is useful. A played log with five years of entries is something richer: a genuine record of how your tastes evolved, which games hit differently at different ages, and what gaming meant to you during specific periods of your life.
They also feed each other. When you finish a game and add it to your played log, it comes off your active playing time. When you look at your backlog next, you're not second-guessing whether you already played something. The two-list system reduces friction in both directions.
According to data from the Two Average Gamers survey, 60-75% of backlog discussions explicitly use guilt, shame, or anxiety language. The played log is the antidote to that mood. It shifts attention from everything you haven't gotten to toward everything you have. That reframing matters more than it sounds.
What a Good Played Log Captures
Not all tracking is equal. A bare list of titles is better than nothing, but the most useful played logs go a level deeper. Consider what actually helps you remember and reflect:
The date you finished it (or the approximate window when you were playing it)
A short note on what you thought at the time, not a full review, just a sentence or two
Whether you completed it or set it down partway through, and why
Co-op details if you played it with someone, because co-op memories are social memories, and those are worth flagging specifically
A rating, even a rough one, to give future-you context for recommendations and preferences
The more you capture at the time, the more useful it becomes later. Memory is most accurate immediately after an experience. A quick note written the day you finish a game will be more accurate and more vivid than anything you try to reconstruct six months later.
The Two Average Gamers backlog study found that tracking emotional responses, not just completion status, is what separates useful records from noise. "How you felt about it" is the data point that turns a list into a history.
Building Both Lists on The EndWiki
The EndWiki is built around exactly this two-list framework. Your backlog lives in your wishlist and "want to play" queue. Your played log lives in your diary and play history, with full support for per-game notes, ratings, and session details.
The combination means you're not juggling separate tools or spreadsheets. You log games you play in the same place where you track what's coming up next, and your whole gaming history becomes searchable, filterable, and shareable from one profile. You can review a game properly with multi-aspect scoring, add diary entries about specific sessions, and build lists that other people can actually discover. If you've been tracking your gaming history in fragments across multiple platforms and your own memory, The EndWiki brings all of that into a single place that doesn't disappear when a platform shuts down or a spreadsheet gets corrupted.
Platform sync means your Steam, PlayStation, and Xbox libraries can come in through the import tool, which is how most people start: bulk-import their history from connected platforms, clean up what's accurate, and then maintain it from there.
Start With Whatever You Remember
The best time to start both lists was when you first started gaming. The second best time is now.
You don't need a complete, perfect record to begin. Start with the games you know you've finished in the last year or two, note what you remember thinking about them, and build forward from there. The incompleteness of early entries matters a lot less than the consistency of new ones.
For the backlog, trim it honestly. The Two Average Gamers data found that most gamers' "real backlog," the titles they'd genuinely play with unlimited time, is around 15-20 games. Not 200. The rest is theoretical ownership, not actual intent.
Two lists. One forward-looking, one backward-looking. Neither one is complete without the other, and together they give you something that most gamers never have: a clear picture of where they're going and a real record of where they've been.
