Setting Up a Keycaps Worksheet Ultimate
Most people try to manage their keycap collections with nothing more than a notes app and a screenshot of their keyboard. That falls apart fast. I learned that the hard way when I had 140 individual sets across six keyboards and couldn't remember which PBT set I'd already matched with my GMK spacebars. A keycap worksheet is just a spreadsheet, but it needs to be built with the right fields from the start, or you'll be retrofitting and losing data. Here is how I actually do it.Keycaps Worksheet Ultimate Setup
Start with a blank Google Sheet or Excel file. The columns you actually need are these: Keyboard Name, Layout (60%, 65%, 75%, TKL, Full), Profile Set, Keycap Material, ABS or PBT, Color Code if applicable, Source or Vendor, Date Purchased, Notes, and a column for Spacebar Style since that causes the most headaches. Don't overcomplicate it at first. I made the mistake of adding columns for stem type, legends print method, and key height ratios all at once. Nobody fills those out. Keep it to the columns you will actually reference when you are standing at your desk trying to decide what to swap in. The Profile Set column is where most people get it wrong. They just write "Cherry" or "OEM." You need to be more specific because Cherry and OEM vary between manufacturers now. I use something like "Cherry MX" versus "Cherry G80-3000" versus "XDA" versus "DSA" versus "MT3." If a set has mixed profiles, I note that in the Notes column. It happens more often than you'd think with aftermarket sets.
For the Color Code column, I use a combination of the official code if the set has one and a simple hex value I grab from a screenshot of the keycaps. The official code is good for searching when you want to reorder. The hex value is what you actually need when you are trying to match a new set against an existing one on your desk. These two numbers together cut down my matching time from maybe twenty minutes per comparison to under two. I keep a second sheet in the same file for legend color tracking. This one has a column for the base color and a column for the character color, separated. If you skip this you will end up with sets that look right from across the room and completely wrong under direct light because you forgot the legends were white on a two-tone set and you paired it with a white spacebar expecting a monochrome look.
The Spacebar Problem and How I Worked Around It
Here is a problem I ran into last year that almost ruined my whole tracking system. I had a set of Santech keycaps in Olive green with a 6.5u spacebar. I also had a set of Absurd keys in the same color family. I put both in my sheet with the same approximate hex code because they looked identical on screen. When I went to build a new keyboard and tried to match them, they were completely different shades. The Santech ones were warmer and yellower, the Absurd ones were cooler and more gray. The workaround was simple but I should have done it earlier. I added a column called Visual Reference and just put a single photo of the set laid out on my desk, taken in consistent lighting. Now when I want to compare two sets I open the photos side by side instead of relying on my memory or a color code from a camera that auto-adjusts everything. I also started writing down the exact lighting condition for each photo. Natural window light in the morning looks different than my LED desk lamp. It seems excessive until you are trying to match a set six months later and the hex code you recorded is useless because it was taken under completely different conditions.
Get the Full Details
How to Keep It Useful Long Term
The biggest failure point for any keycap worksheet is inconsistency. If you stop filling out the Notes column after a few months, the whole thing degrades. I set a rule for myself: if I buy a new set, I log it before I put it on my keyboard. Not after. After is when you forget whether the stems are stabilizer-compatible or whether the set came with a separate numpad block. Another thing that helps is a separate tab for sold or traded sets. I keep a list of everything that leaves my collection with the date it left and who it went to. This prevents me from accidentally recommending a set to someone or trying to source a replacement for something I already sold three months ago. If you have a large collection, the worksheet will get slow in Excel. I noticed it around row 200 when I was doing color-matching calculations across every set I owned. Switching to Google Sheets fixed the performance issue entirely, and the sharing capability means I can pull it up on my phone when I am at a keyboard meetup looking at someone else's setup and want to check if it matches anything I own.
What This Approach Does Not Handle Well
There are limitations worth being honest about. A spreadsheet cannot tell you whether a keycap set is compatible with a particular switch type. It cannot warn you about height differences that only become obvious when you actually type on the board. It cannot track wear patterns or shine development over time. I have seen people try to add columns for these things and abandon the sheet within a month because the data is too subjective to record consistently. For tracking wear and shine, I just take a photo of each set every six months and file it in a folder. That has been more useful than any column I could have added to the worksheet. Photographs do not get outdated the way your recollection of a color does. If your goal is simply to track a small collection of fewer than twenty sets, a spreadsheet might be overkill. A simple folder with photos and a basic text list works fine in that case. The Keycaps Worksheet Ultimate approach makes sense when you have enough sets that manual comparison becomes unreliable, which is usually somewhere around twelve to fifteen different profiles in rotation.
