The short answer
Plan one outcome, prepare safe sample data, record a readable screen with clear narration, and edit for understanding. Refine zooms and captions after the structure works, then review the exported file at the size your audience will watch.
Write the question your demo answers
“How do I share a report with a client?” is a useful brief. “Show all our reporting features” is a tour without a clear finish. Write a one-sentence answer, then list only the actions needed to demonstrate it.
For example: start with the report, choose the client, set the intended access, and show the finished result. A viewer should understand what changed without needing to inspect every menu in the app.
Prepare a believable, safe example
- Use sample records that make the outcome easy to understand.
- Close unrelated apps and notifications.
- Set a readable interface scale before capture.
- Check the save drive, microphone, and any required system audio.
- Rehearse the clicks once so the narration has room for them.
If the passage needs a script, use the teleprompter as a speaking aid. Write a sentence, perform the action, and leave a beat to show the result.
Record enough context to make the cut
Leave a little space before and after the useful action. Move the pointer deliberately, and stop moving it when the viewer should read. If you misspeak, pause and repeat the sentence rather than restarting a long take automatically.
A tutorial can benefit from a presenter introduction, but the screen should have enough room during detailed steps. Use camera placement to support the explanation instead of treating the camera as a permanent decoration.
Edit in a sequence that avoids rework
- Remove false starts and unnecessary waiting.
- Check that the sequence still explains the whole task.
- Balance narration and app audio.
- Refine zooms so important labels remain in frame.
- Correct captions, then style them.
- Add a title or callout only where it clarifies the action.
LumaTake’s timeline editor keeps these elements in the same project. Automatic zoom is a first pass; use the zoom controls to remove incidental movement.
Review like someone seeing the product for the first time
Watch once with sound and once without it. Check whether the captions explain the spoken steps, whether the smallest important label is readable, and whether any private information appears during a transition or zoom.
For a social version, create a separate vertical composition using the reframing guide. For one short silent interaction, consider a GIF export. Keep a clean master and the editable project so a future interface change does not force you to rebuild every element.
Questions about this workflow
How long should the demo be?
Long enough to show the complete outcome without unrelated setup. A single-task demo should not grow into a feature tour just to reach a target duration.
Should every click have a zoom?
No. Emphasize the clicks that reveal information the viewer needs. Incidental zooms can make the interface harder to follow.
Should I record narration live or add it later?
Use the approach that gives you clear timing and comfortable delivery. Live narration connects speech to action; a later voiceover can help when the screen process is difficult to perform while speaking.
About this guide
Published by LumaTake, the product described on this site. This guide covers LumaTake’s recording, editing, and publishing workflows. Platform account requirements and supported formats can change.
Try it with your next recording.
Request access to the LumaTake beta for macOS 26 or later. Tell us about the recording or editing workflow you want to improve.
Request beta accessAccount required. Review the subscription offering and privacy policy.