BlogScreenshots on your device
How to Take Full-Page Screenshots with an Edge Add-On
Capture an entire webpage in Microsoft Edge with its built-in Screenshot tool or a full-page add-on, plus automation options for developers.

Short answer: Microsoft Edge already includes a full-page Screenshot tool. Open the page, press Ctrl+Shift+S, choose Capture full page, then copy or save the result. You do not need an add-on for ordinary captures. Install an Edge extension when you need a dedicated workflow, PDF export, or extra editing controls.
This guide covers Edge’s built-in tool, the GoFullPage add-on, browser-version and managed-device limits, long-page reliability, troubleshooting, and an API path for repeatable developer workflows.
1. Use Edge’s built-in full-page Screenshot tool
Edge’s Screenshot feature (formerly Web Capture) can capture content that continues below the visible viewport. Microsoft documents it as available from any site through the page context menu, with a keyboard shortcut and copy/save controls. The exact wording can vary by Edge version, device type, market, or browser settings.

- Navigate to the page you want to capture.
- Open Screenshot from the page’s right-click menu or Edge Settings, or press Ctrl+Shift+S.
- Select Capture full page. Some versions show this as a full-page capture button in the Screenshot overlay.
- Wait while Edge collects the content below the fold. Very long pages can take longer than a viewport capture.
- Review the resulting image. Use the overlay’s pen or touch tools if you need markup.
- Choose Copy to place the image on the clipboard or Save to write it to a file.
The built-in method is the best first choice when you only need a screenshot because it requires no installation and uses Edge’s own page renderer.
Keyboard and menu routes
| Route | How to open it | Best for |
|---|---|---|
| Keyboard | Ctrl+Shift+S | Fast repeat captures |
| Context menu | Right-click the page, then choose Screenshot | Discoverability and occasional use |
| Settings | Open Edge Settings and find Screenshot/Web Capture | When the context-menu item is hidden |
2. Install an Edge add-on for a dedicated workflow
An add-on is useful when you want a toolbar button, a separate capture review page, PDF export, or editing features beyond Edge’s basic markup.
- Select Extensions beside Edge’s address bar.
- Choose Get Extensions for Microsoft Edge.
- Search for the extension you want and select Get.
- Read the permissions request, then select Add extension if it fits your use case.
Edge can also install extensions from the Chrome Web Store after you enable extensions from other stores. Review the requested permissions before installation, especially for extensions that can read or change data on websites.
3. Capture a page with GoFullPage
GoFullPage – Full Page Screen Capture is a relevant Edge add-on when you want a one-click extension workflow. Its Edge Add-ons listing says that you can select the extension icon or press Alt+Shift+P. It captures successive sections of the page, assembles them, and opens the result in a new tab.
- Install the GoFullPage Edge add-on from Edge’s extension store.
- Open the target webpage and scroll it once if the site loads content only after interaction.
- Select the GoFullPage icon, or use Alt+Shift+P.
- Leave the capture tab open while the extension scrolls through and assembles the image.
- Download the result as an image or PDF from the result page.
The listing also describes a premium editor with crop, annotation, and emoji tools. Exceptionally large pages may be split into separate images. Treat the current listing and feature set as changeable: extension interfaces and capabilities can differ across versions.
Built-in Screenshot versus an add-on
| Decision point | Edge Screenshot | GoFullPage-style add-on |
|---|---|---|
| Installation | Built in | Separate extension and permissions |
| Trigger | Ctrl+Shift+S, context menu, or Settings | Toolbar icon or extension shortcut |
| Output | Copy or save an image | Image or PDF export |
| Editing | Pen/touch markup | Additional editor features may be available, including premium tools |
| Very large pages | Depends on Edge and the device | May be split into multiple images |
| Administration | Can be controlled by Edge policy | Can be blocked by extension policy |
4. Prepare the page before a full-page capture
Long screenshots are a rendering task, not just a save operation. Preparing the page reduces blank sections, missing images, and unexpected layout shifts.
- Wait for the page to finish loading. Watch for skeleton screens, spinners, and late-loading fonts.
- Trigger lazy content. Slowly scroll through the page once so image and video placeholders have a chance to load.
- Close transient UI. Dismiss cookie prompts, chat bubbles, newsletter dialogs, and sticky toolbars if they obscure content.
- Set a stable viewport. Maximize the browser or use a consistent window size when comparing screenshots.
- Stop animations when possible. A moving carousel can produce inconsistent frames between sections.
- Check authentication. A screenshot only includes what your current Edge session can access.
Pages with fixed headers, sticky navigation, or parallax effects can show repeated elements in a stitched image. If the result is visually wrong, try the built-in tool and the add-on separately; they use different capture strategies.
5. Full-page screenshot edge cases
Lazy-loaded images and infinite scroll
A finite article page usually captures well after a preparatory scroll. Infinite-scroll feeds do not have a natural endpoint. The capture may stop at the currently loaded content, continue until a browser or extension limit, or produce a very large file. For an infinite feed, capture a defined segment or use the site’s print/export function.
Sticky and fixed elements
A sticky header may be repeated at every stitched segment. Hide it temporarily with the browser’s developer tools or a page-specific style if you control the site. Do not assume an extension can remove every fixed element.
Cross-origin frames
Embedded content from another origin can be restricted by browser security rules. The outer page may appear in the screenshot while a frame is blank or shows only its fallback content.
Protected pages and bot checks
CAPTCHAs, bot checks, login walls, and pages that require interaction can prevent a meaningful capture. A screenshot tool cannot grant access you do not have.
Very tall documents
Large captures consume memory and can exceed image or PDF limits. If an add-on splits the result, save the parts and combine them in a document editor, or capture logical sections separately.
6. Troubleshooting checklist
| Symptom | Likely cause | Fix |
|---|---|---|
| Screenshot is missing from the right-click menu | Different Edge version, menu customization, or policy | Try Ctrl+Shift+S and Edge Settings. On managed devices, ask whether the WebCaptureEnabled policy is disabled. |
| Shortcut does nothing | Another application owns the shortcut, or focus is in a text field | Click the page, use the context menu, or change the conflicting shortcut. |
| Only the visible viewport is captured | Viewport mode was selected instead of full page | Open Screenshot again and choose Capture full page. |
| Images are blank | Lazy loading, blocked requests, or capture started too soon | Scroll through the page first, wait for images, and retry without aggressive content blocking. |
| Cookie banner or chat widget covers content | Transient overlays remained open | Dismiss them before capture, or hide their selectors with developer tools if you own the page. |
| Page sections are duplicated | Sticky or fixed-position elements were stitched repeatedly | Temporarily disable the fixed element or capture the page in sections. |
| GoFullPage opens a blank result tab | Extension was interrupted, page navigation continued, or permissions are restricted | Reload the page, wait for navigation to finish, pin the extension, and retry. Check extension permissions. |
| GoFullPage creates multiple files | The page exceeded the extension’s practical size | Capture smaller sections or combine the exported images afterward. |
| PDF output has awkward page breaks | The image was placed into a fixed paper layout | Use the add-on’s PDF options if available, or print the page with a deliberate paper size and scale. |
7. Reliability, privacy, and repeatability
For a one-off personal capture, the browser workflow is enough. For documentation, visual regression, archives, or scheduled jobs, browser extensions introduce variables: the signed-in session, extension version, browser updates, device memory, viewport size, and page timing can all change the output.
- Keep a capture record: URL, timestamp, viewport dimensions, browser version, and whether the page required login.
- Use consistent conditions: same window size, zoom level, locale, timezone, and account state.
- Protect sensitive data: screenshots can include personal information, tokens rendered in pages, and private customer content.
- Verify the file: open the saved image or PDF and inspect the top, middle, and bottom before publishing it.
- Prefer sections for huge pages: smaller files are easier to review, upload, and compare.
8. Or skip the browser setup
For repeatable captures, use ScreenshotNeo, a website screenshot API and MCP server for developers. One GET request returns a PNG, JPEG, WebP, or PDF. See the ScreenshotNeo API documentation for request parameters and response details.

