Planning Keycaps Without Losing Your Mind
The Keycaps Planner website is useful but it has some rough edges that nobody talks about. I've spent more time than I care to admit wrestling with it, and most of the tutorials out there skip over the stuff that actually trips people up. Here's what you need to know before you start building your set. People use the phrase Keycaps Planner Aesthetic to describe the process of using the planner tool to preview and coordinate keycap colorways before buying. It's not a special mode or feature built into the tool. It's just the community shorthand for the whole workflow of planning your keyboard look. The planner lets you upload custom color palettes, assign them to key layers, and see how they look on different case colors and switch types. That's basically it. Go to keycaps.planner and sign up with Google or GitHub. The free tier gives you four layout slots, which is enough for most single-board builds. Once you're in, the interface looks intimidating because it throws a lot at you at once. Ignore the right sidebar for now. Start with the palette editor.
Click the palette icon, then pick your main color. Don't overthink it. Pick something from an existing keycap set you already own or a photo you like. You can import colors directly from an image by dragging and dropping. The hex values usually land close enough that you won't need to manually fine-tune every shade. This saves you fifteen to twenty minutes per build compared to guessing hex codes by eye. Assign your palette to the base layer first. That's your bottom row, spacebar, and enter key. Then layer in your accent colors on the modifier keys and number row. The planner doesn't enforce any particular layout, so you're responsible for making sure the color distribution actually looks balanced. I've seen people put the same accent color on all ten modifier keys and wonder why it looks chaotic. It does. Spread the accent across the middle rows instead. It reads cleaner on most keyboards.
The Export Problem Nobody Warns You About
Here's where things get annoying. When you export your planner design as an image, the preview only shows the keycaps. It doesn't include the case color, the switches, or the plate. If you're trying to share your build with someone or send it to a seller for a custom run, they'll ask you what your case color is and it's not in the image. I spent an afternoon trying to figure out why my planner export looked completely different from what I ordered until I realized the case was defaulting to white in the background of the render. I had to manually add a screenshot overlay in Preview to show the actual case. Not ideal, but it works. There's also no bulk export. If you're planning multiple keyboard builds, each one has to be generated individually. I keep a folder of PNG exports organized by date, which has saved me a few times when I wanted to revisit an old palette. The planner doesn't save color palettes across sessions unless you name and bookmark them. Name your palettes something descriptive like something you'll actually remember two months later when you're coming back to tweak it.
Get the Full Details
Common Pitfalls in the Keycaps Planner Aesthetic Process
Beginners always pick too many colors. The planner makes it easy to add as many as you want, but a functional colorway usually has a base color, one or two mid-tones, and an accent. Three or four is the practical maximum before it starts looking like a grocery receipt. I learned that the hard way with a five-color set that ended up looking muddy because the colors competed with each other instead of working together. Another thing that catches people off guard is the stem color setting. The planner lets you choose stem color independently from the keycap color, but most aftermarket keycaps have stems that match or closely approximate the cap color. If you set a contrasting stem in the planner, your actual set might not look anything like the preview. Double check the manufacturer's specs before you commit to a dual-stem design. It's especially relevant with PBT doubleshot keycaps, where the stem color is baked into the plastic during molding and you can't really change it. The planner also doesn't account for legends. If your keycaps have white legends and you plan to pair them with a light-colored base, the text becomes unreadable in the preview and on the actual set. I made this mistake once and ended up with a full set of keycaps where the lettering disappeared against the base color. The workaround is simple: preview your set with the legend opacity set to high in the planner, and physically hold a sample keycap next to the color you're testing before you order a full set. Most sellers on BoardZero or Drop offer samples for a few dollars each. It's cheaper than replacing an entire set.
Advanced Workflow Stuff
Once you get comfortable with the basics, there are a few things that make the planner significantly more useful. The clone feature lets you duplicate a palette across layouts, which is handy if you're building multiple boards with the same color scheme but different layouts like a 65 percent and a 75 percent. The undo history goes back about ten steps, which is not nearly enough for complex builds but better than nothing. For people who want more control, the planner supports custom SVG uploads for key legends, but the resolution needs to be at least 512 by 512 pixels or the preview gets blurry. I've used this for monogram keycaps on my spacebar, and it works fine as long as you keep the design simple. Detailed artwork doesn't scale well in the planner's rendering. One counter-intuitive thing about the planner is that the color wheel inside it is slightly desaturated compared to real life. The rendered colors look a little duller than the physical keycaps will. If you pick a pastel that looks soft in the planner, it might come out looking slightly more saturated in person. I always bump the saturation up by about ten percent in the planner before exporting my final palette. It's a small adjustment but it brings the digital preview closer to reality.
Limitations and When to Walk Away
The Keycaps Planner Aesthetic workflow is fine for standard ANSI or ISO layouts with up to four palettes per project. It breaks down if you need to plan for split keyboards with mirrored layouts, because the planner assumes a single mirrored or symmetrical layout. You can sort of fake it by duplicating palettes, but it's tedious and error prone. For split builds, I've had better luck using Keyboard Layout Editor alongside the planner, since KLE handles split and ergonomic layouts natively. The planner also doesn't integrate with any major keyboard community or marketplace. You can't share your design to a forum thread with a live preview link. You have to screenshot or export the image. This means if you want feedback from people, you're stuck with static images. It's a minor inconvenience but it adds up if you're actively iterating on a design and asking for input from others. If you're doing anything beyond a straightforward custom keycap run, the planner might not be the right tool. For full custom PCB and case coordination, something like Preonic Planner or even just a spreadsheet with your parts list will give you more actionable information. The planner is really just for keycap visualization. Treat it as what it is instead of expecting it to replace the broader build planning process.
The tool itself is free, and the core functionality works reliably for its intended purpose. It's just that the gaps in the documentation mean you'll run into the same issues repeatedly if you don't already know them. A little upfront knowledge saves a lot of frustration.
