How to Capture a Full-Page Screenshot with Snipping Tool

Short answer: Microsoft’s Snipping Tool does not document a scrolling or stitching mode for an entire webpage. Its documented modes capture a rectangle, window, full screen, or freeform selection. The full-screen option captures everything currently visible on your monitor, not the page content below the fold. For a complete webpage, use Microsoft Edge’s Screenshot feature, or use a screenshot API such as ScreenshotNeo.

What Snipping Tool can capture

Snipping Tool is designed for still images of content currently displayed on your Windows screen. Microsoft documents four image modes:

Snipping Tool captures the viewport; full-page tools continue below it and assemble the document.

Rectangle: drag around a region of the visible display.
Window: select one open application window.
Full screen: capture the entire display area currently shown.
Freeform: draw an irregular outline around a visible area.

Microsoft’s support documentation does not list an automatic scrolling mode. Therefore, you cannot select a long article in Snipping Tool and have it scroll through the page, stitch the sections together, and produce one full-page image. This distinction matters: a full-screen snip and a full-webpage capture are different results. See Microsoft’s Snipping Tool capture guidance for the supported modes and editing workflow.

Capture the visible page with Snipping Tool

Use this process when you need only the section currently visible in your browser.

Open the webpage and position the viewport over the content you need.
Press Windows logo key + Shift + S. Windows opens the Snipping Tool capture overlay.
Choose Rectangle, Window, Full screen, or Freeform from the capture bar.
Select the area or window. For a full-screen snip, Windows captures the current display exactly as shown.
Select the notification or open Snipping Tool from the Start menu to edit the result.
Use the editor to annotate, crop, copy, extract text where supported, save, or share the image.

The shortcut launches the capture interface; it does not turn the tool into a scrolling webpage recorder. If the page is taller than the viewport, repeat the process for additional sections or use the browser method below.

Choosing the right Snipping Tool mode

Need	Mode	What you receive
A paragraph or image	Rectangle	A rectangular region inside the visible display
One browser window	Window	The selected window as currently displayed
Every visible monitor pixel	Full screen	The complete current display, including taskbars and other visible windows
An irregular shape	Freeform	The area enclosed by your drawn outline

Capture an entire webpage in Microsoft Edge

When the requirement is one image containing content below the fold, Microsoft Edge’s Screenshot feature is the practical built-in route. Microsoft describes it as a full-page capture tool that includes content outside the current viewport. The feature can copy or save the resulting capture. Entry points and availability can vary by device type, market, and browser version, so menus may differ from the steps below. Refer to Microsoft’s Edge Screenshot documentation if the command is missing.

Open the target webpage in Microsoft Edge.
Open the page context menu with a right-click and choose Screenshot, or open Edge’s Settings and more menu and select the Screenshot tool.
You can also try Ctrl + Shift + S if that shortcut is enabled in your version.
Choose the option to capture the full page, rather than only the visible area.
Review the generated capture in the overlay.
Copy it to the clipboard or save it to a file.

Edge’s full-page operation scrolls through the document and includes sections below the initial viewport. This is different from Snipping Tool’s full-screen mode, which samples only what is currently displayed.

If Screenshot is missing in Edge

Update Edge, then reopen the browser and check the page menu again.
Look in both the right-click menu and the Settings and more menu; the placement can change.
Confirm that you are capturing a normal webpage rather than a restricted internal page or an embedded document.
Check Microsoft’s current documentation because feature availability and behavior can vary by browser version, device type, and market.

Do not assume that every Edge installation exposes the same command. If the feature is unavailable, use a dedicated browser automation workflow or an API.

Full-page capture with browser automation

For repeatable captures, developers often control a browser with Playwright or Puppeteer. The general workflow is:

Launch Chromium in headless mode.
Navigate to the URL and wait for the page to finish loading.
Optionally wait for a selector, a delay, fonts, images, or network activity.
Set fullPage (Playwright) or the equivalent full-page option.
Write the PNG, JPEG, or WebP bytes to disk or object storage.

A minimal Playwright example in JavaScript is:

import { chromium } from 'playwright';

const browser = await chromium.launch();
const page = await browser.newPage({ viewport: { width: 1440, height: 900 } });
await page.goto('https://example.com', { waitUntil: 'networkidle' });
await page.screenshot({ path: 'example-full.png', fullPage: true });
await browser.close();

Automation gives you control, but you must operate the browser infrastructure: Chromium binaries, sandboxing, concurrency, timeouts, fonts, cookies, consent dialogs, lazy-loaded images, and failures caused by bot checks. A page can also change while it is being scrolled, producing inconsistent sections. For production jobs, record the URL, viewport, wait policy, response status, and output checksum so a failed or changed capture is diagnosable.

Or skip the browser setup

