- Size the browser window to your final output and set display scaling and browser zoom before you record, because most of the sharpness you see in the finished file is decided here.
- Use 30 frames per second for most interface demos and raise the bitrate if small text smears, then confirm both with a ten-second test.
- Check the export at normal playback speed on a phone and on a laptop, and fix anything unreadable before you publish, not after.
Most screen recordings that look amateur don’t have a camera problem or a software problem. They have a setup problem that was decided before the first click. The text is a little soft, the cursor disappears on a dark theme, a notification slides in during the best part, and the file is so large it stutters on the viewer’s laptop. Each of these is small on its own. Together they make a recording feel like a screenshot someone happened to move.
The screen recording tips below are mostly boring fixes, and most of them happen before you press record. This list is organized in the order you’d actually work through them: first the screen, then the settings that shape the file, then what the viewer sees while you record, then how to protect the take and check the result. The tips are the ones that tend to make the biggest difference in the finished video, and each one comes with the reason it works.
Screen recording tips that start before you press record
Most of the quality in a finished recording is set before you start. These first three tips are about the screen itself.
1. Match the window to the output size
Decide the size of the video you’re going to publish, then make the browser window that size before you record. A 1920 by 1080 tutorial should be recorded from a window at that resolution, not from a full-size display that gets shrunk down to 1920 by 1080 in the export.
The reason is simple. When the capture is composed at the size you’ll deliver, every pixel in the frame is used. When a large display is scaled down, each label on the screen is averaged with its neighbors, and thin text loses its edges. Small type is the first thing to go soft, and it’s what viewers struggle to read.
Here’s a rule of thumb that holds up across most recordings. Choose one output size for the whole series, and keep the window at that size every time. A consistent window is also what lets a viewer who watched one video find the controls in the next one without searching.
2. Set display scaling and browser zoom together
Display scaling, the setting that makes text bigger on high-resolution screens, and browser zoom, the setting that makes a web page bigger, both change how large the interface looks in your recording. If you set one without the other, you can end up with a page where the text is too small to read or the layout is so cramped the controls overlap.
Pick a combination you like and stick to it. A common starting point is 125 percent display scaling with the browser at 100 percent, or the browser at 110 to 125 percent on a standard display. Test it on a short clip and look at the smallest label. If you need to squint at a settings menu in the test, the viewer will squint too.
The reason to set these before recording, rather than adjusting them mid-session, is that changing them changes the capture, and a changed capture shows up as a jump in the finished video. The warning later in this piece covers that in more detail.
3. Clear the layer that gets recorded
Whatever is on your screen gets recorded, including things you forgot were there. Notifications, the dock or taskbar, a chat window in the corner, a password manager prompt, the bookmarks bar and a tab with an unrelated name all appear in the frame if they’re visible.
Before every serious take, turn on focus mode or Do Not Disturb, quit anything that sends notifications, hide the bookmarks bar, and close tabs you don’t need. On macOS, auto-hiding the dock removes a constant distraction from the bottom edge of the frame. On Windows, the same kind of cleanup applies to the taskbar and system tray. The goal is a frame where nothing competes with the thing you’re showing.
Check the corners of your test recording. The top-right corner is where a notification usually lands, and the bottom-left is where a chat popup tends to appear. Those are the two spots that cause the most embarrassing edits.
Choose the settings that shape the file
The next three tips concern the settings that determine how the file is encoded. They’re easy to leave at their defaults, and the defaults aren’t tuned for interface content.
4. Pick a frame rate for the content, not the default
Frame rate is the number of images captured per second. For most software demos, 30 frames per second is plenty. Interface content changes slowly: a page loads, a button is clicked, a panel slides in. Sixty frames per second helps when motion is the point, such as a smooth scroll or an animation you want viewers to see clearly, but it’s rarely needed for a normal tutorial.
Higher frame rates produce larger files for the same visual quality, and larger files are harder to upload, slower to load on the viewer’s side and more likely to stutter on a busy machine during recording. If your recorder drops frames during a take, lowering the frame rate is often the fastest fix.
Choose 30 by default, and move to 60 only when a specific motion needs it. Then make the same choice for the whole series, so the playback feels consistent from one video to the next.
5. Keep the bitrate high enough for small text
Bitrate is how much data the encoder spends on each second of video, and it’s the setting most responsible for whether small text stays sharp. Interface content is hard to compress. It has long straight edges, flat colors and fine type, and a low bitrate smears those edges into blur that looks like soft focus.
When text looks fuzzy in the export, raise the bitrate before you change anything else. You’re looking for the point where the smallest label is crisp at the size viewers will watch it. That point varies with the output size and the density of the interface, so test it. A dense admin screen with small type needs more bitrate than a landing page with large headings.
The trade-off is file size. Keep the bitrate as low as you can while keeping small text readable, and test the result on the device your viewers are most likely to use.
6. Make the cursor readable on your theme
The cursor is the viewer’s guide. If they can’t see it, they can’t follow the click. Default cursors are designed for light backgrounds, and a dark-mode interface can swallow a small black arrow. Some applications also use a cursor that’s the same color as the selection highlight, which makes it disappear the moment you click.
Test the cursor on the theme you’re recording, at the size you’re delivering. If it’s hard to see in the test clip, enlarge it or add a cursor effect that makes it stand out, such as a subtle highlight ring. The cursor should be the easiest thing in the frame to find, especially at the moment of a click, because that’s where the viewer’s attention needs to go.
Control what the viewer sees while you record
These next two tips are about what happens on screen during the take, which is the part of the recording that’s easiest to change without touching any settings.
7. Pause between actions so the zoom and transitions read
Viewers need a fraction of a second to notice a change. When you click and immediately move to the next control, the viewer’s eye is still on the previous one, and the next step arrives before they’ve processed the last. A pause of about one second after each meaningful click gives the frame time to settle, and it gives any automatic zoom time to land on the right area.
This is also the easiest habit to build. Count to one in your head after each result before you move. The recording will feel slower to you in the moment, and it will feel clear to everyone who watches it.
Avoid rushing the cursor across the screen. A fast, long movement is hard to follow and can make the viewer lose the cursor entirely. Move it deliberately toward the control, pause over it, and click.
8. Keep important content away from the frame edges
Anything near the edge of the frame risks being cut off, covered by a player control or hidden by an overlay the viewer’s device adds. A button at the very bottom of the screen might end up under the progress bar. A status message in the corner might be hidden by a chat bubble or a caption.
Keep the important parts of the interface in the central area of the frame, with a margin around the edges. Check the test export at the edges, not just the center. If a control you need to show sits at the border, move the window, or zoom so the control is comfortably inside the frame.
Protect the take
The final two tips are about protecting your work during the recording and checking it afterward. These are the habits that turn a bad take into a quick fix.
9. Record in short takes with a clear stopping point
Long takes are hard to recover. A stumble in minute twelve of a single recording means re-recording the whole thing or trying to cut around the mistake in an editor. Short takes, each covering one step or one small sequence, are much easier to redo. A stumble costs you one take, not the whole session.
Give each take a clear start and end. Begin with a moment of stillness, the cursor resting in a neutral place, so the first frame is clean. End with the result on screen for a beat before you stop. That gives you clean material to cut from and makes the joins between takes invisible.
10. Check the export on two screens
The test that matters is the one you watch at the size and speed your viewers will use. Play the export at normal speed, not fast-forward, on a phone and on a laptop. On the phone, check whether the smallest text is readable without zooming. On the laptop, check whether the cursor and the zoom behave as you intended.
If you find a problem, fix it at its source. Blurry text is usually a bitrate or window-size issue. A missing cursor is a theme or cursor setting. A stuttering playback is often a frame rate or a busy machine during the take. Fixing the cause means the next take won’t repeat the mistake.
Keep a settings note: write down the window size, scaling, zoom, frame rate and bitrate you used for each series. The next video in the series will look identical when you reuse those settings, and you won't have to rediscover them.
Clean up what you captured
11. Trim the last second and the first frame
The last second of a take is often the cursor drifting toward the stop control, and the first frame is sometimes a half-loaded page or a wrong window. Both are easy to trim and look sloppy when they’re left in. Cut the first frame so the video opens on a clean state, and cut the last second so it ends on the result rather than the exit.
This is a small edit that makes a large difference. Viewers notice the difference between a video that starts and ends cleanly and one that doesn’t, even if they can’t say why. For more on the editing work that follows capture, the guide to making tutorials people finish covers pacing and cuts in detail.
Before and after: what the settings change
The difference these tips make is easiest to see side by side. The diagram below compares a common setup with a deliberate one, using the same interface and the same content.
When something goes wrong during a take
Even with good setup, takes go wrong. A notification appears, the page freezes, the cursor misses a button. The right response is usually to stop, fix the one thing, and start that take again rather than pushing through. A recording with a visible glitch in the middle is harder to fix than a clean take you record a minute later.
Keep a note of what went wrong. If the same problem recurs across takes, such as a particular notification or a page that loads slowly, that’s a setup issue to fix once, not a per-take problem to work around every time.
Don't change display settings mid-recording: changing resolution, scaling or the window size during a take alters what's captured, and the file will show a visible jump at that point. Finish the take at the settings you started with, then adjust between takes.
The short version
Clean screen recordings come from decisions made before the first click. Match the window to the output and set scaling and zoom together. Clear the notifications and the clutter. Use 30 frames per second for most demos, raise the bitrate when small text smears, and make sure the cursor is visible on your theme. Pause after each action, keep important content away from the edges, record short takes, and check the export on a phone and a laptop before you publish.
Most of these habits are easier to keep when the recorder handles some of the work for you. RecordlyPro records in your browser with nothing to install, and adds auto-zoom on every click, cursor effects, captions and chapters, which covers the parts of this list that are otherwise manual. If you’re recording in Chrome specifically, the walkthrough on recording screen in Chrome covers the capture choices in more detail.
Keep reading
Async video: stop scheduling the meeting you could record
A hundred random links can do less than five relevant ones. Here's what makes a backlink pass real ranking value in 2026 — and what makes it worthless or worse.
Sofia Meyer
October 6, 20262 min readAuto-zoom in screen recordings: what it is and why your demos need it
A hundred random links can do less than five relevant ones. Here's what makes a backlink pass real ranking value in 2026 — and what makes it worthless or worse.
Sofia Meyer
October 13, 20262 min readHow to choose a screen recorder for product demos in 2026
A hundred random links can do less than five relevant ones. Here's what makes a backlink pass real ranking value in 2026 — and what makes it worthless or worse.
Sofia Meyer
October 16, 20262 min readDofollow vs nofollow in 2026: what still passes value
The link attributes changed, Google's treatment changed, and a lot of advice is out of date. Here's what dofollow, nofollow, sponsored and ugc actually do now.
The Recordly Team
October 10, 20262 min read