How to Take a Long Screenshot in Microsoft Edge
Capture an entire webpage in Microsoft Edge with DevTools, troubleshoot missing options, and automate full-page shots with ScreenshotNeo.
Use Edge DevTools’ Device Emulation mode, then choose Capture a full size screenshot. This command captures the entire page, including content outside the current viewport. The separate Capture screenshot command captures only the visible viewport.
Fast method: capture the whole page in Edge
- Open the webpage in Microsoft Edge.
- Open DevTools. You can right-click the page and select Inspect.
- Turn on Device Emulation (also called Device Mode) from the DevTools Activity Bar. You can also open DevTools’ Customize and control DevTools (…) > Device Emulation.
- On the Device Toolbar, open More options.
- Select Capture a full size screenshot.
Edge saves an image containing the full emulated page. Microsoft documents this workflow in its Device Emulation guide.
Full-size versus viewport screenshots
| Command | What it captures | Use it when |
|---|---|---|
| Capture screenshot | Only the content currently visible in the viewport | You need a quick view of the current screen |
| Capture a full size screenshot | The whole emulated page, including content below the fold | You need a long webpage image for review, documentation or sharing |
Both commands are in the Device Toolbar’s More options menu. Selecting the ordinary screenshot command does not automatically scroll through the page.
Before you capture
- Wait for the page’s main content to finish loading.
- Scroll through the page once if it uses lazy-loaded images or sections that appear only after entering the viewport.
- Close temporary overlays that you do not want in the result, such as sign-in dialogs or open menus.
- Choose a suitable emulated viewport. Device Emulation affects the layout, responsive breakpoints and image dimensions in the output.
- After saving, inspect the image’s bottom edge and several lazy-loaded sections. Microsoft does not publish a numeric maximum page length or guarantee behavior for every dynamically generated page.
If Edge’s regular Screenshot or Web Capture option is missing
Microsoft’s policy documentation calls the built-in feature Screenshot and notes that it was previously named Web Capture. The WebCaptureEnabled policy controls the feature in managed environments. Consumer menu labels can vary between Edge builds, so do not depend on an undocumented shortcut or a specific three-dot menu path.
If the regular browser menu does not show a full-page option, use the documented DevTools workflow above. It exposes Capture a full size screenshot through Device Emulation.
What Windows Snipping Tool can and cannot do
Windows Snipping Tool supports captures of a selected region, window or the whole screen. Its documented modes do not provide the cited scrolling-webpage workflow for a page taller than the viewport. For a complete webpage, Edge DevTools’ full-size command is the direct Microsoft-documented option. See Microsoft’s Snipping Tool instructions for its supported capture modes.
Troubleshooting
The Device Toolbar is not visible
Cause: Device Emulation is off. Fix: Open DevTools, then select the Device Emulation icon in the Activity Bar, or use Customize and control DevTools (…) > Device Emulation.
I only get the visible part of the page
Cause: You selected Capture screenshot. Fix: Open More options on the Device Toolbar and select Capture a full size screenshot.
The full-page command is unavailable
Cause: You may be using the regular browser menu, a restricted profile or an Edge build with different menu labels. Fix: use DevTools Device Emulation. In a managed installation, ask an administrator whether screenshot policies are disabled.
Images or sections are missing near the bottom
Cause: Lazy loading, delayed JavaScript or content that requires scrolling. Fix: let the page settle, scroll through it once, trigger any required interactions, and capture again. Verify the saved image rather than assuming every off-screen section loaded.
The page looks different from the normal browser view
Cause: Device Emulation changes viewport size and responsive CSS. Fix: select a desktop-sized preset or set a custom viewport that matches the layout you need, then recapture.
The result is extremely tall or difficult to use
Edge does not document a universal page-height limit. For very long pages, check the output for missing sections, excessive memory use and an impractical image size. Consider capturing logical sections separately when a single image is not useful.
Reliability and workflow checklist
- Open the final URL, not a redirect or preview URL.
- Wait for fonts, images and client-rendered content.
- Dismiss overlays and expand content that must appear.
- Scroll once to activate lazy loading.
- Enable Device Emulation and choose the intended viewport.
- Choose Capture a full size screenshot.
- Open the saved file and check the top, middle and bottom.
Or skip the browser setup
ScreenshotNeo provides a website screenshot API when you need repeatable captures from code or CI. It accepts a URL and returns PNG, JPEG, WebP or PDF. Cookie and consent banners are accepted before capture, then more than 60 known consent platforms, newsletter popups and chat widgets are removed. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and each response identifies the result with X-Page-Verdict and X-Billed headers. An MCP server lets Claude, Cursor and other MCP clients call take_screenshot, get_page_info and capture_pdf.
See the ScreenshotNeo API documentation for the complete option list.
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)
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}`);
ScreenshotNeo also supports full-page capture with lazy images, CSS-selector element capture, dark mode, device presets or custom viewports, retina scale, custom CSS and JavaScript, click and wait actions, blocked requests and resource types, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, selectable cache TTLs, signed image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, usage reporting and an OpenAPI specification. Parameter names used by other screenshot APIs are accepted to ease migration.
The Free plan includes 1,000 screenshots each month with no card. Paid plans start at $5 for 3,000 shots; yearly billing provides two months free, and every feature is available on every plan. Create a free ScreenshotNeo account.
Performance, reliability and cost considerations
- Edge: capture time depends on page loading, JavaScript, image count and your local machine. A long image can consume substantial memory.
- Automation: use explicit waits for a selector, delay or network idle when a page is rendered after navigation. Block ads, trackers or unnecessary resource types when they are not part of the result.
- Repeat captures: choose a cache TTL when identical pages do not need a fresh render. Use asynchronous jobs and signed webhooks for slow or high-volume work.
- Billing: ScreenshotNeo bills only clean captures. Bot checks, blank pages, timeouts, failed loads and cache hits cost nothing, with the verdict and billing status returned in headers.
FAQ
Does Edge’s normal screenshot command capture a scrolling page?
Use Capture a full size screenshot in DevTools for the documented full-page workflow. Capture screenshot is the viewport-only command.
Can I capture a page without opening DevTools?
The regular Screenshot/Web Capture feature may be exposed in your Edge build, but its menu path can vary. DevTools is the documented fallback. For code-driven captures, use ScreenshotNeo.
Will full-size capture include content loaded only after scrolling?
Not necessarily. Trigger lazy loading first, then verify the saved image. Edge’s documentation does not guarantee behavior for every dynamic page.
Can I produce a PDF instead of an image?
Edge’s command creates a screenshot image. ScreenshotNeo’s API includes PDF capture with paper size, margins, landscape mode and page ranges.


