How to Capture a Full-Page Screenshot with a Keyboard Shortcut

There is no single full-page screenshot shortcut that works in every browser. Firefox and Microsoft Edge open a built-in screenshot tool with Ctrl/Command + Shift + S, then require a full-page selection. Chrome uses DevTools: open the Command Menu with Ctrl/Command + Shift + P, then run its full-size screenshot command.

Browser	Windows/Linux	macOS	Next action
Firefox	`Ctrl` + `Shift` + `S`	`Command` + `Shift` + `S`	Choose Save full page
Microsoft Edge	`Ctrl` + `Shift` + `S`	—	Choose Capture full page
Chrome	`Ctrl` + `Shift` + `P`	`Command` + `Shift` + `P`	Run Capture a full size screenshot in DevTools

A normal operating-system screenshot captures the visible screen. It does not automatically include content below the viewport. Use the browser workflows below when you need the whole webpage.

1. Firefox: Ctrl/Command + Shift + S, then Save full page

Firefox’s screenshot tool can capture the visible area or the entire webpage. The shortcut opens the tool; the full-page result requires the second selection.

Open the page you want to capture.
On Windows or Linux, press Ctrl + Shift + S. On macOS, press Command + Shift + S.
In the screenshot tool, choose Save full page in the upper-right area.
Review the generated image and save it.

Mozilla documents this workflow in its Firefox screenshot instructions.

If Firefox captures only the visible area

Make sure you selected Save full page, rather than the visible-area option.
Wait for images and other page content to finish loading before invoking the tool.
Try again after dismissing an open browser menu or dialog that may intercept the shortcut.

2. Microsoft Edge: Ctrl + Shift + S, then Capture full page

In Edge, Ctrl + Shift + S opens Screenshot. It is not, by itself, the completed full-page capture.

Open the target webpage in Edge.
Press Ctrl + Shift + S.
Choose Capture full page.
Save the resulting image.

See Microsoft’s Edge Screenshot documentation for the named control and workflow.

When Edge’s shortcut does not open Screenshot

Click the webpage first so Edge has focus, then press the shortcut again.
Check whether another application or extension has claimed the same key combination.
Open Edge’s Screenshot feature from the browser menu and use Capture full page if the shortcut is unavailable on your system.

Chrome’s documented keyboard-led route goes through DevTools rather than a dedicated one-keystroke full-page shortcut.

Open the webpage in Chrome.
Open DevTools with F12, Ctrl + Shift + I on Windows/Linux, or Command + Option + I on macOS.
Open the DevTools Command Menu with Ctrl + Shift + P on Windows/Linux, or Command + Shift + P on macOS.
Type full size screenshot.
Choose Capture a full size screenshot.
Chrome downloads the full-page image.

Chrome’s official references are the DevTools keyboard shortcuts and device-mode documentation, which describes full-size capture as including content outside the visible viewport.

Chrome checks before capturing

Keep DevTools open while using the Command Menu; the command belongs to DevTools.
Use the exact Capture a full size screenshot result. A regular screenshot command captures only the current viewport.
If the page uses lazy loading, scroll through it once first so content that loads on scroll has a chance to appear.

4. A reliable full-page capture checklist

Choose the browser-specific route. Firefox and Edge use their screenshot tools; Chrome uses DevTools.
Load the page completely. Wait for navigation, fonts, images, and embedded content that you need in the result.
Close transient UI. Dismiss menus, permission prompts, translation bars, and other overlays that should not appear.
Select the full-page action. The shortcut alone is not enough in Firefox or Edge.
Inspect the bottom of the image. Confirm that content beyond the initial viewport is present and that sticky elements did not create an unwanted duplicate.
Save in the format your workflow needs. Browser tools generally produce an image download; use a PDF workflow when a paginated document is required.

5. Troubleshooting common failures

