Most screen recordings fail for boring reasons. The demo is fine, the product works, the person knows their material — but the audio is hollow, the cursor wanders, the framerate stutters at the exact moment something important happens. The fixable problems are almost never about the content. They are about a dozen small decisions made before and after you hit record. Here is what actually moves the needle, in rough order of impact.

Audio: the half nobody forgives

Viewers tolerate a blurry screen. They will not tolerate bad audio. If you fix one thing, fix this.

Microphone choice

Your laptop's built-in mic sounds like you are recording from inside a filing cabinet, because acoustically you are — it picks up fan noise, keyboard clatter, and room reflection. A $60-$100 USB condenser or a basic lavalier clipped 6-8 inches below your chin beats it every time. If all you have is wired earbuds with an inline mic, use those instead of the laptop. Position matters more than price: a cheap mic close to your mouth outperforms an expensive one across the desk.

Levels

Speak a few test sentences and watch the meter. You want peaks landing around -12 dB to -6 dB, never kissing 0 dB (that clips and distorts irreversibly). If your recorder shows no meter, record ten seconds, play it back at the volume you would normally use, and listen for whether you have to lean in. Set the gain once and leave it — riding the level mid-take creates an audible pumping.

The room

Hard parallel surfaces cause echo. You do not need a treated studio; you need soft things. Record in a room with a rug, curtains, a couch, or a closet full of clothes. A corner with a blanket pinned behind you removes most of the slap-back that makes home recordings sound amateur.

Killing background noise

Turn off the dishwasher, mute notifications, and close the window. For the hum that remains — HVAC, computer fans, a refrigerator two rooms away — record two seconds of pure silence at the start of your take. That gives any noise-reduction tool a clean noise profile to subtract, which works dramatically better than guessing. Light reduction cleans up the floor; heavy reduction makes you sound like you are underwater, so go easy.

Lighting & webcam

If you appear on camera, even in a small corner bubble, lighting decides whether you look present or like a hostage. The fix is one light, not three.

Framing: Put your eyes on the upper third of the webcam frame, with a little headroom above and your shoulders visible. Raise the camera to eye level — stacking the laptop on books beats filming up your own nose. Look at the lens, not your own preview, when you want to feel like you are talking to someone.

Key light: The single biggest upgrade is a soft light source slightly above and to one side of your face, angled down at roughly 45 degrees. A window during the day works for free; a $30 ring light or a desk lamp bounced off a white wall works at night. Never sit with a bright window behind you — the camera exposes for the window and turns you into a silhouette. Light comes from the front.

Resolution & framerate settings

More pixels is not automatically better. The right settings depend on what is moving on screen.

1080p vs 4K

Record at 1080p for almost everything: tutorials, app demos, code walkthroughs, meeting recaps. It is sharp, it exports fast, and it plays back smoothly on any connection. Reach for 4K only when fine detail genuinely matters — dense spreadsheets, design pixel-peeping, or footage you intend to crop and zoom into during editing. 4K quadruples your file size and your export time, so do not pay that tax without a reason. One critical detail: record at the native resolution of the region you are capturing. Recording a small window at 4K just upscales blur.

30 vs 60 fps

Use 30 fps for talking-head explainers and static UI demos. Use 60 fps when the screen has continuous motion — scrolling-heavy walkthroughs, animations, transitions, or anything gaming-adjacent — where 30 fps reads as stutter. Sixty fps doubles your data rate, so only spend it where motion is the point.

Bitrate

Bitrate is what actually controls perceived quality; resolution just sets the ceiling. Rough targets for clean H.264: around 8-12 Mbps for 1080p30, 12-20 Mbps for 1080p60, and 35-50 Mbps for 4K. Screen content with large flat color areas compresses well, so you can sit at the lower end. If text looks mushy on playback, your bitrate is too low — raise it before you raise resolution.

Scripting & planning

Improvised recordings ramble, double back, and run long. You do not need a word-for-word script — that sounds robotic — but you need a skeleton. The trick is scripting structure and bullet points, then speaking the connective tissue naturally.

Here is a reusable template that works for almost any demo or tutorial:

Hook (10-15 sec): State the one outcome the viewer gets. "By the end of this you will have X working." No "hey guys, welcome back."
Context (15-30 sec): The problem this solves and who it is for. Skip if obvious.
Steps (the body): One idea per segment. For each: what you are about to do, do it, then the result. Number them in your notes so you never lose your place.
Recap (10-20 sec): The three things they should remember.
Call to action (5-10 sec): The single next step you want them to take.

