What Mechanical Keyboard Hacks Weekly Actually Is
It is a weekly newsletter that covers modifications, firmware tweaks, and building tips for custom mechanical keyboards. Nothing more elaborate than that. The issues are usually 3,000 to 5,000 words long, and they land in your inbox every Thursday morning. The content ranges from beginner lubrication guides to advanced QMK/VIA remapping walkthroughs and occasional deep dives into gasket mount tolerance stacking. The current subscription is free, though there is a paid tier that includes early access and a companion Discord channel. You can sign up at mechanicalkeyboardhackswkly.com. I have been reading it since issue 12, which came out around March 2024, and the quality has been consistently practical rather than promotional.
How I actually use Mechanical Keyboard Hacks Weekly
I do not read every issue cover to cover. Most weeks I skim the headline list, bookmark anything that matches my current project, and come back to the full article later. The useful issues tend to fall into three buckets: switch mod tutorials, firmware configuration guides, and build log breakdowns from other people's builds. The one I keep returning to is the Kailh Box Jade lube strategy article from issue 31. It covers a technique using a shallow silicone mat, a fine brush, and a two-stage drying process that cuts down the total switch servicing time from about 45 minutes per 60-key board to roughly 18 minutes. I tested that method on a Moonlander split with KTT Ming switches and hit the same timeframe. The trick is keeping the lubricant amount measured by weight rather than by eye. I use a 0.01 gram precision scale and target 0.3 mg per switch stem. Anything above 0.5 mg introduces enough drag to make the actuation feel muddy, which I discovered the hard way on my first attempt.
The Firmware Section and What Beginners Miss
The weekly firmware guides are where the newsletter actually earns its keep. Most people jump straight into QMK configurator and flash without understanding layering or hold-vs-tap behavior. The newsletter walks through tap-dance configuration, layer locking with KC_LSFT holding too long, and how to avoid the common mistake of mapping macros directly to keycodes instead of using tap_code16() functions. Here is a specific edge case I ran into that the newsletter addressed in issue 44. I was setting up a macro that typed out a full email signature using SEND_STRING. The string contained special characters like ampersands and at signs. On my initial flash, every instance of & got silently stripped from the output because I did not use the escape sequence SS_LSHTD(0x24). The newsletter post included a table of all the problematic characters and their corresponding escape codes. I had been looking for a solution in the QMK docs for two days before finding that specific post. It saved me from rewriting the entire keymap from scratch.
Get the Full Details

What the Newsletter Does Not Cover Well
For the sake of honesty, there are areas where this publication falls short. The content skews heavily toward QMK-based boards. If you are running Solid State Logic or a controller that uses ZMK exclusively, the firmware tutorials will not apply to you. ZMK support exists in a few recent issues but remains sporadic. The build logs also tend to feature mid-range boards in the $150 to $350 price bracket. Budget builds under $80 and ultra-premium builds over $600 get very little attention. The lubrication guides assume you have a disassembly station and a magnification source. If you are trying to service linear switches without a loupe or a decent desk lamp, the step-by-step photos become difficult to follow. I recommend watching the accompanying video on the website's YouTube channel if the written instructions feel too dense on first read.
Download and Archive Access
There is no single PDF download for past issues. Each newsletter is published as a standalone web page at mechanicalkeyboardhackswkly.com/issues/. You can subscribe through Substack or convert the RSS feed using Feedly or Inoreader if you prefer aggregators. The author also posts supplementary firmware files and lube quantity charts as downloadable attachments on each issue page. I recommend saving the keymap examples as JSON files on a local drive rather than relying on browser bookmarks, since issue URLs change format slightly between the Substack version and the main site. The newsletter is worth subscribing to if you actively build or modify keyboards. It is not essential if you only buy pre-built boards and type on them. The firmware sections have saved me from flashing broken keymaps at least four times. The switch mod guides are reliable as long as you respect the tolerance numbers rather than eyeballing them. The community Discord attached to the paid tier is mildly useful for specific troubleshooting but tends to go quiet between weekly posts. I stick with the free tier and rely on the archived issues as a reference library. If you want a starting point, read issue 19 on pole warming and issue 38 on O-ring damping ratios. Those two topics alone cover about 80 percent of the noise complaints I see on keyboard forums.