To show key labels and hear keyboard sounds on Windows, configure the visual overlay and audio playback separately. Keyviz Free displays keypresses; Klakk Windows 1.4.1 plays its included sound packs. When recording, check the image source and audio source separately too. Seeing labels on your monitor does not confirm that the saved video contains them or their sound.
I’m Levin, Klakk’s developer, and prepared this guide with AI assistance. I checked the official Keyviz and OBS documentation and Klakk’s current Windows implementation on October 11, 2026. This describes the settings and capture checks; we have not tested the two apps together or measured their synchronization.
Choose what you want people to see and hear
| Your goal | What to configure |
|---|---|
| Show keys or shortcuts | A keypress visualizer and the recorded image |
| Hear keyboard effects | A sound app and its playback output |
| Include both in a video | Both of the above, plus recorded audio |
Klakk does not provide a floating key-label overlay for presentations. A visualizer supplies that part of the setup.
The distinction also appears in a March 30, 2026 Keyviz feature request: a user who already used its visual overlay asked for optional keypress audio. That request is evidence of one person’s requirement, rather than a promise that an audio feature has shipped.
Set up the visual layer with Keyviz Free
The official Keyviz site describes live keyboard and mouse visualization, key filtering, history and adjustable positioning. Its free release is currently named 2.1.1-beta, dated April 1, 2026. The official release includes a Windows MSI installer; the tag’s shorter name, v2.1.1, does not remove the beta label.
Use the free release for this visual layer. Review its requirements before installing; Klakk’s native x64 and ARM64 support does not establish the same architecture support for another app.
Open Keyviz’s settings and start with these choices:
- In General → Filter, the current version offers Off, Hotkeys and Custom. Choose the key display you need, then check the actual keys shown.
- Decide whether to keep History visible. A history trail can leave earlier inputs on screen after you release them.
- Put the overlay where it does not cover the text, menus or controls you are demonstrating. Its official README describes positioning and appearance options.
Test with harmless sample text and the shortcuts used in your demonstration. A displayed key label is different from the final text inserted by an input method or paste command. The software-generated input guide explains that distinction for Klakk’s audio triggers.
Add keyboard audio separately
Get Klakk playing before configuring the recorder. In Windows 1.4.1, use General → Enable Klakk, then Audio to choose a sound pack, volume and Output Device. Begin at a modest level and confirm that ordinary typing reaches the output you intended. The Windows setup guide covers installation and the first sound.
Klakk has 14 included packs. The visualizer’s filter changes which labels it displays; it does not change which inputs Klakk accepts or mute Klakk for those same keys. Treat hiding the overlay and pausing audio as separate controls. Use the pause guide when you want to stop sound playback.
If one part works and the other does not, troubleshoot that part. A moving label does not prove that the sound app is enabled, has an active trial or license, and has an available output. Audio playback does not prove that the overlay is visible in the recorder.
Check which image OBS captures
On Windows, OBS’s Display Capture captures an entire monitor. Start with the monitor containing your demonstration and overlay, then inspect the OBS preview. This also means that other visible windows and notifications can enter the recording.
Window Capture captures the selected window and its contents, even when other windows sit in front of it. A separate floating overlay can therefore be visible on your desktop but absent from that window source. Do not assume that moving the overlay over the target app embeds it in the target window.
Check the scene and capture method you will actually use. A preview containing the target app alone needs a different image arrangement if you also want the overlay. Check the finished recording before sharing it; this guide does not establish compatibility with every capture method, game or full-screen configuration.
Capture audio deliberately
An image of the keyboard overlay does not supply its own audio track. OBS must receive the sound app through an audio source you select.
Use the separate keyboard audio track guide for application capture and a mixed playback track. If you only want to hear Klakk yourself, check that the active desktop, application and other audio sources exclude it. Headphones change where you hear playback; they do not guarantee that OBS excludes it.
Make a short local recording with sample typing, a shortcut and a quiet pause. Play the saved file and check:
- The labels are visible without covering the demonstration.
- The keyboard audio is included or excluded as intended.
- Any timing difference between the visible labels and audio is acceptable for your use.
This is a check for your setup, rather than a measured latency or synchronization result from us.
Keep private input out of the demonstration
A visible key history can reveal inputs to viewers. Stop the overlay before entering passwords, license keys, private messages or other sensitive information. A custom filter is not proof of automatic password masking. Also check what the captured screen itself shows.
For Klakk Windows, input events and key codes are processed locally for playback; typed text and raw keystrokes are not uploaded. Usage and licensing communication still occurs. See the Windows privacy policy. These statements concern Klakk, and do not establish another app’s data practices.
Before buying a visual-and-sound bundle, compare live labels, saved shortcut history and editable recording labels. Choose the information you want to show or keep alongside the audio you want to hear.
Try the sound layer before buying
You can preview Klakk’s included packs in the browser before choosing the Windows download. The current Windows edition is 1.4.1, for Windows 10/11 on native x64 and ARM64. Its installers are unsigned; review the Windows product page and installer information before proceeding.
The website trial lasts three days from first launch. Continued use is US$4.49 once for Windows, plus applicable tax. The website Mac edition and Mac App Store edition have separate licenses. The trial lets you assess the sound layer in your own workflow; it does not validate the visualizer, recording source or a guaranteed match between their timing.
FAQ
Can Klakk display the keys I press on screen?
Klakk Windows 1.4.1 plays keyboard effects and does not supply a floating key-label overlay. A separate visualizer can provide labels, which you should check in the recorder’s actual preview and saved file.
Why can I see the overlay but not find it in my recording?
The recorder may be capturing a selected app window rather than the monitor containing the separate overlay. Check the image source, selected monitor or window, and the saved recording. Audio capture needs its own check.
Will a shortcut sound confirm that the command worked?
A key event or visible shortcut does not confirm that the target app completed Copy, Paste, Save or another command. Check the app’s result. Klakk Windows 1.4.1 does not offer a user-configurable library of different sounds for named shortcut commands.