Basic cURL request:
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 is useful when browser setup is the bottleneck:
- Cookie and consent banners, newsletter popups, and chat widgets are removed before the shot. Each cleanup step can be turned off.
- Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. Response headers identify the page verdict and whether it was billed.
- You can capture full pages with lazy images, one element by CSS selector, dark mode, custom viewports, 12 device presets, retina scale, PDFs, HTML/CSS, custom CSS and JavaScript, clicks, waits, blocked resources, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, caching, signed links, asynchronous jobs, webhooks, bulk requests for up to 100 URLs, usage data, and an OpenAPI specification.
- An MCP server provides
take_screenshot,get_page_info, andcapture_pdftools for Claude, Cursor, and other MCP clients.
Plans include 1,000 screenshots per month free with no 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 to start.
9. Choosing the right method
- Use Edge Screenshot for a quick, manual, no-install capture.
- Use a GoFullPage-style add-on when you need an extension button, image/PDF export, or extra editing.
- Use ScreenshotNeo when captures must run from scripts, CI jobs, backend services, bulk URL lists, or AI-agent workflows.
Frequently asked questions
Can Edge capture an entire webpage without an extension?
Yes. Press Ctrl+Shift+S or open Screenshot from the context menu and select Capture full page.
What is the Edge shortcut for a full-page screenshot?
Ctrl+Shift+S opens the Screenshot tool. Select the full-page option in the overlay.
Why is my full-page screenshot cut off?
The page may still be loading, use infinite scroll, exceed practical image limits, or contain a protected frame. Scroll through the page first and try capturing smaller sections.
Can an Edge add-on save a full page as PDF?
GoFullPage’s current listing describes image and PDF downloads. Extension features can change, so confirm the listing for your installed version.
Can an administrator disable Edge Screenshot?
Yes. Microsoft’s enterprise policy reference identifies WebCaptureEnabled as the policy controlling the feature on supported Edge versions.
Is an API better than an add-on?
An API is better for automation, consistent parameters, bulk jobs, and server-side workflows. An add-on is convenient for a person capturing the page currently open in Edge.


