How to Screenshot a Full Webpage in Safari on a Mac

To capture a full webpage as one tall image in Safari on a Mac, enable Safari’s developer features, open Web Inspector, select the page’s top-level html element, and look for a screenshot capture command. The capture command and its menu location can vary by Safari version; Apple documents how to enable developer features and open Web Inspector, but the research sources do not confirm that exact full-page command for every release.

1. Enable Safari’s developer features

1. Open Safari and choose Safari > Settings.
2. Select Advanced.
3. Check Show features for web developers. Older Safari versions may call Settings “Preferences” or use different wording.

Developer features are off by default. Enabling them adds the Develop menu. See Apple’s instructions for enabling developer features.

2. Open Web Inspector and look for page capture

1. Open the webpage you want to capture and make its Safari tab active.
2. Choose Develop > Show Web Inspector, or right-click the page and choose Inspect Element. Apple documents Option-Command-I as a shortcut for opening Web Inspector. See Apple’s Web Inspector instructions.
3. In the inspector’s element view, select the top-level html element.
4. Look for a screenshot or capture command in the contextual menu or inspector controls. A third-party guide describes choosing Capture Screenshot for the top-level page element. The exact label and availability are version-sensitive; if you cannot find it, use one of the alternatives below.
5. Save the resulting image where you can find it and check that the bottom of the page is present.

Apple’s cited documentation confirms how to enable developer features and open Web Inspector. It does not confirm the exact full-page capture command described above, so check the controls in your installed Safari version rather than assuming the menu is identical.

3. Prepare pages with lazy or changing content

A capture can only include content that has loaded into the page state being captured. Long pages may load images or sections as you scroll; interactive pages may require a click or a consent choice before content appears.

• Scroll through the page from top to bottom before capture, pausing where images or content load on demand.
• Expand any sections you want included and handle page prompts that block the content you need.
• Return to the top before capturing if the capture command uses the current page state.
• After capture, inspect the image for missing lower sections, blank areas, overlays, or content that changed during capture.

These are practical precautions based on how pages load and change; they are not a guarantee that every site can be captured as one complete image.

4. Choose the right output for the job

What you need	Use	What you get
One image of the whole scrolling page	Web Inspector capture command, if present in your Safari version	A tall image; the command is version-sensitive.
An image of the current Mac display	Shift-Command-3	A screenshot of the display, not a documented scrolling-page capture.
An image of a chosen area	Shift-Command-4	A screenshot of the selected screen region.
A saved webpage with resources	File > Save As > Web Archive	A webpage archive. Links can work while their destination pages remain available; some sites may prevent saving items.
The page’s markup	File > Save As > Page Source	HTML source, not a rendered screenshot.
A full-page capture through an extension	FullPage Screenshot for Safari	The App Store listing describes full-page and visible-area captures, editing, PNG download, and PDF export. Check current price and compatibility in the listing.

Apple’s Mac screenshot guide documents the standard screen shortcuts and window capture. Its guide to saving part or all of a webpage in Safari explains Web Archive and Page Source.

5. Troubleshoot common capture problems

Problem	Likely cause	What to try
No Develop menu	Developer features are disabled, or the Safari version uses different labels.	Open Safari > Settings > Advanced and enable Show features for web developers. Check the equivalent Preferences panel on older releases.
No screenshot command in Web Inspector	The command may be absent or located differently in your Safari version.	Confirm you selected the top-level html element and inspect the available menus. If the command is unavailable, use a current compatible extension or a screenshot API.
The image only shows the visible screen	A standard macOS screenshot shortcut captures the display or selected region, not the entire scrolling document.	Use a full-page capture command or extension, and verify the output dimensions and lower-page content.
Images or sections are missing	Content may load only when scrolled into view or after interaction.	Scroll the page before capture, wait for loading to finish, and expand the sections you need.
A banner or chat widget covers the page	The overlay is part of the page’s current visible state.	Dismiss it if appropriate and allowed, or use a capture workflow that can remove known overlays. Check the final image for remaining overlays.
Web Archive is not available or incomplete	The site may prevent saving some items; archived links also depend on their destination pages remaining available.	Try another output format if you need a visual record. Use Page Source only when HTML markup is the goal.

Performance, reliability, and cost

For a single page, the built-in Safari route avoids installing another tool, but its full-page capture control is not confirmed by the Apple sources cited here and can vary by version. Dynamic content, lazy loading, overlays, and pages that change while loading can affect what appears in the result. Always review the saved image before sharing or relying on it.

A Safari extension may be convenient for repeated manual captures, but availability, compatibility, and price can change. For scripted captures or captures from outside your Mac, an API avoids setting up a local browser workflow. The result and cost depend on the service and its current terms; do not assume a screenshot represents content behind a login or a page state you did not configure.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. One GET request can return a PNG, JPEG, WebP, or PDF. For this example, request a WebP screenshot of the page:

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,
)
r.raise_for_status()
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}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));

See the ScreenshotNeo API documentation for request options. Cookie banners, 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, and response headers report the page verdict and billing status. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots. Sign up for 1,000 free screenshots a month, with no card required.

FAQ

Does Shift-Command-3 capture an entire scrolling webpage?

No. Apple documents it as capturing the Mac screen. Use a full-page capture workflow for the whole scrolling document.

Is a Web Archive a screenshot?

No. It saves a webpage package, while Page Source saves HTML markup. Choose an image capture when you need a rendered visual record.

Can every Safari version capture a full page from Web Inspector?

The Apple sources reviewed do not establish that. The inspector route is version-sensitive, so verify whether your installed Safari exposes a page capture command.

Can I capture a page that requires a login?

Only if the capture method has access to the required authenticated session or credentials. A normal Safari capture uses the page state available in that browser; an API needs its supported authentication setup.