What is a screencast?

How screencasts are recorded

The capture itself is simple and built into most systems. On a Mac, Apple's support guide shows Shift Command 5 opening a toolbar to record the entire screen, one window or a selected portion, with a microphone option, saving a MOV file. OBS Studio, a free open source recorder, sets up scenes and sources for screen and camera capture, and TechSmith's Camtasia Recorder captures screen, microphone, system audio and camera on separate tracks for editing. In a browser, the Screen Capture API's getDisplayMedia method, documented on MDN, asks the user to choose a screen, window or tab to share. What separates a screencast from a raw recording is everything after the capture.

What makes a screencast easy to follow

Viewers are trying to copy what they see, so clarity beats polish. Record at a resolution where interface text is legible on a phone, and zoom in on small controls instead of expecting viewers to find them. Close notifications, clear private data and use a clean demo account. Move the pointer deliberately and pause on each control before clicking, since a fast cursor is hard to track. Name the exact label of every button in the narration. Cut loading waits and mistakes. Keep each video to one task, because a viewer searching for how to export a report does not want to sit through account setup first.

Screencast or screenshot based video

A continuous recording is essential when motion is the point: dragging items, drawing, animations, scrolling behaviour, or anything where the path between two states matters. For most step by step software help, though, the viewer only needs to see the screen at each step and where to click. A video built from one screenshot per step is quicker to make, has no dead time to edit out, and is easier to update, because a renamed button means replacing one image rather than re-recording the whole flow. It cannot show a transition or animation, so choose it for stable screens and linear tasks.

Common mistakes

Recording at a huge desktop resolution and letting it be scaled down turns interface text into mush on a phone. Narrating from memory without a list of steps produces pauses, backtracking and filler words. Leaving the whole desktop visible exposes browser tabs, bookmarks and messages that should not be public. Many screencasts also run too long by recording setup, logins and waiting rather than starting at the first relevant screen. Finally, sound quality is neglected; viewers forgive plain visuals far more readily than a hollow or noisy voice, so a basic external microphone is often the best single upgrade.

Keeping screencasts current

Software changes, and a screencast showing an old interface quietly becomes misleading. Plan for updates from the start: keep each video short and focused on one task, so a change affects one video rather than a long course. Keep the script or step list alongside the video so it can be re-recorded consistently. Add the version or date to the description. Where an interface changes often, screenshot based videos or written guides with images are cheaper to maintain, and a continuous screencast can be reserved for the parts of the product that rarely change.

Where it shows up in the product

The video generator does not record screencasts. Its screen capture, offered with the Tutorial type on desktop browsers, shares a screen, window or tab and takes a still PNG frame each time Capture step or the Space bar is pressed; no motion video is recorded and nothing is processed from a recording. Each shot can be marked with a click point and a zoom of No zoom, Zoom in at 1.5 times or Close-up at 2.1 times, which plays as a cursor gliding to the spot, a click ripple and the camera easing in over one second. The password reset example is built this way.

Questions people ask