Choose the source
Select screen, webcam, or screen plus webcam. Your browser will ask which screen, window or tab to share when display capture is used.
Record your screen, webcam, or both directly in your browser.
Record your screen, webcam or both
Preview the finished recording before downloading it.
Select screen, webcam, or screen plus webcam. Your browser will ask which screen, window or tab to share when display capture is used.
Allow microphone or camera access only when those options are enabled. System or tab audio must also be approved in the browser sharing dialog.
Pause temporarily without ending the current file, resume when ready, or stop to finalize the recording. Ending screen sharing from the browser also stops capture automatically.
CyberTools Screen Recorder records a browser tab, application window, display, webcam, or screen-and-webcam composition directly through supported browser capture APIs. You can include a microphone, request supported system or tab audio, choose a 1080p, 720p, or 480p capture target, pause and resume the recording, preview the result, and download the finished file. The recorder uses MediaRecorder for browser capture and can use FFmpeg WebAssembly to create a compatible H.264 and AAC MP4 when conversion is available. If MP4 encoding cannot be completed, the original browser WebM recording is preserved instead of discarding a successful capture.
Choose Screen, Webcam, or Screen + Webcam, select the audio sources you want, choose a quality target, and press Start Recording. Your browser will ask for the required screen, camera, or microphone permissions. While recording, you can pause, resume, or stop. After stopping, CyberTools finalizes the recording in your browser, attempts compatible MP4 encoding when needed, and provides the finished file for preview and download.
A browser recorder is useful when you need to capture activity without opening a full desktop video editor. The best recording configuration depends on whether the important content is the screen, the presenter, the audio, or a combination of those sources.
Use Screen mode when the important content is an application, browser tab, presentation, website, software demonstration, dashboard or other visible desktop activity. The browser itself controls which capture surfaces it offers. CyberTools receives only the source you approve in the sharing dialog.
Use Webcam mode when you need a camera recording without capturing the desktop. This is useful for short explanations, video messages, introductions, demonstrations and other camera-first recordings. Camera access remains subject to browser permission and device availability.
Screen + Webcam mode combines display capture with a camera feed through a canvas composition. The screen remains the main visual source while the webcam is rendered as a picture-in-picture overlay. This is useful for tutorials, walkthroughs, presentations and reaction-style explanations where both the content and presenter matter.
Enable Microphone when you want commentary, narration, training instructions or spoken explanations in the recording. The current recorder requests echo cancellation, noise suppression and automatic gain control where the browser provides those audio constraints.
System or tab audio can be requested for screen-based capture, but availability depends on the browser, operating system, selected sharing surface and the options shown in the browser capture dialog. You may need to explicitly enable Share tab audio or Share system audio when the browser presents that option.
Pause lets you temporarily stop adding new media to the same recording without finalizing the file. Resume continues that recording, while Stop ends capture and begins result finalization. The timer excludes the paused interval so the displayed duration represents active recording time.
The quality control defines the target dimensions requested for capture and composition. Higher resolution can preserve more visible detail, but it also requires more decoding, rendering, encoding, memory bandwidth and storage. The best choice depends on the source content and the device performing the recording.
| Setting | Target | Best for | Trade-off |
|---|---|---|---|
| 1080p | 1920 × 1080 target | Detailed software interfaces, presentations and larger displays | Highest processing and file-size demand of the three presets |
| 720p | 1280 × 720 target | General tutorials, browser demos and balanced recording | Less detail than 1080p but lighter processing |
| 480p | 854 × 480 target | Quick captures, smaller previews and lower-resource devices | Smallest visual detail of the three presets |
| Screen only | Shared display source | Software demonstrations and presentations | No webcam overlay unless combined mode is selected |
| Webcam only | Camera source | Presenter-first recordings and video messages | Does not include desktop content |
| Screen + Webcam | Canvas-composited output | Tutorials and presenter-led walkthroughs | Requires simultaneous screen/camera processing and composition |
The recorder uses standard browser media APIs for capture and MediaRecorder for the initial recording. Combined screen-and-webcam mode uses an HTML canvas as a compositing surface. Multiple requested audio sources can be mixed through the Web Audio API before they are attached to the recording stream. After capture stops, an optional FFmpeg WebAssembly stage can create an MP4 version with H.264 video and AAC audio.
Screen capture uses navigator.mediaDevices.getDisplayMedia(), while webcam and microphone access use navigator.mediaDevices.getUserMedia(). The browser displays its own permission interfaces and decides which screen surfaces, cameras and microphones are available.
In combined mode, CyberTools creates a canvas at the selected quality target and draws the shared screen plus webcam frames into that canvas. The canvas is captured as a 30 FPS video stream that becomes the visual source for MediaRecorder.
When more than one requested audio source is available, the recorder can route those tracks through AudioContext and MediaStreamDestination. This produces one mixed audio track for the recording instead of depending on inconsistent browser handling of multiple simultaneous output audio tracks.
The recorder checks MediaRecorder.isTypeSupported() instead of assuming one codec works everywhere. It prefers WebM with VP9 and Opus when supported, then tries VP8 and Opus variants, and finally allows the browser to choose its default recording format if necessary.
When the browser produces WebM and the local FFmpeg WebAssembly engine is available, CyberTools can transcode the recording to H.264 video with libx264 and AAC audio. The MP4 path uses yuv420p pixel format and fast-start metadata for broad playback compatibility.
MP4 conversion is a post-processing step, not the only copy of the recording. If FFmpeg cannot load or MP4 encoding fails, CyberTools preserves the original browser WebM result so a successful recording is not lost simply because optional conversion was unavailable.
Choose settings according to the content viewers need to see and hear. Higher settings are not automatically better if they increase processing load without adding meaningful detail.
| Use case | Recommended setting | Why |
|---|---|---|
| Software tutorial | Screen + microphone, 1080p or 720p | The screen remains clear while narration explains the workflow. Choose 1080p when small interface text matters and the recording device can handle the higher workload. |
| Presentation with presenter | Screen + Webcam + microphone | Combined mode keeps slides or desktop content visible while also showing the presenter and recording spoken narration. |
| Quick browser demonstration | Screen, 720p | 720p is often a practical balance for general web demonstrations where Full HD detail is not essential. |
| Simple video message | Webcam + microphone | There is no reason to request display capture when the camera and voice are the only content required. |
| Recording tab playback | Screen + requested tab/system audio | Enable the system/tab audio option and then also approve audio sharing in the browser dialog if the browser exposes it for the selected capture surface. |
| Lower-resource device | 480p or 720p | Reducing the target resolution lowers the amount of video data that must be composed, recorded and potentially transcoded in the browser. |
Screen recording quality is influenced by the source, capture resolution, browser encoder, frame delivery, audio sources and any post-recording transcode. A container such as WebM or MP4 does not by itself determine visual quality; the codecs and encoder settings inside that container matter.
A 1080p target can retain more interface detail than 720p or 480p when the original source contains that detail. It also increases the amount of pixel data processed during capture and encoding.
The first recording is produced through MediaRecorder. CyberTools checks supported WebM codec combinations rather than forcing VP9 on browsers that cannot record it.
MP4 and WebM describe media containers, not a single fixed quality level. The current MP4 compatibility path uses H.264 video and AAC audio, while the initial browser recording commonly uses VP9 or VP8 with Opus when those combinations are supported.
A VP8 or VP9 WebM stream cannot be treated as a universally compatible H.264 MP4 merely by changing the file extension. The current conversion path performs real H.264 and AAC encoding when FFmpeg is available.
Media chunks accumulate while recording and the final file must be processed in the browser. Long duration, high resolution and complex composition can therefore increase memory pressure and finalization time.
Choosing 1080p does not recreate detail that was absent from the shared source or webcam. Recording and transcoding can preserve or transform available media, but they cannot recover visual information the source never contained.
The current Screen Recorder capture pipeline runs through browser media APIs on your device. MediaRecorder creates the recording locally, combined screen-and-webcam composition is performed in a browser canvas, audio mixing can run through the Web Audio API, and optional MP4 conversion uses the FFmpeg WebAssembly engine loaded by the page.
CyberTools cannot silently choose a display, camera or microphone. The browser permission system mediates capture and presents the available sources according to browser and operating-system rules.
If the user stops sharing from the browser interface, the display video track emits its ended event and the recorder finalizes the active capture instead of continuing with a dead screen source.
Browser-based processing means your computer performs capture, composition and encoding work. CPU speed, available memory, browser implementation and hardware load can therefore affect recording stability and finalization time.
The recorder is designed around local browser capture and processing. This does not mean browsers can bypass operating-system restrictions or guarantee every audio source on every platform. The browser remains the authority for capture permission and available media features.
Browser recording is powerful, but it operates inside browser security and resource limits. Understanding those boundaries prevents incorrect expectations about audio capture, background behavior, resolution and device access.
The system/tab audio request does not guarantee an audio track. Support varies by browser, operating system and selected sharing surface, and the browser may require a separate audio-sharing checkbox.
Camera, microphone and display capture are permission-controlled capabilities. CyberTools cannot automatically approve those permissions or secretly select a capture source.
Large recordings can require substantial memory for captured chunks and additional memory and CPU during MP4 encoding. Available device resources can become the practical recording limit.
The actual captured source, browser implementation and selected device determine the available detail. Requesting a 1920 × 1080 target does not upscale a low-detail source into genuine Full HD information.
The current workflow records, pauses, resumes, combines supported sources and finalizes the media. It does not automatically remove mistakes, generate captions, summarize speech, track speakers or perform AI editing.
Browsers and operating systems can throttle, suspend or terminate media processing under certain conditions. A web recorder cannot guarantee uninterrupted capture after a tab, device or browser enters a restricted background state.
These terms describe the browser technologies and media concepts involved in the current Screen Recorder workflow.
Answers about browser screen capture, webcam recording, microphone and system audio, pause and resume, quality settings, MP4/WebM output, privacy and browser limitations.
Choose Screen as the capture source, select microphone or supported system/tab audio if needed, choose a quality target and press Start Recording. Select the screen, window or tab in the browser sharing dialog. Stop when finished, then preview and download the finalized recording.
Yes. Choose Screen + Webcam. CyberTools captures both approved sources and combines them through a browser canvas so the webcam appears as a picture-in-picture overlay on the screen recording.
Yes. Enable Microphone before recording and approve microphone access when the browser asks. Screen-only recording with microphone is supported by the current recorder workflow.
It can request system or tab audio for screen-based capture, but actual availability depends on the browser, operating system and selected sharing surface. If the browser presents a Share audio option, you must enable it in the capture dialog.
Yes. Pause temporarily suspends MediaRecorder without finalizing the file. Resume continues the same recording, and the displayed timer excludes the paused interval.
The browser initially records in a supported MediaRecorder format, commonly WebM. When FFmpeg WebAssembly is available, CyberTools can transcode WebM to an H.264/AAC MP4. If MP4 encoding fails, the original WebM is preserved.
They are different capture targets. 1080p requests 1920 × 1080, 720p requests 1280 × 720 and 480p requests 854 × 480. Higher resolution can preserve more detail but requires more processing, memory and storage.
The current capture workflow uses browser media APIs, MediaRecorder, canvas composition, Web Audio processing and an FFmpeg WebAssembly post-processing path on the device. Browser permissions still control which media sources are accessible.
Long or high-resolution recordings can consume significant browser memory and CPU. Final MP4 conversion adds additional encoding work, so device resources, browser limits and recording duration can affect reliability.
No. Display, camera and microphone capture are controlled by browser and operating-system permissions. CyberTools cannot silently choose a screen, bypass a permission prompt or guarantee system-audio access when the browser does not provide it.
Feel free to request missing tools or give us feedback using our contact form.
Contact Us