Voice to Text for Karabiner-Elements
Karabiner-Elements is powerful keyboard customization software, but naming your rules and documenting complex modifications takes time. Blurt lets you speak directly into any text field in Karabiner-Elements. Hold a button, describe your rule or profile, release. Text appears where you need it. No more hunting and pecking to write 'Remap Caps Lock to Hyper Key for application-specific shortcuts.' Your hands stay on the keyboard. Your voice handles the documentation.
The Typing Problem
Complex modification names that actually describe what they do
You've built an intricate key remapping with multiple conditions, layers, and simultaneous key requirements. The modification name field stares at you. Typing 'Change right option plus HJKL to arrow keys only in terminal apps with hyper escape toggle' takes forever. You settle for 'vim arrows' and forget the details within a week.
Profile descriptions for different use cases
You maintain multiple profiles: one for coding, one for gaming, one for video editing. Each needs a clear description so you remember which is which and when to switch. Typing out 'Development profile with IDE shortcuts, vim-style navigation, and caps lock as control' feels tedious. You skip it. Then you forget which profile does what.
Rule documentation in JSON configuration
Power users edit karabiner.json directly. Adding descriptive comments about what each rule does and why requires switching mental gears from code to prose. The comments never get written. Six months later, you're reverse-engineering your own configuration trying to understand why you remapped that specific key combination.
Application-specific layer explanations
You've created conditional rules that only activate in certain applications. Documenting which apps trigger which behaviors, and why you set it up that way, means typing paragraphs. It's faster to skip it. Future you will have no idea why Photoshop gets different shortcuts than Figma.
Sharing configurations with context
You want to share your Karabiner setup on GitHub or with teammates. But a JSON file without explanations is useless to others. Writing clear descriptions for every rule so someone else can understand your workflow takes hours of typing that you'll never recoup.
How It Works
Blurt works anywhere you can type on macOS, including every text field in Karabiner-Elements. Rule names, profile descriptions, JSON comments in your editor. If you can put a cursor there, Blurt can insert text.
Hold your hotkey
Press your chosen shortcut. A small indicator shows Blurt is listening. Karabiner-Elements stays focused.
Speak your description
Describe your rule, profile, or modification. Say what it does and why. Speak naturally.
Release and continue
Text appears at your cursor. Keep customizing your keyboard. No context switching required.
Real Scenarios
Naming complex modifications clearly
You've built a modification that turns your right Command key into a layer activator when held, while still functioning as Command when tapped. The name field awaits. Hold your hotkey and speak: 'Hold right Command for navigation layer, tap for normal Command behavior.' Done in 3 seconds. Anyone reading your config will understand exactly what this rule does.
Profile descriptions for quick switching
You're setting up a new profile for video editing. Put your cursor in the description field and speak: 'Final Cut Pro and DaVinci Resolve shortcuts with JKL playback controls and custom modifier for timeline navigation.' When you see the profile list, you'll know exactly which one to pick.
JSON configuration comments
You're editing karabiner.json in VS Code and need to document a complex rule. Add a comment line and speak: 'This rule creates a Vim-style navigation layer that activates when holding Caps Lock, allowing HJKL movement in any application.' Future maintainers will thank you.
Documenting keyboard layers
You've built a multi-layer keyboard setup with different functions accessible via different modifier holds. Speak the explanation: 'Layer one via Caps Lock for navigation, layer two via right Option for symbols, layer three via both for macros.' Your layer architecture becomes self-documenting.
Application-specific rule notes
You've set up rules that only activate in specific applications. Document them by speaking: 'These shortcuts override default behavior in Xcode to match VS Code keybindings for consistency across IDEs.' Context preserved for when you forget why it exists.
Shared configuration documentation
You're preparing to share your Karabiner config on GitHub. Each major rule needs context. Speak: 'This modification implements a home row mods setup with ASDF as Control, Option, Command, Shift when held.' Your README writes itself.
Troubleshooting notes for complex setups
You've finally gotten a tricky rule working after hours of debugging. Document what you learned: 'Key order matters here. The from key must be defined before conditions or the rule silently fails.' Save future debugging time.
Why Karabiner-Elements users choose Blurt for documentation
| Blurt | macOS Dictation | |
|---|---|---|
| Technical vocabulary | Handles modifier keys, layer terminology | Struggles with technical keyboard terms |
| Activation method | Single hotkey, instant start | Double-tap Fn or click microphone |
| Text field compatibility | Works in all Karabiner UI fields | Inconsistent in utility app interfaces |
| Speed | Text appears in under 500ms | 2-3 second delay typical |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt