Free Screen Recorder

How It Works

1. Click Start Recording: Your browser will prompt you to select what to share, your entire screen, an application window, or a specific browser tab.
2. Record your content: Everything you do on screen is captured. Use the pause and stop controls to manage the recording.
3. Download the video: Click Stop when done and download your recording as a WebM video file directly from your browser.

Why Use Screen Recorder?

Screen recordings are essential for creating tutorials, reporting bugs, documenting software, recording presentations, and capturing screen content for review. Most screen recording tools require software installation, subscriptions, or upload your content to cloud servers. This browser-based recorder uses the Web Screen Capture API to record directly from your browser, no installation, no account, and your recordings stay on your device.

Features

• Screen, window, or tab capture: Choose to record your full screen, a specific app window, or a single browser tab.
• Microphone audio: Optionally include microphone audio for voiceover commentary.
• System audio: Capture tab audio along with the screen (when recording a browser tab).
• Pause and resume: Pause the recording mid-session without stopping the capture.
• Instant download: The recording is saved as a WebM file directly to your device, no cloud upload.

Frequently Asked Questions

What format are recordings saved in?

Recordings are saved as WebM (VP8/VP9 video, Opus audio), which is natively supported by Chrome, Firefox, and Edge. To convert to MP4 for broader compatibility, use the Video Converter tool.

Does this record what is on my second monitor?

When you select "Entire Screen" and have multiple monitors, you can choose which monitor to share from the browser's sharing dialog. Each monitor appears as a separate option.

Are my recordings private?

Yes. The recording is captured using the browser's Screen Capture API and processed entirely locally. The video data is never transmitted to any server, it downloads directly to your device.

What a browser screen recorder actually does

A screen recorder captures what is on your screen as a video file, so you can replay it later, share it, or edit it into a tutorial. Traditional screen recorders are desktop apps you install (OBS Studio, Camtasia, ScreenFlow, QuickTime) which have full access to the operating system's graphics pipeline. A browser-based screen recorder is different: it uses the Screen Capture API introduced in 2017, which lets a webpage ask the operating system "please share your screen, a window, or a browser tab with me." The user explicitly picks what to share through a system dialog the browser cannot bypass, then the page receives the video stream and encodes it to a downloadable file in real time. No install, no admin permissions, and no service to upload to.

The trade-off versus desktop apps is power versus convenience. Desktop tools record multiple sources at once (screen + webcam + microphone + system audio + separate audio tracks), add real-time effects, support advanced codecs, and let you live-stream to YouTube, Twitch, or RTMP servers. A browser recorder records a single screen source, optionally with system audio + microphone, into a single WebM file. For a 30-second bug reproduction video, a 2-minute tutorial clip, or an async standup update, the browser tool is faster from "I want to record" to "I have a file" than any installed app. For full content production, dedicated software wins.

Privacy is the secondary appeal. Cloud-based screen recorders like Loom upload your video to their servers automatically, where it is hosted, processed for AI features, and accessible to anyone with the link. For confidential recordings (proprietary code, internal bug reproductions, family content) this is unacceptable. A browser recorder that runs entirely client-side and produces a local download has different privacy properties: nothing leaves your machine unless you choose to upload the resulting file somewhere yourself. For users handling sensitive content, that distinction is meaningful.

How this tool works under the hood

The recording process begins with navigator.mediaDevices.getDisplayMedia(), the standardized browser API for screen capture. Calling it triggers the browser's native sharing dialog where you choose Entire Screen, Application Window, or Browser Tab. If you tick "Record Audio," the call also requests system audio (on supported browsers) and a microphone permission. The returned MediaStream object contains video and audio tracks identical to what a webcam would produce, except the source is your display.

The stream is passed to a MediaRecorder, a built-in browser encoder that compresses raw video frames into a streaming container format in real time. The output container is WebM, an open format using VP8, VP9, or AV1 for video and Opus for audio. The browser picks the codec based on its capabilities; modern Chrome and Firefox typically choose VP9 (better compression than VP8) or AV1 (better still, slightly higher CPU). Each "chunk" of encoded video (typically 1 second at a time) accumulates into an in-memory Blob until you press Stop.

When you stop recording, the script concatenates the chunks into a final Blob, creates an object URL pointing to that blob, and triggers a synthetic download click. The resulting WebM file lives in your browser's memory until you download it; refresh the page and the recording is gone. The tool never makes a network request with your video data; the only network activity during recording is whatever your operating system normally does, and the only thing the recording itself produces is a local file. WebM plays directly in Chrome, Firefox, and Edge; for compatibility with iMovie, Premiere, or other editors that prefer MP4, run the file through a converter like FFmpeg (also free) or our Video Converter tool.

Brief history of screen recording

