How to Add Mouse Click Sounds to Your Screen Recording

Add click sounds to a screen recording: where the setting lives in Recorded, how clicks stay in sync through cuts and speed changes, and when to leave them off.

Watch someone else’s screen recording and you’ll notice how often you lose track of what just happened. A menu appears, a panel slides in, a value changes — but did they click something, or did the app do it on its own? Your own recordings have the same gap, and you don’t see it because you remember pressing the button.

A click sound closes that gap. It is a tiny piece of audio, barely a tenth of a second, and it tells the viewer “that was me, on purpose, right there.” This guide covers where the setting lives in Recorded, how click audio behaves once you start cutting and speeding up footage, and the cases where adding it makes a recording worse rather than better.

Why Click Audio Helps More Than It Looks Like It Should

Screen recordings are missing almost all of the feedback a real interaction has. In person, you hear the physical click of a mouse or trackpad, you feel the press, and your hand is visibly on the device. On video, a click is zero pixels and zero decibels. The only evidence is whatever the UI does next — which is often a change that looks identical to a page loading by itself.

That ambiguity costs the viewer attention in three specific places:

  • Dense interfaces. When a settings panel has twelve toggles, a visible highlight tells the viewer where the cursor is but not when it fired.
  • Fast sequences. Three clicks in two seconds read as one continuous blur without audio to separate them.
  • Interactions with delayed results. If a click triggers a spinner and then a result, the sound anchors the cause to the moment it happened instead of to the result a second later.

Click audio also makes a recording far more watchable when the viewer is not looking straight at the screen — someone following along in their own app, or half-listening on a second monitor. The sound pulls their eyes back at exactly the moment something changed.

Where the Setting Is

In the Recorded editor, click sound lives with the rest of the pointer settings rather than with the audio tracks, which makes sense once you see why: it is generated from recorded cursor data, not from your microphone.

Open a recording in the editor and go to the Cursor tab. Under Click Sound you get three choices:

  • None — the default, no click audio
  • Click 1 — the first built-in click sample
  • Click 2 — the second built-in click sample

Pick either preset and a Volume slider appears below, shown as a percentage. That slider is the whole control surface. There is no per-click editing, no custom sample upload, and no separate pitch or decay setting — the trade-off is that you are done in about five seconds.

The two presets differ in character rather than loudness. Play a few seconds of the timeline with each one and keep the one that disappears into your recording instead of standing out from it. A click you consciously notice on the second listen is usually too loud or too sharp for the content.

What Actually Triggers a Sound

Worth knowing before you turn it on, because it explains most of the surprises:

Only the left button counts. Recorded samples the pointer about sixty times a second during capture and stores the position along with whether the left mouse button is down. Right-clicks and middle-clicks are not in that data, so a context menu you open with a right-click appears silently. If a right-click matters to your tutorial, say it out loud or mark it with a text overlay.

One sound per press, not per release. The renderer fires on the transition from “not pressed” to “pressed.” A click plays a single sound; so does a click-and-hold. A double-click correctly produces two.

Drags produce one sound at the start. Press, move, release gets exactly one click, at the press. That is usually what you want, though it does mean a long drag ends without any audio cue. For drag-heavy footage, the techniques in recording hover states, drags, and micro-interactions do more for comprehension than click audio does.

It is independent of whether the cursor is visible. Turning off Show cursor does not remove click sounds, because the audio comes from the recorded click data rather than from the drawn pointer. If you hide the cursor for a clean product shot, remember to set Click Sound back to None too — otherwise the video clicks with nothing on screen to explain it.

Clicks Stay Put When You Edit

This is the part that makes click audio practical rather than fragile. When you export, Recorded renders every click into its own audio track and maps each one through your timeline edits before mixing it with the rest of the audio.

In practice that means:

  • Trimming and cutting. Remove a thirty-second detour and the clicks that lived inside it disappear with it. The clicks on either side stay locked to their own frames instead of sliding. Combine it with the pass described in trimming and cutting screen recordings.
  • Speed changes. Speed up a long form-filling stretch to 4x and the clicks compress along with the video, still landing on the frames where the button presses happen. They do get dense — see the next section.
  • Zoom and background changes. Purely visual, so click timing is untouched.

The thing to avoid is mixing in click audio as a finishing touch and then going back to restructure the timeline, expecting to re-check sync. You don’t have to. Do your cuts and speed ramps in whatever order you like, and the click track follows.

When Click Sounds Make a Recording Worse

They are not free, and three situations argue against them.

Heavy narration. If you are talking over the whole recording, every click competes with a consonant. Narrated tutorials usually work better with a visual cue — the click animations in the same Cursor tab, Wave or Aura, are silent and read clearly even at small sizes. The cursor effects and highlights guide covers choosing between them, and the cursor highlight feature page shows what the visual treatments look like.

Fast sequences at high speed. A 4x speed segment over a form with twenty fields turns twenty clicks into a burst of noise about a second and a half long. It stops being information and becomes texture. Either drop the speed on that segment, or leave click audio off and let the sped-up motion carry it, as in speed ramping your screen recordings.

Sound-off viewing. On social feeds and in docs where most views are muted, click audio reaches almost nobody. Design those recordings around visual cues first; designing screen recordings that work with the sound off walks through the alternatives. And if the output is a GIF, the point is moot — the GIF format carries no audio at all, so a GIF export drops narration, music, and clicks alike. Creating GIFs from your screen recordings covers what survives that conversion.

Setting the Volume Against Everything Else

Click audio is the quietest thing in the mix and should stay that way. A click that competes with narration is a click that will make viewers reach for the volume control.

A workable order of operations:

  1. Set narration first. Your voice is the priority track; everything else is placed around it. Audio recording best practices covers getting that level right at the source, which matters more than anything you do afterwards.
  2. Then system audio. The Audio tab has separate Microphone and System Audio controls, and you can add volume segments on the timeline to duck one track where it collides with the other.
  3. Then clicks. Start low and raise the slider until each click is clearly audible under your voice but never pulls focus from it. If you find yourself above the halfway mark on the slider, the problem is usually a quiet microphone rather than a quiet click.
  4. Music last, if any. Background music eats the same frequency space as a short click transient. With a music bed running, click audio often needs to come up a little — or come off entirely. Using background music in your screen recordings goes into that balance.

Check the result on laptop speakers, not headphones. Headphones flatter quiet detail; a laptop speaker is where a too-quiet click vanishes and a too-sharp one grates.

A Quick Decision Table

Recording typeClick soundWhy
Silent product demo or loopOn, moderateThe only feedback the viewer gets
Narrated tutorialOff, or very lowCompetes with speech; use click animations instead
Bug report or handoff videoOnProves exactly what you pressed, and when
Sped-up workflow montageOffClick density becomes noise
Social or feed videoOffWatched muted
GIF exportIrrelevantGIFs have no audio track

Give It One Take

The fastest way to decide is to compare. Record twenty seconds of a real interaction — a few clicks, one menu, one form field. Export it once with Click Sound off and once with Click 1 at a low volume, then watch both. Most people pick the version with click audio for silent demos and the version without for anything narrated, and knowing which one you prefer for your kind of content means you stop re-deciding on every project.

If you want to run that comparison on your own footage, download Recorded for macOS or Windows and try it on your next recording.