Record your screen, a window or a browser tab — with your mic and tab audio — right here in your browser. Trim and crop the result, then download. Nothing is uploaded.
Recording in progress — switch to whatever you're capturing. Come back here (or use the browser's "Stop sharing" bar) to finish.
Drag the handles to set the start and end of your clip. Click the timeline to preview.
Drag handles or drag inside the box to move. The shaded area will be removed.
Rendering edited video…
🔒 The recording is captured and saved by your own browser — it never touches a server.
Drag two handles to cut the start and end of your clip. Preview instantly, export when it's right.
Draw a crop box over your recording to focus on what matters — free crop or locked aspect ratios.
Everything happens on your device. No server, no upload, no account. Sensitive screens stay private.
Screen recording in a browser uses the Screen Capture API, which requires an explicit user gesture and shows a picker offering the whole screen, a specific window, or a single browser tab. This permission model is deliberate: a page cannot start recording silently, and the browser displays an indicator while capture is active.
The three scopes differ in ways worth knowing. Capturing a tab records only that tab's content and follows it, so notifications and other windows never intrude — the safest choice for a demonstration. Capturing a window records that application only, and capturing the entire screen records everything, including anything that appears unexpectedly.
Audio capture is more constrained. System audio can generally be captured when sharing a whole screen or a Chrome tab, but not when sharing a window, and support varies by browser and operating system — on macOS, system audio capture is more limited than on Windows. Microphone audio is a separate stream and needs its own permission.
Screen content is unlike camera footage: it is mostly static, with sharp text edges and flat colour. That means frame rate matters less and resolution matters more. Recording at 30 frames per second is ample for most demonstrations, and 60 is worth it only for genuinely smooth motion such as animation or gameplay.
Resolution should match the display rather than be scaled. Recording a high-density screen and exporting at half size makes small text unreadable, and enlarging afterwards makes it worse. If the recording will be viewed in a small embedded player, the answer is to increase the interface's font size or zoom level before recording, not to enlarge afterwards.
Bitrate governs whether text stays crisp. Video codecs are tuned for photographic content and discard exactly the high-frequency detail that text is made of, producing the shimmer around characters familiar from poor screen recordings. A generous bitrate, and where available a codec setting favouring detail over motion, addresses it.
Screen recordings disclose far more than intended with striking regularity. Notification banners arriving mid-recording have exposed private messages, browser tabs have revealed unrelated work, bookmark bars have shown internal tool names, and autocomplete dropdowns have displayed previously entered addresses and search terms.
Before recording: enable do-not-disturb, close unrelated tabs and applications, hide the bookmark bar, sign out of or switch to a clean profile, and clear anything on screen you would not publish. Recording a single tab rather than the whole screen eliminates most of these at once.
Watch the content itself too. API keys in a terminal, tokens in a URL, email addresses in a test account, and real customer data in a demonstration environment are all common leaks — and unlike a screenshot, a recording exposes everything that appears at any moment, including things visible only briefly. Review the finished recording before publishing, since that is the only way to catch what appeared for half a second.
Really. The recording is made by your own browser with the built-in MediaRecorder — there's no server in the loop to impose limits or stamp watermarks.
After recording, drag the two handles on the timeline to set where your clip starts and ends. Switch to the Crop tab to draw a region — only that area will appear in the exported video. Click "Export edited" and the browser re-renders the clip in real time, then downloads the result.
Keep "Tab / system audio" on, and when the share dialog opens pick a browser tab and enable "Also share tab audio". On Windows, sharing your entire screen can capture system audio too. macOS only exposes tab audio.
Chrome, Edge and Firefox save WebM (VP9/VP8). Safari saves MP4. Both upload fine to YouTube, Google Drive, Slack and most editors. If an app insists on MP4, any free converter can transcode WebM instantly.
Mobile browsers don't allow web pages to capture the screen. Use your phone's built-in recorder (iOS Control Center, or the Android quick-settings tile) — on a laptop or desktop this tool does it all.
Video codecs discard the high-frequency detail that text is made of. Record at the display's native resolution rather than scaling, raise the bitrate, and increase the interface font size before recording rather than enlarging afterwards.
Sometimes. It is generally available when sharing a whole screen or a browser tab, but not a single window, and support varies by browser and operating system. Microphone audio is a separate permission.