Setting Up a Keycap Journal That Actually Works
Most people treat keycap collecting like a database problem. It's not. It's an inventory problem with a aesthetics tax. You buy keycaps, you put them on a board, you discover halfway through the year that you forgot what Cherry MX Clear feels like after six months of typing because you didn't write anything down. I learned that the hard way after buying a second set of GMK PANS from a reseller and having no record of whether my first set was v1 or v2. A proper journal for custom keycaps 2026 doesn't need to be fancy. It needs to answer three questions fast: which set is this, where did I get it, and what does it feel like on a real keyboard. Everything else is decoration.
Journal For Custom Keycaps 2026
Start with a spreadsheet or a simple database. Not a Notion template with seven linked pages. A spreadsheet. Columns should include: set name, brand, profile, switch type, plate material, top plate material, foam configuration, purchase date, price paid, source, photo link, and a notes column for impressions. That's it. Don't add columns for things you will never fill out. I use Google Sheets because it syncs across devices and I can take a photo from my phone and link it without opening a separate app. I also keep a single folder on Google Drive named after each keycap set. One photo per row. No gallery apps. You won't find the photo later if it's buried in an album. The one thing nobody mentions is the switch impression column. Write how the switch actually feels after two weeks, not day one. Day one feel is usually wrong. PIMs settle. Lubing spreads. A Gateron Yellow that feels mushy on arrival often firms up by the end of the first week.
How to Record Keycaps Without Losing Patience
The process takes about five minutes per set once you know your own shorthand. Photograph the caps on a neutral background. Photograph them on your actual board. Link both photos. Type the basic specs from the retailer page. Write one sentence about the sound and one about the feel. Done. When I started doing this properly in early 2024, I spent maybe twenty minutes per set and logged around forty sets over the following year. The time adds up, but it stops the reseller spiral. I've seen people list a set as "silent linear" when it's actually a moderately loud tactile because they didn't write down the switch model at the time of purchase. Here's a practical workaround for a problem I ran into: I once bought three different variations of a set from different sellers without tracking the variant names properly. The sheet showed "GMK + Grey" three times. I had no idea which was the original run and which was a reprint. After that, I added a field for batch or wave number whenever the brand uses them. If the seller didn't provide it, I write the order number instead. The order number is your backup when the variant name is vague.
Get the Full Details
What Most People Miss When Building a Keycap Log
People focus on the keycaps. They forget the plate and the foam. Two keyboards with identical keycaps can sound completely different because one uses a polycarbonate middle plate and the other uses FR4. If you don't log the plate material, you're going to compare bass tones that aren't comparable. Another thing: log the stabilizer setup. A set on naked stabilizers sounds different from a set on wire brackets with switches lubed and pads installed. I stopped writing "sounds good" because that phrase is meaningless. I write the stabilizer type and whether I lubed them. Now I can look back and actually understand why a set sounded the way it did. One more counter-intuitive point: don't log every single keycap set you ever own. If you bought a set three years ago and haven't touched it, and you're unlikely to sell it, drop it from the main sheet. Keep a separate archive tab for dead inventory. It reduces noise when you're trying to decide which set to use for a build tonight.
Practical Entry Template
Set name: GMMK Polaris Gray
Profile: Cherry
Switches: Gateron Oil Kings, lubed
Plate: PC 1.5mm top, PC 1.5mm middle
Case: POM
Foam: bottom foam only, 3mm
Stabilizers: Durock V2, lubed
Purchase date: March 12, 2025
Price: $89
Source: Geon
Order number: 4491022
Photos: [link], [link]
Notes: Thocky but not bass-heavy. Oil Kings are smoother than I expected out of the box. The PC case adds a slight ping on hard presses. That's a real entry I filed last year. It looks dry. It works.
When to Switch Tools
If your collection stays under twenty-five sets, a spreadsheet is fine. If it goes past that, or if you want sound comparisons side by side, you'll outgrow it. At that point, Obsidian with a structured note system or a dedicated database like Airtable works better. Airtable handles photo attachments natively, which saves the external link step. But Airtable charges for more than fifty records, so don't jump to it before you need to. I switched to Airtable when I passed thirty sets and started needing to filter by switch type and foam configuration simultaneously. The spreadsheet filter system became too slow for quick decisions.
Common Mistakes
Don't log keycaps you plan to sell within a month. You'll resell it, then forget why you logged it. Log it only when you commit to keeping it. Don't rely on retailer descriptions alone. Write your own impression. Seller photos are staged. Your board sounds different because your desk surface, room acoustics, and switch lube method are all different from theirs. Don't use a mobile note app as your primary journal. Notes apps fragment data. You'll have one set in Apple Notes, another in Google Keep, and a third in your head. When you want to find a specific set later, you'll spend more time searching than you saved by not building a proper log. A spreadsheet or database is boring. Boring is what makes it work.
