Screen Recording for Beginners
Your first screen recording, step by step — what to use, how to get audio working, and the five mistakes that make a first attempt unwatchable.

Screen recording sounds like it should take one click. It nearly does — until you discover the audio did not record, the text is too small to read, or the file is 3 GB.
This is the version of the instructions that assumes nothing. It gets you a first recording in about two minutes, then explains the handful of things that separate a usable recording from one you have to redo.
Quick comparison
| Tool | Platform | Price | Best for |
|---|---|---|---|
| Screenshot toolbar | macOS | Free, built in | Your first recording, right now |
| Xbox Game Bar | Windows | Free, built in | Same, on Windows |
| Screenify Studio | macOS | Free tier · Pro from $19/mo | Recordings other people will watch |
| OBS Studio | Mac, Win, Linux | Free | Streaming, complex setups |
Start with what is already installed. Move on only when something specific is missing.
Before you record: three decisions
Making these consciously saves the most common redo.
1. What are you capturing? The whole screen, one window, or a region. Choose the smallest that shows what you mean. A full 5K display shrunk into a web page makes every button unreadable. A window or region fills the frame with the thing that matters.
2. What audio do you need? Three separate things, often confused:
- Your voice — the microphone
- Computer sound — what apps are playing, sometimes called system audio
- Both, on separate tracks, which is what you want if you might edit later
3. Where is it going? A colleague in Slack needs something different from a landing page. That decides length, resolution, and whether you need captions.
Method 1: macOS, built in
Already on your Mac. No install.
Step 1 — press ⇧⌘5. A toolbar appears at the bottom of the screen.
Step 2 — choose a mode. The five icons are, left to right: capture entire screen, capture window, capture selected portion — then record entire screen and record selected portion. You want one of the last two.
Step 3 — set your microphone. Click Options and pick your mic under Microphone. This is the step everyone misses, and it is why a first recording is so often silent. The default is None.
Step 4 — set where it saves. Also under Options. Desktop is the default; ~/Movies is a better choice if iCloud syncs your Desktop.
Step 5 — turn on Show Mouse Clicks under Options. It draws a circle on each click, which makes any walkthrough dramatically easier to follow.
Step 6 — click Record. For a region, drag to select first.
Step 7 — stop with the ■ in the menu bar, or ⌃⌘Esc.
Good for: your first recording, bug reports, quick internal clips. It is genuinely fine for those.
Bad for: system audio — it cannot capture what the Mac is playing, only your microphone. No zoom, no captions, and trimming is the only editing available. See why that limitation exists and how to work around it.
Method 2: Windows, built in
Step 1 — press Win+G to open Xbox Game Bar. The name is misleading; it records ordinary apps too.
Step 2 — find the Capture widget. If it is not visible, click the camera icon in the overlay bar.
Step 3 — check the microphone icon is not muted.
Step 4 — click Start Recording, or Win+Alt+R.
Step 5 — stop with the floating bar, or Win+Alt+R again.
Files land in Videos\Captures.
Good for: a quick capture with no install.
Bad for: recording File Explorer or the desktop, which Game Bar refuses. For those, Snipping Tool on Windows 11 now records, or use OBS.
Method 3: Screenify Studio
Worth the install once the recording is for someone outside your team.
Step 1 — pick what to capture from the welcome screen: a display, one window, several windows at once, or an iPhone connected over USB.
Step 2 — set audio. Mic and system audio are separate toggles and record to separate tracks. No virtual audio device to install.
Step 3 — record. Nothing else to configure.
Step 4 — let auto-zoom do the framing. Because it captured the session, it knows where you clicked, and it zooms into those moments. This is the single biggest difference between a raw capture and something watchable, and it is the part that is genuinely hard to do by hand.
Step 5 — trim the dead air at both ends. Every first recording has eight to fifteen seconds of you finding the window.
Step 6 — add captions if it is going anywhere with autoplay. Generated on your Mac, not uploaded.
Step 7 — export at a size matched to the destination.
Good for: anything published — a demo, a tutorial, a landing page clip. Free tier covers 1080p up to five minutes with a watermark.
Bad for: Windows and Linux, which it does not support. Also more app than you need for a ten-second bug report.
Try Screenify Studio — free, unlimited recordings
Auto-zoom, AI captions, dynamic backgrounds, and Metal-accelerated export.
Method 4: OBS Studio
Free, cross-platform, and the answer if you want to stream.
Step 1 — install and skip the auto-configuration wizard's streaming questions if you only want to record.
Step 2 — add a source. In the Sources panel, + → Display Capture or Window Capture.
Step 3 — set your canvas under Settings → Video. Set Base and Output both to 1920×1080 unless you have a reason not to.
Step 4 — for system audio on a Mac, install BlackHole and route through a Multi-Output Device in Audio MIDI Setup. This is four steps in a utility you have never opened, and it is where most beginners stop.
Step 5 — Start Recording.
Good for: streaming, and complex multi-source setups.
Bad for: a first recording. The learning curve is real and unnecessary for simple capture.
The five mistakes that ruin a first recording
Ordered by how often they happen.
1. No audio, because the mic was set to None. Always record five seconds and play it back before the real take. This one check prevents more redos than everything else combined.
2. Recording the whole 5K display. Shown at 800px wide in a browser, your 14px UI text becomes 4px. Record a window or a region.
3. Not trimming the start. The first ten seconds are you finding the window and settling. Cut to the first frame where something purposeful happens.
4. Notifications on screen. Turn on Do Not Disturb before recording. A Slack message from a colleague in a published demo is a bad day.
5. No plan. Not a script — just knowing the three things you will show, in order. Rambling is the most common reason a recording gets redone, and it is the one nobody blames on the tool.
Window, region, or whole screen
The first decision, and the one that most affects whether the result is watchable. Worth more than one line each.
A window. The recorder follows that window even if you move it, and nothing else on your desktop appears — no other apps, no wallpaper, no menu bar clutter. This is the right default for demonstrating one application. The catch: if the app opens a dialog or a separate panel window, that may not be captured, because it is technically a different window.
A region. You drag a rectangle and everything inside it is recorded, whatever app it belongs to. Right when you need part of one app plus part of another, or when you want a specific aspect ratio. The catch: if you move a window during recording, it moves out of frame — the region is fixed to the screen, not to the content.
The whole screen. Simplest, and almost always the wrong choice for anything published. Everything on your desktop is in the video, at a resolution that will be shrunk to fit wherever it ends up. Reserve it for demonstrating something that genuinely spans applications.
A practical trick: before recording a region, resize the app window to roughly the shape you want, then drag the region to match. Aiming a region at a badly-sized window is how you end up with letterboxing.
What to do with the file afterwards
The recording is not the deliverable. Four things take five minutes and change how it lands.
Trim both ends, hard. Cut to the first frame where something purposeful happens. Most first recordings lose eight to fifteen seconds at the front, and it is the single most noticeable improvement available. Be more aggressive than feels comfortable.
Rename it. Screen Recording 2026-08-13 at 14.22.11.mov tells the recipient nothing. checkout-bug-safari.mov tells them everything.
Compress it before sending. A five-minute capture can easily be a gigabyte. See why screen recordings are so large — a tuned export is usually 80–90% smaller and looks the same.
Watch it once before you send it. At the size it will be viewed. Half the problems on this page are visible in the first ten seconds of playback and invisible while recording.
Your second recording: what to improve
Once the basics work, these are the changes with the best return, roughly in order.
Slow down. First recordings are almost always too fast, because you know where everything is and the viewer does not. Pause for a beat after each click before you speak again.
Say what you are about to do before you do it. "I'll open Settings" then open Settings. The reverse order makes viewers chase the cursor.
Stop the cursor moving while you talk. Idle cursor drift is distracting. Park it when you are not pointing at something.
Increase the cursor size. System Settings → Accessibility → Display → Pointer size. A slightly larger pointer is far easier to follow in a scaled-down video, and nobody notices it is enlarged.
Record in segments. Three two-minute takes beat one six-minute take. Re-recording a bad section costs two minutes instead of six, and the cut points already exist for editing.
Then, and only then, worry about zoom, captions, and framing. Polish applied to a rambling recording is still a rambling recording.
Getting audio right
The most common failure, so it gets its own section.
Your voice. Any microphone beats laptop speakers-adjacent built-in mics, but the built-in mic on a modern Mac is genuinely fine for internal videos. Record in a room with soft furnishings; a bare room sounds hollow no matter what you record with.
Computer sound. On macOS this is the hard one. The built-in Screenshot toolbar and QuickTime cannot capture it. Your options: a virtual audio device (BlackHole is free), or an app that supports system audio directly. On Windows, Game Bar and most tools capture it without extras.
Both at once. If there is any chance you will edit, record them as separate tracks. Merged audio cannot be unmerged, and the first time you need to lower a background video under your voice, you will want them apart.
Always test. Five seconds, played back, before the real take.
Three common jobs, start to finish
Most first recordings are one of these. Here is the whole sequence for each.
A bug report
The goal is a developer reproducing the problem, not a polished video.
Record a window, not the screen. Start recording before you trigger the bug, so the steps that cause it are captured. Narrate what you expected versus what happened — that sentence saves more time than the video itself. Keep it under sixty seconds. Trim to just the reproduction. Name the file after the bug. Compress before sending.
The mistake to avoid: recording only the broken state. Half the value is the sequence that got you there.
A how-to for a colleague
The goal is that they can do it themselves afterwards.
Decide the three steps before you record. Turn on Do Not Disturb. Record a window. Say each step before performing it. Pause a beat after each click. Keep it under three minutes — beyond that people stop and never come back. Trim the start, rename, send.
The mistake to avoid: showing every option along the way. Show the path, not the map.
A demo people outside the company will see
The goal is that it looks considered, because it represents you.
This is the one worth using a purpose-built recorder for. Record a window at a deliberate size. Use auto-zoom so small UI reads at small sizes. Add captions, because most feeds autoplay muted and without them the video says nothing. Trim aggressively at both ends. Export at a size matched to where it is going.
The mistake to avoid: publishing the raw capture. A recording that is fine for a colleague reads as unfinished on a landing page.
Troubleshooting
No sound at all. Microphone set to None, or the app lacks microphone permission. On macOS: System Settings → Privacy & Security → Microphone.
My voice recorded but not the app's sound. Expected with built-in Mac tools. You need a virtual audio device or a recorder that supports system audio.
The recording is black. Either a missing screen recording permission — see fixing macOS screen recording permission — or DRM-protected content, which no recorder can capture.
The file is enormous. Normal, and fixable. See why screen recordings are so large.
It stopped before I finished. Usually disk space or the display sleeping. See screen recording stops by itself.
The text is too small to read. Record a window or region rather than the whole display, or zoom into the parts that matter.
Xbox Game Bar will not record File Explorer. By design. Use Snipping Tool on Windows 11 or OBS.
The cursor is hard to follow. Turn on click indicators. On macOS that is Show Mouse Clicks in the ⇧⌘5 Options menu.
FAQ
How do I screen record on a Mac? Press ⇧⌘5, choose record entire screen or record selected portion, set your microphone under Options, and click Record. Stop from the menu bar or with ⌃⌘Esc.
How do I screen record on Windows?
Press Win+G for Xbox Game Bar and use the Capture widget, or Win+Alt+R to start directly. Files save to Videos\Captures.
Why is there no sound in my screen recording? Almost always because the microphone was set to None. On macOS, set it under Options in the ⇧⌘5 toolbar. If you wanted the computer's own sound, built-in Mac tools cannot capture that at all.
What is the easiest screen recording software? Whatever is already installed — the macOS Screenshot toolbar or Xbox Game Bar. For recordings other people will watch, a purpose-built recorder saves more time than it costs to learn.
Do I need to pay for screen recording software? No. Both major operating systems include one, and OBS is free and unlimited. Paid tools buy polish and speed, not the basic capability.
How long can a screen recording be? Built-in tools have no fixed limit but fail in practice on disk space and display sleep. Plan for segments of a few minutes rather than one long take.
Should I record at 30 or 60 fps? 30 for anything UI-based. It halves the file size and looks identical for screen content.
How do I add captions? Not possible in built-in tools. Recorders with on-device transcription generate them directly; otherwise export and use a separate captioning tool.
Your first recording, in order
Open the tool. Set the microphone. Record five seconds and play it back. Turn on Do Not Disturb. Decide your three points. Record a window rather than the whole screen. Trim the start.
That is the whole thing. Everything else — zoom, captions, frames, backgrounds — is polish you can add once the basics are reliably working.
Related reading: Programs like OBS for Mac · Why screen recordings are so large · Fix macOS screen recording permission
Try Screenify Studio
Record your screen with auto-zoom, AI captions, dynamic backgrounds, and Metal-accelerated export. Free plan, unlimited recordings.
Download Free