ScreenshotNeo

BlogScreenshots on your device

How to Take a Scrolling Screenshot in Microsoft Edge on Mac

Capture an entire webpage in Microsoft Edge on Mac with the built-in Screenshot tool, DevTools, or ScreenshotNeo’s screenshot API.

By the ScreenshotNeo team1 October 20266 min read

Fast answer: Open the page in Microsoft Edge, right-click anywhere on it, choose Screenshot or Web capture, then select Capture full page. Review the result and use the capture overlay to copy it or save it. Microsoft describes Screenshot as being able to capture the parts of a webpage that normally require scrolling.

Edge’s wording can differ by browser version. On a Mac, use the page context menu instead of relying on a keyboard shortcut: Microsoft’s documentation lists Ctrl+Shift+S, but does not confirm a Mac-specific mapping.

Use Edge’s built-in full-page capture

  1. Open Microsoft Edge on your Mac.
  2. Navigate to the webpage you want to capture. Wait for the main content, images and embedded sections to finish loading.
  3. Right-click inside the webpage. On a trackpad, click with two fingers or hold Control while clicking.
  4. Choose Screenshot or Web capture. The label depends on the Edge version and interface you have installed.
  5. In the capture controls, choose Capture full page.
  6. Review the long image in the preview overlay.
  7. Choose the option to copy the capture to the clipboard or save it to a file.

The built-in feature is documented on Microsoft’s Edge Screenshot page. It captures content below the current viewport, so you do not need to scroll manually and stitch several images together.

Before you capture: make the page complete

A full-page screenshot captures the document Edge can render. If the page is still loading, the result can contain placeholders, missing images or collapsed sections.

  • Wait for visible images, charts and embedded media to load.
  • Scroll through the page once if it uses lazy-loaded images. This can trigger content that only loads near the viewport.
  • Dismiss cookie banners, newsletter popups and chat bubbles if they cover the content you need.
  • Expand accordions, tabs or “show more” controls before capturing when their contents should appear.
  • Check that you are signed in if the page requires an account.
  • For a page that changes continuously, pause animations or capture after the layout has settled.

What to do when Screenshot or Web capture is missing

Feature availability and behavior can vary by device type, market and Edge version. Update Edge, restart it, and check the page context menu again. You can also look in Edge’s Settings menu for Screenshot-related commands.

Some managed work or school profiles can restrict browser features. If the command is absent only in a managed profile, try an allowed personal profile or ask the administrator whether web capture is disabled.

Advanced fallback: capture a full-size screenshot with DevTools

Edge DevTools provides a full-size screenshot command that includes content outside the current viewport. This is useful when the regular context-menu command is unavailable or when you need a developer-oriented workflow.

  1. Open the target page in Edge.
  2. Open DevTools with Option+Command+I, or open Edge’s menu and choose More tools followed by Developer tools.
  3. Enable device emulation by selecting the Toggle device emulation button in the DevTools toolbar.
  4. Open the DevTools More options menu.
  5. Choose Capture a full size screenshot.
  6. Save the generated image when Edge prompts you.

Microsoft documents full-size capture in its Edge DevTools device-mode guidance. DevTools exposes more controls, but it is less convenient for a quick one-off capture.

Optional extension fallback

If the built-in command is unavailable for your installation, the Microsoft Edge Add-ons store lists extensions such as GoFullPage – Full Page Screen Capture. Review the extension’s current listing, permissions and privacy terms before installing it. An extension is useful when you need a repeatable toolbar workflow, but it adds another piece of software to maintain.

Common problems and fixes

Problem Likely cause Fix
The Screenshot/Web capture item is not in the menu Different Edge version, profile policy or feature rollout Update Edge, check Settings, try another profile, or use DevTools full-size capture.
Only the visible viewport is captured A selected-area mode was used Open the capture controls and choose Capture full page.
Images are missing lower down the page Lazy loading had not been triggered Scroll through the page once, wait for images to appear, then capture again.
A cookie banner or chat bubble covers the result The overlay was present when Edge rendered the page Dismiss it before capture. If it returns, use a clean profile or a capture service that removes common overlays.
The page is cut off or sections overlap Sticky elements, animations or unusual CSS changed layout during capture Wait for the page to settle, pause animations where possible, or use DevTools and capture again.
The saved image is difficult to read A very long page was scaled down in an image viewer Open it at 100% zoom, crop into sections for sharing, or export a PDF when a document format is more useful.
The shortcut does nothing The documented shortcut is not confirmed as a macOS mapping Use the right-click menu instead of relying on Ctrl+Shift+S.

Choosing the right method

Method Best for Trade-offs
Edge Screenshot/Web capture Fast manual captures on a normal webpage Feature labels and availability vary; dynamic pages may need preparation.
Edge DevTools Developers who need full-size capture controls More setup and browser-tool knowledge.
Extension A repeatable toolbar workflow when built-in capture is unavailable Requires installing and reviewing third-party software.
Screenshot API Automated, scheduled or server-side screenshots Requires an API key and request handling.

Or skip the browser setup

ScreenshotNeo captures a URL with one GET request, returning PNG, JPEG, WebP or PDF. Its capture flow accepts cookie and consent banners, removes more than 60 known consent platforms plus newsletter popups and chat widgets, and lets you turn each cleanup step off. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed; response headers identify the page verdict and whether the request was billed.

See the ScreenshotNeo API documentation for all options. The same endpoint supports full-page capture, CSS-selector element capture, device presets, custom viewports, retina scale, waits, custom CSS and JavaScript, hidden selectors, request blocking, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, caching, signed links, asynchronous jobs, webhooks, bulk capture and usage reporting.

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 data = Buffer.from(await res.arrayBuffer());
require('fs').writeFileSync('shot.webp', data);

ScreenshotNeo also provides 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 screenshots each month with no card; paid plans start at $5 for 3,000 screenshots, and every feature is available on every plan.

Create a free ScreenshotNeo account and start with 1,000 screenshots per month at no charge.

Performance, reliability and cost considerations

  • Long pages: Full-page images can be very tall and memory-heavy. Prefer WebP or JPEG for smaller files, or capture a specific element when you only need one section.
  • Dynamic content: Wait until lazy images, charts and fonts finish loading. A screenshot is a visual snapshot, not a guarantee that every asynchronous request has completed.
  • Repeatability: Use a consistent viewport, zoom level, signed-in state and cookie state when comparing captures over time.
  • Privacy: Avoid sharing screenshots that contain account data, private URLs, tokens or personal information.
  • Automation: For scheduled jobs, handle timeouts and non-success responses, retain the response headers, and use caching when the page does not change frequently.
  • Cost: Manual Edge and DevTools captures have no API charge. ScreenshotNeo bills only clean shots; failed loads, bot checks, blank pages, timeouts and cache hits are free.

FAQ

Does Edge on Mac have a scrolling screenshot feature?

Yes. Edge’s Screenshot/Web capture feature can capture the full webpage, including content below the visible viewport.

What is the difference between a scrolling screenshot and a full-page screenshot?

They describe the same goal: one image containing the complete document rather than only the currently visible screen.

Can I capture only one part of a long page?

Yes. Use an area or selected-region mode in Edge, or use ScreenshotNeo’s CSS-selector element capture for automated requests.

Why does the menu say Web capture instead of Screenshot?

Microsoft has used both labels across Edge versions and interfaces. Look for the command that opens the webpage capture controls.

Can I save a full webpage as a PDF instead?

Use Edge’s print dialog for a browser-generated PDF, or use ScreenshotNeo’s PDF capture when you need API-controlled paper size, margins, orientation or page ranges.