ScreenshotNeo

BlogHow-to

4 Ways to Capture a Full-Page Website Screenshot

Capture an entire webpage in Chrome, Firefox, or Edge. Compare four browser methods, save or copy the result, and troubleshoot common capture problems.

By the ScreenshotNeo team4 October 20267 min read

A full-page screenshot captures the webpage from top to bottom, including content outside the visible browser window. You can take one with Chrome DevTools, Firefox’s screenshot menu, Firefox DevTools, or Microsoft Edge’s Screenshot/Web Capture control. Firefox’s page menu is the simplest route; Chrome DevTools is useful when you already have developer tools open.

1. Capture a full page in Chrome

  1. Open the page in Chrome and wait for the content you need to appear.
  2. Open DevTools with F12 or Ctrl+Shift+I on Windows or Linux, or Command+Option+I on Mac.
  3. Open the DevTools Command Menu with Ctrl+Shift+P on Windows or Linux, or Command+Shift+P on Mac.
  4. Type screenshot, then choose the full-page command, commonly labeled Capture full size screenshot.
  5. Chrome saves the capture as an image file, typically in your downloads folder.

Chrome’s DevTools includes full-page capture, so this method does not require an extension. The command name can change between Chrome versions. If the exact label differs, search the Command Menu for “screenshot” and choose the command that captures the full page. See the Chrome DevTools Command Menu documentation and Chrome’s screenshot documentation.

2. Save a full-page screenshot from Firefox’s page menu

  1. Open the page in Firefox.
  2. Right-click an empty area of the page, or Control-click on Mac, and choose Take Screenshot. You can also press Ctrl+Shift+S on Windows or Linux, or Command+Shift+S on Mac.
  3. Choose Save full page.
  4. Choose Download to save a PNG in Firefox’s normal download location, or Copy to put the screenshot on your clipboard.

Choose Save visible instead if you only need the current viewport. Firefox’s page menu is the most direct option here because it does not require opening DevTools. Mozilla documents the controls and output options in its Firefox screenshot help.

3. Capture a full page with Firefox DevTools

Firefox DevTools provides a screenshot toolbar button and a Web Console helper. Use the toolbar if you prefer a visible control; use the console when you want to set a filename or delay.

Enable and use the screenshot button

  1. Open Firefox DevTools.
  2. Open DevTools Settings and find Available Toolbox Buttons.
  3. Enable Take a screenshot of the entire page.
  4. Click the screenshot button in the DevTools toolbar to capture the full page.

Use the Web Console

Open the Web Console, enter this helper, and press Enter:

:screenshot --fullpage

Firefox’s screenshot helper also supports options for a delay, filename, clipboard, and device pixel ratio. Check the current Firefox DevTools Web Console helper documentation for option names and syntax for your version.

4. Capture a full page in Microsoft Edge

  1. Open the page in Edge.
  2. Open the three-dot menu and look for Screenshot or Web Capture. You may also find a screenshot shortcut in your Edge version.
  3. Choose Capture full page if the option is available.
  4. Save or copy the result using the choices Edge presents.

Edge’s menu label and availability have varied. If you cannot find the feature or the full-page option, check the current three-dot menu and Edge’s help for your installed version. Microsoft-hosted community reports describe the changing labels and behavior, so treat this route as version-dependent rather than assuming every installation has the same control: Microsoft community support.

Choose the method that fits

Method Best for Output and controls Version sensitivity
Firefox page menu A quick capture without opening developer tools Save a PNG or copy to clipboard; choose full page or visible area Menu wording can vary
Chrome DevTools Developers already working in DevTools Full-page image saved as a file Command wording may change
Firefox DevTools Developer workflow or extra capture controls Toolbar button or console helper; helper supports options such as delay and filename Settings and helper syntax may vary
Edge Screenshot/Web Capture Captures directly in Edge when the option is available Full-page capture, with save or copy choices depending on version Labels and availability vary

