What it does
Useful, focused capabilities
- Browser-controlled screen source picker
- Optional system audio and microphone
- Optional camera overlay
- Pause, resume, preview, verification, and local download
- Direct-to-file mode where supported
Capture & video · browser-local
Private screen recorder
Record your screen, window, or browser tab locally with optional microphone and camera overlay. No upload, account, or cloud processing.
Work happens in the current browser. The route does not require an account or a server-side processing job.
Interactive browser workspace
Private screen recorder
The live tool is loaded in this browser only. This tool can request display-capture, microphone, camera only after you choose the relevant action.
Open this local tool →Browser compatibility
Requirements and honest fallbacks
JavaScript and a modern browser; media capture tools require HTTPS and explicit permission.
- JavaScript
- HTTPS or localhost
- getDisplayMedia
- MediaRecorder
- getUserMedia for microphone or camera overlay
- CanvasCaptureMediaStream
- File System Access API
Questions people ask
Clear answers and limits
Does Aftermath see my screen?
No. The browser displays the picker and exposes only the source you approve to this local page. This implementation has no upload endpoint.
Can it record system audio?
Sometimes. Availability depends on browser, operating system, and whether you choose a tab, window, or whole display.
Why is camera overlay more demanding?
It requires continuous local canvas composition before encoding, which uses more CPU and may lower frame stability on weaker devices.
Why might the result be WebM instead of MP4?
MediaRecorder support is browser-specific. The tool selects a supported local format and reports it honestly rather than promising an unsupported codec.
What happens if I stop sharing from the browser bar?
The selected display track ends and the tool finalizes the recording with the media produced so far.
Can I record for hours?
The reference build has a one-hour safety limit. Standard mode also consumes memory; direct-to-file is preferable for longer supported captures.