Planning Keycaps Without Losing Your Mind
Most people jump into custom keycaps blind. They browse Artisan shops, pick switches on Amazon, and order profiles from Taiwan without really mapping anything out first. That works fine for one board. It falls apart fast when you start wanting consistency across multiple keyboards or when you try to coordinate legends with switch travel. I spent about three months building a basic spreadsheet system for tracking keycap orders, switch testing, and profile measurements before I realized there was no single resource that covered everything in one place. What exists online is scattered across Reddit threads, Discord servers, and forgotten forums from 2019. So I built my own reference document and ended up refining it through actual use rather than theory.
What a Workbook For Custom Keycaps Diy Actually Covers
A functional workbook for this hobby isn't a fancy tool. It's a spreadsheet with columns for keycap profile, stem compatibility, legend style, thickness, material, and cost per unit. You log the maker or manufacturer, the batch number, your order date, and when it arrived. You track switch type alongside each key since some switches bottom out differently depending on keycap depth. The real value shows up when you need to reorder the same profile six months later and remember exactly which batch had the acceptable tolerances versus the ones that wobbled on Cherry stems. The most useful section I added was a simple grid matching my keyboard layout to each key position. Standard ANSI and ISO layouts are well documented. But once you start using split keyboards, column-staggered boards, or 60 percent layouts with macros, you need your own reference for what occupies each slot. I measured my spacebar stabilizers, my shift key positions, and my modifier keys individually and logged the travel distances. That became the baseline for choosing keycaps with enough stem length for each switch type.
The Spreadsheet Breakdown
I use Google Sheets because it syncs across devices and I can share specific tabs with friends who build boards together. The main sheet has these columns: Profile Name, Material, Thickness at Keybase Center, Stem Type, Compatible Switches, Legend Method, Cost Per Key, Total Order Cost, Batch Number, Supplier Link, and Notes. The Notes column is where most people skip but should pay attention. I write things like "slight rattle on stabilizers at position F3" or "legend faded after three months of UV exposure near window." There's a second tab for switch testing. I log switch type, actuation force, bottom-out feel, noise level, and which keycap profiles pair well with each. This sounds excessive until you've spent $40 on PBT keycaps that feel terrible on linear switches because the stem is too short and the housing is too wide. The workbook saved me from repeating that mistake roughly five times over two years. Another section I maintain tracks keycap legends. Standard OEM profile legends don't always align perfectly with custom legends. I measured the offset on my current set and noted it. When ordering custom kits with printed legends, I now account for a 0.5mm vertical shift that happens on certain profiles. That detail only appeared in my notes after my second batch arrived with misaligned characters.
Get the Full Details
Building the System From Scratch
Start with a blank spreadsheet. Create a new row for every keycap you own or order. Fill in whatever details you can access. Don't skip the batch number even if it feels pointless. Batch numbers matter because dye-sub legends vary between production runs. Two orders from the same supplier three months apart can look noticeably different. Without batch tracking, you won't know why your set doesn't match your pictures. Measure your existing keycaps with a caliper or even a ruler if you don't have precision tools. Record height, width, and stem dimensions. You'll use these measurements when evaluating new purchases. Most sellers list profile dimensions but rarely publish the actual stem height or wall thickness. Your own measurements become the reference point for compatibility checks. Add a column for your current keyboard configuration. List each key position and which keycap occupies it. This helps when you want to swap layouts or rebuild. I keep a separate sheet for each board I own. When I disassemble a keyboard, I photograph the layout before removing keycaps. That photo becomes the visual reference I return to when reassembling or modifying.
Common Pitfalls and What Actually Works
People underestimate how much keycap height affects switch feel. A taller profile like XDA or DSA changes the actuation sensation compared to OEM height, even on the same switch. I learned this the hard way when I switched from Cherry MX Browns to the same switches with SA profiles and thought the switches had degraded. They hadn't. The keycap geometry changed the bottom-out depth by nearly two millimeters. My workbook caught this pattern after I logged three separate instances of the same confusion. Another issue is stabilizer compatibility. Some keycaps have narrow stems that don't engage stabilizer wires properly. I once ordered a budget PBT set that worked fine on single switches but skipped off the wire on my spacebar. The workaround was wrapping thin fishing line around the stabilizer wire before inserting the stem. It's a known fix in the mechanical keyboard community, but having it documented in your notes prevents panic when it happens to you. Cost tracking is where most people drift. I track not just the purchase price but the shipping cost per key. Ordering from different regions affects total spend more than people realize. A $30 set from Europe with $15 shipping breaks down to higher per-key cost than a $45 set from Korea with $8 shipping. The spreadsheet makes those comparisons automatic when you add a formula for total divided by quantity.
Sharing and Maintaining It
I keep my workbook updated after every purchase or swap. The habit takes about ninety seconds per transaction. I log the order, record the specs, and add any observations after testing. That consistency is what makes the system useful months later. A spreadsheet you fill in once and forget is just a list with no analytical value. If you want a starting template, you can find community-shared versions in keyboard subreddits and Discord servers. The quality varies. Some are overcomplicated with conditional formatting that doesn't serve the actual use case. Others are too bare to track what matters. The simplest version that works for me has four tabs: Inventory, Switch Profiles, Layout Maps, and Reference Measurements. Everything else lives in the Notes column where I keep it practical rather than polished. The workbook approach isn't required for casual builders. But if you're collecting keycaps, experimenting with profiles, or building more than one keyboard, the effort pays off within a few orders. You stop repeating mistakes and start making decisions based on recorded experience instead of guesswork.
