Screen Recording & Tutorials

This hub is about screen recordings made to explain something: a software walkthrough, an onboarding video, a bug reproduction for a teammate, a YouTube tutorial. It is for developers, support staff, teachers, and indie makers who record alongside their real work, usually alone, with whatever microphone is plugged in.

In our experience, what goes wrong with a tutorial is rarely the recording software. It is the decisions made before anyone presses record: touring a whole feature instead of finishing one task, recording in an echoing room, leaving chat notifications on mid-demo. These guides move the effort to planning, setup, and a short pre-flight check, leaving less to fix in the edit and nothing to regret after publishing.

Plan one task, then record it in beats

Viewers arrive with a job to do, not a wish to tour your menus. Scope each recording to one task, titled the way someone would search for it ("Set up automatic backups", not "Settings overview"), and plan it as a beat sheet: one line per step, naming the action and the one thing worth saying. Record each beat as its own take, pausing before a retake so the edit has a clean cut point. The tutorial recording workflow covers it end to end.

Assume every frame will be paused

Anyone can pause a published recording and step through it frame by frame (on YouTube, the comma and period keys do it), so a token on screen for half a second is as exposed as one left up for a minute. The usual leaks are mundane: notification banners, browser autocomplete, terminal history, a real customer record in the demo account. If a key does appear, revoke and replace it rather than trusting a blur or a deletion. The pre-flight privacy checklist covers what to close, hide, and swap before every take.

Fix the room before you buy a microphone

A tutorial survives a slightly soft picture; echo, hiss, and a voice that jumps in volume make it hard to follow. Most fixes cost nothing: record in the softest room you have, bring the microphone close enough that your voice outweighs the room's reflections, and set the input level so the loudest moments never clip (distort at the maximum level). Echo baked into a recording is hard to remove cleanly, so placement comes before plugins. The budget audio guide covers gear, room, and levels.

Check what your Mac can already record

On a Mac, Shift-Command-5 opens the built-in Screenshot toolbar, which records the screen plus the microphone you pick under Options; from macOS 27 (Golden Gate), that menu can add system audio too. Third-party recorders need your permission in System Settings > Privacy & Security > Screen & System Audio Recording.

Make the finished video easy to skim

Chapters, the titled sections in YouTube's progress bar, let a returning viewer jump to the step they forgot; your beat sheet is already the chapter list. YouTube only builds chapters from description timestamps when the first is 00:00, there are at least three in ascending order, and each lasts at least 10 seconds. Treat automatic captions as a draft: YouTube itself says to review them, and speech recognition can trip over product names and commands. The guide to chapters, captions, and descriptions covers each piece.

How to use this hub

New to recording? Start with these three, in order:

1. The tutorial recording workflow, the backbone the other guides plug into.
2. The privacy pre-flight checklist, before your next recording: a leak that reaches viewers is the one mistake a re-recording can't fix.
3. The budget audio guide, one round of setup that improves every video after it.

Then add the Mac and chapters guides. If you already record, start with the stage your last video struggled with: plan, screen, sound, or publishing.

None of this requires special software; TechCast Studio, the local-first recording workspace we build (in founding beta on Apple silicon), runs audio, readability, and privacy checks before you record.