What Keycaps Journal Quick Actually Is
It's a lightweight keycap tracker and journal system — part spreadsheet, part visual log, part reference sheet for mechanical keyboard people who have too many sets and can't keep track of profiles, materials, and compatibility without losing their minds. I built the first version for myself because I was tired of writing down keycap info on scraps of paper and then misplacing those scraps. The core idea is simple. You log each keycap set with its profile (Cherry, OEM, MT3, SA, XDA, whatever), the material (PBT, ABS, POM, nylon, double-shot, dye-sub, laser etched), the switch compatibility notes, and a photo or two if you're feeling thorough. Then you can sort, filter, and search through the whole collection without opening a bunch of different apps or spreadsheets scattered across your desktop.
Keycaps Journal Quick Setup Walkthrough
Grab the tool and unzip it. It runs from a single folder, no installation required. Double-click the main entry file and you'll see a blank journal sheet with a few pre-formatted tabs: Collection Log, Quick Reference, Switch Compatibility Matrix, and Notes. The layout is intentionally minimal so you aren't spending more time setting it up than you would just writing the names down on a napkin. Start with the Collection Log. Create a new row for each keycap set you own. Fill in the mandatory fields first — name, profile, material, and whether it's full-size or tenkeyless. Everything else is optional but useful. I add a color palette field and a notes column for things like "quiet for office use" or "rattle-prone on thick stems." The field list is customizable. If you want to add a column for stem type specificity (Cherry-compatible vs. Kailh vs. topre), you can. Right-click any column header and add a new one. Takes about thirty seconds. One thing the tool does well that most alternatives don't: the Quick Reference tab auto-generates a compact summary of your entire collection based on what you've logged. It shows you at a glance how many PBT sets you have versus ABS, which profiles are overrepresented, and where your gaps are. This saved me from buying three more OEM-profile sets when I already had five. I'm not proud of that mistake.
For the Switch Compatibility Matrix, you map out which keycap profiles work with which switch types. This matters more than most people realize. A profile designed for Cherry stems will sit weirdly on a Kailh box stem even though both are technically "Cherry-compatible." I learned this the hard way when I bought a batch of GMK-style keycaps that looked fine in the photos but had a slightly narrower stem slot that made them wobble on my Gateron Milky Clears. The Matrix tab helped me flag that and avoid repeating it. The Notes tab is where I dump everything that doesn't fit neatly into structured fields. Photos go here as embedded links to cloud storage. Review snippets go here. Prices paid, vendors, order dates — all of it. I keep a running expense tally in a separate column at the end of the Notes sheet so I can answer "how much have I actually spent on keycaps this year?" when someone asks at a keyboard meetup.
Get the Full Details
When It Works and When It Doesn't
The system works best for collections between twenty and two hundred keycap sets. Below twenty, you probably don't need a tracker. Above two hundred, you'll outgrow the interface and want something with database-level search and relational linking between entries. That's fine. Just don't force it into this tool past its design limits. The biggest bottleneck is data entry consistency. If you log one set as "PBT double-shot" and another as "Double Shot PBT," the Quick Reference summary will treat them as two different categories until you manually merge them. I wasted about two weeks caught in this exact loop with my dye-sub versus Dye-Sub entries before I realized what was happening. The workaround is to pick a naming convention early and stick to it religiously. I settled on a strict format: Material Type | Construction Method | Finish, and I haven't deviated since. Another limitation you should know about: there's no built-in cloud sync. The tool is entirely local. If your computer dies, your journal dies with it. I solved this by setting up a weekly auto-backup to an external drive and a secondary cloud folder. Takes four minutes a week. The alternative is losing three years of collection history because a hard drive failed on a Tuesday. I recommend the backup routine even if you think you're organized enough to skip it.
There's also no mobile app. If you're in a store looking at keycaps and want to check your existing collection on your phone, you can't. The workaround I use is keeping a read-only export PDF on my phone that I update monthly. It's not real-time, but it's better than opening a browser and logging into a web app that may or may not have your latest entries depending on whether I remembered to hit save.
Practical Details Most Guides Skip
The file size stays small even with heavy use because it stores references rather than embedding actual image files. Full-resolution photos live in your cloud folder; the journal just links to them. This keeps the total file under fifty megabytes even with hundreds of entries. If you're storing images directly inside the journal, you'll inflate it quickly and slow down the load time significantly. Don't do that unless you enjoy watching a progress bar crawl. The search function is basic but functional. It does full-text matching across all logged fields. No fuzzy search, no partial stem matching, no autocomplete. If you type "SA profile 124 key" it'll find anything containing those words in any order. That's it. Advanced users will want richer search capabilities. If that's you, export the data to a proper spreadsheet and use its filtering tools, or migrate to a database tool once your collection grows past the journal's comfort zone. The print layout is surprisingly usable. If you want a physical reference sheet you can take to a swap meet or review event, the tool generates a clean PDF with one keycap per page including the photo, specs, and notes. I've printed dozens of these for conventions. They fold into a standard three-ring binder without falling apart, which is more than I can say for most keyboard community resources.
Bottom Line
Keycaps Journal Quick is a practical, no-frills tracking tool that does one thing well and does it adequately. It won't replace a full-featured database application if you're running a massive collection or running a reselling business. But for someone who wants to know what they own, what it costs, and whether that mysterious keycap in their drawer from 2019 is PBT or ABS, it cuts the setup time from several hours to roughly fifteen minutes and the ongoing maintenance to maybe five minutes a week. That's the value proposition. Anything beyond that is where you'd look at more complex solutions.