Write your steps as imperative bullets — "open the recorder," "pick the tab," "hit record" — not full sentences. Bullets keep your delivery conversational while still hitting every beat. Time each section in your notes; if the body is more than five or six steps, it is probably two videos.

Keyboard shortcuts & workflow

Fumbling for the record button on camera looks unprepared, and reaching for the mouse to pause breaks your flow. Learn the start, stop, and pause shortcuts for whatever tool you use so your hands never leave the keyboard. Before a take, hide your bookmarks bar, close noisy tabs, and switch your OS to Do Not Disturb so a Slack toast does not appear mid-demo.

Build a repeatable pre-flight you run every single time — same window size, same zoom level, same browser profile with a clean set of tabs. Muscle memory is the goal: when the workflow is identical every session, you stop thinking about the mechanics and start thinking about what you are saying. If you are recording in the browser, a dedicated tool like Reqo's screen recorder keeps record, region selection, and webcam in one place so there is nothing to fumble for. Record short segments rather than one marathon take — it is far easier to redo a 40-second clip than to find the one flubbed line inside twelve minutes.

Cursor effects, highlights & zoom

The viewer is watching your screen, and they do not know where to look. Your cursor is the pointer that tells them. Move it deliberately: glide to the target, pause, then click — do not jitter or circle elements while you talk. A still cursor is a calm cursor.

Three effects earn their keep:

Cursor highlight: a soft halo or enlarged pointer so viewers can track it on a busy screen.
Click indication: a ripple or flash on click so people know when you acted, not just where the mouse sits.
Zoom-and-pan: the single most effective edit for any screen recording. When you reference a small button, a line of code, or a form field, zoom in on it. It directs attention, hides irrelevant clutter, and makes 1080p footage feel high-resolution. Add these in post rather than zooming during the take — manual zooming mid-record almost always looks jerky.

Apply zoom and highlights afterward in an editor like Reqo's video editor, where you can place them precisely on the timeline instead of hoping you nailed them live.

Accessibility

An accessible recording reaches more people and, not coincidentally, is a clearer recording for everyone. Build these in rather than bolting them on:

Captions: add them to every video. Many people watch muted, and captions are essential for deaf and hard-of-hearing viewers. Auto-generated captions are a starting point — always read them back and fix the product names and jargon your tool will mangle.
Contrast & text size: if your demo involves small or low-contrast UI, bump your OS zoom or browser font before recording. What is legible on your 27-inch monitor is invisible on a phone.
Pacing: leave a beat of silence after each action so screen-reader users and slower viewers can catch up. Do not narrate faster than you click. Pauses also give you clean cut points in editing.
Verbal alt descriptions: say what is happening, not just "click here." "I'm clicking the blue Export button in the top right" works for someone who cannot see the cursor and for someone listening while they commute.

Your pre-record checklist

Run this every time. It takes ninety seconds and saves you from the re-record that eats an afternoon.

Notifications off — OS Do Not Disturb, Slack and email closed.
Record ten seconds, play it back, confirm audio peaks around -12 to -6 dB with no clipping.
Close every tab and window you will not show; hide the bookmarks bar.
Set resolution and framerate for your content (1080p30 default; bump only with a reason).
Check the light is in front of you and the webcam is at eye level.
Have your step bullets visible on a second screen or printed beside you.
Pour water, take a breath, and do one practice run of the opening line.

Polish in editing

The best recordings are made twice — once at capture, once in the edit. You do not need a Hollywood pass; you need to remove the friction. Cut the dead air at the top and tail, snip out the long pauses and the "umm, let me find that" moments, and tighten anywhere you backtracked. This single step turns a meandering eight-minute take into a crisp five-minute one that people actually finish.

Then add the layer that makes it feel intentional: zoom into the details you referenced, drop in cursor highlights on the key clicks, add captions, and put a one-line title card at the start so viewers know they are in the right place. None of this requires a separate download — you can record and edit in the browser, then export. Reqo is free to record, edit, and share with no time limit (a small badge sits on free exports); Pro at $19/mo removes the badge and adds team features and the AI Studio. Whatever tool you use, the principle holds: capture clean, then cut tight.

Put these tips into practice

Record and edit in your browser with Reqo — free, no download.

Start recording free →