• Lotus ScreenCam, 1992. One of the first commercial screen recording tools, designed primarily for software training. ScreenCam files were a proprietary format only viewable in their own player. Lotus eventually discontinues it as competitors emerge with more accessible formats.
• Camtasia Studio, 2002. TechSmith releases Camtasia for Windows, combining screen recording with built-in editing. Becomes the industry standard for instructional designers, corporate training, and online course creators throughout the 2000s. Pricing of $300+ keeps it out of reach for casual users.
• QuickTime Player ships with screen recording, 2009. Apple adds a free screen recorder to QuickTime Player in macOS 10.6 Snow Leopard. Suddenly every Mac user has a serviceable screen recorder at no cost. Windows users still rely on third-party tools.
• OBS Studio, 2012. Hugh "Jim" Bailey releases Open Broadcaster Software as a free open-source project. Originally built for game streamers, OBS becomes the dominant free recording and live-streaming tool by 2015. Powers most YouTube and Twitch streams, replaces Camtasia for many content creators.
• Screen Capture API in browsers, 2017. The W3C Screen Capture API specification reaches Chrome 72 and Firefox 66 with widespread support across desktop browsers by 2019. For the first time, a webpage can record the screen without any plugin, install, or extension; user permission is required per session through a browser-native picker.
• Loom and cloud screen recording, mid-2010s. Loom (founded 2015) builds a multi-billion-dollar business around cloud-hosted screen recording for async work. Records via browser extension, uploads automatically, generates shareable links. Acquired by Atlassian in 2023 for $975 million. Browser-based screen recording tools (like this one) emerge alongside as privacy-focused alternatives.

Real-world workflows

• Bug reproduction videos. When reporting a bug to support or a developer, a 30 to 60 second screen recording with audio narration is dramatically more useful than a text description. Show the steps, capture the error message, narrate your expectations versus what happened. Engineers can reproduce 10x faster with video than with a bug report that says "the button doesn't work sometimes."
• Short tutorials and how-to clips. Show a colleague how to use a feature, explain a workflow to a new team member, demonstrate a tip on social media. Browser-based recording is fast enough to capture spontaneous "here, let me show you" moments without setting up software. For polished tutorials, switch to dedicated tools with editing; for ad-hoc explanations, the browser is fine.
• Async standups and updates. Distributed teams increasingly replace scheduled standup meetings with async video updates. Record a 2 to 4 minute walkthrough of yesterday's progress, today's plans, and any blockers. Team members watch on their schedule. Reduces meeting load and timezone friction. Browser tools let you record without leaving the project context.
• Virtual classroom recordings. Teachers record lectures, demonstrations, and screen-shared activities for students who missed class or need to review. With LMS uploads supported by most school systems, screen recordings become permanent resources. Browser-based tools work on Chromebooks, the dominant K-12 device class, without admin install permissions.
• Gaming highlights and clips. Capture short clips of in-browser games, demo reels, or browser-based development showcases. For full streaming and high-frame-rate gaming capture, OBS Studio is dramatically better; for one-off browser-game clips, the built-in browser tool is sufficient and faster.
• Customer support recordings. Support agents record walkthroughs answering specific customer questions, then share the recording for the customer to follow at their own pace. Better than long email chains for visual steps. Customer can pause, rewind, and re-watch indefinitely. Reduces repeat support tickets when the recording covers a common question that other customers will also have.

Common pitfalls and what they mean

