How to Record Your Screen with Audio, Webcam & More

Recording a screen sounds like a one-button job, and most of the time it is. The fiddly parts show up at the edges: the audio that never made it into the file, the webcam bubble sitting in the wrong corner, the gameplay clip that stutters because you asked for 4K at 60fps on a laptop that could not keep up. This guide walks through the seven situations people actually record for, with the settings that make each one come out right the first time.

Everything below works in a browser with Reqo's screen recorder — no install, no time limit on the free plan — but the logic about resolution, frame rate and audio routing applies to any tool you use.

A 60-second pre-record checklist

Run through this before every recording. It takes less time than re-doing a take.

• Close noisy tabs and apps. Notifications, Slack pings and email banners all show up on screen and in system audio. Turn on Do Not Disturb.
• Pick the audio you actually need — mic, system audio, or both — before you hit record, not after.
• Do a 10-second test. Record yourself saying one sentence, stop, and check that the meter moved and the playback has sound. This single habit prevents the most common screen-recording disaster.
• Clear your desktop or use a clean window. Hide personal files, bookmarks bars and that 200-tab browser.
• Set your canvas. 1920×1080 for almost everything; only go higher when fine text or detail genuinely matters.

Recording with system audio and microphone

There are two separate audio sources and they are not the same thing. System audio is what your computer plays — a video, a notification chime, the sound coming out of an app. Microphone audio is your voice. A tutorial usually wants both: the app's sounds plus your narration. A reaction or commentary clip wants both too. A silent walkthrough wants neither.

1. Open the recorder and choose your capture area (full screen, a window, or a single browser tab).
2. In the audio controls, enable Microphone and pick the right input — your headset, not the built-in mic, if you have one.
3. Enable System audio if you need the app's own sounds. In a browser tab capture you will see a "Share tab audio" checkbox — tick it, or the tab's sound will be missing.
4. Watch the input meter while you talk. It should bounce in the middle of the range, not pin to the top (clipping) or barely move (too quiet).

The "no audio" problem, and the one fix that solves most cases

If you finish a recording and it has no sound, the cause is almost always the same: system audio was never shared at the capture step. On most browsers, system or tab audio only gets captured if you explicitly check "Share tab audio" (or "Share system audio") in the screen-picker dialog at the moment you start — there is no way to add it afterward. The other usual suspects are an external mic that the OS muted, or the wrong input device selected when you have several plugged in. The 10-second test recording catches all three before they cost you a real take.

One more thing worth knowing: capturing a single browser tab gives you a "Share tab audio" toggle, while capturing the whole screen or a desktop window may not offer system audio at all on some operating systems. If you specifically need an app's sound and your setup will not share it, record that app inside a browser tab where the toggle is available, or route the system audio through your microphone path as a fallback. When in doubt, share the tab — it is the most reliable way to get both the visuals and the sound in one file.

Adding a webcam overlay (picture-in-picture)

A small webcam bubble in the corner turns a faceless screen recording into something that feels like a person talking to you. It measurably lifts watch-through on tutorials and async updates.

1. Toggle Webcam on before recording and grant camera permission.
2. Position the bubble in a corner that does not cover anything important — bottom-left is safe for most apps, since toolbars and primary content usually sit top and center.
3. Frame yourself with your eyes in the upper third and a little headroom. Look at the camera lens, not at your own preview.
4. Light your face from the front. A window or lamp in front of you beats any expensive camera lit from behind.

If the overlay ends up in an awkward spot, you do not have to re-record — drop the clip into the editor afterward and reposition, resize or round the webcam however you like. Recording first, arranging later, is almost always faster than getting it perfect live.

Recording a presentation or slides

Slide recordings have one rule the others do not: text legibility beats everything. A blurry bullet point ruins the whole point.

1. Put your deck into presenter or full-screen mode first, then start the recorder and capture that window. Capturing the editing view with thumbnails and panels visible looks unpolished.
2. Record at 1080p. Slides are mostly static, so resolution (sharpness) matters far more than frame rate here.
3. 30fps is plenty. Static slides do not benefit from 60fps; you would only inflate the file size for no visible gain.
4. Enable your microphone for narration, and enable system audio only if a slide contains an embedded video or sound.
5. Advance slides deliberately and pause a beat after each transition. It reads as confident and gives editing room later.

Making a tutorial or how-to video

The difference between a tutorial that gets watched to the end and one people abandon is rarely production value — it is structure and pacing. A loose plan fixes both.

