Free screen recorder online: what Screencast includes

What "free" actually means with Screencast

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

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

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

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

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

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

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

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

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

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.