What to look for in a keystroke visualizer for Mac

A good keystroke visualizer for the Mac keeps your passwords out of your videos, shows keys your viewers can read and follow, matches the keyboard you actually type on, and stays out of the way when you are not recording. Before you settle on one, check seven things: privacy, whether it names shortcuts, keyboard layouts, how it behaves when you record, clicks, how well it runs, and how it is priced. Below is what each one means, and a ten-minute test to run before you commit.

Privacy: what it can see and what it keeps

A keystroke visualizer sees everything you type. That is its job, so the questions are what it does with it and how it stays out of the places it should not be.

  • Permissions. To see keys, a Mac app needs Accessibility or Input Monitoring permission. Seeing keys does not take Screen Recording permission, so if a visualizer asks for that, it should say what for. Why a keyboard overlay needs Accessibility permission on a Mac explains what the permission allows.
  • Password fields. When a password field has focus, macOS turns on secure input and no key display gets the keys. A good visualizer goes quiet there and tells you why, so a blank overlay does not look like a broken one. Secure input on a Mac covers how that works and what to do when it gets stuck.
  • Apps that hold secrets. Password managers have ordinary text fields too. Look for a list of apps in which typing never shows.
  • Live demos. Look for a way to hide letters while shortcuts still show, so a password typed into the wrong field shows as dots, not text.
  • Pause. One shortcut that stops everything showing, for the moment you have to log in on camera.
  • What it keeps. It should say plainly whether it saves or sends what you type.

Typebar asks for one permission, Accessibility. In a password field the pill says “Typing hidden in a password field”. Its “Hide typing in these apps” list starts with 1Password, Bitwarden, Keychain Access and Passwords, Hide letters and Pause are in Settings > Privacy, and nothing you type is saved or sent anywhere.

Does it name shortcuts, or only show keys

“⇧⌘4” tells a viewer what you pressed. “⇧⌘4 Screenshot Selection” also tells them what it did, and gives them a name they can look for in the menu later. For tutorials aimed at people new to an app, names make the difference between a video they can follow and one they keep pausing.

Things to check:

  • Where the names come from. Names read from the app’s own menus match what viewers see in their copy of the app, and they change when you switch apps, which matters because the same keys do different things in different apps.
  • Clutter. Ordinary typing should gather into one chip, not a stream of single letters, and a shortcut pressed several times should count up rather than repeat.
  • Filters. You should be able to show everything, or only shortcuts, and choose whether keys like Return and Tab appear.

In Typebar, the pill does each of these: names from the app’s menus, typing in one chip, repeats as ×2, ×3, and both filters.

Does it match your keyboard

A visualizer that draws a full keyboard should draw yours. Three things to check:

  • Shape. A MacBook keyboard, a Magic Keyboard with a number pad and a tenkeyless board look different, and viewers copy what they see.
  • ANSI, ISO or JIS. Return is a different shape on ISO and JIS keyboards than on ANSI ones, and ISO and JIS keyboards have keys that ANSI ones lack. If you are not sure which you have, ANSI, ISO and JIS Mac keyboards: how to tell which you have shows how to tell.
  • Input source. If you type in QWERTZ, AZERTY, Dvorak or Colemak, a board fixed to the US layout labels its keys wrong for you.

Typebar’s board comes in MacBook, Magic Keyboard with or without a number pad, and tenkeyless shapes, in ANSI, ISO and JIS, and follows your input source. A visualizer that shows keys as a line of text, without a keyboard, avoids the shape question, which is a fair reason to prefer one.

Does it show up when you record, and only then

You will forget to turn it on at least once, usually for the take that went perfectly. Look for:

  • Auto-show. It appears by itself when a screen recording or screen share starts and hides when it stops, with lists of apps to show it in or never show it in.
  • A show and hide shortcut for the times you want it by hand.
  • Size and place per mode, so a keyboard and a pill can each sit where they cover nothing.

Also check how it reaches the recording. An overlay that appears as an ordinary window is captured by QuickTime Player, Command-Shift-5 (⇧⌘5), OBS and screen sharing in Zoom or Google Meet, as long as you record or share the whole screen or an area that includes it. A recording or share of one other app’s window leaves it out, whichever visualizer you use.

In Typebar, “Show when a screen recording starts” is in Settings > Recording, with “Show in these apps” and “Never show in these apps” lists, and Control-Option-Command-K (⌃⌥⌘K) shows or hides it by hand.

Clicks and the pointer

In a tutorial, keys are half the action. If the visualizer can show clicks, check that left and right clicks look different, that drags are visible, and that clicks can appear in the same strip as keys, so viewers see the order of “⌘ click, then Return”. A halo around the pointer, or a spotlight that dims everything else, helps viewers find a pointer on a large screen.

Typebar has click ripples with their own shape for left, right and middle clicks, a drag trail, a cursor halo and a Spotlight, and it can show clicks in the pill as Click, Right Click or ⌘ Click.

How well it runs

A visualizer runs all the time you record, so check it behaves:

  • It keeps up. Type a fast paragraph during a test recording and scrub through it. Keys should appear as you press them, not catch up afterwards.
  • It stays quiet on the processor. Open Activity Monitor, in Applications > Utilities, and watch its CPU column while you type quickly.
  • It respects your settings. Reduce Motion and Increase Contrast, in System Settings > Accessibility > Display, should change how it draws.
  • It is signed and notarized, runs on your macOS version, and runs natively on your Mac’s chip.
  • Sounds, if it has them, keep time with your keys and can be turned off.

Typebar is signed and notarized, runs on macOS 14 Sonoma or later on Apple silicon and Intel, follows Reduce Motion and Increase Contrast, and plays its optional typing sounds within 10 ms on built-in and wired speakers.

How it is priced

Keystroke visualizers come in three pricing models, and each is a fair choice:

Model What you get Good for
Free, often open source Keys on screen at no cost; code you can read Occasional recordings, plain keystrokes
Trial, then a free mode Full app for a while, then a reduced free version Trying slowly, paying only if you need more
Trial, then paid only Full app for a short time, then a license to keep going Deciding fast on a full feature set

Also check how many Macs one license covers, whether it is a one-time payment or a subscription, and the refund window. Typebar is the third kind: $9 once for up to 5 Macs, free for 24 hours with everything on, with no free mode after that and 7-day refunds.

A ten-minute test before you commit

  1. Install it and note which permissions it asks for.
  2. Start a recording with Command-Shift-5 and see whether it appears by itself.
  3. Press five shortcuts you use every day in your main app, and read what it shows.
  4. Click into a password field and type a made-up password. Nothing should show.
  5. Type a fast paragraph, then right-click and drag something.
  6. Stop, and watch the recording full screen and on a phone. If you cannot read the keys on the phone, your viewers cannot either.

Questions

Does macOS have a keystroke visualizer built in?

Not one made for recordings. The Keyboard Viewer and the Accessibility Keyboard put a keyboard on screen, but they are made for typing and finding characters. The macOS Accessibility Keyboard and when an overlay suits you better compares them.

Do I need to pay for one?

No. Free visualizers exist, some of them open source. Paying makes sense for things like shortcut names, a full keyboard, auto-show and privacy settings.

Is it safe to leave a keystroke visualizer running?

It sees what you type, so choose one that says plainly it saves and sends nothing, and rely on secure input for password fields.