Script the beats, not every word

Reading a word-for-word script out loud sounds robotic. Instead, write a bullet list of the steps in order and the one key point for each. You stay on track without sounding like a teleprompter. Open with the outcome — "by the end of this you'll have X working" — so viewers know it is worth their time.

Record in takes, edit out the gaps

You do not need a flawless single run. Record in chunks: do a step, pause, do the next step. If you fumble a sentence, stop talking for two seconds, then say it again cleanly — the silence makes the bad take trivial to find and cut. Trim the dead air and stitch the good takes together in the editor afterward. This is how nearly every polished tutorial is actually made.

Settings: 1080p, 30fps, microphone on. Turn on system audio only if the app you are demonstrating makes meaningful sounds. Slow your cursor down — moving deliberately reads as clear, while fast erratic mousing reads as chaos.

Recording gameplay

Gameplay is the one case where frame rate is not optional. Games run at high frame rates, and capturing them at 30fps makes fast motion look choppy. But there is a real trade-off, because recording also costs performance.

• 60fps is the target for anything fast — shooters, racing, platformers — so motion stays smooth.
• Resolution vs. frame rate is a budget. If your machine struggles, drop from 4K to 1080p before you drop frame rate. Smooth 1080p60 looks far better than stuttering 4K30.
• Free up headroom. Close other apps, and if the game itself is dropping frames while recording, lower the game's graphics settings — the recorder can only capture what the game manages to render.
• Audio: capture system audio for game sound, and add your mic if you are commentating. Keep them as separate sources so you can balance them later.

Long gameplay sessions produce huge files. Record the whole run, then cut it down to the highlights in the editor rather than trying to capture only the good moments live — you will never anticipate the best clip in real time anyway, and stopping to start recording mid-match is how the great moments get missed. If storage is tight, drop to 1080p for the capture and let the editor handle the trimming; a focused two-minute highlight reel beats a forty-minute file nobody finishes.

Turning a recording into a GIF

GIFs are unbeatable for a quick "here's the bug" or "click this button" in a chat, a ticket, or a README — they autoplay, loop, and need no player. The craft is keeping them small.

1. Record only the few seconds that matter. A good UI GIF is 3–8 seconds; anything longer balloons in size and stops looping cleanly.
2. Keep the capture area tight — one window or panel, not the whole screen. Fewer pixels means a smaller, sharper GIF.
3. GIFs are silent, so skip audio entirely.
4. Trim to the exact in and out points in the editor, then export as GIF.

If your file comes out enormous, the fix is almost always a smaller capture area and a shorter clip, not a quality setting. You can make a GIF straight from a recording in the editor, or start from one of the free tools built around a single task.

Adding annotations and cursor highlights

Annotations are how you direct attention. Without them, viewers hunt around the screen wondering where to look; with them, their eye goes exactly where you point.

• Cursor highlight: a soft ring or glow around the pointer so people can follow your mouse, especially useful on dense interfaces.
• Click effects: a small ripple or flash on each click so viewers register that something was pressed — invaluable in step-by-step tutorials.
• Arrows, boxes and text: add these in the editor after recording to circle the button you mean or label a field. Keep them on screen long enough to read — roughly two seconds minimum.
• Zoom: punch in on a small detail rather than telling people to "look at the tiny menu in the corner."

Recording the raw screen first and adding annotations in the editor keeps your live take clean and lets you place every callout precisely.

Recommended settings at a glance

Use case	Resolution	Frame rate	Audio
Tutorial / how-to	1080p	30fps	Mic (+ system if app has sound)
Presentation / slides	1080p	30fps	Mic
Gameplay	1080p–4K	60fps	System + mic (separate)
Webcam talking head	1080p	30fps	Mic
GIF for chat / docs	720p–1080p, tight crop	15–30fps	None
Bug report / demo	1080p	30fps	System + mic

The pattern is simple: 1080p and 30fps cover the overwhelming majority of recordings. Reach for 60fps only when motion is fast (gameplay), and for 4K only when fine detail genuinely needs to survive (and your machine can handle it).

One tab for the whole workflow

The reason to record, trim, annotate and share in the same place is that you stop losing files between tools. Reqo's free plan gives you unlimited recording with no time limit, the full editor for trimming and captions, and share links — the only catch is a small Reqo badge on free exports. If you need watermark-free exports, unlimited team seats, or the AI Studio, that lives on Pro at $19/month. For most people the free plan does the entire job described above.