How to Screenshot an Entire Page in Microsoft Edge
Capture a full webpage in Edge with the built-in Screenshot tool, including content below the screen, plus automation options for developers.
Quick answer: Open the webpage in Microsoft Edge, press Ctrl+Shift+S, choose Capture full page, review the result, and save it. Edge captures content below the visible screen in one shareable image.
Capture a full webpage in Microsoft Edge
- Open the page you want to capture in Edge.
- Press Ctrl+Shift+S.
- Select Capture full page.
- Review the long screenshot, add markup if needed, and save it to your device.
Microsoft currently calls this feature Screenshot. Older Edge documentation and menus may call it Web Capture. The full-page option captures the webpage beyond the current viewport, so you do not need to scroll manually.
Other ways to open Edge Screenshot
If the keyboard shortcut does not work, use either menu route:
- Right-click the webpage and choose the Screenshot option.
- Open the Settings and more menu (the three dots), then choose Screenshot.
The exact menu wording can change as Edge updates. If Screenshot is missing, an administrator may have disabled the feature, or the feature may not be available in your region or build.
Choose the correct capture mode
| Option | What it captures | Use it when |
|---|---|---|
| Capture full page | The complete webpage, including content below the screen | You need one long image of the page |
| Selected area | A region you drag over the current page | You need only part of the visible page |
| Snipping Tool | A screen region, window, or full screen | You need a screen snip rather than the entire webpage |
| A printable document through Edge’s print flow | You need a printout or PDF-style document |
On Windows, Windows+Shift+S opens Snipping Tool. It is useful for visible screen content, but it is a different workflow from Edge’s full-webpage Screenshot feature.
Platform and version support
Microsoft’s policy documentation lists Screenshot support for Edge version 87 or later on Windows and macOS. It marks Android and iOS as unsupported for this policy-controlled feature. Organizations can disable Screenshot through Edge policy. Availability and labels can vary by region and may change with future releases.
When the full-page screenshot is blank or incomplete
Lazy-loaded content is missing
Some pages load images or sections only after they enter the viewport. Edge’s capture may not trigger every site’s lazy-loading behavior. Try waiting for the page to finish loading, dismissing overlays, and scrolling through the page once before capturing.
Sticky headers or floating widgets repeat
Fixed navigation bars, chat buttons, cookie notices, and newsletter popups can appear in the captured image. Close them before starting the capture. If a site keeps reopening them, use a controlled browser capture workflow or an API that can hide selectors and remove known overlays.
The page stops at the visible viewport
Confirm that you selected Capture full page, not Selected area. If the option is unavailable, update Edge, check whether an administrator policy disabled Screenshot, and try the Settings and more menu.
The shortcut does nothing
- Click the webpage first so Edge has focus.
- Try the context-menu or Settings and more route.
- Check for keyboard software that remaps Ctrl+Shift+S.
- Ask your administrator whether Screenshot is blocked by policy.
The result has layout shifts or missing fonts
Wait until web fonts, images, and client-rendered content finish loading. Close dialogs and avoid capturing while the page is still changing. For repeatable results, use a scripted browser or screenshot API with an explicit wait condition.
Save, share, and edit the result
After Edge creates the capture, review the image before saving. The Screenshot tool supports markup and a selected-area mode, so you can annotate or crop the result for sharing. Save a lossless format when text clarity matters, and use a compressed image when file size matters.
Automate full-page screenshots for developers
Edge’s built-in tool is convenient for one-off captures. For documentation builds, visual regression checks, scheduled archives, or many URLs, automation gives you repeatable viewport, timing, authentication, and output settings.
Browser automation checklist
- Set a fixed viewport and device scale factor.
- Wait for a selector, a known delay, or network idle.
- Dismiss cookie banners and modal dialogs before capture.
- Scroll or otherwise trigger lazy-loaded images.
- Use a full-page screenshot mode rather than a viewport screenshot.
- Store the URL, timestamp, viewport, and browser version with each image.
For private pages, provide authentication through a controlled session, cookies, or headers. Never put session tokens in a public image URL or commit them to source control.
Or skip the browser setup
ScreenshotNeo provides a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. Cookie and consent banners, newsletter popups, and chat widgets are removed before capture. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing result.
See the ScreenshotNeo API documentation for the complete option list, including full-page capture with lazy images loaded, CSS-selector element capture, device presets, custom viewports, retina scale, waits, custom CSS and JavaScript, hidden selectors, headers, cookies, user agents, authorization, timezone, geolocation, request blocking, transparent backgrounds, resizing, caching, signed links, asynchronous jobs, webhooks, bulk capture, usage data, and PDF output.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
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(`HTTP ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));ScreenshotNeo has an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
Performance, reliability, and cost notes
- One-off work: Edge Screenshot has no API setup and is usually the fastest path for a human-operated capture.
- Repeatable work: Automation should use explicit waits and a stable viewport to reduce layout differences.
- Large pages: Full-page images can be very tall and memory-intensive. Consider JPEG/WebP, resizing, or PDF output when the image does not need pixel-level losslessness.
- Dynamic pages: Ads, animations, personalization, consent tools, and login state can change the result between runs.
- API cost control: Cache captures when the source has not changed, set a cache TTL, and use bulk capture for batches. ScreenshotNeo bills only clean shots; failed loads, bot checks, blank pages, timeouts, and cache hits cost nothing.
Troubleshooting checklist
| Symptom | Likely cause | Fix |
|---|---|---|
| No Screenshot command | Unsupported build, region rollout, or administrator policy | Update Edge, check both menu routes, or ask your administrator |
| Only the visible area is saved | Selected-area capture was used | Run Screenshot again and choose Capture full page |
| Cookie banner covers the image | The site overlay remained open | Accept or close it before capture, or use an automated cleanup step |
| Images are absent | Lazy loading or blocked resources | Wait, scroll once, and verify the page is fully loaded |
| Text is blurry | Low display scale or aggressive compression | Save the original capture and avoid repeated resizes |
| Automated request returns an error | Invalid URL, credentials, timeout, or blocked page | Validate the URL, increase the timeout, check authentication, and inspect the response status and headers |
FAQ
Does Edge scroll while taking the screenshot?
The full-page feature captures content beyond the visible screen without requiring you to scroll manually.
What was Web Capture called?
Web Capture is the former name. The current feature name is Screenshot.
Can I use Edge Screenshot on an iPhone or Android phone?
Microsoft’s policy documentation lists Android and iOS as unsupported for this feature.
Should I use Screenshot or Print?
Use Screenshot for one shareable webpage image. Use Print when you need a printable document or print-oriented output.
Can I capture only one element?
Edge’s built-in tool is designed for a full page or selected screen area. For a specific DOM element, use browser automation or an API that supports CSS-selector capture, such as ScreenshotNeo.