A full-page capture is different from a normal screenshot of the screen or browser viewport: it includes page content below the visible area. These built-in browser routes do not require a separate physical product or a screenshot extension.

Make the capture complete and readable

  • Wait for the page to finish loading. If images, charts, or other content appear late, wait for them before capturing.
  • Scroll through the page once first. Some sites load images and other content only as you approach them. Scrolling gives those sections a chance to load.
  • Close overlays when appropriate. Cookie notices, chat panels, and newsletter dialogs can cover content. Dismiss them if you need an unobstructed capture and the site permits it.
  • Check the full image after saving. Look for missing sections, cut-off content, or overlays before sharing it.
  • Use clipboard output when you need to paste immediately. Firefox’s screenshot interface offers Copy; otherwise save the image and insert the file into your document or message.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server from ScreenshotNeo. A single GET request can return a screenshot as PNG, JPEG, or WebP, or a PDF. For API options and configuration, see the ScreenshotNeo documentation. This call captures the page as a WebP file:

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

Cookie banners, popups, and chat widgets are removed before the shot; each cleanup step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers report the page verdict and billing status. AI agents can take screenshots through the MCP server. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.

Sign up free and get 1,000 screenshots a month with no card.

Troubleshooting

The capture only contains the visible screen

You likely chose a viewport or visible-area command. In Firefox, choose Save full page; in Chrome, use the full-size screenshot command; in Edge, look for Capture full page.

Images or sections are missing

The page may load content as you scroll, or content may still be loading. Scroll through the page, wait for images and sections to appear, then capture again. Some pages update continuously, so the result can reflect a moment during that update.

The browser command or menu item is missing

Menu names and availability can vary by version. In Chrome, search the Command Menu for “screenshot.” In Firefox, try the page context menu or check DevTools’ available toolbox buttons. In Edge, inspect the current three-dot menu for Screenshot or Web Capture.

The image is hard to paste into another app

Use Firefox’s Copy option to place the capture on the clipboard. If your browser only saves a file, insert the downloaded image from its folder.

The capture includes a banner or chat panel

Dismiss the overlay before taking the screenshot, then capture again. If it reappears or blocks the page, use a capture workflow that supports removing consent banners and chat widgets.

Edge’s full-page capture is unavailable or incomplete

Edge’s screenshot controls have changed across versions and reports describe differing behavior. Check the installed version’s current menu and retry after the page has loaded. If the option is unavailable, use one of the Chrome or Firefox methods above.

Performance, reliability, and cost

For an occasional screenshot, a built-in browser capture is usually the simplest path and adds no separate service charge. Capture time and file size depend on page length, image content, and how much content the page loads. Waiting for lazy-loaded content improves completeness but adds time. Dynamic pages can change while a capture is being assembled, so check the saved image when accuracy matters.

If you need repeatable captures across many URLs, scripted settings, or a workflow for AI agents, an API can avoid repeating the browser steps. ScreenshotNeo provides configurable waits, full-page capture with lazy images loaded, caching with a chosen TTL, bulk capture for up to 100 URLs per call, and an MCP server. Its plans are Free for 1,000 shots a month, Starter $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. Every feature is on every plan. See the ScreenshotNeo site for the product and plan details.

Frequently asked questions

How do I take a full-page screenshot?

Use the browser’s full-page command: Chrome DevTools, Firefox’s Save full page menu, Firefox DevTools, or Edge’s Screenshot/Web Capture option if available.

How do I screenshot an entire webpage?

Choose a full-page capture mode rather than the standard screen or visible-area mode. The exact control depends on your browser.

Can I capture a full webpage in Safari with these steps?

No Safari full-webpage image workflow is established by the sources used for this guide. Apple’s Mac screenshot support describes screen, window, and selected-area captures, not a native Safari full-page image capture.

Can I save the screenshot directly to the clipboard?

Firefox’s screenshot interface offers a Copy choice. In the other methods, use the save option and then insert the resulting file if clipboard output is not offered.