• System audio capture is browser-dependent. Chrome and Edge can capture system audio (the sound coming from your computer's speakers) when you choose "Entire Screen" or "Browser Tab." Firefox does not support system audio capture at all. Safari supports tab audio but not full-screen audio. If your recording is silent when you expected sound, try Chrome and select "Share tab audio" in the picker.
• File sizes scale fast. A 1080p screen recording at 30 fps with VP9 encoding produces roughly 8 to 15 MB per minute, depending on motion complexity. A 10-minute recording is 80 to 150 MB. For typical 1- to 5-minute clips this is fine; for hour-long recordings, expect files in the 500 MB to 1 GB range. Encode at 720p for smaller files if you don't need 1080p detail.
• Sharing the wrong screen reveals private content. The "Entire Screen" option shares everything visible on that monitor, including notifications that pop in, password prompts, and unrelated app windows. Before recording, close unrelated apps, turn off notifications (Focus / Do Not Disturb mode), and ideally use a single-monitor setup or pick "Application Window" or "Browser Tab" to restrict the capture scope. Sensitive content has been leaked in screen recordings many times.
• WebM compatibility outside browsers. WebM is well-supported in browsers but spotty elsewhere: iMovie does not import WebM, Premiere Pro requires plugins, many social-media platforms convert WebM to MP4 on upload (sometimes badly). For maximum compatibility, convert your WebM to MP4/H.264 after recording using FFmpeg, HandBrake, or our online Video Converter.
• Recording impacts performance. Real-time video encoding is CPU-intensive. On older laptops or low-power devices, you may see frame drops during recording, especially at 1080p 60 fps. Symptoms include choppy playback or visible stuttering in the recording even though your screen looks smooth in real time. Drop to 720p, close other apps, or use a more powerful machine for high-quality recordings.
• Pause behavior varies by browser. The MediaRecorder API includes a pause() method that suspends recording without ending the stream, but support is inconsistent: works in Chrome and Edge, partial in Firefox, missing in older browsers. If pause doesn't work, you can still stop and start a new recording, but the resulting files will be separate. Plan around this if you need pause-resume mid-recording.

Privacy: recordings never leave your device

Screen recordings are among the most sensitive content a person creates. They capture exactly what is visible: emails, code, internal documents, family members in webcam overlays, passwords in autofill, browsing history visible in tabs. Cloud-based recorders like Loom upload everything by default, with the company holding copies of your recordings on their servers, sometimes used for AI training depending on terms of service. Several high-profile leaks (corporate secrets, customer data) have occurred via cloud recording services where users did not realize the privacy implications.

This tool runs entirely client-side. The Screen Capture API requires explicit user permission per session, granted through a browser-native dialog the page cannot bypass or fake. The captured stream stays in browser memory, encoded by the local MediaRecorder, and ends up as a downloadable file on your machine. Open the browser's Network tab during recording: zero outbound requests. The resulting WebM file is yours to keep, share, or delete; if you never upload it, it never leaves your device. For confidential recordings (proprietary work, medical screen captures, legal evidence), this is the privacy property that matters.

When another tool is the right pick

• OBS Studio for streaming and multi-source recording. OBS Studio (free, open source) is the standard for live streaming to Twitch, YouTube, or Facebook, and for recordings that combine multiple sources (screen + webcam + microphone + game audio + commentary). It supports scene transitions, real-time filters, and broadcast-quality output. For any content that goes beyond a single-source quick recording, OBS is the right tool.
• Loom for async cloud collaboration. Loom is built for the workflow where you record a video, share a link, and your colleague watches with reactions and comments. The cloud storage, transcription, analytics, and team workspace are core features, not afterthoughts. For high-volume async video communication, Loom or a similar tool is faster than recording locally then uploading manually. Privacy tradeoff: your recordings live on Loom's servers.
• Native OS recorders for system integration. macOS Screen Recording (Shift+Cmd+5) and Windows Game Bar (Win+G) integrate deeply with the OS, support hardware-accelerated encoding, capture system audio reliably, and produce MP4 directly. For one-off recordings on your primary OS, the native tool is usually fastest. Browser tools matter when you need cross-platform consistency or work on managed devices where you cannot use native recorders.
• ScreenFlow or Camtasia for tutorial production. ScreenFlow (Mac, $169) and Camtasia (Windows/Mac, $300) are professional screen-recording-plus-editing tools designed for course creators, technical writers, and corporate training teams. They include zoom-and-pan, callout annotations, multi-track editing, and library asset management. For polished educational content, these tools justify their price; for ad-hoc or one-off clips, the browser tool is enough.

Other frequently asked questions

Why is my microphone audio not being captured?

The Screen Capture API does not directly include microphone audio; it captures the screen and optionally system audio. This tool requests microphone access separately via getUserMedia({audio: true}) and merges the two streams. If microphone audio is missing, check: (1) you granted microphone permission when prompted, (2) you selected the right microphone in your OS sound settings, (3) the microphone is not muted at the hardware level (many laptop mics have physical mute switches), and (4) you ticked "Record Audio" in the tool settings before starting.

Can I record my webcam in a picture-in-picture overlay?

Not in this tool. The Screen Capture API records the screen as-is; if you want a webcam overlay, the webcam preview needs to be visible on screen during recording (place it in a small window in the corner of your screen and record the whole screen). For professional picture-in-picture compositing, use OBS Studio (free) or ScreenFlow ($169), which support layered video tracks. The "PiP from API" approach is not possible in current browser screen-capture APIs.

Why is my recording lower quality than my screen?

Three common causes: (1) The quality setting is set to "Auto" which may default to 720p for performance; switch to 1080p Full HD for higher fidelity. (2) Your screen is a high-DPI display (Retina, 4K) but the recording captures at logical pixels, not physical, so a 4K screen captures at 1920x1080 even at "1080p" setting. (3) CPU bottleneck causes the encoder to drop quality to maintain frame rate; close other apps. For pixel-perfect captures of high-resolution screens, use a dedicated recorder.

How long can I record for?

There is no hard time limit in the Screen Capture API itself, but practical limits exist: (1) Browser memory must hold the in-progress recording, so very long recordings (multiple hours) on low-memory devices can fail. (2) File size grows linearly: 1 hour of 1080p is roughly 500 MB to 1 GB. (3) Some browsers have soft limits where memory pressure causes the recording to stop unexpectedly. For recordings longer than 30 minutes, dedicated desktop apps are more reliable.

Can I record on iPhone or iPad?

No. Apple does not support the Screen Capture API on iOS Safari (a long-standing platform restriction). For iOS screen recording, use the native iOS Screen Recording feature: Settings > Control Center > add Screen Recording, then swipe to access the Control Center and tap the record button. iOS native recordings save to Photos as MP4 (MOV container with H.264). For iPad, the same applies.

How do I edit the recording?

After downloading, the WebM file can be edited in any video editor that supports WebM (DaVinci Resolve free, Kdenlive free, ShotCut free). For editors that prefer MP4 (iMovie, older Premiere), convert with our Video Converter or with FFmpeg using the command ffmpeg -i input.webm -c:v libx264 output.mp4. For trimming start and end only, our Video Trimmer tool works directly on WebM without conversion.

Related Tools