Keystroke Display for Screen Recordings — Free in Chrome

Every tutorial video has the same invisible failure: you press ⌘⇧P, the interface obeys, and the viewer has no idea what just happened. Narrating “now I press command shift P” every time gets old for you and them. The fix is old and proven — presenters have used keystroke visualizers for years — but it usually means installing a separate desktop tool and compositing its output into your recording.

SuperchargeCapture builds it in. Keys you press during a tab recording render as clean pill chips near the bottom of the video, timed to the moment you pressed them. And it comes with a privacy rule most keystroke tools skip entirely: anything typed into a password, payment, or verification field is never captured in the first place.

Chips, Not Clutter

During a tab recording, each key press is sampled with a timestamp. In the editor, flip the Keystrokes toggle and those presses appear as a centred row of rounded dark pills — white text on near-black, with a soft shadow so they read over any page. Each chip stays up for about 1.2 seconds; up to five show at once, oldest first, so a fast shortcut sequence reads as a sequence instead of a blur. The chips are sized off the video itself, so they stay proportionate whether you export a small clip or the full frame.

Keys render the way keyboard keys should:

Dead keys and anything un-renderable are simply dropped, so the chip row never shows garbage.

Decide After Recording, Not Before

Keystroke visualizers traditionally make you configure everything up front, then re-record when you forgot to turn them on. Here the samples are collected during every tab recording automatically, and the display decision lives in the editor: toggle chips on for the tutorial cut, off for the version you send a client. The Tutorial preset makes the common case one click — keystroke chips, auto-zoom on clicks, and click effects together, which is most of what a polished software walkthrough needs.

Like auto-zoom and cursor polish, this is a tab-recording feature: the keystrokes are sampled by the recording overlay inside the page, so record with the “This tab” source if you want the chips.

Passwords Are Dropped, Not Blurred

Here is the part worth being precise about, because a keystroke recorder that ignores it is a liability. If you log in, pay for something, or enter a 2FA code mid-recording, a naive visualizer captures the secret verbatim, with timestamps, into a file you’re about to share.

SuperchargeCapture checks what a keystroke is aimed at before recording it. Keys typed into any of these are dropped at the source:

• Password fields — anything the page marks as a password input
• Payment fields — card number, CVV, and other card-autocomplete fields
• One-time codes — 2FA, OTP, and verification-code inputs
• Fields hinting at secrets — PINs, SSNs, private keys, seed phrases, routing and account numbers, based on how the field names and labels itself

Dropped means dropped: the keystrokes are never sampled, never written to disk, and cannot appear in any export. They are deliberately not replaced with a masked ●●● chip, because a row of placeholders still tells the viewer exactly how long your password is.

The check also errs on the side of caution. When a page hides its input inside a component the extension cannot inspect — a closed shadow root, for instance — those keystrokes are treated as sensitive and dropped too. The cost is an occasional missing chip on an exotic widget. The alternative is a password baked into a shared video, which is not a mistake you can take back.

Privacy

Keystrokes are sampled only while a recording you explicitly started is running, only in the recorded tab, and stop the moment it ends. The samples are stored locally next to the recording, drawn into the video on your device at export, and only if the toggle is on. Nothing is transmitted anywhere — no account, no telemetry, no cloud.

Questions? Reach out at support@superchargebrowser.com.