Setting Up a Steam Deck Tracking Tool Without Losing Your Mind
I've been running various tracking solutions on my Steam Deck for about two years now, mostly because I wanted to know how much time I was actually spending on games versus how much time I thought I was spending on games. The discrepancy is usually embarrassing. Easy Steam Deck Tracker is one of the simpler tools in this space. It sits in your tray, watches your playtime, and logs it to a file or dashboard. That's basically the entire pitch. You install it, point it at your Steam library, and it starts counting. I use it primarily because it doesn't try to be a full gaming dashboard. It does one thing and does it without pulling system resources away from whatever you're actually trying to run.
The Installation Process
Grab the latest release from the official GitHub page. The direct download link is https://github.com/CreeperMarius/EasySteamDeckTracker/releases and you want the Windows installer if you're running Decky Loader or the Linux binary if you're on native SteamOS. I've never gotten the Linux build to work reliably on SteamOS 3.5, so stick with the Windows route through Decky if you can manage that. Once downloaded, run the installer. It asks for your Steam library path, which on Deck defaults to /home/deck/.local/share/Steam/steamapps. Select that, let it scan your library, and you're done. The whole process takes about three minutes if your library isn't absurdly large. Mine has about two hundred games and it took roughly ninety seconds to index everything.
How It Actually Works in Practice
The tracker hooks into Steam's app launch events. When you start a game, it timestamps the event. When you close the game, it records another timestamp. The difference becomes your playtime entry. It writes to a JSON file by default, though you can export to CSV or push to Google Sheets if you're into that kind of thing. Here's something most guides don't mention: the tracker doesn't distinguish between full shutdown and closing back to the desktop. If you Alt-Tab out of a game and leave it running in the background while you browse the web, that time still counts toward your session. I learned this the hard way when I noticed my Elden Ring playtime showed 4.7 hours after what I genuinely believed was a 3-hour session. Turns out I'd left it running while I watched videos for almost an hour without thinking about it.
Get the Full Details
Configuration Details That Matter
Open the settings panel after installation. The default log location is fine for most people, but I recommend moving it somewhere with regular backups. The tracker creates a new log file for each day, named by date. After six months of daily use, you'll have roughly one hundred eighty files cluttering the folder. I compress the older ones into zip archives and store them separately. The export options include local CSV, Google Sheets via OAuth, and a basic HTTP endpoint. The Google Sheets integration is decent but flaky. It worked fine for about three weeks, then started failing silently with no error message in the logs. I switched to CSV exports and wrote a simple Python script that runs weekly to parse and aggregate the data. Takes me maybe ten minutes to set up the cron job and another five to run it each Sunday. The reliability is worth the extra effort.
Known Issues and Limitations
The biggest problem I've run into is related to Steam's own time tracking. When the tracker reads playtime data from Steam's backend API rather than from local events, the numbers don't always match. Steam rounds playtime to the nearest fifteen minutes in some cases and the tracker logs exact timestamps. This creates mismatched reports when you pull data from both sources. The workaround is to disable Steam's built-in playtime reporting entirely and let the tracker be the single source of truth. You lose Steam's dashboard stats, but you gain accuracy. Another edge case: the tracker doesn't handle Steam Input remapping well. If you change controller profiles mid-session, the tracker sometimes registers it as a new game launch and splits one continuous play session into two separate entries. This happened to me with God of War when I switched between the default profile and a custom one I'd made for tighter turning sensitivity. I ended up with two logged sessions for what was clearly one sitting. I just merge them manually afterward, which adds maybe thirty seconds to my end-of-week review. Performance impact is negligible on the Deck itself. The tracker uses somewhere between 30 and 80 megabytes of RAM while idle, which is nothing compared to what modern games consume. CPU usage stays under one percent during normal operation. I haven't noticed any frame rate drops or input latency in any game I've tested it with over the past eight months.
There's also no cloud sync built in. If your Deck breaks or you lose it, your logs go with it unless you've been backing them up. I sync the log folder to a local network share using rsync on a schedule. It's not elegant but it works and I've already recovered from one hardware failure with zero data loss thanks to it. If you want something more feature-rich that handles all these edge cases automatically, tools like SteamBoost or DeckDrops exist, but they add complexity and resource overhead that most people don't need. Easy Steam Deck Tracker is the right choice if you want simplicity and don't mind doing a little manual configuration. It's free, it's lightweight, and it does exactly what the name promises without trying to be something it's not.
