Screen Recorder

A desktop browser can already do it. Chrome, Edge and Firefox expose a screen capture API to any page, and that is what this one uses — no download, no extension, no account. The trade is that it is desktop only: mobile browsers do not offer screen capture to a web page, and rather than failing halfway this page says outright that recording is not supported and points you at a desktop browser. Your operating system still has a say. On macOS the browser itself needs Screen Recording permission under Privacy and Security before the picker will show anything beyond its own windows, and the first attempt often comes back empty until you grant it and restart the browser.

Because two different sounds are involved and only one of them is yours to switch on here. Your voice comes from the microphone, and the box for it has to be ticked before you start — it is locked once recording begins. The sound the computer is making is asked for at the same time as the picture, but whether any arrives is decided in the browser's share dialogue rather than on this page. Sharing a single Chrome tab usually offers a share tab audio checkbox that is not ticked by default; sharing a whole screen often has no such option, and on macOS browsers generally cannot take system audio at all without an extra audio driver. If the sound you want is playing in a tab, share the tab.

You need a converter, because nothing here does it — the file comes out as WebM and that is what browsers record. WebM plays in any browser, in VLC and in most video editors, so a lot of the time no conversion is needed. It stumbles elsewhere: the Mac preview pane, slide decks, older phones and upload forms with a strict format list. VLC can do the job through its convert and save option, HandBrake handles it with a preset, and on the command line ffmpeg -i recording.webm -c:v libx264 -c:a aac out.mp4 covers it. Re-encoding costs a generation of quality, which on flat screen content is close to invisible.

Not from this page. The encoder writes into an array inside the tab, those pieces are joined into one file in memory when you stop, and both the preview player and the download link point at that in-memory copy — there is no upload step and no peer connection anywhere in the component. Every captured track is stopped the instant you press Stop, which is what clears the browser's sharing indicator. Two practical notes. The file is not stored, so download it before you close or leave the tab. And the real exposure is what you shared rather than where the file went: a whole-screen capture records the email preview and the notification that arrives mid-take.

Nothing on the page caps it — no timer, no size limit, no account tier. Your machine sets the limit instead, because the recording accumulates in the tab's memory until you stop, so a long full-screen capture grows the tab's footprint the whole way through and a very long one can end with the tab being killed and the take lost. Size depends far more on movement than on minutes: screen content compresses well because most pixels do not change between frames, so a still slide costs almost nothing while a scrolling page or an embedded video costs a great deal. For anything past a few minutes, record in sections and download each one before starting the next.

Capture, encoding and whatever you are recording are all competing for the same machine at the same moment, and when it cannot keep up the recorder drops frames rather than falling behind. Sharing one window or one tab instead of a large high-resolution screen is usually the single biggest improvement, followed by closing everything you are not using. Text tends to soften while a page is scrolling and sharpen once it settles, because the codec spends its bits where things are moving. There is no quality slider to raise: no resolution, frame rate or bitrate control exists here, the browser decides what to hand over, and the file is never re-encoded afterwards.

There are two separate obstacles. Technically, protected video from a paid streaming service usually comes out black or as an empty rectangle, because that playback path is deliberately kept out of reach of capture. A meeting running in a browser tab records like any other tab; a native desktop meeting app records only if you share its window or the whole screen. Legally, recording other people talking is not a decision you make alone. Consent rules differ by country and some require everyone's, employers often have their own policy, and meeting platforms announce their own recordings to participants while a capture made this way announces nothing. Ask the room first.

Neither, here. It runs from Start to Stop as one continuous take, and the elapsed seconds ticking on the button are the only thing you can watch while it goes. If you fumble the opening, stop and start again — but download anything worth keeping first, because beginning a new recording discards the previous one. Ending the share from the browser's own sharing bar counts as pressing Stop rather than throwing the take away, so the video still appears in the player. To trim afterwards you need an editor, and most of them open WebM directly; convert to MP4 first only if yours refuses.