Add a screen recording voiceover on a Mac: capture the screen silently, script it scene by scene, then lay a separate narration track under the video.
Direct answer: to add a voiceover to a screen recording on a Mac, record the screen silently first, write a script that follows what happens on screen, then produce the narration as a separate audio track and place it under the video. Keeping the picture and the voice as two files means you can fix one line, change the voice, or retime a scene without capturing the screen all over again.
Most how-to pages treat a screen recording voiceover as something you talk over the capture. That works for a quick clip, but it ties the words to the take: a stumble means a new take, and a changed fact means re-shooting the whole demo. The alternative is to split the job in two. Capture the screen as a silent movie, write the script against that movie, then generate or record the narration as its own track and lay it under the picture. This is also how a product demo script is usually produced, and it is the workflow this guide walks through end to end.
Record the screen first and narrate second
Choose the method before you start, because the cleanup is different for each one.
| Approach | What you do | Strengths | Weaknesses |
|---|---|---|---|
| Narrate live while recording | Talk through the steps as the screen records, capturing voice and picture in one pass. | Fastest for a personal one-take clip, and the timing is automatic because you speak as you click. | A stumble means redoing the take, the mic also picks up room noise, and you cannot fix one sentence without re-shooting. |
| Record silent, add a narration track | Capture the screen with the microphone off, then write and produce the voice as a separate audio file. | The script can be written, reviewed, and regenerated; one line can change without re-recording the screen. | You have to plan the timing and sync the track yourself. |
The separate-track method is the one that scales to a tutorial, a course module, or a support walkthrough, because the two parts change at different rates. Screen actions are stable; wording is not. When a control label changes, you edit one line of the script and regenerate one audio file instead of re-shooting the demo. A live take is still the right choice for a casual update where the point is your voice reacting in the moment.
Script the demo from the screen actions
Write the narration against the capture, not against your memory of the app. Watch the silent recording once and note where the cursor lands and what changes on screen, then fill one short block per scene. Keep the words the audience must hear in the spoken script, and keep production directions such as zoom in here out of it.
| Script beat | What the narration says | What the capture shows |
|---|---|---|
| Goal | One sentence naming the task the viewer has. | The starting screen, before anything changes. |
| Setup | One sentence naming the file, project, or account in use. | The open window or selected item. |
| Action | The exact control name and what happens when it is used. | The click or selection, without a cut in the middle. |
| Result | What the viewer should now see. | The changed state, held long enough to read. |
| Boundary | What this demo does not cover. | The context needed to make the limit clear. |
| Next step | One action for the viewer to take. | The destination or final instruction. |
A useful test: cover the video and read only the spoken column. If the words still work as a set of steps, the narration can stand on its own. If it only makes sense while pointing at the screen, replace here and this with the control name and a description of the result. Name the panel, the button, and the state that appears, because a viewer following along on their own Mac cannot see your cursor.
Here is a short three-scene script written against a silent capture. Each scene maps to one continuous take.
Scene 1, New project
In this clip we create a project and add one audio file. Start on the home screen, where saved projects appear as cards. Choose New project, name it Sample greeting, then choose Create.Scene 2, Add the narration
Open Add audio, then pick the file sample-greeting.wav from the folder on the left. The clip drops onto the timeline at the playhead.Scene 3, Export
With the clip in place, choose Export. Pick the format and the location, then start the export. A progress bar runs across the top until it finishes.This demo shows adding one file and exporting it. It does not cover trimming, multi-track mixing, or any cloud feature.
Record a silent screen capture on a Mac
macOS records the screen with the Screenshot tool, and you can open it from the keyboard or from QuickTime Player. For a narration workflow, record with the microphone set to None so the file holds picture only, then add the voice later.
- Press Shift-Command-5 to open the Screenshot toolbar. In QuickTime Player you can also choose File > New Screen Recording to open the same tools.
- Pick a capture target: record the entire screen, a window, or a selected portion. Drag the frame to reposition it, or drag its edges to resize the area.
- Open the Options menu and set Microphone to None so no microphone audio is captured. This is the step that keeps the recording silent.
- In the same Options menu, choose where the file saves, set a timer delay if you need a moment before recording begins, and turn on Show Mouse Pointer if the clicks matter to the viewer.
- Click Record, perform the workflow at a steady pace, then click the Stop Recording button in the menu bar. Screen recordings save as .mov files.
Record the whole workflow once, even if you expect to cut it. A silent capture costs nothing to re-trim, and the extra footage gives you room to match a line of narration to the exact frame where a change appears. Keep cursor movement deliberate: a pointer that wanders makes the viewer guess which control you mean. If the demo has a step that is hard to reproduce on demand, a quick rehearsal before the real take saves more time than a re-record.
Produce the narration track scene by scene
Once the screen capture exists, the script becomes audio. Generate or record one file per scene and name each file after the scene, so a later revision maps to the right place in the timeline. Murmur is a local-first macOS voice studio for Apple Silicon and Intel Macs running macOS 15 or later. It handles text to speech, voice cloning, voice design, and multi-speaker projects, and it runs the models on your own machine, so there are no per-character fees and nothing is uploaded to a cloud service. That matters when the demo shows an unreleased screen or a client name. Murmur costs $49 one-time and has a free plan and a 3-day Pro trial.
- Split the approved script into one block per scene and keep the file next to the project.
- Generate the audio, then export a format your editor accepts, such as WAV or M4A. The audio export guide explains master versus delivery files.
- Name each file to match its scene, for example 01-new-project.wav, so the files sort in order in the Finder.
- Listen to each clip against its scene and note any line that lands late or early, then fix the script rather than the timeline where you can.
- Keep the clean audio files outside the editor so you can swap one scene without disturbing your edits.
Use one voice for the whole demo, chosen before you generate anything. A voice that changes between scenes reads as a mistake even when the words are identical. If you are still choosing, the narration voice roundup compares the options, and the Mac narration workflow covers the script to audio handoff in more depth. Export a consistent level and sample rate across scenes so the joins do not jump in volume, and keep the master files outside the editor.
Sync the narration under the video
Place the narration under the video, not in a background music well, so it moves with the picture when you trim a scene. In iMovie, drag the audio file right under the video clip it belongs to, and a connecting bar shows the two are attached. A file dropped in the music well stays independent and will not follow a video edit.
- Drop each scene's audio under the matching video clip so the two stay attached.
- If a clip runs long, trim the silence at its head or tail before you move it, so the first spoken word lands where the action starts.
- Select the narration clip and lower the volume of other clips so any music or system sounds duck under the voice.
- Watch the whole demo on the speakers your audience will use, then check every join, because an audio clip can start a beat early or end with a tail of silence.
If the recording needs to go to a platform video rather than a standalone tutorial, the AI voiceover workflow covers publishing the finished piece, and the audio export guide explains the difference between an editing master and a delivery file. For a longer training build, the training video narration guide covers the wider production loop.
When Murmur is not the right choice
Murmur is a Mac app, so if you edit on Windows, need live or real-time streaming speech, or want several people editing one cloud project at once, a cloud service will suit you better. Tools that combine recording, hosting, and transcription in a browser, such as Loom or Descript, are a better single-tool fit for that workflow, so compare their plans directly. Murmur also does not do speech to text, so it cannot turn a recorded walkthrough into a script. And if the demo needs a specific celebrity voice or an emotional read that a stock generated voice cannot carry, plan on recording a person instead. Murmur is strongest when you want private, repeatable narration you can regenerate from the same script, scene after scene.
Frequently asked questions
How do I add a voiceover to a screen recording on Mac?
Record the screen silently first, then add the narration as a separate audio track. On a Mac, press Shift-Command-5 to open the Screenshot tools, set Microphone to None so the recording holds no voice, capture the workflow, and then place a generated or recorded narration file under the video in your editor.
Should I talk while recording the screen or record the voice separately?
Talking live is fastest for a one-take clip, because the timing is automatic. A separate track is better when the narration has to be repeatable, reviewed, or revised, because you can change one line and regenerate one file without recapturing the screen. Pick the method based on how likely the wording is to change.
Where does macOS save a screen recording?
Screen recordings save as .mov files, and the Screenshot Options menu sets the save location. The filename begins with Screen Recording and includes the date and time. You can change the folder, or choose a preset location, before you click Record.
Why is my narration out of sync with the screen?
A long take that was never split, or an audio file dropped in a background music well instead of under a video clip, is the usual cause. Attach each scene's audio under its clip, trim the silence at the head of the clip, and nudge it until the first spoken word lands where the action starts.
Can Murmur record the screen for me?
No. Murmur produces the narration audio; the screen capture comes from macOS or another screen recorder. Record the screen with the Screenshot tools or QuickTime Player, then use Murmur to make the voice track that you lay under the video.
Sources
- Apple Support: Take screenshots or screen recordings on Mac
- Apple Support: Record your screen in QuickTime Player on Mac
- Apple Support: Record audio in QuickTime Player on Mac
- Apple Support: Record a voiceover in iMovie on Mac
Try Murmur - $49 one-time. No subscriptions, no cloud, no per-character fees.
Originally published at murmurtts.com
Top comments (0)