# Screencast Complete Documentation and Technical Reference (llms-full.txt) > Canonical URL: https://onlinescreencast.com/ > Documentation Hub: https://onlinescreencast.com/guides/ > Format: Full context knowledge base for AI Answer Engines, LLMs, and RAG pipelines. > License: 100% Free, no login, no watermark, local-first. --- ## 1. System Overview & Core Architecture Screencast is a zero-friction, client-side browser screen recorder and video review application. All media capture, compositing, live annotation, and format transcoding run locally within the user's browser sandbox using modern web standards. ### Architectural Principles: 1. **Local-First Privacy**: Video frames and audio samples never leave the browser sandbox. No media stream or file is transmitted to remote servers. 2. **Zero Account Friction**: No account creation, email capture, passwords, or subscriptions. The application is completely functional upon page load. 3. **No Watermarks**: Exported WebM and MP4 files contain strictly the captured visual and audio content without logos, overlay stamps, or sponsored intro cards. 4. **Resilient Local Storage**: Capture chunks are committed incrementally to IndexedDB during recording, enabling post-recording review and crash recovery. 5. **Dual-Path Local Export**: - **WebM**: Immediate container assembly and download without re-encoding. - **MP4**: Local conversion using browser WebCodecs (hardware accelerated when supported), falling back to in-browser FFmpeg WebAssembly (WASM). --- ## 2. Technical Q&A & Answer Engine Reference (FAQ) ### Q: How do I record my screen on Mac? **A:** Open Screencast in Chrome, Firefox, or Edge and choose Start recording. Select Entire Screen to capture across apps, or select a window or tab. Allow microphone or camera access only when you want those sources included. Then stop the recording and export WebM or MP4 locally. ### Q: How do I record my screen on iPhone? **A:** Mobile browsers on iOS do not currently support web-based screen recording. Use Screencast on a Mac or PC. To record directly on an iPhone, use the built-in Screen Recording control in Control Centre. ### Q: How do I record my screen on Windows? **A:** Use Screencast in Chrome or Edge. Select a recording mode, choose Start recording, and pick the screen or window in the browser sharing dialog. When finished, download the recording as WebM or MP4. ### Q: How do I record my screen on Chromebook? **A:** Open Screencast in Chrome, choose Start recording, and capture your screen with an optional camera overlay and microphone audio. Your recording is processed locally and can be exported as MP4 or WebM. ### Q: How do I record my screen on Android? **A:** For the full browser recording experience, use Screencast on a desktop or laptop. To record directly on Android, use the built-in Screen recorder tile in Quick Settings. ### Q: Can I record my screen with audio? **A:** Yes. Enable Microphone before recording and grant browser permission when prompted. Enable System audio as well when your browser and shared source support it. You can use either source or both together. ### Q: Does recording capture system and tab audio? **A:** When enabled, System audio can capture tab audio, application sound, and music. In the browser sharing dialog, make sure Share system audio is selected when it is available. ### Q: Is my recording saved to the cloud? **A:** No. Screencast records and stores video locally in your browser on your device. Nothing is uploaded unless you choose to export or share it yourself. ### Q: How do I save or convert a recording to MP4? **A:** Stop the recording and select Stop and review. Choose Download WebM for an immediate local file, or Convert to MP4 to create an MP4 on your device. ### Q: What is a good free online screen recorder? **A:** Screencast records in your browser without an account, watermark, or automatic cloud upload. You can record the screen, camera, or both with audio, then review and export locally. ### Q: Does Screencast work in Safari? **A:** Current Safari versions on macOS support browser screen capture, but available audio sources, camera compositing, recording formats, and local MP4 export can differ from Chromium browsers. Make a short test recording first, or use a current version of Chrome or Edge when you need the most complete workflow. ### Q: Can I record a Zoom or Google Meet call? **A:** Yes. Choose Entire Screen or the specific browser tab in the sharing dialog when you start recording. This captures whatever is visible on your screen, including Zoom, Google Meet, or any other app. Screencast records the browser-level capture — it does not hook into meeting software directly. ### Q: Can I pause and resume a recording? **A:** Yes. Once recording has started, use the Pause button to pause and the same button to resume. The finished file is one continuous recording with the paused intervals removed. ### Q: Is there a maximum recording length? **A:** There is no hard time limit set by Screencast. In practice, the limit is your browser's available local storage and device memory. For very long recordings, export as WebM immediately after stopping rather than relying on browser storage recovery. ### Q: How do I share my recording after exporting? **A:** Export the recording as WebM or MP4 to your device, then share it using any method you would use for a regular video file — email attachment, cloud storage link (Google Drive, Dropbox), or a video hosting service. Screencast does not host or share files; sharing happens through your own tools after export. --- ## 3. Comprehensive Technical Guides ### Guide: Screencast browser compatibility and requirements - **Canonical URL**: https://onlinescreencast.com/guides/browser-compatibility/ - **Last Reviewed**: 2026-10-02 - **Summary**: Which desktop browsers support screen, camera, audio, and local MP4 export in Screencast, what differs between them, and how to test an important setup. - **Verification Scope**: Compatibility statements were checked against the current recorder feature checks and browser API documentation. They describe documented support and known constraints, not a guarantee for every browser, device policy, or hardware combination. #### Which browsers work best with Screencast? **Direct Answer:** A current desktop version of Chrome or Edge gives you the most complete workflow: screen capture, camera overlay, shared audio where the operating system allows it, and local MP4 conversion. Screencast is built entirely on browser capture APIs rather than a downloaded helper application. That is what lets it run without an install, and it is also why what you can record depends on the browser you open it in. There is no Screencast-side setting that can add a capability your browser does not expose. Chrome and Edge share the same underlying engine and behave almost identically here. Firefox records screen and camera reliably and exports WebM without trouble, but its system-audio support in the screen-sharing picker is more limited, and MP4 export falls back to the slower in-browser encoder described below. Safari is the most constrained of the desktop browsers. Screen capture works, but the combination of capture, camera compositing, and local MP4 conversion is not something we would rely on for an important recording. If Safari is your daily browser, it is still worth opening Screencast in Chrome for anything you only get one take at. If a browser cannot support recording at all, Screencast tells you directly rather than failing silently part-way through: it checks for MediaRecorder and the screen-capture API before it asks for any permission, and shows a message naming Chrome, Edge, or Firefox as alternatives. #### What actually differs between browsers? **Direct Answer:** Three things vary: which audio sources the share picker offers, which local MP4 conversion path is available, and how the browser labels the surface you chose to share. Audio is the largest difference and the one that surprises people most often. Current desktop browsers generally support microphone capture after permission, but device policy or an unavailable input can still block it. Shared audio is less consistent. On Windows, Chrome and Edge commonly offer system audio for an entire screen and tab audio for a browser tab. On macOS, tab audio is generally the more predictable browser option. MP4 export differs next. Screencast records to WebM first, then converts locally when you ask for MP4. If the browser exposes a compatible WebCodecs encoder, Screencast uses it and asks the browser to prefer hardware acceleration. The browser may still choose software. Otherwise, Screencast falls back to FFmpeg running in the page, which can take longer for large recordings. Screencast identifies the active path while it works. Finally, browsers differ in how precisely they report what you picked. Screencast reads the share surface back from the browser and adjusts its on-screen notice accordingly, so you get a different message for an entire screen, a single window, and a browser tab. Where a browser reports the surface vaguely, that notice is correspondingly less specific. #### Can Screencast record an iPhone or Android screen? **Direct Answer:** No. Mobile browsers do not implement the screen-capture API at all, so no browser-based recorder can capture a phone screen — this is a platform restriction rather than a Screencast limitation. Both iOS and Android treat screen capture as a privileged operating-system function and do not expose it to web pages. Any site claiming to record your phone screen from a mobile browser is either recording only its own page or asking you to install something. Use the recorder built into the operating system instead. On iPhone and iPad, add Screen Recording to Control Centre in Settings. On Android, the screen recorder lives in the quick-settings panel on most recent devices. Both save a video file you can then move wherever you need it. Camera-only recording is a partial exception, since mobile browsers do expose the camera. It works in some mobile browsers, but the review-and-export step is built for a larger screen and we would not recommend depending on it. #### What permissions does Screencast ask for, and when? **Direct Answer:** Only what you have switched on, and only at the moment you press record — the share picker for screen capture, and a separate camera or microphone prompt when those sources are enabled. Nothing is requested when the page loads. Screencast asks your browser for a capture stream only after you choose Start recording, which is why you will not see a permission prompt while you are still setting up the frame, background, or camera layout. The screen prompt is your browser's own share picker, not a Screencast dialog, and it is the point at which you decide what is actually visible in the recording. Screencast cannot pre-select a screen for you or see anything you do not choose there. Camera and microphone are requested separately and only when the corresponding control is on. If you record in Screen mode with the microphone toggle off, no camera or microphone permission is requested at all. If you previously denied a permission, the browser will usually not ask again — it will just fail. Clear the block from the padlock or camera icon in the address bar, reload, and try again. #### Why does Screencast keep suggesting Entire Screen? **Direct Answer:** Because the share surface you choose is fixed for the whole recording. If you pick a single tab or window and later switch to another application, the recording keeps showing the original surface, not what you moved to. This trips up more recordings than any other single setting. A demonstration that moves between a browser, a terminal, and a design tool has to be recorded as an entire screen; there is no way to widen the selection once recording has started. Screencast reads back what you actually chose and shows a notice naming it, so you can catch the mistake in the first seconds rather than at the end. If the notice says you are recording a browser tab or a window and that is not what you intended, stop and start again before you have spent ten minutes on a take you cannot use. Choose a narrower surface deliberately when the tighter framing is the point: a single tab keeps notifications, other monitors, and unrelated windows out of the video without any editing afterwards. #### How do I check my setup before a recording that matters? **Direct Answer:** Do a fifteen-second dry run with the exact sources and settings you intend to use, then play it back and export it before you record the real thing. Record a short take with the same mode, the same share surface, the same audio toggles, and the same frame and background settings. Most problems — a muted microphone, a system-audio box you did not tick, the wrong share surface, a camera overlay covering something important — are obvious within a few seconds of playback and invisible while you are recording. Export the test file too, not just play it. Export is where browser differences show up: it tells you whether the browser uses the WebCodecs path or the FFmpeg fallback, which matters if the real recording will be long. Check your free disk space if the recording will be long. Screencast writes the video to browser storage as it goes and warns you when less than roughly 150 MB is available, because a recording that runs out of space part-way through may not be fully recoverable. --- ### Guide: Browser-based vs desktop screen recorder: which to choose - **Canonical URL**: https://onlinescreencast.com/guides/browser-screen-recorder-comparison/ - **Last Reviewed**: 2026-10-02 - **Summary**: Complete comparison of browser-based and desktop screen recording: installation, privacy, features, performance, use cases, and when to choose each approach. - **Verification Scope**: Browser and desktop recorder trade-offs were verified against current Chrome, Edge, Safari, and Firefox capabilities and OS sandboxing models. #### Browser-based vs desktop screen recording: key differences **Direct Answer:** Browser-based screen recorders run entirely in your web browser with no installation required. Desktop recorders are standalone applications you download and install. Each has distinct advantages for different use cases. Browser-based recorders like Screencast work through web APIs built into modern browsers. You open a webpage, grant permissions, and start recording—no download, no installation, no system-level software. Everything runs in the browser sandbox, using standard web technologies (MediaRecorder API, Canvas, WebCodecs). These tools are instantly accessible from any computer with a compatible browser. Desktop recorders like OBS Studio, Camtasia, or built-in OS tools (Screenshot.app on Mac, Xbox Game Bar on Windows) are native applications installed on your computer. They have deeper system integration, can access hardware directly, and often offer more advanced features—but they require installation, updates, and platform-specific versions. The fundamental trade-off: browser-based tools prioritize convenience and accessibility (no installation, works anywhere, privacy through local processing), while desktop tools prioritize power and flexibility (advanced features, better performance for high-end recording, deeper system integration). Neither is universally better; the right choice depends on your specific needs. For most everyday use cases—recording a quick demo, capturing a bug, making a tutorial, documenting a process—browser-based recording is simpler and sufficient. For professional video production, game streaming, or highly customized recording setups, desktop software provides capabilities browsers cannot match. | Dimension | Screencast (Browser) | Desktop (OBS / Native) | Cloud (Loom / Vidyard) | | --- | --- | --- | --- | | Installation | Zero install (Runs in browser) | Software download required | Extension or desktop app | | Privacy & Storage | 100% Local (IndexedDB) | Local hard drive | Uploaded to cloud servers | | Account / Login | None required | None required (OBS) | Account required | | Watermarks | Zero watermarks | Zero watermarks (OBS) | Watermark or time caps on free tier | | Export Formats | WebM & local MP4 | MKV, MP4, MOV, FLV | Hosted video link / cloud MP4 | | Best For | Demos, bug tickets, tutorials | Live streaming, game capture | Async team messaging links | #### Installation, updates, and accessibility **Direct Answer:** Browser-based recorders require no installation and work instantly on any device with a compatible browser. Desktop recorders require downloading, installing, and maintaining software on each device you use. Browser-based accessibility: open a link, grant permissions, start recording. If you switch computers, the tool is immediately available—no need to install anything on the new machine. If you are using a shared computer, public terminal, or work machine where you cannot install software, browser-based recording is often the only option. The tool is as accessible as any website. Desktop installation overhead: downloading an installer, running through installation steps, potentially granting administrator permissions, configuring settings, and dealing with platform-specific installers (Windows vs Mac vs Linux). On locked-down corporate machines, you may not have permission to install desktop software at all. Updates: browser-based tools update automatically—the webpage you load is always the latest version. Desktop tools require checking for updates, downloading patches, and occasionally dealing with breaking changes that require reconfiguration. OBS Studio, for example, releases regular updates that users must manually download and install. Multi-device workflows: if you work across multiple computers (desktop at home, laptop while traveling, work machine at office), browser-based tools work identically on all of them with no setup. Desktop tools must be installed and configured on each device, and keeping settings synchronized across installations requires manual export/import of configuration files. The convenience factor is significant: browser-based recording means you can help a colleague record their screen right now by sending them a link, rather than walking them through downloading and installing software. For ad-hoc recording needs, immediate access matters more than advanced features. #### Privacy: local processing vs cloud uploads **Direct Answer:** Browser-based recorders like Screencast can process everything locally on your device with no uploads. Most desktop recorders also keep recordings local, but some include cloud features that upload your content. Browser-based local processing: tools like Screencast record, process, and export entirely on your device. Your screen recording never uploads to any server. The browser's MediaRecorder API writes directly to local storage (IndexedDB), and export runs locally using WebCodecs or WebAssembly. This is verifiable—watch your browser's network traffic during recording and you will see no video data transmitted. Desktop local recording: tools like OBS Studio, Screenshot.app, and Xbox Game Bar also keep recordings entirely local by default, saving directly to your chosen folder. They have no internet connection requirement and no cloud component. For pure local recording, both browser-based and desktop tools can be equally private. Desktop tools with cloud features: some desktop recorders (Loom, Camtasia with cloud library, Snagit with sharing features) integrate cloud uploads, either as required or as opt-in features. These uploads can be convenient (instant sharing links, cross-device access) but mean your recordings exist on someone else's servers. Check the tool's privacy policy and understand where your data goes. Platform trust: browser-based tools run in the browser sandbox, isolated from your system. They cannot access files outside what you explicitly provide, cannot install system extensions, and are constrained by browser security. Desktop tools run with much broader permissions—they can access any file, run at system startup, and potentially monitor more than just the recording session. This is necessary for their advanced features but means you must trust the desktop software more deeply. For sensitive recordings—internal company demos, client projects under NDA, anything with proprietary information—local-only recording is essential. Both browser-based and desktop tools can provide this, but you must verify the specific tool does not include surprise uploads or cloud "backup" features enabled by default. #### What you can capture: screen, window, tab, audio **Direct Answer:** Browser-based recorders capture screen, windows, and browser tabs through the operating system's screen sharing APIs. Desktop recorders can additionally capture specific application windows, game overlays, and have more reliable system audio capture. Browser-based recording uses your operating system's native screen sharing dialog (the same one used by Zoom, Teams, etc.). You can share your entire screen, a specific window, or a browser tab. This works reliably for most recording needs and provides the same familiar interface across different browser-based tools. Desktop recording with OBS Studio or similar tools offers "source" flexibility: you can add specific application windows as sources, capture game overlays with minimal performance impact, monitor individual audio channels separately, add static images or overlays, and build complex multi-source scenes. This matters for streaming and production work, less so for simple screen recording. Audio capture: current desktop browsers generally support a microphone after permission, while shared tab, window, and system audio depend on the browser, operating system, and selected share surface. Desktop tools can offer deeper operating-system audio integration. If dependable application audio is essential, test the exact browser workflow or use a desktop recorder. Camera overlay: browser-based tools like Screencast can compose your webcam over the screen recording with layout options (corner, circle, split-screen). Desktop tools can do the same but often with more control over positioning, sizing, and layering. For basic "face in corner" use cases, browser-based is sufficient; for complex picture-in-picture with multiple cameras, desktop tools offer more. Tab recording is unique to browser-based tools: the ability to record a single browser tab (with its audio) is not something desktop recorders can replicate in the same way, because tabs are a browser concept, not an OS one. This makes browser-based recording particularly good for demonstrating web applications or recording web content. #### Performance, file size, and recording quality **Direct Answer:** Desktop recorders generally have better performance for long or high-resolution recordings because they are native applications. Browser-based recorders work well for typical screen recordings but may struggle with very long 4K recordings or when system resources are constrained. Performance ceiling: desktop applications can optimize for the specific platform they run on, use native codecs directly, and aren't constrained by browser sandbox limitations. For recording 4K at 60fps, or for multi-hour recordings, desktop tools are more reliable and efficient. Browser-based recording performance is limited by what the browser can do, and browsers prioritize safety and compatibility over raw performance. Real-world performance: for typical use cases—recording 1080p or 1440p at 30fps for 5-30 minutes—browser-based recording performs excellently on modern hardware. Most people will not notice performance differences between browser and desktop recording until they push into high-end scenarios (4K, very long duration, recording while running other intensive applications). File size and quality: both approaches can produce high-quality recordings. Browser-based recorders typically use WebM with VP9 video, which provides good compression and quality. Desktop recorders offer more codec choices (H.264, H.265, AV1, various presets) which can result in smaller files at equivalent quality if you tweak settings—but require understanding those codecs to use effectively. For default settings, file sizes are comparable. Resource usage during recording: browser-based recording adds overhead to your browser, which is already running other tabs and extensions. Desktop recorders are dedicated applications that can be prioritized. If you are recording while also running memory-intensive applications, a desktop recorder may leave more resources available for those other apps. System impact: browser-based recording is temporary—close the tab and the recorder is gone. Desktop recorders remain installed, may run background processes, can consume startup resources, and live permanently on your system. For occasional recording needs, browser-based tools have less overall system impact despite comparable performance during actual recording. #### Features: live editing, post-processing, and export **Direct Answer:** Browser-based recorders focus on streamlined recording and export, usually with limited post-processing. Desktop recorders often include editing capabilities, effects, and advanced export options but with steeper learning curves. Browser-based feature set: Screencast and similar tools offer live annotation (draw on the recording as it happens), framing options (aspect ratios, backgrounds), basic camera compositing, and direct export to common formats. The focus is on making recording easy and fast, with features that work during capture rather than extensive post-processing. Desktop feature set: OBS Studio offers scene composition, source layering, filters and effects, audio mixing with EQ and compression, chroma key, transitions, and streaming integration. Camtasia includes a full timeline editor, titles, animations, zoom/pan effects, and captioning. These advanced features support professional production but require learning the interface. Post-recording editing: most browser-based tools do minimal post-recording editing—you get what you recorded. Desktop tools often include editing: trimming, cutting unwanted sections, adding titles or overlays, adjusting audio levels. If your workflow requires editing recordings, desktop tools (or browser-based recording followed by a separate editor) are necessary. Export format flexibility: browser-based recorders typically export WebM and MP4. Desktop recorders support dozens of formats, multiple quality presets, custom encoding parameters, and can optimize for specific platforms (YouTube, Twitch, file archival). Most users never need this flexibility, but for specific technical requirements, desktop tools provide it. Simplicity vs power: browser-based tools make common tasks trivial (record screen, export file, done in under a minute). Desktop tools make complex tasks possible (multi-source composition, advanced audio routing, live streaming with overlays) but add complexity even for simple tasks. Choose based on which end of that spectrum your needs fall. #### When to use browser-based vs desktop recording **Direct Answer:** Use browser-based recording for quick demos, tutorials, bug reports, and everyday screen capturing where convenience matters more than advanced features. Use desktop recording for streaming, professional video production, and scenarios requiring complex setups. Browser-based is better for: recording a bug to attach to a ticket, making a quick tutorial for a colleague, capturing a demo for a client, documenting a procedure, recording your screen on a shared or locked-down computer, situations where you need to start recording immediately without setup, recordings you want to keep private with no cloud uploads. Desktop is better for: live streaming to Twitch/YouTube, producing polished video content with editing, recording long-form content (webinars, presentations over an hour), situations requiring complex audio routing, recordings where you need advanced post-processing, game recording with minimal performance impact, professional video production workflows. Specific scenarios: Teaching a class remotely? Browser-based is simpler and works on any student's computer without installation. Creating course content for sale? Desktop tools give you editing and production capabilities. Reporting a software bug? Browser-based gets you a video in 30 seconds. Recording gameplay for YouTube? Desktop tools handle game capture better and integrate with streaming platforms. Hybrid approach: record with a browser-based tool for convenience and privacy, export the file, then import into a desktop video editor (DaVinci Resolve, Adobe Premiere) if you need advanced editing. This combines the ease of browser recording with the power of desktop editing without requiring the complexity of desktop recording software. Team collaboration: if you need to share the recording as a link for others to watch in a hosted player, track who viewed it, or organize recordings in a team library, you need cloud-based recording tools (which may be browser-based like Loom or desktop apps with cloud integration). Local-only recording—browser or desktop—gives you a file, not a hosted link. #### Browser support and desktop platform differences **Direct Answer:** Browser-based recorders work best in Chromium-based browsers (Chrome, Edge, Brave) on desktop operating systems. Safari and Firefox have more limitations. Desktop recorders are platform-specific (Windows, Mac, or Linux builds). Best browser support: Google Chrome, Microsoft Edge, Brave, and other Chromium-based browsers have the most complete implementation of recording APIs. They support screen/window/tab capture, system audio (OS-dependent), camera compositing, and modern export codecs. Use these browsers for the best experience with browser-based recording. Safari limitations: Safari on Mac supports basic screen recording but has no system audio capture, occasional compatibility issues with newer web APIs, and less reliable camera compositing. If you must use Safari, browser-based recording works but with reduced capabilities. Consider Chrome or Edge on Mac for better results. Firefox limitations: Firefox supports screen and camera recording but has limited system audio support and sometimes lags behind Chrome in implementing the latest web standards for recording. It works for basic use cases but is not the optimal choice. Desktop platform specifics: OBS Studio has Windows, Mac, and Linux versions but with different feature sets—Windows has the broadest plugin ecosystem, Mac has application audio capture limitations, Linux support depends on your audio system (PipeWire vs PulseAudio). Screenshot.app is Mac-only. Xbox Game Bar is Windows-only. Desktop tools require using the right version for your OS. Cross-platform workflow: browser-based recording works identically on Windows, Mac, and Linux (as long as you use a compatible browser). Desktop tools require switching applications or learning different tools if you work across platforms. This makes browser-based recording better for teams or individuals using multiple operating systems. #### Cost: free options, paid tiers, and hidden expenses **Direct Answer:** Free browser-based recorders like Screencast have no costs—no paid tiers, no feature limitations. Free desktop recorders like OBS Studio are open source. Many desktop recorders have paid versions with more features or free versions with limitations. Completely free: Screencast (browser-based), OBS Studio (desktop, open source), Screenshot.app (built into macOS), Xbox Game Bar (built into Windows 10/11). These cost nothing, have no paid tiers, and no feature upsells. They are sustainable through different models: Screencast via web advertising on the site, OBS through donations and community support, OS tools as part of the operating system. Freemium desktop recorders: Camtasia (free trial, then paid), Bandicam (free with watermark and time limit, paid license to remove), Filmora (free with watermark, paid to remove). These have capable free tiers but push you toward paid upgrades for the full experience. Cloud recording costs: Loom, Vidyard, and similar tools (browser-based or desktop app) are free for basic use but have paid tiers for removing watermarks, unlimited recording length, more storage, team features, and advanced analytics. The recurring subscription cost adds up over time—these are services, not one-time purchases. Hidden costs of "free" tools: some free tools sell access to your data (analytics on how you use the tool, aggregated usage patterns), serve aggressive advertising, or require creating accounts that become marketing targets. Tools that keep everything local (browser-based with no uploads, or desktop tools without telemetry) avoid these hidden costs. Total cost of ownership: browser-based local recording has zero cost and no ongoing expenses. Desktop free tools also cost nothing but consume disk space and require occasional time investment in updates. Paid desktop tools are one-time purchases (Camtasia, ScreenFlow) or subscriptions (many others). Cloud recording services are ongoing subscriptions. Factor in not just the initial price but the ongoing relationship with the tool. --- ### Guide: Should you export a screen recording as WebM or MP4? - **Canonical URL**: https://onlinescreencast.com/guides/export-webm-or-mp4/ - **Last Reviewed**: 2026-10-02 - **Summary**: How WebM and MP4 differ for screen recordings, how Screencast converts locally, and what to do when an export fails. - **Verification Scope**: Export claims were checked against the current WebM save, WebCodecs, and FFmpeg fallback paths. Timing and hardware-acceleration guarantees were removed because the browser and device control them. #### Which format should you pick? **Direct Answer:** Choose WebM when the video is going somewhere on the web — an upload, a chat message, a ticket attachment. Choose MP4 when it is going into software that is fussy about formats: a video editor, a presentation, a phone camera roll, or a colleague on an older machine. WebM is what Screencast records natively, so exporting it is effectively instant regardless of how long the recording is. Nothing is re-encoded; the file you already have is handed to your browser's downloads. MP4 requires a conversion step, which takes time proportional to the length of the recording and the capability of your device. The upside is compatibility: MP4 is the format almost everything will accept without complaint. When you are unsure, export WebM first. It costs you nothing, gives you a file immediately, and you can always come back and export MP4 from the same recording afterwards — the recording stays in the review panel until you clear it. | Format | Export Speed | Encoding Location | Best Used For | Compatibility | | --- | --- | --- | --- | --- | | WebM | Instant (No re-encode) | Direct browser capture stream | Web apps, Slack, YouTube, Discord | All modern browsers | | MP4 | Requires conversion time | Local WebCodecs or FFmpeg WASM | Video editors, Keynote, iOS/QuickTime | Universal across all devices | #### What actually accepts WebM **Direct Answer:** Every major browser, YouTube, Google Drive, Slack, Discord, Notion, and most modern ticketing and documentation tools play WebM without any conversion. If the destination is a web page or a web application, WebM is almost always fine and often preferable — the files are typically smaller than an equivalent-quality MP4, which matters for upload time and attachment limits. Where WebM tends to fail is outside the browser. Older versions of Windows Media Player, QuickTime on macOS, PowerPoint and Keynote, the iOS and Android photo libraries, and several video-editing applications will either refuse it or import it without audio. The practical test is who receives it. A file going into a shared document, a pull request, or a support ticket can be WebM. A file going to someone who will double-click it on their desktop, or into an editing timeline, should be MP4. #### How the MP4 conversion works, and why it is sometimes slow **Direct Answer:** The conversion happens on your device, using WebCodecs when the browser exposes a compatible encoder and an in-page FFmpeg fallback when it does not. Screencast first tries WebCodecs and asks the browser to prefer hardware acceleration. The browser may still choose a software implementation, and support depends on the input dimensions, codec, browser, and device. If that path is unavailable or fails, Screencast falls back to FFmpeg running in the page. Conversion time can vary substantially with duration, dimensions, device performance, and available memory. Screencast identifies the active path and shows progress while it runs. Neither path uploads anything. The message shown during conversion — that your video is being processed only on this device — is a literal description of what is happening, not a reassurance about a server-side process. Keep the tab open while it works. The conversion is running in that page; navigating away or closing the tab cancels it, and you will have to start again from the recording, which is still saved. #### Does converting to MP4 reduce quality? **Direct Answer:** Slightly, in principle — it is a re-encode rather than a repackage — but the difference is rarely visible in screen-recording content at normal viewing sizes. Screen recordings are unusually forgiving here. They are mostly static regions, flat colour, and text, which compresses efficiently and shows re-encoding artefacts far less readily than camera footage of a moving scene. Where you will see it is in fine text at small sizes and in fast-scrolling content. If the recording is a code walkthrough that people will pause and read, exporting WebM and converting elsewhere with settings you control will preserve more detail than any single-button conversion. The bigger quality lever is upstream of export entirely. Recording at your display's native resolution, leaving the frame on Original, and avoiding unnecessary browser zoom does more for legibility than anything you choose at export time. #### Managing file size **Direct Answer:** Length and visual activity drive size far more than the format does. A still slide deck records tiny; a scrolling page or a video playing inside your recording records large. If a file is too big for where it needs to go, the effective options are recording a shorter take, recording a smaller surface, or trimming afterwards. Choosing a different export format will not change the order of magnitude. Recording a single window or browser tab instead of a full multi-monitor desktop is the largest single saving available, and it usually improves the recording anyway by removing everything the viewer did not need to see. For trimming, Screencast links out to a separate free browser tool rather than building an editor into the recorder. It opens in a new tab and works on the file you have already downloaded. #### When MP4 export fails **Direct Answer:** Export WebM instead — you will still have your recording — then convert separately if you need MP4. Screencast reports a specific reason when the encoder cannot complete: no compatible hardware encoder for that recording, an encoder that produced no output, or a compatibility encoder that could not finish. In every case the underlying WebM recording is untouched and still exportable. The most common practical causes are a very long recording on a machine short of memory, or a browser that claimed a hardware encoder it could not actually use for this particular video. Trying again after closing other tabs sometimes succeeds; trying again in Chrome or Edge more often does. If you have already downloaded the WebM and simply need MP4, any local conversion tool will do it. That keeps the file on your machine, which is the same guarantee Screencast makes. Use Download MP4 again if the conversion completed but your browser did not save the file. Screencast keeps the converted result in the page until you leave it, so a blocked or missed download does not mean re-running the conversion. --- ### Guide: Free screen recorder online: what Screencast includes - **Canonical URL**: https://onlinescreencast.com/guides/free-screen-recorder/ - **Last Reviewed**: 2026-10-02 - **Summary**: What Screencast includes for free, why there is no watermark or account, how local recording works, and when a hosted tool is the better choice. - **Verification Scope**: Product behavior was checked against the current recorder implementation. Browser-controlled details such as bitrate, actual frame rate, audio availability, and conversion speed are described as variable. #### What "free" actually means with Screencast **Direct Answer:** Screencast is free to use with no trial, paid feature tier, Screencast watermark, or account requirement. The recorder you open is the complete product. Most "free" screen recorders fall into one of three categories: trial versions that expire after a few days, freemium products that watermark your videos or limit recording length, or services that require uploading your content to their servers where they own the relationship with your viewers. Screencast is fundamentally different from all of these. The reason Screencast can be truly free is structural, not promotional. It is a static website with no backend server that receives, processes, or stores your video files. There is no cloud infrastructure that scales with usage, no bandwidth costs for hosting your recordings, and nothing to meter or monetize. Your recordings never leave your device, so there is no per-user cost to cover. This architecture avoids storage and video-processing costs that increase with every recording. The website still has ordinary hosting and maintenance costs, but the recording workflow does not require a subscription to fund per-user video storage. If the website displays advertising, it is separate from the exported video. Screencast does not add its branding to recorded frames during capture or export. #### No recording length limits or quality restrictions **Direct Answer:** Screencast does not stop a recording after a paid-tier countdown. Practical limits come from available browser storage, device resources, battery, and the capture stream supplied by your browser. Screencast does not enforce a five, ten, or fifteen minute product limit. A long recording can still fail if the browser runs out of storage, the selected source ends, the computer sleeps, or the operating system interrupts capture. The practical limits are those of your browser and device: available disk space, memory for very long recordings (though Screencast writes to storage in chunks to minimize memory usage), and whatever capture capabilities your browser and operating system support. Screencast warns you when free storage drops below approximately 150 MB, because that is the point where a long recording becomes unreliable. Screencast asks the browser for a capture stream at up to 30 frames per second. The browser and operating system decide the actual dimensions, frame rate, codec, and bitrate. MediaRecorder encodes the stream during capture, so file size and image quality vary by browser, source, motion, and device. For an extended recording, make a one-minute test with the same source and settings, then use that file size to estimate the storage needed. Recording one focused window instead of a large multi-monitor desktop often reduces the amount of changing image data, but the result depends on the browser encoder. #### Every feature included: screen, camera, audio, editing, export **Direct Answer:** Screencast includes everything you need for complete screen recordings: screen and window capture, camera recording (solo or composed over screen), microphone and system audio, live annotation, framing and backgrounds, local review, and WebM or MP4 export. Nothing is locked or requires an upgrade. Screen recording captures your entire display, a specific window, or a single browser tab. The choice happens in your browser's native share dialog, so the experience is familiar and consistent with other screen-sharing tools you may have used. If your demonstration crosses applications, choose "Entire Screen" to record everything. If it stays in one window, choose that window to keep the file size smaller and avoid capturing unrelated desktop activity. Camera recording works standalone or composed over your screen recording. When recording both simultaneously, you can position the camera in the corner, as a circle overlay, or split-screen on the side. Three size options (small, medium, large) let you balance between showing your face and keeping screen content visible. A mirror toggle flips the camera when you are reading your own image while recording. Audio recording can include a microphone and, when the browser offers it for the selected surface, shared tab or system audio. Microphone access can still be blocked by browser permissions, device policy, an unavailable input, or another application using the device. Shared audio support varies by browser and operating system. Live annotation lets you draw on the recording as it happens. The pen tool is for freehand drawing; the arrow tool is for pointing to specific interface elements. Annotations are baked into the recording, so they appear in the exported video exactly as you drew them. Use keyboard shortcut "P" to toggle the pen on and off during recording. Framing options include Original (no letterboxing), 16:9 (widescreen), 1:1 (square for social media), 9:16 (vertical/mobile), and 4:5 (Instagram portrait). Fixed frames letterbox the content rather than cropping it, so nothing is cut off—bars appear to maintain the aspect ratio. Backgrounds and padding sit behind framed recordings to give them a composed, professional look rather than black bars. Local review happens immediately after you stop recording. The video opens in an editor panel where you can play it back with audio, verify the take, and choose your export format. This all happens on your device—nothing uploads during review. Export supports WebM (instant export in the recording's native format) and MP4 (a conversion process that runs locally on your device using WebCodecs or FFmpeg.wasm). WebM is ideal for web use and instant sharing. MP4 is better for importing into video editors, embedding in presentations, or transferring to mobile devices. #### No watermark: your recordings stay clean **Direct Answer:** Screencast adds no logo, watermark, intro frame, or branding to your exported videos. The video file contains exactly what you captured, composed as shown in the preview. Nothing is overlaid during export. Many free screen recorders stamp a logo in the corner of every recording or add an intro screen with their branding. This makes your videos look unprofessional and advertises the tool to your viewers instead of focusing on your content. Screencast never does this. WebM export saves the recording produced by the browser. MP4 export re-encodes that recording locally into a different container and codec. Neither path adds a Screencast logo or promotional frame. If you compose a recording with a background or frame, those design choices are visible in the preview and baked into the recording as you make it—they are your composition, not Screencast branding. If you record with Original framing and no background, the exported video contains only your captured content with no additions. This matters for professional use cases: bug reports, client demos, educational content, portfolio pieces, and documentation all benefit from clean recordings that look like they came from your organization, not a third-party tool. #### Why there is no account signup or cloud upload **Direct Answer:** Screencast requires no account because there is nothing to sign up for. Recordings are not stored on any server, so there is no library to attach to an identity, no usage to track, and no reason to collect an email address. This is the most significant workflow difference from cloud recording tools. With Screencast, you go from opening a link to having a completed recording in under a minute. No signup form, no email verification, no plan selection, no onboarding flow. Just open the page and start recording. The trade-off is explicit: there is no cross-device sync, no cloud library of past recordings, no shareable links that play the video in a branded viewer, and no automatic backup if you lose the file. Your recording lives in your browser on your device. The most recent recording persists there so you can return to it, but that is a convenience, not a backup system. After exporting, treat the file like any other important document: save it somewhere you actually back up. Clearing browser data, switching devices, or recording in a private/incognito window will lose access to the browser-stored recording. This is by design—the browser storage is temporary workspace, not permanent storage. The benefit is privacy and speed. No one else has access to your recordings. They are never transmitted during capture or review. There is no server that could be compromised, no database that could leak your video library, and no service provider with access to what you recorded. Export happens entirely on your device, and only after export do you decide where the file goes. #### Local-first privacy: what stays on your device **Direct Answer:** All recording, processing, and export happens on your device. Your videos never upload to Screencast or any server during capture, review, or export. The only data transmitted is standard website analytics about page visits. Local-first means the video data never leaves your machine. Recording uses your browser's native MediaRecorder API to write directly to browser storage (IndexedDB). Compositing (when combining screen and camera, or applying frames and backgrounds) happens in a Canvas or VideoFrame pipeline on your device. Export to MP4 uses WebCodecs (hardware-accelerated) or FFmpeg compiled to WebAssembly—both run in your browser, locally. This architecture is verifiable. Open your browser's developer tools and watch the Network tab during recording and export. You will see no video data uploaded. The only requests are for page resources (HTML, CSS, JavaScript) and the FFmpeg WebAssembly file if you export to MP4 for the first time. Your actual recording never appears in network traffic. The privacy benefit is that no third party sees your recordings. You are not trusting a service provider to handle your screen captures securely, to not analyze them, or to delete them when you ask. There is nothing to trust because there is no transfer and no storage anywhere but your device. Standard website analytics (Google Analytics) track page visits, button clicks, and feature usage—typical metrics for understanding which parts of the site are used and which browsers people use. These analytics cannot see your recordings because recordings exist only in browser storage that websites cannot enumerate or read across origins. Website analytics and local interface preferences are separate from recording storage. The theme preference is stored in your browser, while recording chunks are stored in this site's IndexedDB database. Google Analytics does not receive the video blob through the recorder's implementation. #### Making your first recording: step-by-step **Direct Answer:** Choose a recording mode (screen, camera, or both), configure audio and framing settings, press Start Recording, select a surface in your browser's share dialog, and press Stop and Review when finished. Everything happens in the browser with no software installation. Before starting, set all recording options. Screencast deliberately locks its controls once recording begins so the video cannot change shape, layout, or audio mix mid-recording. This ensures consistency—what you configured is what you get. Configure mode (screen, camera, or screen+camera), both audio toggles (microphone and system audio), frame aspect ratio, background and padding, and camera layout if using screen+camera. When you press Start Recording, your browser will ask which screen, window, or tab to share. This is a native browser permission dialog, not part of Screencast—your operating system and browser control this step. Choose "Entire Screen" if your demonstration moves between applications. Choose a specific window if it stays in one application. Choose a browser tab if you are recording web content that includes tab audio. After granting permission, Screencast shows a notice confirming what you actually shared. Read this notice—it tells you whether you selected entire screen, a window, or a tab, and whether audio is being captured. This confirmation prevents the common mistake of starting to record, talking for several minutes, and discovering you shared the wrong window or forgot to enable audio. An optional start delay (3 or 5 seconds) gives you time to switch windows, open a menu, or position your mouse before the recording actually begins. The countdown is visible on-screen so you know exactly when capture starts. Recording controls: press the Pause button (or press Space) to pause and resume without splitting the file. The final video will be one continuous recording with the paused portions removed. Press Stop and Review (or press R) to end the recording and open it in the editor panel. If you shared your screen (not just a tab), the recording also stops automatically if you close the shared window or stop sharing from your browser's controls. The keyboard shortcuts work while the Screencast page has keyboard focus: R starts or stops, Space pauses or resumes, and P toggles the pen. A normal web page cannot register these as operating-system-wide shortcuts, so return to the Screencast tab or window before using them. #### Choosing between WebM and MP4 export **Direct Answer:** Export WebM for instant results and web use—it is the recording's native format. Export MP4 when you need to import into video editors, embed in presentations, or play on devices that do not support WebM. MP4 conversion runs locally on your device. WebM export is instantaneous because it is the format Screencast records in. No conversion, no processing—just a direct save of the file your browser created. Use WebM when sharing on the web, uploading to platforms that support it, or when you need the file immediately. MP4 export converts the WebM recording locally using WebCodecs where the browser exposes a compatible encoder, or an in-page FFmpeg fallback. Conversion time depends on duration, resolution, codec support, device speed, and other work happening on the computer. The export screen reports progress instead of promising a fixed time. Why choose MP4: many video editors prefer or require MP4, presentation software (PowerPoint, Keynote) typically expects MP4, mobile devices and older browsers have better MP4 support, and some video hosting platforms are optimized for MP4. If your next step involves editing the recording or embedding it in a presentation, MP4 is usually the better choice. WebM avoids a second encode. MP4 is re-encoded for compatibility, so it may differ slightly in quality and file size. Choose the format based on the software that will receive the file. #### When to use a different tool instead **Direct Answer:** Choose a hosted cloud tool instead of Screencast when you need shareable links to videos hosted by the service, automatic transcripts, viewer analytics, a team video library, or collaboration features. Choose a video editor when you need to cut, splice, add titles, or produce multi-take videos. Hosted recording tools (Loom, Vidyard, etc.) are better when your workflow depends on sending links rather than files. If you need to email a link that plays the video in a branded player, track who watched it and for how long, or organize recordings in a team library, those are server-dependent features Screencast cannot provide. Screencast gives you a file; what you do with it is up to you. Automatic transcripts, captions, and AI summaries all require server processing. Screencast runs entirely in your browser, so it cannot generate transcripts. If transcription is essential to your workflow, choose a tool that provides it. Video editing for production work—multiple takes, cuts, transitions, titles, background music, color grading—belongs in a real video editor (DaVinci Resolve, Adobe Premiere, Final Cut Pro). Screencast records and exports one continuous take. It handles live annotation but not post-capture editing. If you need to splice recordings together or add titles, export from Screencast and import into an editor. Collaboration features like shared team libraries, approval workflows, commenting on specific timestamps, or assigning recordings to team members all require accounts and server infrastructure. If your team's process is built around those features, Screencast is not the right tool. What Screencast is for: the large everyday category between simple recording and full production. Bug reports, walkthroughs for colleagues, demonstrations attached to support tickets, screen captures for documentation, short explanations that are faster to show than write. For these, an account and upload are overhead rather than useful features, and a clean recording you can attach or share as a file is exactly what you need. #### Troubleshooting common recording issues **Direct Answer:** Most issues relate to browser permissions, audio configuration, or storage space. Check that you granted microphone and screen sharing permissions, verify system audio support for your browser and OS, and confirm you have at least 500 MB free disk space. If the Start Recording button does nothing or shows an error: check that you granted necessary permissions. Your browser will ask for screen sharing permission and, if you enabled microphone, microphone permission. Denying either will prevent recording from starting. If you accidentally denied permission, click the lock or info icon in your browser's address bar and reset permissions for the site. If there is no audio in your recording: verify that you toggled Microphone ON before starting and that the browser permission names the intended input. Shared audio is offered by the browser, not guaranteed by Screencast. Chromium browsers commonly offer tab audio, while whole-system and window audio depend on the operating system and selected surface. Check the audio option in the browser share picker and make a short test. If the recording is laggy or dropped frames: close unnecessary applications to free up system resources, lower the recording resolution by sharing a single window instead of a 4K display, and confirm your device is plugged in (not on battery) if you are using a laptop. Very long recordings or recording while other intensive applications are running can cause performance issues. If MP4 export fails or takes a long time: try exporting WebM instead, close other browser tabs to free memory, or wait for the current export to finish before starting another. The WebCodecs path can be faster when a compatible encoder is available; the in-page FFmpeg fallback is more broadly compatible but may take longer. If storage warnings appear: free up disk space by deleting files, or export your current recording and clear the saved recording from Screencast (use the Clear Saved button in the editor) to free browser storage. Each new recording replaces the previous one in browser storage, but exported files remain on disk. --- ### Guide: How Screencast keeps screen recording local - **Canonical URL**: https://onlinescreencast.com/guides/local-first-screen-recorder/ - **Last Reviewed**: 2026-10-02 - **Summary**: What local-first recording means in practice, where recordings are stored while you work, what the website measures, and how to keep a recording you care about. - **Verification Scope**: Local-processing and recovery statements were checked against the current MediaRecorder, IndexedDB, analytics, and export code. The guide distinguishes locally stored recording media from ordinary website analytics. #### What "local-first" means here, precisely **Direct Answer:** Your screen, camera, and microphone data is captured by your browser, held in browser storage, composed and encoded on your device, and written to your disk when you export. The current recorder has no upload step or application endpoint that receives the video. This is a property of the implementation rather than a promise about an unseen cloud process. Screencast is delivered as a static web application. Its recording path writes MediaRecorder chunks to this site's IndexedDB database, and its export path creates a local browser download. The practical consequence is that Screencast does not hold a cloud copy or a per-user recording history. Website analytics can still receive ordinary visit data, as described below, but the recorder does not send the captured media to that analytics service. It also means the recording is only as safe as the device it is on. There is no cloud copy to fall back on if you clear your browser data, if the machine fails, or if you export nothing. Local-first shifts responsibility to you along with the control. #### Where the recording actually lives while you record **Direct Answer:** In your browser's own storage on that device — written incrementally as the recording proceeds, so a long take is not held entirely in memory. Screencast writes the video out in pieces as they arrive rather than accumulating the whole recording in memory and saving at the end. That is what makes long recordings practical, and it is also what makes partial recovery possible if something interrupts you. Before recording starts, Screencast asks the browser to mark that storage as persistent and checks how much room is available. If less than roughly 150 MB is free, it warns you, because a recording that exhausts the quota part-way through may not be fully recoverable. If you reload the page or the tab crashes, Screencast looks for a saved recording on the next visit and offers it back — either the completed video or the portion that had been written before the interruption. Annotations drawn during the recording are restored with it. Private or incognito windows change this. Browser storage there is discarded when the window closes, and some configurations disable it entirely. Recording still works, but recovery does not, so treat a private window as a single-session tool. #### What the website does measure **Direct Answer:** The site uses Google Analytics for ordinary visit information, subject to the consent settings described in the privacy policy. The recording media is not included in those analytics calls. This is the important exception to the shorthand "nothing leaves your device". Analytics can report a page visit and browser or device information allowed by its configuration and your consent state. The app does not attach recording blobs, captured frames, microphone tracks, filenames, or recording duration to its analytics configuration. The distinction worth holding onto is between the website and the recorder. The website is a normal website and behaves like one. The recorder is a local tool that happens to be delivered by that website. Our privacy policy sets out the service used and the regional consent defaults. Browser privacy controls or a content blocker may also restrict analytics; those controls do not form part of the recording pipeline. #### Your browser is the thing enforcing this **Direct Answer:** Screencast cannot see any screen, camera, or microphone you have not explicitly granted through your browser's own prompts, and the choice of what to share is made in the browser's dialog, not ours. When you start a screen recording, the picker that appears belongs to your browser. Screencast cannot pre-select an option, cannot see the list of your open windows, and receives nothing but the single surface you chose. Camera and microphone are requested separately and only when you have those sources switched on. Recording your screen with the microphone off involves no microphone permission at all. You can stop an active screen share from the browser interface and manage camera or microphone access in the site-permission controls. The exact icon and wording vary by browser. #### How to keep a recording you care about **Direct Answer:** Export it and move the file somewhere you actually back up. Browser storage is working space, not an archive. Screencast keeps your most recent recording so you can come back to it, but that is convenience, not durability. Clearing browsing data, a browser storage-pressure eviction, a profile reset, or switching devices will all take it away without warning. Export as soon as you know the take is good, and treat the exported file the way you treat any other important file — into your documents, a synced folder, or wherever your backups actually run. Use Clear saved when you are finished, particularly on a shared or work machine. It removes the stored recording from that browser deliberately rather than leaving it for the next person or the next eviction. #### When a local-first recorder is the wrong choice **Direct Answer:** When you need shared team libraries, automatic transcripts, viewer analytics, comment threads on the video, or a link you can send without sending a file. Those are genuine features and they require a server by definition. A tool that keeps everything on your device cannot offer them, and it would be dishonest to imply otherwise. Screencast is aimed at the large category of recordings that do not need any of that: a bug report, a walkthrough for one colleague, a demonstration attached to a ticket, a quick explanation instead of a long message. For those, a hosted library is overhead you pay for in accounts, uploads, and retention policies. If your organisation requires that recordings never touch third-party infrastructure, the local-first model is the point rather than a limitation — but confirm your own compliance position rather than taking a website's word for it. --- ### Guide: How to record a single browser tab with audio - **Canonical URL**: https://onlinescreencast.com/guides/record-browser-tab/ - **Last Reviewed**: 2026-10-02 - **Summary**: Record one browser tab instead of your whole screen, capture tab audio, understand what a tab recording cannot follow, and frame it for where the video is going. - **Verification Scope**: Tab-selection and audio statements were checked against the current getDisplayMedia request and browser screen-capture documentation. The guide treats shared audio as browser-provided rather than guaranteed. #### Why record a single tab rather than the screen **Direct Answer:** A tab recording contains only that tab. Notifications, your other monitors, your menu bar, your bookmarks, and everything else on the desktop are excluded automatically, without any editing. For a demonstration that stays inside one web page, this is often the most focused choice. It excludes other applications and displays from the captured surface. File size and processor use still depend on the selected tab, its dimensions, motion, and the browser encoder. It is also the most privacy-preserving option available. If you are recording something for a customer or a public audience from a machine that also has your email open, sharing a tab removes an entire category of risk rather than relying on you to remember to close things. On macOS, tab audio in a current Chromium browser is generally more predictable than whole-system audio. The share picker still decides whether audio is offered, so confirm it with a short test. #### Recording a tab, step by step **Direct Answer:** Open what you want to record in its own tab, set your sources in Screencast, press record, and choose the Chrome Tab or Browser Tab section of the share picker rather than Entire Screen. Set everything before you press record. Screencast locks its controls the moment recording begins, so the mode, microphone, system-audio toggle, frame, background, and camera layout all need to be right beforehand. When the share picker appears, look for the tab section — Chrome and Edge separate entire screens, windows, and tabs into distinct groups. Select the tab you want, tick the tab-audio checkbox if the page makes sound you need, and share. Screencast will confirm what you selected with a notice naming the browser tab. If it does not say that, you shared something else, and it is worth stopping immediately rather than discovering it later. Use the start delay if you need a moment to switch to the tab and get the cursor into position. Three or five seconds is usually enough to avoid opening the video on the Screencast interface. #### Capturing the tab's audio **Direct Answer:** Turn on System audio in Screencast before you record, then include tab audio in the browser's share dialog when that option is offered. Screencast can record only the audio track the browser returns. The Screencast toggle requests shared audio. The browser controls the picker and may show a checkbox or another audio control. If the selected stream has no audio track, Screencast cannot add one afterwards. Tab audio and microphone narration can both be on. Screencast mixes them into a single track before recording, which keeps the file simple but means the balance you set beforehand is the balance you keep. If you plan to talk over a video, lower the video first. When the browser supplies tab audio, it is intended to cover the selected tab rather than unrelated applications or system alerts. Browser and operating-system behavior should still be verified before an important recording. Confirm it worked before you record anything long. Record fifteen seconds, open the review panel, enable preview audio, and listen. The live preview is muted during recording by design, so silence while capturing tells you nothing. #### What a tab recording cannot do **Direct Answer:** It cannot follow you. Switching to another tab, another window, or another application leaves the recording showing the tab you selected — not what you moved to. The surface is fixed when you share and cannot be widened afterwards. If the workflow you are demonstrating crosses from a web app into a terminal, a desktop application, or a second browser window, you need to record an entire screen instead. This includes things that feel like part of the same page. A file-picker dialog, a native print preview, an operating-system permission prompt, and a browser extension popup are all outside the tab and will not appear. A page that opens a new tab mid-demonstration will lose you too. If your flow includes an external sign-in, a payment provider, or anything that opens a second tab, record the screen. Decide which of these applies before you start. There is no way to convert a tab recording into a screen recording after the fact, and a long take discovered to be missing the important half is the most expensive mistake available here. #### Framing a tab recording for where it is going **Direct Answer:** Leave the frame on Original for documentation and tickets. Use 16:9 for anything that will be embedded or presented, and 9:16 or 4:5 for a social or mobile destination. Original captures the tab at its natural dimensions with no cropping or padding, and it is also the cheapest option because Screencast can pass the capture through without composing each frame. For a bug report or a walkthrough attached to a ticket, that is all you need. A fixed frame letterboxes the capture into the shape you chose rather than cropping content out, so nothing is lost — but a wide browser tab placed into a 9:16 frame ends up small. If a vertical output is the goal, narrow the browser window before recording so the content fits the shape. Backgrounds and padding sit behind the composed frame and give a tab recording a deliberate look for a presentation or a landing page. They also turn on the compositor, so leave them off when you want the lightest possible recording. Make the content bigger before you record rather than expecting viewers to zoom. Increasing the page zoom to 125 percent or raising the font size in the application costs nothing and is the difference between a readable recording and an unusable one on a laptop screen. #### Preparing the tab itself **Direct Answer:** Use a clean profile or a fresh window: no unrelated bookmarks, no signed-in personal accounts, no autofill about to suggest something you did not intend to show. The tab recording captures the page, and on most browsers the bookmarks bar and tab strip of that window as well. A bookmarks bar is a surprisingly effective way to leak what you are working on. Autofill and browser password suggestions appear over the page and are captured with it. If your demonstration involves typing into a form, check what your browser will offer before you record it. Sign in as a test user rather than as yourself where the application allows it. Real names, real email addresses, and real customer data in a recording that gets shared onward is the most common cause of a recording having to be redone. Close the developer tools unless they are the point. They take up frame space and shrink the content everyone actually came to look at. --- ### Guide: How to record your screen on Mac with audio and camera - **Canonical URL**: https://onlinescreencast.com/guides/screen-record-on-mac/ - **Last Reviewed**: 2026-10-02 - **Summary**: Record a Mac screen, window, or browser tab with optional microphone or browser-provided shared audio, add a camera overlay, and export WebM or MP4. - **Verification Scope**: Mac-specific claims were checked against Screencast's capture constraints and current browser documentation. Because share-picker options vary, the guide recommends a test recording instead of promising whole-system audio, native resolution, or a fixed export time. #### Getting started with screen recording on Mac **Direct Answer:** Screencast runs in a desktop browser, so it does not require a recorder installation. A current Chrome or Edge release provides the most complete path through screen capture, composition, and local export. macOS and the browser jointly control screen-capture permission. A browser recorder is convenient for a file-based workflow, but a dedicated desktop recorder can offer deeper audio routing, editing, and operating-system integration. Safari supports web screen capture, but its available audio and local encoding paths differ from Chromium browsers. Test the exact screen, camera, audio, and export combination you intend to use rather than assuming feature parity. The first time you record, macOS will ask you to grant screen recording permission to your browser. This is a one-time system-level permission. Go to System Settings > Privacy & Security > Screen Recording, and ensure your browser is checked. You may need to quit and restart the browser after granting this permission for it to take effect. Screencast requests the browser's standard screen-capture and media-device APIs. It does not ask you to install a helper application, extension, or system component. #### Choosing between entire screen, window, or browser tab **Direct Answer:** When you start recording, the browser presents a share picker. Choose an entire screen for workflows that cross applications, a window for one application, or a browser tab for web content and optional tab audio. The share picker belongs to the browser and operating system, not Screencast. Screencast cannot preselect a surface or see the list of available screens and windows. Picker layout and labels vary by browser. Entire Screen captures everything: your desktop, all applications, all windows, the menu bar, notifications, and anything else visible on that display. If you have multiple monitors, you will see a thumbnail for each one and can choose which to record. Choose entire screen when your demonstration involves switching between applications, showing system preferences, or when you need to capture more than one window. Window sharing captures the selected application window rather than the rest of the desktop. Choose it when the demonstration stays in one application and you want unrelated windows and notifications excluded. Test window movement or resizing if it is part of your planned take because capture behavior can vary. Browser tab sharing captures one selected tab and may include that tab's audio when the browser offers the option. The recording remains tied to the selected tab when you view other tabs or windows. A narrower share surface often produces a cleaner recording and reduces accidental disclosure. Dimensions, motion, codec, and browser settings all affect performance and file size, so a window or tab is not guaranteed to create a smaller file. #### Recording microphone and system audio on Mac **Direct Answer:** Microphone recording works in current Mac browsers when permission and an input device are available. Shared audio is more limited: Chromium browsers commonly offer audio for a shared tab, while whole-system audio may not be available. Microphone audio is straightforward: when you enable the microphone toggle in Screencast and start recording, your browser will ask for microphone permission. Grant it once, and thereafter your voice will be captured along with the video. Microphone audio works with screen sharing, window sharing, and tab sharing equally. System audio—the sound coming from your Mac, such as application notifications, video playback, or game audio—is more complicated. macOS does not provide a system-wide audio capture API that browsers can access directly. This is a deliberate privacy design by Apple: applications cannot silently record all system audio. In Chromium browsers, sharing a browser tab commonly provides an option to include that tab's audio. Whole-system audio for an entire screen is not consistently exposed on macOS, so do not depend on a "Share system audio" checkbox being present. What is offered depends on the browser release, macOS version, selected share surface, and device policy. Screencast can request audio but cannot create an audio track that the browser does not return. If application or whole-system audio is essential and the browser does not offer it for your chosen surface, use a desktop recorder with an audio-routing option and test it before the real take. Tab audio is a separate case: current Chromium browsers commonly offer an option to include audio from the selected tab. Turn on shared audio in Screencast, enable the option in the share picker when present, and verify the returned track with a short recording. #### Adding your webcam to screen recordings **Direct Answer:** Screencast can compose your webcam over your screen recording, showing your face while you demonstrate. Choose "Screen + Camera" mode, configure the camera layout and size, then share your screen and grant camera permission when recording starts. When you select "Screen + Camera" mode and start recording, the browser requests screen and camera access. If both streams are available, Screencast composites the camera over the screen in real time. Device policy, another application, or a disconnected camera can still prevent access. Camera layout options include Corner (camera in a small rectangle at the bottom-right), Circle (camera in a circular frame), and Side (split-screen with camera on the right). Three sizes (Small, Medium, Large) let you balance between showing your face and keeping screen content visible. Experiment with these before recording to find what works best for your content. The Mirror toggle flips your camera horizontally. Use this when you are reading text or showing objects to the camera and want the image to appear correctly oriented to you while recording. If you are using a teleprompter or reading from notes positioned near the camera, mirroring helps you see yourself as others would see you. Camera and screen are composited in real-time during recording, not added in post-processing. This means the performance impact happens while recording—your Mac needs to handle both capturing the screen and processing the camera feed simultaneously. On older Macs or during intensive screen recordings (4K, high frame rate), this can cause the recording to drop frames or lag. If you experience performance issues, reduce the camera size or record screen and camera separately, then combine them in a video editor. Privacy consideration: if you share your entire screen while recording with camera, notifications and desktop elements will be visible in the recording. Consider using window sharing when recording with camera to keep your desktop private, though this means system audio will not be available. #### Recording quality, resolution, and frame rate on Mac **Direct Answer:** Screencast asks the browser for capture at up to 30 frames per second. The browser decides the actual dimensions, frame rate, codec, and bitrate for the selected screen, window, or tab. A Retina display does not guarantee that the recorded track uses the panel's full physical pixel dimensions. Inspect the exported file to confirm the dimensions supplied by the browser for the selected surface. File size varies with duration, dimensions, motion, audio, codec, and the browser-selected bitrate. Make a one-minute test with the intended settings and use its file size to estimate a longer recording. Screencast warns when the browser reports that storage is running low. The capture request sets 30 frames per second as an ideal and maximum value. The actual track may run below that rate when the source, browser, or device cannot maintain it. Recording a smaller window can reduce the number of pixels the browser has to encode, but the resulting file size also depends on motion, codec, bitrate, and duration. Inspect a short test file instead of predicting size from dimensions alone. macOS display scaling and browser capture constraints can affect the dimensions returned for a shared surface. Screencast does not force a particular pixel size; inspect the exported file when exact dimensions matter. #### Keyboard shortcuts for Mac recording **Direct Answer:** Use R to start or stop recording, Space to pause and resume, and P to toggle the annotation pen while the Screencast page has keyboard focus. These shortcuts are handled by the Screencast page. They work only while that page or its browser window has keyboard focus; they are not global macOS shortcuts. R starts a recording or stops the active recording. Return to Screencast before pressing it so the page receives the key event. Space (the spacebar) pauses and resumes recording without splitting the file. If you need to pause mid-recording to set up the next step, collect your thoughts, or handle an interruption, press Space to pause, then press Space again to resume. The final exported video will be continuous with the paused time removed. P (letter P) toggles the annotation pen on and off. When the pen is active, you can draw on the recording in real-time to point out interface elements, circle important areas, or add visual emphasis. Press P again to turn the pen off and return to normal cursor control. The handlers ignore key presses with Command, Control, or Option held and ignore typing inside form fields. If a shortcut does nothing, click the Screencast page and try again. #### Exporting recordings to WebM or MP4 on Mac **Direct Answer:** Export WebM for instant results—it is the native recording format. Export MP4 when you need compatibility with iMovie, Final Cut Pro, Keynote, or other Mac applications that prefer MP4. MP4 conversion runs entirely on your Mac. WebM export is instant because Screencast records in WebM format. No conversion happens—it is just a direct save of the file your browser created. Use WebM when sharing on the web, uploading to platforms like YouTube (which accepts WebM), or when you need the file immediately. MP4 export converts the WebM recording locally using WebCodecs when a compatible encoder is available, or an in-page FFmpeg fallback. Conversion time varies with duration, dimensions, codecs, device performance, and other work running on the Mac. Choose MP4 when the receiving application does not accept the recorded WebM. Import support changes by application and version, so check the requirements of the editor, presentation tool, or device that will receive the file. WebM is the direct recording output. MP4 requires another encode, so quality and file size can differ. MP4 is often easier to use in Apple and presentation software, while WebM avoids the conversion step. The conversion happens entirely on your Mac. The WebM file is not uploaded—instead, your browser loads FFmpeg (a video processing library) or uses built-in WebCodecs APIs, reads the WebM file from browser storage, re-encodes it to MP4, and saves the result locally. This respects the same privacy guarantees as recording: your video never leaves your device. #### Screencast vs macOS Screenshot app (Command-Shift-5) **Direct Answer:** macOS Screenshot is a strong choice for quick, offline screen recordings. Screencast is useful when you need a camera composition, live annotation, framing options, or direct WebM and MP4 choices. Screenshot.app (accessed with Command-Shift-5) is built into macOS and requires no browser or internet connection. It records a screen or selected area and saves directly to your chosen location as a QuickTime .mov file. For a simple capture with no camera layout or browser export step, it is often the shorter workflow. Screenshot.app limitations: no camera overlay (you cannot show your face while recording your screen), no live annotation, no framing or background options, no format choice (it always saves .mov), and no built-in MP4 export. If you need to convert .mov to MP4, you must use QuickTime Player's export function or a separate conversion tool. Screencast advantages: camera compositing with layout options (corner, circle, side), live annotation (pen and arrow tools), framing for specific aspect ratios (square, vertical, widescreen), backgrounds and padding for composed recordings, and direct WebM/MP4 export. These matter when you are producing recordings meant to be shared, embedded in documentation, or posted online. Do not assume either workflow will capture all Mac system audio. Confirm the audio-input options available in the tool and make a short test. For dependable application-audio routing, a dedicated desktop recorder may be necessary. Use Screenshot.app for quick or offline captures. Use Screencast when you need a camera overlay, live annotation, a specific frame and background, or a choice between direct WebM and locally converted MP4. #### Troubleshooting common Mac recording issues **Direct Answer:** Most Mac recording issues stem from permissions (screen recording, microphone, camera), browser choice (Safari limitations), or system audio configuration. Check System Settings permissions first, use a Chromium browser, and verify that applications are unmuted. If recording does not start: check System Settings > Privacy & Security > Screen Recording and ensure your browser is listed and checked. You may need to quit and restart the browser after enabling this permission. If the browser is not listed at all, try starting a recording anyway—macOS will add it to the list when it requests permission. If there is no microphone audio: check System Settings > Privacy & Security > Microphone and ensure your browser has permission. Also verify that you toggled Microphone ON in Screencast (it is on by default but can be turned off). Test your microphone in another application to confirm it is working. If there is no shared audio: try sharing the browser tab that produces the sound in a current Chromium browser and enable its audio option in the share picker. macOS may not offer whole-system audio for screen or window sharing. If the browser returns no audio track, Screencast cannot add it later. If the recording is laggy or choppy: close unnecessary applications to free CPU and memory, lower the recording resolution by sharing a window instead of entire screen, and ensure your Mac is plugged in (not running on battery). Very high-resolution recordings on older Macs may drop frames. If the camera does not appear in Screen + Camera mode: check System Settings > Privacy & Security > Camera and ensure your browser has permission. Test the camera in another application (Photo Booth, FaceTime) to confirm it is working. External USB cameras may require reseating the USB connection. If MP4 export fails: try exporting WebM instead (instant), close other browser tabs to free memory, or wait for the current export to complete before starting another. The export happens locally on your Mac and can be memory-intensive for very long or high-resolution recordings. --- ### Guide: Record screen with audio: microphone and shared audio setup - **Canonical URL**: https://onlinescreencast.com/guides/screen-recorder-with-audio/ - **Last Reviewed**: 2026-10-02 - **Summary**: How to record microphone narration and browser-provided shared audio. Understand browser and operating-system limits, quality settings, and troubleshooting. - **Verification Scope**: Audio claims were checked against the recorder's MediaRecorder configuration and the Screen Capture API documentation. No fixed bitrate, sample rate, or shared-audio source is promised because the browser controls those details. #### Understanding audio recording: microphone vs system audio **Direct Answer:** Microphone audio comes from an input device. Shared audio comes from the tab, window, or screen selected in the browser, but only when the browser and operating system provide an audio track for that surface. Microphone recording is the most common audio source for screen recordings. Current desktop browsers generally support it, but access still depends on site permission, device policy, an available input, and whether another application has exclusive control of the device. Whole-system audio refers to the computer's output, while tab audio is limited to a selected browser tab. A share picker may offer one, the other, or no shared-audio option depending on the selected surface and platform. The distinction matters because the sources use different browser APIs. Microphone access uses getUserMedia; shared audio is an optional part of the stream returned by getDisplayMedia. Permission, policy, and device availability can affect both. Most screen recordings use microphone-only audio: you are narrating what you are demonstrating. System audio is needed when the demonstration itself produces sound you want to capture—recording gameplay, demonstrating audio software, capturing a video call (with participants' permission), or showing how a sound effect triggers in an application. #### Setting up microphone recording **Direct Answer:** Enable the Microphone toggle before starting. The browser then requests access to its current default input, and Screencast includes the returned track in the recording. The Microphone toggle is on by default in Screencast, so if you do nothing, microphone audio will be included. If you want to record without narration, toggle it off before starting. Once recording begins, this cannot be changed—you cannot add or remove microphone audio mid-recording. Permission persistence varies by browser and policy. If access was denied, open the browser's site settings, restore microphone permission, reload, and try again. Microphone level is controlled outside Screencast. Make a short recording at your normal speaking volume and listen for quiet audio, clipping, or the wrong input device before recording the real take. Use headphones while recording to prevent echo and feedback. If your microphone picks up the sound from your speakers (system audio, video playback, etc.), it will be recorded along with your voice, creating an echo effect. Headphones isolate your voice from system sounds, producing a cleaner recording. If several inputs are connected, choose the intended device in your operating-system or browser settings before starting. Screencast currently requests the browser's default input rather than presenting its own device selector. #### System audio support by browser and operating system **Direct Answer:** Shared audio is offered by the browser for particular share surfaces. Chromium browsers commonly support tab audio, while whole-system or window audio depends on the browser, operating system, and the option selected in the share picker. On Windows, current Chromium browsers often offer a system-audio option when an entire screen is selected. Tab sharing can offer audio from the selected tab. The exact checkbox and available source are controlled by the browser and may be restricted by enterprise policy. On macOS, Chromium browsers commonly offer audio for a shared browser tab, but whole-system audio may not be offered. Safari and Firefox have different capture capabilities and should be tested with the exact source you intend to record. On Linux, results depend on the browser and audio stack. PipeWire-based systems can expose more capture options than older configurations, but Screencast cannot force an audio track when the browser returns video only. The System audio toggle is a request to the browser, not a guarantee. After the share picker closes, Screencast can record only the tracks the browser returned. A short test recording is the reliable way to confirm the selected surface includes audio. If system audio is essential for your recording and your browser or operating system does not support it, consider using desktop recording software (OBS Studio on Windows/Mac/Linux, Screenshot.app on Mac, Xbox Game Bar on Windows) which have deeper system integration and more reliable system audio capture. #### Recording browser tab audio **Direct Answer:** A browser may offer an option to include audio from a shared tab. When it does, enable that option in the share picker and verify the result with a short test recording. Tab audio is neither whole-system audio nor microphone audio. It is an optional track associated with the browser tab chosen in the share picker. To request it, turn on System audio in Screencast, select a browser tab in the share picker, and enable the picker's audio option when present. If the browser returns the tab's audio track, Screencast mixes it with the microphone when the microphone is also enabled. This is particularly useful for recording web-based demonstrations, capturing online meeting or webinar audio (with permission), recording streaming content for review, or demonstrating web applications that include audio elements. Tab audio keeps the recording focused on just that tab's content. Tab audio is intended to exclude other tabs, desktop applications, and system alerts. If you need broader audio, check whether the browser offers audio for an entire-screen share on your operating system; that option is not universal. Tab-audio support and share-picker wording change across browsers. Current Chrome or Edge is the most predictable choice for this workflow, but the returned stream should still be tested before an important recording. #### Audio quality and recording settings **Direct Answer:** Screencast lets the browser choose the audio sample rate, codec, bitrate, and channel layout. The app does not promise a fixed 48 kHz or 128 kbps setting. Audio quality in screen recordings is typically "good enough" rather than audiophile-grade, and this is appropriate: the focus is on the visual content, with audio providing context and narration. High-fidelity audio would increase file size substantially with no perceptible benefit for typical screen recording use cases. The recorder does not pass an audio bitrate or sample-rate override to MediaRecorder. Browser defaults can vary with the input sample rate, channel count, codec, and browser implementation. Inspect the exported file if a downstream workflow requires a specific format. Shared audio may already be compressed at its source, and MediaRecorder encodes the final mixed stream. Do not assume that a recording is lossless or identical to the source audio. Background noise from your microphone is not filtered or removed. Record in a quiet environment, use a directional microphone if possible, and avoid recording near fans, air conditioning, or other noise sources. Some external microphones have built-in noise cancellation or cardioid pickup patterns that reduce background noise. Audio and video are passed to the same MediaRecorder stream, but overloaded devices and browser encoder problems can still produce drift or gaps. If synchronization matters, test with the intended resolution, audio sources, and recording duration. #### Recording both microphone and system audio together **Direct Answer:** Enable both toggles before starting. Screencast mixes the microphone with shared audio only when the browser successfully returns both tracks. Combined audio is useful when you are narrating over application sounds, demonstrating audio software, recording gameplay with your commentary, or showing how sound effects work in an application. Both your voice and the system audio will be captured and mixed into a single audio track in the recording. The mixing happens automatically and Screencast has no per-source level controls. Adjust the source and microphone levels before recording, then confirm their balance with a short test because platform capture levels vary. Be aware that if system audio is loud and your microphone is sensitive, the microphone may pick up sound from your speakers (echo/feedback) in addition to system audio being captured directly. Always use headphones when recording with both microphone and system audio to prevent this. Headphones isolate your microphone from speaker output. On some systems, particularly macOS, capturing both microphone and system audio can be unreliable. If you find that system audio is not being captured when both are enabled, try recording with system audio only, then record a separate microphone-only track, and combine them in a video editor. This gives you more control and works around browser/OS limitations. For professional recordings where audio quality is critical, consider recording audio separately using dedicated audio recording software (Audacity, GarageBand) while screen recording silently, then combining them in post-production. This gives you much more control over audio levels, noise reduction, and editing. #### Troubleshooting audio recording issues **Direct Answer:** Most audio problems stem from denied permissions, wrong input/output device selection, or system audio configuration. Check browser permissions, verify your microphone and speakers are selected correctly, and ensure system audio is supported on your platform. If there is no microphone audio in your recording: check that you enabled the Microphone toggle before starting, verify your browser has microphone permission (check site settings or the lock icon in the address bar), confirm your microphone is not muted in your operating system's audio settings, and test your microphone in another application to ensure it works. If there is no shared audio: confirm the System Audio toggle was enabled before starting, then check whether the browser share picker offered an audio option for the surface you selected. On Chromium, try sharing the specific browser tab that produces the sound. Whole-system audio may be available on some Windows configurations but should not be assumed on macOS or Linux. If audio is extremely quiet: check your microphone input level in system audio settings and increase it, verify your system audio output level is reasonable (30-70% volume), and ensure nothing in your audio chain (microphone, interface, system settings) is muted or set to minimum. If audio is distorted or crackling: lower your microphone input level to prevent clipping, reduce system audio output level if it is near 100%, close other applications that might be consuming audio resources, and check that your microphone is not physically damaged or having connection issues. If audio is out of sync with video: this usually indicates your system was overloaded during recording. Close unnecessary applications, record at a lower resolution, avoid recording while doing CPU-intensive tasks, and ensure your computer is plugged in (not on battery power). If this happens consistently, your hardware may not be powerful enough for real-time recording at the resolution you selected. If tab audio does not work: ensure the tab is playing audio before sharing, check that it is not muted, and confirm the browser share picker included an audio checkbox or label. Try a current Chrome or Edge release if your usual browser does not expose an audio track. #### Audio recording for specific use cases **Direct Answer:** Different recording scenarios require different audio approaches. Tutorials need clear narration (microphone-only), game recordings need both gameplay audio and commentary (microphone + system audio), and bug reports often need no audio at all. Tutorial and educational recordings: use microphone-only audio. System audio is usually just distracting background noise. Focus on clear narration explaining what you are demonstrating. Record in a quiet space, speak clearly at a moderate pace, and pause briefly between major steps. This produces the most professional-sounding instructional content. Game recordings and gameplay videos: use both microphone and system audio. Viewers want to hear the game audio (music, sound effects, dialogue) alongside your commentary. Balance the levels so your voice is clearly audible over the game audio—if necessary, lower the game's audio in its settings before recording. Software demonstration and product tours: microphone-only unless the software itself produces important audio cues. Most productivity software demonstrations do not need system audio—viewers are watching what you are clicking and hearing your explanation. Bug reports and issue reproduction: often no audio is needed. If you are showing a visual bug or broken workflow, the video alone is sufficient. Adding microphone narration can be helpful ("Notice how the button doesn't respond when I click it"), but system audio is rarely relevant. Meeting and presentation recordings: if recording a video call or webinar, tab audio captures the other participants' voices if you share the meeting tab. Add microphone audio if you are also speaking. Note that recording others requires their consent—do not record calls without permission. Music and audio software demonstrations: system audio is essential. Consider recording system audio only without narration, or record your spoken explanation separately and combine them later. This ensures the audio being demonstrated is captured clearly without your voice overlapping the sounds you are trying to show. --- ### Guide: Screen recorder without watermark: clean recordings - **Canonical URL**: https://onlinescreencast.com/guides/screen-recorder-without-watermark/ - **Last Reviewed**: 2026-10-02 - **Summary**: How Screencast avoids adding a logo or promotional frame, how to verify an exported video, and what else to compare when choosing a recorder. - **Verification Scope**: Watermark claims were checked against the current WebM save path and local MP4 conversion path. Time-sensitive competitor plan claims were removed rather than presented without current primary evidence. #### What "no watermark" actually means for your recordings **Direct Answer:** Screencast never adds any logo, watermark, intro frame, credits, or branding to your exported videos. The video file contains exactly and only what you captured, with no overlays or modifications added during export. Many free screen recorders stamp a logo in the corner of every video, add a branded intro screen before your content, or overlay text like "Made with [Tool Name]" across the bottom. These watermarks serve as advertising for the tool and make your videos look unprofessional, turning your work product into a vehicle for someone else's marketing. Screencast does not add branding to recorded frames. WebM export saves the browser recording, while MP4 export re-encodes it locally into a different format. Neither path adds a Screencast logo, intro, or promotional text. This matters for professional use cases: client presentations, bug reports to customers, educational content for your students, portfolio pieces, product demonstrations, and documentation all benefit from clean recordings that represent your brand or organization, not a third-party tool's branding. If you compose a recording with a frame and background in Screencast—16:9 frame with a gradient background, for example—those design choices are part of your recording, visible in the preview, and intentionally added by you. They are not watermarks; they are your composition. If you record with Original framing and no background, the video contains only your captured screen content with absolutely nothing added. #### Why most free screen recorders add watermarks **Direct Answer:** Watermarks are a monetization strategy. Free tiers include watermarks to encourage users to upgrade to paid plans that remove them. Tools also use watermarks to gain brand exposure when free users share watermarked videos. The freemium model—free tier with limitations, paid tier without them—is common in screen recording software. The watermark is one of the most visible limitations, designed to be annoying enough to motivate upgrades but not so restrictive that users abandon the tool entirely. Every watermarked video shared publicly advertises the tool to potential new users. From a business perspective, this makes sense for tools that need to cover server costs, support teams, and development. If they are hosting your recordings, managing accounts, and processing videos on their infrastructure, they need revenue. The watermark becomes both a conversion funnel (upgrade to remove it) and marketing channel (every free user's videos promote the tool). Screencast can avoid watermarks entirely because it has no per-user server costs to recoup. Your recordings never upload, there is no cloud storage or processing to pay for, and there are no usage-based expenses. The tool's costs are fixed (hosting the static website) rather than variable (scaling with your usage), so there is no financial pressure to convert free users or use their videos as advertising. This creates a better situation for users: your recordings represent you and your work, not the tool you used to make them. You can share them with clients, embed them in professional documentation, or post them publicly without advertising someone else's product. #### Verifying the exported video has no watermarks **Direct Answer:** You can verify that Screencast adds no watermark by examining the exported video file. Open it in any video player or editor, scrub through the entire recording, and check all corners and edges—you will find only your captured content, nothing added. The easiest verification is simply watching the exported video. Play it back in VLC, QuickTime, Windows Media Player, or any video player. Scrub through the entire duration, paying attention to all four corners and the top/bottom edges. If there were a watermark, you would see it—logos typically appear in corners, text overlays across the bottom or top. Open the video in a video editor (DaVinci Resolve, Adobe Premiere, iMovie, CapCut) and look at the video on the timeline. Watermarks are part of the video frames themselves, so they would be visible in the editor's preview. If you see only your screen content, there is no watermark. You can inspect the file in a media tool to see its video, audio, codec, dimension, and encoder metadata. The current export implementation does not intentionally add a branding track, subtitle track, or Screencast promotional tag. WebM is saved from the browser recording. MP4 passes through a local conversion pipeline, but that pipeline does not render a Screencast watermark. The useful verification is visual: review the exported file before publishing it. #### Professional use cases that require watermark-free recordings **Direct Answer:** Client-facing deliverables, educational content, product demonstrations, bug reports, marketing materials, and portfolio work all require clean, unbranded recordings. Watermarks undermine credibility and distract from your content. Client presentations and demonstrations: when showing a client how your software works, walking them through a solution, or demonstrating project progress, a watermark brands the recording with someone else's product rather than presenting it as your professional work. Clients expect polished deliverables, and a watermarked video signals amateur tools or corner-cutting. Educational content and tutorials: teachers, instructors, and content creators producing course materials need clean recordings that focus students on the content, not on the tool used to create it. A watermark in a 20-minute tutorial video is a constant distraction, pulling attention away from what is being taught. Bug reports and issue reproduction: when submitting a bug report to a client, partner, or open-source project, a watermark makes the report look less professional and suggests the reporter is using free/limited tools. More importantly, watermarks add visual noise to the bug demonstration itself—viewers should focus on the issue you are showing, not on overlay text. Marketing and product demos: companies creating product videos, feature announcements, or marketing materials cannot use watermarked recordings. Those videos represent the company's brand, and third-party watermarks dilute that branding. Watermark-free recordings are essential for any content that will be published under a company's name. Portfolio work and case studies: designers, developers, and other professionals showcasing their work in portfolios or case studies need clean screen recordings of their projects. A watermark turns a portfolio piece into an advertisement for someone else's tool, undermining the professional presentation. Documentation and knowledge bases: technical documentation, help articles, and internal wikis often include screen recordings to show procedures step-by-step. Watermarks serve no purpose in this context and add clutter to what should be clear, focused instructional content. #### How to export watermark-free recordings from Screencast **Direct Answer:** After recording, press "Stop and Review" to open the editor, verify your take, then press "Export WebM" or "Export MP4" to download the video file. Both formats produce clean, watermark-free videos—choose based on your next step. Exporting is straightforward: once you stop a recording, it opens in the editor panel where you can review it. Play it back to verify the take is good, the audio is clear, and you captured everything you needed. When satisfied, choose an export format. Export WebM for instant results. WebM is the native recording format, so export is immediate—no conversion, no waiting. Use WebM when uploading to platforms that accept it (YouTube, many CMS systems), sharing on the web, or when you need the file immediately. WebM files are typically smaller than MP4 at equivalent quality. Export MP4 when the software receiving the file does not support WebM. Conversion runs on your device, and its duration varies with the recording, codec support, and device performance. Both WebM and MP4 exports produce watermark-free videos. There is no difference in whether a watermark is present—neither format has one. The choice is purely about compatibility and speed. If you are unsure, export MP4 for maximum compatibility. After export, the downloaded file is yours to use however you want: upload it, embed it, edit it further, share it with clients, post it publicly. There are no usage restrictions, no licensing fees, no attribution requirements. The video is your work, and you have complete control over it. #### Comparing watermark policies across screen recorders **Direct Answer:** Recorder plans and watermark policies change frequently. Compare the current provider documentation for watermarking, recording limits, export formats, storage, and account requirements before choosing a tool. Check whether the free plan adds visible branding, limits duration, reduces export resolution, restricts formats, or caps the number of stored videos. These are different limitations and should not be collapsed into a single "free" label. Desktop recorders can provide deeper operating-system integration and more control over audio and encoding, but require installation and configuration. Built-in operating-system tools are convenient for simple captures but may not include camera composition, live annotation, or multiple export formats. Screencast does not add its own watermark, does not require an account, and does not provide cloud storage or hosted share links. Browser and device limits still apply, and MP4 is produced by local conversion rather than direct browser recording. #### When you might actually want to add your own branding **Direct Answer:** If you are creating content to distribute publicly under your brand, you may want to add your logo or branding in post-production. Screencast gives you a clean recording to brand as you choose, rather than forcing third-party branding onto it. Content creators, course producers, and marketing teams often want to brand their videos with their own logo, intro sequence, or end cards. The difference is choice and control: you are choosing to add your branding in a way that represents your design, not having someone else's branding forced onto your content. Add branding in a video editor after export. Import your Screencast recording into DaVinci Resolve, Adobe Premiere, iMovie, or another editor, then add your logo in a corner, create a custom intro/outro, insert title cards, or overlay your brand colors and design. This gives you full control over placement, timing, and appearance. Why this is better than built-in watermarks: you choose where the logo appears, how large it is, and for how long. You can brand some recordings and not others. You can match your brand guidelines precisely. And most importantly, the branding represents YOU, not a third-party tool. For educational content, consider whether branding is even necessary. Most instructional recordings benefit from being as clean and distraction-free as possible. Students focus better when the video contains only the content being taught, not logos, watermarks, or other visual noise. Add branding only if it serves a purpose—brand awareness, copyright protection, or professional presentation standards in your field. #### What about hidden watermarks or metadata? **Direct Answer:** The current Screencast implementation does not intentionally add a hidden watermark, tracking pixel, user identifier, or promotional metadata tag to exported recordings. Hidden watermarks are invisible marks embedded in video frames that can survive re-encoding and identify the source. Some tools use these for piracy prevention or usage tracking. Screencast does not. The video frames contain only your screen recording, with no invisible data or steganographic information. Video containers normally include technical metadata such as dimensions, codec, duration, and encoder information. Exact fields depend on the browser and the local MP4 conversion path. Screencast does not attach an account ID because the recorder does not use accounts. You can inspect a video file's metadata with MediaInfo, ExifTool, or FFprobe. Check the actual export rather than relying on a fixed list of fields, since the browser and encoder version can change the container metadata. This reflects the same privacy-first approach as the rest of the tool: your recordings are yours, contain only what you put in them, and carry no hidden tracking or identification that could link them back to the tool or to you beyond what you choose to include. #### Ownership and licensing of your watermark-free recordings **Direct Answer:** You own your recordings. Screencast makes no claim to ownership, does not require attribution, and imposes no licensing restrictions on how you use the exported video files. They are your work product to use commercially or otherwise as you see fit. Unlike some free tools that claim rights to content created with them or require attribution in exchange for free use, Screencast's terms are simple: you own what you record, period. There is no requirement to credit Screencast, no license grant back to the tool, no restrictions on commercial use. This matters for professional and commercial use. You can sell products that include Screencast recordings (courses, tutorials, documentation), use them in client work, include them in paid presentations, distribute them commercially, and exercise complete ownership without attribution or licensing complications. The reason this is possible is the same reason there are no watermarks: Screencast never sees your recordings, so there is no mechanism by which it could claim any rights to them. The recordings are created on your device, stored on your device, and exported from your device. Screencast the tool facilitates the recording, but the content never passes through any Screencast infrastructure that could theoretically claim involvement. Compare this with cloud recording tools where you upload your content to their servers. Those tools often include terms granting them certain rights to your content—the right to display it (for hosted playback links), the right to process it (for transcription, compression, analytics), sometimes even broader rights. When content never leaves your device, none of those rights grants are necessary or possible. --- ### Guide: Screen recording troubleshooting - **Canonical URL**: https://onlinescreencast.com/guides/screen-recording-troubleshooting/ - **Last Reviewed**: 2026-10-02 - **Summary**: Fix the common browser screen-recording failures: the wrong surface captured, silent recordings, blocked permissions, frozen camera overlays, failed exports, and interrupted takes. - **Verification Scope**: Troubleshooting steps were checked against the current capture, chunk recovery, and export paths. Browser-controlled audio and encoder behavior are described as conditional rather than guaranteed. #### The recording shows the wrong thing **Direct Answer:** You selected a single tab or window in the browser's share picker, and the recording stayed on that surface when you switched applications. The share surface is fixed once recording starts. This is the most common failure and the most expensive, because it usually is not noticed until playback. What you saw on your own screen while recording is not what the recording captured — the recording only ever contained the surface you chose. Screencast reads the surface back from the browser and shows a notice naming it in the first seconds: entire screen, a window, or a browser tab. Get into the habit of reading that notice before you start talking. There is no fix after the fact. Stop, start again, and choose Entire Screen in the picker. Choose it by default for anything that moves between applications; choose a narrower surface only when the tighter framing is deliberate. #### There is no sound in the recording **Direct Answer:** Check whether the browser's share dialog offered and enabled audio for the surface you selected. Enabling System audio in Screencast requests a shared-audio track but cannot make the browser provide one. The Screencast toggle and the browser's audio control perform different jobs. Screencast requests audio; the browser and operating system decide whether the chosen tab, window, or screen can return it. If it is microphone audio that is missing, check which input your operating system currently considers default. Connecting headphones, a monitor with a built-in microphone, or joining a call can change it silently. Then check whether another application is holding the microphone. Video-conferencing tools frequently keep the device claimed after a call ends; quit the application rather than just leaving the meeting. On macOS, whole-system audio is not consistently offered to browser capture. Sharing a browser tab with its audio enabled in a current Chromium browser is usually the more predictable route for web content. #### The browser will not ask for permission **Direct Answer:** A previous denial is remembered. Clear it from the padlock or camera icon in the address bar, reload the page, and start again. Once you deny screen, camera, or microphone access for a site, browsers generally stop asking and simply fail. Because the prompt never reappears, this looks like the recorder is broken rather than blocked. Open the site settings from the icon at the left of the address bar, set the relevant permissions back to Ask or Allow, then reload. The prompt returns on the next attempt. On macOS there is a second layer: the browser itself needs Screen Recording permission in System Settings under Privacy & Security. If no browser can capture your screen, this is almost always why, and it requires quitting and reopening the browser after you grant it. #### The camera overlay froze or disappeared **Direct Answer:** Composed recordings depend on the browser continuing to deliver camera frames. Some browsers throttle that work heavily when the tab is not visible, and annotation makes the page more sensitive to it. Screencast avoids the common animation-loop freeze by driving the composite from video frames rather than a page animation timer, which is why a plain Screen and camera recording generally survives being in the background. Annotations are the exception: keep Screencast visible while you draw so the overlay stays in sync with the video. If the overlay stops mid-recording, Screencast tells you and the take cannot be repaired. Start a new recording rather than continuing, because everything after the failure will be missing the camera. Reduce the load if this recurs. Recording a single window rather than an entire multi-monitor desktop, leaving the frame on Original, and closing other heavy tabs all cut the per-frame work substantially. #### Export will not finish **Direct Answer:** Export WebM instead — it is the format the recording is already in, so it completes immediately and your work is safe. Then convert to MP4 separately if you need it. MP4 is a separate conversion step. Screencast first tries a compatible WebCodecs encoder and then an in-page FFmpeg fallback. An encoder can be unavailable, reject the input, or fail to produce output; the saved WebM remains available in those cases. Keep the tab open and in the foreground while a conversion runs. It is executing in that page; navigating away cancels it. If the conversion completed but no file appeared, use Download MP4 again rather than re-converting. Screencast holds the finished file in the page, so a blocked download does not cost you the processing time. Long recordings and limited available memory can make conversion harder. Closing other heavy tabs may help. A current Chrome or Edge release may expose a compatible WebCodecs path, but the browser can still use software encoding or fall back to FFmpeg. #### The tab closed or the browser crashed mid-recording **Direct Answer:** Reopen Screencast. It looks for a saved recording on load and offers back either the completed video or the portion written before the interruption. Because the video is written to browser storage in pieces as it records rather than held in memory until the end, an interrupted recording usually leaves a usable partial file. Annotations drawn during the recording are restored alongside it. Recovery is per-browser and per-device. A recording made in Chrome will not appear in Firefox, and one made on your laptop will not appear on your desktop. Private and incognito windows discard their storage when the window closes, so nothing is recoverable there. If a recording matters, do not make it in a private window. If Screencast warned you about low storage before recording, expect recovery to be less reliable. That warning appears when under roughly 150 MB is free, which a long recording will exhaust. #### The recording is choppy or the machine struggles **Direct Answer:** Reduce what has to be composed per frame: record a single window rather than every monitor, leave the frame on Original, and turn off background and padding unless you need them. Screencast takes a shortcut when it can. A single source with the frame on Original, no background, no padding, and no annotation is passed straight through from the browser's capture track with no per-frame compositing at all. That is by a wide margin the cheapest way to record. Every setting that changes the picture — a fixed aspect ratio, a background, padding, a camera overlay, annotations — turns on the compositor, which draws each frame. On a machine already under load, that is where dropped frames come from. Close what you are not demonstrating. Other browser tabs playing video, a running build, and video-conferencing software are the usual competitors for the same resources the encoder needs. Recording an entire multi-monitor desktop is the single most expensive option available, because the composed frame is as wide as all your displays combined. Share one display or one window instead. --- ### Guide: How Screencast guides are tested and maintained - **Canonical URL**: https://onlinescreencast.com/guides/testing-methodology/ - **Last Reviewed**: 2026-10-02 - **Summary**: Our process for checking product claims, documenting browser limitations, dating reviews, and correcting screen-recording guidance. #### What Screencast publishes **Direct Answer:** Our guides explain the recorder, the browser APIs it depends on, and the practical limits users may encounter. We publish a page when it answers a distinct user question. We do not set a target article length, split one answer into several pages to create more URLs, or publish a browser claim only because it appears on another screen-recording site. Product claims are limited to behavior that exists in the public recorder. Browser and operating-system claims are qualified because capture options can vary by browser version, device policy, hardware, operating system, and the surface selected in the share picker. #### How product claims are checked **Direct Answer:** We compare each claim with the current Screencast implementation and the relevant browser or platform documentation. Implementation checks confirm what the public code actually requests from the browser, what it stores locally, and which settings it passes to recording and export APIs. A guide should not promise a bitrate, resolution, frame rate, audio source, or conversion time that the implementation does not control. Platform checks use primary documentation such as MDN Web API references, web standards, and browser-vendor documentation. When support depends on the environment, the guide says so and recommends a short test recording rather than presenting a browser capability as universal. Hands-on results are identified as tests only when the exact browser, operating system, device, settings, and test date were recorded. Otherwise, the page describes implementation behavior and documented platform support, not a benchmark. #### Review dates and changing browser behavior **Direct Answer:** Every guide shows a publication date and a last-reviewed date so readers can judge how current the information is. Browser recording behavior changes. A browser update can add a capture option, remove an encoder, or change the labels in a share picker without any change to Screencast. We review compatibility content after meaningful recorder changes and when browser documentation changes. A last-reviewed date means the text was checked against the code and sources listed on the page. It does not guarantee that every browser and hardware combination was physically tested on that date. #### Corrections and reproducible reports **Direct Answer:** If a guide does not match what you see, send the page URL and enough environment details for us to reproduce it. Useful reports include the browser name and version, operating system version, recording mode, selected share surface, audio options, export format, and the exact result. Do not send a private recording unless you have removed confidential information. Email support@onlinescreencast.com with the subject "Guide correction". We update inaccurate claims and change the last-reviewed date when the correction is published. #### Advertising and editorial independence **Direct Answer:** Advertising does not determine the conclusion of a guide, and an ad placement is not presented as a recommendation. If advertising is enabled, ads are visually separated from recorder controls and editorial content. We do not accept payment to change a compatibility result or describe an unsupported feature as available. Comparisons avoid time-sensitive competitor pricing and plan details unless they are checked against the provider's current documentation and dated. Readers should verify another product's current terms before making a purchase decision. ---