Screen Capture

Screen capture is the umbrella term for taking a digital image of what's displayed on a screen — whether that means the full display, a single window, or a selected region.

Related workflow terms: Full-Page Screenshot, Viewport Screenshot.

Types of screen capture

Screen capture is not a single action — it is a category of methods, each suited to a different situation. The most common types are:

• Full-screen capture — grabs everything visible on the display, including the taskbar, dock, and all open windows. Useful for documenting the full working environment.
• Window capture — isolates a single application window, excluding the desktop background and other windows. Clean and focused.
• Region (area) capture — lets the user draw a rectangle around a specific area. Good for isolating a particular element without extra context.
• Viewport capture — captures exactly what a browser renders in its visible area, at a specific width and height. Common in web development and QA.
• Full-page capture — extends beyond the visible viewport to capture the entire scrollable length of a page. Produces a single long image.

The right method depends on what the recipient needs to see. More context is not always better — a tightly cropped region capture can communicate a point more clearly than a full-screen grab.

Where screen capture is used

Screen capture shows up in almost every workflow that involves visual communication:

• Bug reports — attaching a capture to a ticket so developers can see exactly what the reporter sees
• Documentation — illustrating steps in guides, tutorials, and knowledge bases
• Design reviews — sharing the current state of a page or component for feedback
• QA and testing — recording visual evidence of pass/fail states across browsers and devices
• Sales and marketing — creating product visuals, social media assets, and comparison graphics

In each case, the capture method and the framing of the image affect how clearly the message comes through.

Screen capture vs screen recording

Screen capture and screen recording both document what happens on a display, but they serve different purposes.

A screen capture freezes a single moment. It produces a lightweight image file that is easy to annotate, embed in documents, and store. It works well for static states — a UI in a particular configuration, a rendered page, or a specific error message.

A screen recording captures motion over time. It produces a video file that shows transitions, interactions, and sequences. It works well for demonstrating flows — reproducing a bug, walking through a feature, or recording a presentation.

When the goal is to document a state, capture is the right tool. When the goal is to document a process, recording is usually better. Some workflows combine both: a recording to show the steps, and a capture to highlight the final result.

Common mistakes with screen capture

• Capturing too much. A full-screen grab when only one element matters forces the viewer to search for the relevant detail. Crop to the minimum context needed.
• Ignoring pixel density. Captures taken on high-DPI (Retina) displays produce images at 2x resolution. This can result in oversized files and unexpected scaling when embedded in documents or web pages.
• Forgetting sensitive information. Browser tabs, notification banners, email previews, and URL bars can all contain private data. Review the full capture before sharing.
• Using the wrong format. JPEG compression blurs sharp text and UI edges. PNG preserves detail but produces larger files. Match the format to the content — PNG for text-heavy captures, JPEG for photographic content.
• Not standardizing capture dimensions. When captures are used for documentation or marketing, inconsistent sizes create a messy layout. Setting a consistent viewport or region size before capturing avoids rework later.