Understanding Keycap Tracking Without Losing Your Mind
Most people don't realize how quickly a keycap collection grows past whatever system they started with. I've seen keyboards with 47 different keycaps across six different sets, scattered between a spreadsheet, a notes app, and three separate Discord servers. The real problem is keeping everything organized when you're buying new sets, swapping kits, or just trying to remember what profile a specific colorway uses. That's where a proper tracking system actually matters. A Keycaps Worksheet Easy is essentially a structured spreadsheet or template designed to log your keycap inventory. It tracks things like layout, profile height, key legends, material, and purchase date. The "easy" versions strip out the complex formulas and conditional formatting that most hobbyists never actually use. You get a clean grid, some basic columns, and the ability to search or filter when you need to find something specific. I spent about six months using an overly complicated Notion database before I realized I was spending more time maintaining the system than using it. The simpler template wins every time. The ones that work best have maybe eight to ten columns max: set name, layout, profile, material, number of keys, acquisition date, current status, and a notes column. That's it.
Setting Up a Practical Keycap Tracking Sheet
Start with Google Sheets or Airtable. Google Sheets is fine if you're just logging data and need basic search. Airtable adds a bit more structure if you want image attachments per set or relational links between layouts and profiles, but it also introduces friction because now you're managing a database instead of a simple list. Create these columns at minimum: Set Name — The vendor's name for the keycap set. Include the colorway if they have multiple. "GMK Dracula" is not the same as "GMK Dracula Lite" and you will regret merging them later.
Profile — Cherry, XDA, DSA, ODM, SA, MT3, MOG. If you don't know the exact profile, write what you think it is and move on. You can refine later. Layout — Full-size, 75%, 65%, TKL, 60%, 40%. This matters because you'll eventually swap sets between keyboard formats and need to know what keys you're missing or have duplicates of. Material — PBT, ABS, PC, POM. This is useful when you're comparing legends or wear resistance across sets.
Get the Full Details
Key Count — Total number of keys in the set. I learned this the hard way when I bought a split kit that looked complete but was actually 84 keys, not 96. A spreadsheet caught it before the mount arrived. Status — Owned, wanted, on order, sold. This alone prevents about 70% of the duplicate purchases I used to make. Notes — Throw everything else here. Legend font, filament color code, whether it came with a coiled cable, if the stabilizers were pre-lubed, that kind of thing.
The whole setup takes about twelve minutes if you've done it before. First time it took me about forty because I was overthinking the column headers.
The Problem Nobody Talks About
The actual pain point isn't creating the worksheet. It's keeping it updated. I had a habit of buying new keycaps and then forgetting to log them for weeks. Meanwhile the collection grew in my head as "organized" while in reality I had no idea what I actually owned. The sheet became useless because it stopped being current. The workaround that actually stuck for me was attaching a photo to every entry. Not a screenshot from the store page, but an actual photo of the keycaps in a pile on my desk. It takes ten seconds to snap and it anchors the data to something real. When I'm deciding whether to buy a new set, I scroll through the photos instead of reading rows of text. It's faster and it surfaces things I'd forgotten I already owned. Here's another thing that trips people up: profile consistency within a single set. Some modern keycap sets mix profiles across the keyboard. A set might be XDA across the main block but switch to OEM around the arrow cluster. If you only record "XDA" in the profile column, you'll end up with a mismatch when you're building a clean setup. I started noting profile variations in the notes column specifically for this. It's saved me from exactly two broken builds so far.
When a Keycaps Worksheet Easy Doesn't Work
There are scenarios where a simple spreadsheet becomes a liability. If you're working with custom artisan keycaps or limited production runs where each piece is unique, a single row per set won't capture what you actually own. You end up with a row that says "Artisan Set 2024" and fourteen individual pieces that don't share any attributes. In that case, you need a separate tracker or a completely different approach. Another limitation is resale tracking. A basic keycap worksheet tells you what you own but not what it's worth. If you buy and sell frequently, you need a separate column for acquisition cost and ideally a current market value estimate. GMK sets in particular fluctuate enough that knowing your cost basis matters. I add a Resale Value column to my sheets, even though I hate it. It's one more thing to update and it still saves me from selling a set for less than I paid because I forgot what I originally spent. The biggest blind spot is layout fragmentation. Most people track full sets but don't account for individual key replacements. I have three sets where I've lost or damaged individual keys and replaced them with spare stems from another kit. The worksheet shows me the original set as intact, which is misleading when someone asks me what's actually on my keyboard right now. I resolve this by keeping a secondary sheet called Current Build that lists only the keys actually mounted on my keyboards at any given time. It syncs manually with the main sheet whenever I swap something out.
Building the Current Build Tracker
This second sheet is the one most people skip and it's the one that matters most in practice. The master inventory sheet answers "what do I own?" The current build sheet answers "what am I actually typing on right now?" Those are two different questions and mixing them creates errors. The current build sheet has these columns: keyboard model, layout, date assembled, and then one row per key position with the keycap set name and profile in each cell. It looks like a grid that mirrors your actual keyboard layout. When you change a key, you edit the cell. Done. I know that sounds tedious to set up initially. A 65% layout means roughly sixty cells to fill. But you only do it once per keyboard and it takes about eight minutes the first time. After that, a single cell edit when you swap a key is genuinely faster than digging through a long spreadsheet to find what you currently have installed.
The real value shows up when you're shopping. Instead of wondering whether a new keycap set will work with your existing keyboard, you pull up the current build sheet, compare the profile column against the new set's profile, and you know immediately whether there's going to be a height mismatch. This caught me twice when I nearly ordered a SA-profile set for a keyboard running XDA keys. The cost difference between a return shipping fee and five seconds of cross-referencing is obvious in hindsight.
Maintenance Reality
Here's what no one tells you: these systems degrade. Every week you don't update them, they become less useful. The ones who keep theirs accurate treat it like a checkout process. When a new set arrives, the first thing you do is log it. When you sell something, you update the status. When you swap a key on your board, you update the current build sheet. That's the entire workflow. If you let it slide for more than two weeks, you'll catch yourself second-guessing entries and then spending more time verifying old data than you would have spent updating it in the first place. I've done this. It's not fun. A simple Google Sheet with conditional formatting on the status column and a pinned tab for the current build sheet is usually enough. Don't overcomplicate it with pivot tables or VLOOKUP chains unless you genuinely need them. Most of us don't. The friction of maintaining a complex system is almost always higher than the friction of a straightforward one.
The only version of this that truly works long-term is the one you actually use consistently. A basic Keycaps Worksheet Easy that you update weekly beats a sophisticated database you abandon after three weeks. Start simple. Add columns only when you find yourself needing them repeatedly. The rest is just discipline.