ScreenshotNeo provides a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF, and full-page capture loads lazy images before creating the result. The API accepts the URL and an access key; see the ScreenshotNeo documentation for all options.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://stripe.com \
  -o shot.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://stripe.com'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
const bytes = Buffer.from(await res.arrayBuffer());
await Bun.write('shot.webp', bytes);

With Node.js versions that do not provide a file writer such as Bun, write the returned buffer with the standard filesystem module:

import { writeFile } from 'node:fs/promises';
// after obtaining bytes from res:
await writeFile('shot.webp', bytes);

Options useful for a full-page result

Requirement	ScreenshotNeo capability
Long pages and lazy images	Full-page capture with lazy images loaded
Only one component	Capture one element by CSS selector
Consistent appearance	Device presets, custom viewport, retina scale, dark mode, timezone, and geolocation
Dynamic pages	Wait for a selector, a delay, or network idle; run custom JavaScript or click an element
Clean output	Accept cookie or consent banners, then remove more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off
Privacy and access	Custom headers, cookies, user agent, and Authorization
Noise and cost control	Block ads, trackers, requests, or resource types; choose a cache TTL
Documents	PDF paper size, margins, landscape mode, and page ranges
Delivery at scale	Async jobs with signed webhooks, bulk capture for up to 100 URLs per call, signed links, and a usage API

ScreenshotNeo reports whether a response was clean, and whether it was billed, in the X-Page-Verdict and X-Billed headers. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. An MCP server exposes take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients.

Free accounts include 1,000 shots per month without a card. Paid plans start at $5 for 3,000 shots; yearly billing gives two months free, and every feature is available on every plan. Create a free ScreenshotNeo account.

Troubleshooting

“Full screen” still misses the bottom of the page

This is expected. Snipping Tool’s full-screen mode captures the display, not the scrollable document. Use Edge Screenshot’s full-page option or an API with full-page capture.

A capture workflow can clear consent banners and overlays before saving the page.

The Edge Screenshot command is not visible

Menus and availability vary by version, device, and market. Update Edge, check both menu locations, and consult Microsoft’s current Screenshot documentation.

Dismiss overlays before a manual capture. In automation, wait for the consent UI and click its accept or close control. ScreenshotNeo can accept consent banners and remove known consent platforms, newsletter popups, and chat widgets before capture.

Images are missing near the bottom

Many sites lazy-load images only after they approach the viewport. Scroll the page before taking manual segments, wait for image requests in automation, or use ScreenshotNeo’s full-page capture, which loads lazy images.

The result is blank, incomplete, or blocked

Check the URL, authentication, redirects, JavaScript errors, and bot protection. Supply cookies, headers, an Authorization value, a realistic user agent, or a longer wait when appropriate. For ScreenshotNeo responses, inspect X-Page-Verdict and X-Billed to distinguish a clean result from a failed or non-billable attempt.

The output is too large

Reduce the viewport width, capture a specific element, choose JPEG or WebP, or use image resizing. For a document deliverable, PDF page size, margins, orientation, and page ranges can reduce unnecessary output.

Performance, reliability, and cost notes

Manual Snipping Tool: fastest for a visible region, with no service cost, but it requires repeated scrolling and manual stitching for long pages.
Edge Screenshot: convenient for occasional whole-page captures; results depend on the installed Edge version and page behavior.
Self-hosted automation: gives maximum control and predictable local data flow, but browser startup, memory, fonts, concurrency, and site-specific waits become your responsibility.
ScreenshotNeo: removes browser orchestration, supports caching with a chosen TTL, bulk and asynchronous jobs, and does not bill bot checks, blank pages, timeouts, failed loads, or cache hits. Use the usage API and response headers when reconciling spend.

For any method, make captures deterministic by fixing viewport dimensions, color scheme, timezone, locale, authentication state, and wait conditions. Avoid capturing while animations are running. Store the source URL and capture settings alongside the image so a later comparison can be reproduced.

FAQ

Can Snipping Tool capture a scrolling webpage?

Microsoft’s documented Snipping Tool modes do not include scrolling capture. It captures the visible screen area.

Does Windows logo key + Shift + S capture the whole webpage?

No. It opens the Snipping Tool overlay. The selected mode still determines which visible pixels are captured.

What is the simplest Microsoft option for a full webpage?

Use Microsoft Edge’s Screenshot feature and choose full-page capture, if that feature is available in your version.

Manual tools use your active browser session. Automation and APIs require you to provide the necessary cookies, headers, or authorization securely.

Should I use PNG, JPEG, or WebP?

PNG preserves sharp text and transparency. JPEG is useful for photographic pages and smaller files. WebP often provides a smaller modern image when your downstream systems support it.

Can an AI agent request screenshots?

Yes. ScreenshotNeo provides an MCP server with take_screenshot, get_page_info, and capture_pdf for MCP clients such as Claude and Cursor.