How to Record Clean Screen Footage

Screen recordings fail in a specific way. They look fine on the monitor where you made them and then arrive in a vertical video as unreadable grey mush, because a 1920-wide window squeezed into a 1080-wide phone screen has thrown away most of the detail that made the text legible.

Almost every problem is decided before you press record: how much is on screen, how large the text is, and whether the capture is scaled or cropped.

Record at the size you will publish

If the finished video is 1080 by 1920, then a screen recording of a full desktop is the wrong input — it is horizontal, and cropping it to vertical keeps a narrow slice.

The better approach for tutorial and demo content is one of these:

• Record a window, not the desktop. One app, sized to a portrait-friendly shape, with the content you actually need. It fills the vertical frame instead of floating in it.
• Record at 2x and crop in. Capture a large region at high resolution, then crop the part you use. You keep detail because the source has more pixels than the destination.
• Design for the crop. Put the thing you are demonstrating in the middle of the screen and the empty space at the edges, so a vertical crop does not cut the content.

Whichever you choose, decide before you record. Re-framing a screen capture afterwards means re-recording it.

Make the text genuinely large

Text in a phone video must be readable at arm's length on a small screen while someone is scrolling. That is a far higher bar than readable on a laptop.

• Increase the app's zoom or font size before recording. Browsers and most code editors can zoom to 125 or 150 percent.
• Reduce what is on screen: close the sidebar, hide the file tree, collapse panels.
• If you are demonstrating a menu, open it and leave it open long enough to read — roughly two seconds longer than feels natural.
• One idea per screen. Scrolling to show three things means none of them is readable.

Frame rate and cursor behaviour

30 frames per second is fine for most screen content and produces smaller files. 60 is worth it when the motion matters: dragging, scrolling, animation, cursor-driven interaction.

What matters more than the frame rate is whether it is constant. Screen recorders frequently write variable frame rate files, which some editors handle badly and which can cause audio to drift away from the video over a long recording. Set constant frame rate if the tool offers it, and export at the same rate.

Cursor habits, in order of how much they help:

1. Move slowly and deliberately. Real cursor speed looks like panic on a compressed video.
2. Enlarge the cursor in the capture tool if the option exists.
3. Do not wiggle to find it. If you lose the cursor, stop and find it, then move.
4. Hide the cursor entirely when you are not clicking. Many recorders offer this.
5. Click once, deliberately. Double-clicking by accident opens something you did not want on screen.

Clean the desktop before you start

Everything visible is content. A messy desktop, a personal photo in a dock, an email notification with a name in it — all of it ends up in the video.

• Turn on do not disturb so notifications do not appear mid-take.
• Hide the dock or taskbar if it is not needed.
• Close every window that is not part of the demonstration.
• Empty the desktop, or switch to a plain wallpaper.
• Check bookmarks and tab titles, which often contain client names.

This is also a privacy step, not just a polish one. A notification banner with a message preview is the most common accidental disclosure in screen-recorded tutorials.

Audio for screen footage

Laptop microphones pick up the fan, the keyboard and the room. Two rules:

• Use a separate microphone if you have one, even a cheap USB one, and put it close to your mouth rather than to the laptop.
• Narrate after recording, not during, when the demonstration needs clicking. Clicking while talking produces a soundtrack of clicks under every sentence, and recording the voice separately lets you describe smoothly while the video shows the action.

If you must narrate live, keep the microphone off the same surface as the laptop and speak slightly away from it.

Choose the tool by what it must do

The built-in recorders on Windows and macOS are adequate for a single window and no editing of the capture. They are poor at selecting a region precisely, at constant frame rate, and at recording system audio.

Dedicated capture tools give you region selection, frame rate control, cursor options and separate audio tracks. If you are producing screen content regularly, that control is the reason to use one. If you record a screen twice a year, the built-in tool is fine.

Either way, do a ten-second test recording and play it back before the real take. It is the fastest way to catch a muted microphone or a capture that recorded the wrong monitor.

The mistakes that show up most

1. Recording the full desktop for a vertical video. The content ends up as a small strip in the middle.
2. Text at normal size. Unreadable on a phone, and no amount of sharpening fixes legibility.
3. Recording 4K and shrinking to 1080 without checking. Usually fine, occasionally soft if the scaling is done twice.
4. Notification banners. They appear at the exact moment you are demonstrating something.
5. Cursor jitter. The mouse movement reads as nervous system rather than demonstration.
6. Recording system audio when you only needed the voice, so music from another tab plays underneath.

Recording a phone app

Demonstrating a mobile app adds one problem: the phone screen is already the right shape, so recording it horizontally wastes most of the frame. Use the device's own screen recording, which captures at the device resolution, and present it inside the vertical video at full height with the rest of the frame filled by a background or your face in a corner.

Two details worth handling before you record: turn off the device's notification banners, and slow the taps down. A real interaction speed looks like a blur on video, and a tutorial that moves at real speed is a tutorial nobody can follow.

A short checklist

• Window sized and zoomed for the final vertical frame.
• Text large enough to read on a phone.
• Notifications off, desktop clean, nothing personal visible.
• Constant frame rate, 30 for static content, 60 for motion.
• Cursor enlarged, or hidden when idle.
• Separate microphone, or narration recorded afterwards.
• Ten-second test played back before the real take.

Once the capture is clean, the settings in export settings for vertical video are what stop the platform's re-encode from undoing it.