Keyboard Shortcut to Screenshot a Whole Page

There is no universal whole-page screenshot shortcut. In Microsoft Edge, press Ctrl+Shift+S, then choose Capture full page. In Firefox, press Ctrl+Shift+S on Windows or Linux, or Command+Shift+S on macOS, then choose Save full page.

A normal screen shortcut captures pixels currently visible on your display. A whole-page capture renders or stitches the document beyond the viewport, including content you would otherwise need to scroll through.

1. Quick shortcut reference

Browser or system	Shortcut	Next action	What it captures
Microsoft Edge	Ctrl+Shift+S	Select Capture full page	The complete webpage, including below-the-fold content
Firefox on Windows/Linux	Ctrl+Shift+S	Select Save full page	The complete webpage or the visible area, depending on your choice
Firefox on macOS	Command+Shift+S	Select Save full page	The complete webpage or the visible area, depending on your choice
macOS Screenshot	Shift+Command+3	None	The entire display, not a scrolling webpage

2. Capture a whole page in Microsoft Edge

1. Open the webpage in Edge.
2. Press Ctrl+Shift+S.
3. Choose Capture full page.
4. Use the overlay to copy the result or save it.

Edge’s Screenshot feature is designed to capture a full webpage, including content outside the current viewport. You can also open it from the right-click menu or Edge Settings. The exact controls and availability can vary by browser version, device type, and market.

Moving content such as GIFs or web carousels may remain active while the capture is made. If a page changes while it is being captured, pause animations or use a different capture method for a stable result.

3. Capture a whole page in Firefox

1. Open the page in Firefox.
2. Press Ctrl+Shift+S on Windows/Linux, or Command+Shift+S on macOS.
3. Choose Save full page.
4. Save the image, or choose Copy to place it on the clipboard.

You can also right-click an empty area of the page and select Take Screenshot. Firefox then offers Save full page and Save visible. Use the first option for a scrolling capture and the second for only the current viewport.

For developer workflows, open Developer Tools, enable the Take a screenshot of the entire page toolbox button, or use the Web Console command :screenshot --fullpage. Firefox also supports keyboard movement of the selection crosshair: arrow keys move it, Shift plus an arrow moves it by 10 pixels, and Ctrl or Command plus an arrow moves the selection to a viewport edge.

4. Why macOS screen shortcuts stop at the display

macOS’s built-in shortcuts operate at the screen or window level:

• Shift+Command+3: capture the entire screen.
• Shift+Command+4: capture a selected region.
• Shift+Command+4, then Space: capture a window or menu.
• Shift+Command+5: open the Screenshot app on macOS Mojave 10.14 and later.

These commands do not automatically scroll a browser document. Use Firefox’s Save full page command or Edge’s full-page capture when the page is taller than the display.

5. Android and other devices

Android’s screenshot controls vary by manufacturer and device. Official Android guidance covers taking, editing, and sharing screenshots, but it does not define one universal keyboard shortcut for scrolling webpage captures. Look for a device-specific option such as a scrolling or extended screenshot after taking a normal capture.

6. When a full-page capture is the wrong choice

• Need only what is visible: choose Firefox’s Save visible, or use the operating system’s region shortcut.
• Need a document for printing: export or print to PDF so text remains selectable.
• Need a repeatable build artifact: use an automated browser or screenshot API instead of a manual shortcut.
• Need one component: capture the element rather than the entire document to avoid a huge image.

7. Common problems and fixes

Problem	Likely cause	Fix
The shortcut does nothing	The browser version, platform, or keyboard layout does not expose the command.	Open the browser’s right-click menu and choose Take Screenshot or Screenshot; update the browser if appropriate.
Only the visible area is saved	You selected a viewport option such as Save visible.	Run the command again and choose Save full page or Capture full page.
The bottom of the page is missing	Lazy-loaded content has not rendered, or the page changes while it is captured.	Scroll through the page once, wait for images to load, stop animations, and retry.
Sticky headers appear repeatedly	The capture process records a fixed element during multiple viewport segments.	Hide the header with developer tools or use an automated capture that supports custom CSS.
Capture is extremely tall or blurry	The document is unusually long, or the output is being scaled down.	Capture a section or element, use a higher-resolution output, or export to PDF.
Menus, consent banners, or chat bubbles cover content	Those overlays are part of the rendered page.	Dismiss them before capture, use a reader mode where available, or apply a capture tool that can hide selectors.

8. Or skip the browser setup

ScreenshotNeo returns a webpage screenshot with one request. Its capture options include full-page screenshots with lazy images loaded, element capture by CSS selector, dark mode, device presets, custom viewports, retina scale, custom CSS and JavaScript, click actions, waits, request blocking, headers, cookies, user agents, timezone and geolocation, transparent backgrounds, resizing, caching, signed links, asynchronous jobs, bulk capture, PDFs, HTML/CSS rendering, and a usage API. See the ScreenshotNeo documentation for parameter details.

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

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)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Cookie banners, newsletter popups, and chat widgets are removed before the shot. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. An MCP server lets Claude, Cursor, and other MCP clients take screenshots with take_screenshot, inspect pages with get_page_info, and create PDFs with capture_pdf. The free plan includes 1,000 screenshots each month with no card; paid plans start at $5 for 3,000 shots.

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

9. Performance, reliability, and cost considerations

• Manual shortcuts: best for occasional captures, but results depend on browser version, page state, animations, and loaded assets.
• Very long pages: increase memory use and produce unwieldy image files. Capture sections or use PDF when readers need navigation and selectable text.
• Dynamic pages: wait for network activity and lazy images to settle before capturing.
• Repeat jobs: use a fixed viewport, explicit waits, and a stable user agent so output changes less between runs.
• ScreenshotNeo billing: only clean shots are billed; failed loads, bot checks, blank pages, timeouts, and cache hits cost nothing. A cache TTL you choose can reduce repeat work.

10. FAQ

Is Ctrl+Shift+S the Chrome shortcut for a full-page screenshot?

Do not assume it is universal. The documented shortcuts in this guide are for Edge and Firefox. Chrome versions and installed extensions can expose different commands, so check the browser’s menu or DevTools.

Does Shift-Command-3 capture a whole webpage on a Mac?

No. It captures the entire display. Use Firefox’s Command+Shift+S and then Save full page, or use Edge’s full-page Screenshot feature.

Can I copy a full-page screenshot instead of saving it?

Firefox offers Copy after a full-page capture. Edge’s overlay also supports copying or saving.

What should I use for automated screenshots?

Use a browser automation workflow when you need full control over rendering, or ScreenshotNeo when you want a hosted endpoint, cleanup of common overlays, billing for successful clean shots only, and MCP access for AI agents.