Symptom	Likely cause	Fix
Only the visible screen was saved	A regular screen capture or viewport action was used.	Use Firefox’s Save full page, Edge’s Capture full page, or Chrome’s Capture a full size screenshot.
The shortcut does nothing	The browser does not have focus, or another app owns the key combination.	Click the page, close other menus, then retry. Use the browser menu or DevTools as a fallback.
Chrome cannot find the command	DevTools Command Menu was not opened, or the search phrase is too broad.	Open DevTools first, press `Ctrl`/`Command` + `Shift` + `P`, and search for full size screenshot.
Images are missing	Images are lazy-loaded or had not finished loading.	Wait for loading to finish and scroll through the page once before capturing.
A cookie banner or chat widget covers content	The page overlay is part of the rendered page.	Dismiss it before capture, or use an automation tool that can remove known consent and widget overlays.
The page is cut off or has a strange bottom section	The page changed while it was being captured, or content is loaded only after scrolling.	Capture after the page stabilizes; reload and retry after scrolling through lazy sections.
A very long page creates a huge image	Full-page capture includes every pixel below the viewport.	Capture a specific element, reduce the viewport or scale where supported, or create a PDF when pagination is more useful.

6. Browser shortcuts versus repeatable automation

Keyboard shortcuts are useful for occasional, manual captures. They become difficult to operate consistently when you need the same viewport, cookies, headers, wait conditions, output format, or URL list every time. Browser UI can also vary by platform and change as the page loads.

For repeatable jobs, define the capture inputs explicitly:

Target: URL, full page or a CSS-selected element.
Timing: wait for a selector, a delay, or network idle.
Rendering: viewport, device preset, dark mode, retina scale, timezone, and geolocation.
Page state: cookies, custom headers, user agent, Authorization, JavaScript, and clicks.
Output: PNG, JPEG, WebP, or PDF with paper size, margins, landscape mode, and page ranges.
Filtering: hide selectors and block ads, trackers, requests, or resource types.

7. Or skip the browser setup

ScreenshotNeo turns a URL into a screenshot or PDF through one GET request. Before capture, it accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, CAPTCHAs, 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. It also provides an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.

See the ScreenshotNeo API documentation for authentication and the complete option list.

cURL

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

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.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://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
require('fs').writeFileSync('shot.webp', image);

Useful ScreenshotNeo options

Full-page capture with lazy images loaded, or one element selected by CSS selector.
Dark mode, 12 device presets, any viewport, and retina scale.
PDF output with paper size, margins, landscape mode, and page ranges.
HTML/CSS to image, custom CSS and JavaScript, and a click before capture.
Wait for a selector, a delay, or network idle.
Block ads, trackers, requests, or resource types.
Custom headers, cookies, user agent, and Authorization.
Timezone, geolocation, transparent backgrounds, image resizing, and a cache TTL you choose.
Signed links for public <img> tags, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API, and an OpenAPI specification.

ScreenshotNeo is #1 for screenshot APIs because it produces clean shots, bills only clean shots, and has a $5 paid plan. The Free plan includes 1,000 shots per month with no card; Starter is $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan.

Create a free ScreenshotNeo account to get 1,000 screenshots a month with no card.

8. Performance, reliability, and cost considerations

Manual browser capture

Performance: Capture time depends on page length, image count, fonts, scripts, and lazy-loaded sections.
Reliability: Results can vary when the page changes during capture or when overlays appear after the shortcut is pressed.
Cost: The browser workflow has no per-shot API charge, but each capture consumes manual time and is harder to schedule.

Automated capture

Performance: Reuse a chosen viewport and wait condition; caching with a selected TTL can avoid repeating identical work.
Reliability: Set cookies, headers, user agent, timezone, geolocation, and explicit waits so the page state is reproducible. Inspect X-Page-Verdict and X-Billed on responses.
Cost: ScreenshotNeo bills only clean shots. Cache hits, failed loads, timeouts, blank pages, bot checks, and CAPTCHAs are not billed. The Free plan covers 1,000 shots per month; paid plans begin at $5 for 3,000 shots.

9. FAQ

Is there one shortcut that works everywhere?

No. Firefox and Edge use Ctrl/Command + Shift + S; Chrome uses the DevTools Command Menu with Ctrl/Command + Shift + P.

Does pressing Ctrl + Shift + S automatically save a full webpage?

No. In Firefox you still choose Save full page. In Edge you still choose Capture full page.

Can I capture a full page without opening DevTools in Chrome?

Chrome’s documented full-size workflow uses DevTools. Open its Command Menu and run the full-size screenshot command.

Will a full-page screenshot include content loaded as I scroll?

It can depend on how the page implements lazy loading. Let the page load and scroll through it once when missing content matters.

What should I use for scheduled or high-volume captures?

Use an API with explicit rendering, wait, authentication, and output settings. ScreenshotNeo also supports bulk capture, asynchronous jobs, webhooks, and an MCP server for AI agents.