Everything you need to know — from choosing the right tool and setting up your recording to delivering a polished result and sharing it effectively.
Screen recording is the process of capturing everything that appears on your display as a video file. You press record, do something on your computer, press stop, and you have a video of exactly what happened on screen — optionally with your voice narrating over the top of it.
The resulting file can be shared with a colleague, uploaded to a platform, attached to a support ticket, embedded in documentation, or kept as a personal reference. It's one of those capabilities that sounds simple but turns out to be genuinely useful in dozens of different situations once you start using it.
Screen recording is distinct from screenshotting (which captures a single still frame) and from streaming (which broadcasts live to an audience in real time). A screen recording is a local file you control, made at your convenience, watched at the viewer's convenience.
Under the hood, screen recording works by capturing frames from your display at a regular interval — typically 24 to 60 frames per second — and encoding them into a video file. The encoder compresses the frames using a codec (VP8, VP9, H.264, or HEVC/H.265 are the most common) to keep file sizes manageable without sacrificing too much visual quality.
Audio is captured separately — either from your microphone, from the system's audio output, or from a specific application — and mixed into the video file during encoding.
Modern browsers expose a Screen Capture API that lets web applications request access to your display, a specific window, or a browser tab. When you grant permission, the browser captures the pixels from whatever you selected and streams them to the web app, which encodes them using the browser's built-in MediaRecorder API. The result is a video file that the browser downloads to your device.
This approach has meaningful advantages over traditional desktop software: nothing is installed, the recording never leaves your computer (unless you upload it), and the permission model is controlled by the browser rather than by a third-party app with full system access.
Native recording applications (like OBS Studio, QuickTime, or Camtasia) work at the OS level, capturing frames directly from the graphics output. This gives them more flexibility — they can capture system audio, record at higher frame rates, and access hardware encoding — but it comes with more setup, more system permissions, and more complexity.
For most screen recordings — software demos, bug reports, walkthroughs — 30 frames per second (fps) is more than sufficient. 60fps is worth considering only if you're recording fast-moving content like games or animation, where motion blur at 30fps becomes noticeable. Higher frame rates increase file size without adding much for typical screen content.
Resolution matters more. Recording at your native display resolution produces the sharpest result. If file size is a concern, 1080p (1920×1080) is the sweet spot — readable on any device, reasonable file size, universally supported by every video platform.
There are four main categories of screen recording tools. The right one depends on what you're recording, how often, and what you plan to do with the result.
Best for: Quick recordings, one-off use, anyone who doesn't want to install software.
Browser-based recorders run entirely in your browser tab. You open the page, click record, share your screen, and download the file. Nothing is installed. Your recording stays on your device. There's no account required and typically no watermark on tools that are genuinely free.
The trade-off is that browser-based recorders can't capture system audio on macOS (a macOS restriction, not a tool limitation) and don't support advanced features like picture-in-picture webcam overlays, built-in editing, or real-time annotations. For straightforward recordings they're the fastest and least complicated option.
Best for: Quick recordings on a device that already has what you need.
macOS includes QuickTime Player (File → New Screen Recording) and the Screenshot toolbar (Cmd+Shift+5). Both are free and require no setup beyond granting screen recording permission once. QuickTime saves .mov files and records full screen or a selected region. It doesn't support tab-only capture or easy mic+system audio mixing.
Windows 10 and 11 include Xbox Game Bar (Win+G), which records the currently active application window. It doesn't record the desktop itself or capture a single browser tab in isolation. For most software-demo use cases it works, but the limitation on what it can target is a real constraint.
ChromeOS has a built-in screen recorder accessible from the system tray. It's simple, no-install, and handles full screen, window, and partial-screen recording.
Best for: Regular recording, streaming, advanced editing, or high-frame-rate gaming capture.
OBS Studio is the most powerful free option. It's open source, supports full scene composition (multiple sources, webcam, overlays), hardware encoding, and can both record and stream simultaneously. The learning curve is steep compared to simpler tools, but for anyone who records regularly, it's worth the investment.
Camtasia and ScreenFlow (Mac only) are paid tools that bundle a recording interface with a built-in video editor. If you produce polished tutorial content and want editing tools that understand screen recording (like zoom-and-pan, cursor highlighting, and callouts), they're worth the cost.
Loom is a cloud-based option — it records locally but uploads automatically and hosts the video for you. Useful if you want sharable links rather than files, but the free tier has a 5-minute cap and watermarks, and your recordings live on Loom's servers rather than your device.
Best for: Recording game consoles, external devices, or content that requires capturing an HDMI signal.
Capture cards (like those made by Elgato or AVerMedia) sit between a video source (a console, a camera, an external display) and your computer. They're not relevant for standard computer screen recording but are the only option for recording a PlayStation, Xbox, or Nintendo Switch.
Every screen recorder offers at least one capture mode. Most offer several. Understanding the difference matters — the wrong mode captures too much (or the wrong thing entirely).
Captures everything on your display — your wallpaper, all open windows, your taskbar or Dock, notifications, everything. Use this when you need to show context across multiple applications, or when you're demonstrating a workflow that spans several windows.
The downside: it captures everything. If you have unrelated tabs, personal notifications, or cluttered windows you don't want visible, they'll be in the recording. Always clean up your screen before recording full screen.
Captures a single application window, cropped to exactly that window's boundaries. The background isn't captured — if the window is partially obscured by another window when you switch to it, the recording updates to show the full window again.
Window capture is ideal when you're demonstrating one piece of software and don't want anything else in the frame. It also means you can keep other windows open without worrying about them appearing in the recording.
Available in browser-based recorders and some desktop tools. Captures a single browser tab — including the tab's audio in Chrome and Edge — with no other content in the recording. The video shows exactly what's in that tab, regardless of what's behind it.
Tab capture is the cleanest option for recording web applications, demos of browser-based tools, or any workflow that takes place entirely in the browser. It's also how the region clipper works — tab capture is a prerequisite for cropping down to a specific section of the page.
Some tools let you draw a rectangle on screen and record only that area. Useful for recording a specific part of your screen — a chart, a modal, a sidebar — without capturing the full window or display. Browser-based region recording (like the clipper at /clipping/) works by capturing a tab and then cropping the output in real time using canvas rendering.
Video without audio is surprisingly hard to follow. A recording where someone narrates what they're doing — "I'm going to click Settings, then scroll down to the Notifications section" — is dramatically easier to understand than the same recording in silence. Audio is almost always worth including.
The most universally available audio option. When you enable mic recording, your voice is captured alongside the screen content. This works on every operating system and every recording tool.
Mic quality matters more than most people realize. The built-in microphone on a laptop picks up keyboard noise, fan noise, and room echo. A USB headset or a dedicated USB microphone dramatically improves audio quality for minimal cost. If you record regularly, a $50 microphone will improve your output more than most other investments.
System audio is the sound that applications on your computer are playing — video playback, notification sounds, music, app effects. Capturing it is easy on Windows (most recorders support it out of the box) and complicated on macOS.
On Windows, Chrome and Edge can capture tab audio automatically when you share a tab. For full-screen or window recordings, tools like OBS can route system audio into the recording directly.
On macOS, the OS doesn't allow applications to tap the system audio output by default. To capture system audio on Mac, you need a virtual audio driver — BlackHole (free) and Loopback (paid) are the two most popular options. Both route system audio through a virtual device that recording software can access. For most screen recording use cases (bug reports, walkthroughs, async updates), this is overkill — mic audio is sufficient.
When you share a browser tab using Chrome or Edge's screen share dialog, those browsers automatically include the tab's audio in the capture. This means if you're recording a web app that plays sounds, or a video embedded in a web page, that audio comes through without any extra configuration. Firefox does not include tab audio in tab capture.
Five minutes of preparation before you record saves twenty minutes of re-recording after. Most bad screen recordings are the result of not doing a few simple things before hitting go.
Close tabs, windows, and applications you won't use in the recording. Clutter on screen distracts viewers and risks accidentally capturing private information — a personal email, a notification, a calendar event that's nobody's business.
If you're recording full screen, consider using a clean browser profile or a guest profile with no bookmarks bar, no autofill, and no saved history. On macOS, you can enable Do Not Disturb before recording to suppress notifications. On Windows 11, Focus Assist does the same thing.
If you're recording a specific resolution (say, to produce a 1080p output), set your display to that resolution before you start. Recording at a higher resolution and scaling down is fine, but recording at a lower resolution and scaling up produces a blurry result.
Scan your screen for anything you don't want recorded: personal email addresses in the browser bar, sensitive documents in the Dock or taskbar, calendar items visible in a widget. It's easier to hide them before recording than to blur them in editing after.
For anything over two minutes, do a dry run first. Not a full recording — just mentally walk through the steps you'll take. Know where you're going before you start moving. The most common cause of meandering recordings is the presenter discovering mid-recording that they're not sure what to click next.
If you're recording audio, do a 10-second test recording and listen to it before your real recording. Confirm the mic is selected, the gain level is reasonable (not too quiet, not clipping), and there's no unexpected background noise. This takes 30 seconds and prevents starting a 15-minute recording only to find out your mic was muted.
Before you do anything on screen, say one sentence that tells the viewer exactly what they're about to see. "I'm going to show you the checkout flow bug that appears when you apply a coupon code on mobile." Now the viewer knows what to watch for, and they won't spend the first minute trying to figure out what the recording is about.
Your cursor is visible in the recording. Use it deliberately. When you're talking about something on screen, move your cursor to it and park it there. Don't let it wander. A cursor that drifts randomly across the screen while you're talking about something else is one of the most common distractions in screen recordings.
Some recorders let you highlight the cursor or add a click effect. If your tool supports it, enable it — it makes it easier for viewers to follow where you're clicking, especially in recordings that will be watched at a smaller size.
Say what you're doing, not just what you're looking at. "I'm clicking the Settings icon in the top right" is more useful than "here's the settings icon." The first tells the viewer what's happening and what to watch for. The second is just describing what they can already see.
When you're about to navigate to a new page, open a new application, or start a new section, give a deliberate half-second pause before you do it. This gives the viewer time to catch up and signals that something new is coming. It also makes the recording easier to skim — transitions become natural chapter markers.
If you're recording at full screen and need to draw attention to something small — a field, a button, a value in a table — zoom in using your OS's accessibility zoom (Ctrl+scroll on Windows, Cmd+Option+= on Mac) or your browser's zoom (Ctrl/Cmd + plus). Viewers watching your recording at reduced size won't be able to read small text. Zoom in, show the thing, zoom back out.
If you make a mistake — click the wrong thing, say the wrong word, navigate somewhere you didn't mean to — don't panic and try to cover for it. Either stop and re-record, or just keep going and let the mistake be. Trying to explain a mistake mid-recording ("wait, that's wrong, let me go back...") is usually more disorienting for the viewer than the mistake itself.
Don't trail off. End with a clear closing sentence — "That's everything, let me know if you have questions" or "So that's how the flow works end to end" — before you click stop. Recordings that just cut off abruptly feel unfinished, even if the content was complete.
The goal is to give the developer everything they need to reproduce and understand the bug without a single back-and-forth. Cover: where you are in the app, the exact steps to reproduce, what happens, and what you expected to happen. Mention your browser and OS out loud. Keep it under two minutes — a focused bug report is more useful than a comprehensive one.
→ More on screen-recorded bug reports
New users need to see the software in action, not read about it. A 3–5 minute walkthrough covering the core workflow — from login through first value — is more effective than a written tutorial of the same material. Use tab capture to isolate just the application. Go slowly and narrate every action explicitly, because first-time users don't know what to expect next.
→ More on screen-recorded walkthroughs
Written feedback is slow and ambiguous. "The header feels off" tells a designer nothing. Recording yourself talking through a design — "the header feels cramped here because the logo and nav are fighting for space, I'd try giving the nav more breathing room on the right" — communicates the same feedback in a third of the time and with zero ambiguity about what you mean.
→ More on async screen feedback
Tutorial recordings are produced, not captured. They're planned, rehearsed, and often re-recorded. Unlike bug reports or async feedback (which are one-off), tutorials will be watched by many people over time — so the investment in quality pays off more. Write a loose script, do a dry run, record, watch it back, and re-record anything that's confusing. Keep chapters short — under 5 minutes per concept — and structure the content so viewers can jump to the section they need.
A 2-minute recording showing what you shipped this week communicates more than a written update and takes less time than a status meeting. Show the actual thing — the dashboard, the code, the design — and narrate what changed and what's next. Viewers can watch at their own pace and skip to the relevant part.
→ Why async video is replacing the status update meeting
Recorded QA sessions serve as documentation of what was tested and what was found. Record as you test — narrate each step, call out any unexpected behavior, and note your environment. If something looks wrong but you're not sure it's a bug, a recording is better than a screenshot because it shows the sequence of events that led to the state.
→ More on screen recording for QA
Recorded demos are evergreen sales assets. A live demo requires scheduling, depends on internet reliability, and can only be watched once. A recorded demo can be watched on demand, shared in a sales email, embedded on a landing page, and re-used indefinitely. Keep the focus on outcomes, not features — show the viewer what they can accomplish with your product, not a comprehensive tour of every setting.
→ More on recording product demos
.mp4 (H.264) is the most universally compatible video format. It plays in every browser, every media player, every phone, and uploads to every video platform. If you need one format that works everywhere, it's MP4. The trade-off is that H.264 encoding is patented, though this doesn't affect the viewer at all.
.webm (VP8/VP9) is the format produced by browser-based recorders. It's an open format that plays in all modern browsers and most desktop media players. File sizes are similar to or smaller than equivalent MP4 files at the same quality. If you need to share via email or upload to a platform that requires MP4, you can convert .webm to .mp4 quickly using HandBrake (free, all platforms) or via an online converter.
.mov is the default format for QuickTime on Mac. It plays natively on Apple devices and in QuickTime Player, but requires QuickTime installed on Windows and isn't universally supported by web platforms. Convert to MP4 before sharing outside an all-Apple environment.
The right sharing method depends on the context and the audience.
If your recording is large and you're sharing via a method with size limits, HandBrake can reduce file size significantly. Use the "Fast 1080p30" preset as a starting point — it produces an MP4 that's universally compatible and about half the size of an uncompressed recording without visible quality loss for typical screen content.
Frame drops during recording usually mean your computer is under too much load. Try: closing background applications before recording, lowering the target frame rate to 24fps or 30fps if your tool allows, and closing browser tabs you're not using. If you're recording at high resolution, try reducing your display scaling.
First, confirm the mic was selected and enabled before you started recording — not after. Check that your browser (for browser-based recording) or your recording app has microphone permission in your OS settings. On Mac: System Settings → Privacy & Security → Microphone. On Windows: Settings → Privacy → Microphone. Make sure the correct microphone is selected if you have more than one audio input device.
Browser-based recorders capture at your display's resolution by default. If the output looks blurry, check that your display scaling isn't set unusually low. For browser-based tools, try recording a full browser tab rather than full screen, as the tab capture sometimes produces sharper output on high-DPI displays. If you're on a Retina Mac, the recorded video should be crisp at 1080p or higher.
Window capture records the selected window even when it's not in focus, but some recorders show a black frame if the window is minimized or fully obscured. The fix: keep your target window visible on screen during recording (even if it's behind other windows). Alternatively, use tab capture if you're recording a browser-based application — tab capture is completely immune to window positioning.
For .webm files from browser-based recording, convert to MP4 using HandBrake and select the "Fast 1080p30" preset. A 5-minute .webm at 1080p is typically 150–400MB; the HandBrake output is usually 50–150MB for the same content. For even smaller files, reduce the constant quality (RF) value in HandBrake — increasing it from 22 to 28 can halve file size with minimal visible quality loss for screen content.
If you're using a browser-based recorder, the file is local on your device — just delete it. If you uploaded it somewhere, delete it from the platform. For the future: close sensitive windows before recording, use Do Not Disturb to suppress notifications, and do a quick scan of your screen before you click record.
Screen recording is the process of capturing everything that appears on your display as a video file. The resulting file can be shared, uploaded, or kept as a reference. Modern screen recorders can also capture audio from your microphone or from applications playing on your computer.
It depends on your needs. For quick, no-install recordings with no watermark, browser-based recorders work well — Record Your Screen Free runs in your browser with no account or download required. For advanced features like scene composition and streaming, OBS Studio is the most powerful free option. For Mac users, QuickTime is built in and free for basic use.
Enable the microphone option before you click record. In most browser-based recorders, this is a toggle on the main interface. When sharing a browser tab in Chrome or Edge, the tab's audio is also captured automatically alongside your mic if you enable it.
MP4 (H.264) is the most universally compatible format for sharing and uploading. WebM is a good open alternative produced by browser-based recorders — it plays in all modern browsers and can be converted to MP4 in HandBrake in seconds.
When the screen share dialog appears, switch from "Entire Screen" to "Window" to select a specific application, or "Tab" to capture a single browser tab. Tab capture is the cleanest option for recording web applications — it shows only that tab's content with nothing else in the frame.
Most screen recordings are longer than they need to be and harder to follow than they should be. Here's how to fix that.
Read more →Teams are ditching weekly syncs in favor of short screen recordings. Here's why it works and how to make the switch.
Read more →Free, no account, no watermark, no time limit.
Start Recording Free