Visit Website →
← Back to blog

Full Page Screenshots in Firefox: Built In, Console, or Extension

October 13, 2026
Full Page Screenshots in Firefox: Built In, Console, or Extension

The fastest way to grab a full page screenshot in Firefox is to right-click anywhere on the page, choose "Take Screenshot," and select "Save full page," which saves a PNG straight to your Downloads folder. For repeatable or scripted captures, open the Web Console and run :screenshot filename.png --fullpage. When a page has inner scroll panels or lazy-loaded content that breaks the built-in tool, an add-on fills the gap.

TL;DR:

  • If Take Screenshot is missing, open DevTools settings, enable Take a screenshot of the entire page under Available Toolbox Buttons, and restore its camera icon.
  • For repeatable captures, the Web Console supports custom filenames and clipboard copying, and it can capture one selected page element instead of the whole page.
  • Cropped captures often result from inner scroll panels or late loading images; scroll through the page first, then capture the scrolling element if needed.
  • Choose an extension for inner panels, then check its permissions, local image processing, update history, and compatibility with your Firefox version before installing.
Usepinhub
Make Screenshot Feedback More Precise
Upload screenshots and pin comments to specific points, so teams and clients can discuss visual details without vague feedback.
Explore Pinhub

Table of Contents

Capturing a full page with Firefox's built-in screenshot tool

Firefox ships with a screenshot tool that handles most pages without any setup. Right-click an empty area of the page, select "Take Screenshot," then choose "Save full page" instead of "Save visible." The browser scrolls through the entire page, stitches the result together, and downloads a PNG using the page title as the default filename, according to Firefox's support documentation. No extension or account is needed for this workflow.

If the "Take Screenshot" option is missing from your right-click menu, it usually means the camera button has been removed from DevTools rather than disabled entirely. You can bring it back manually:

  • Open DevTools with F12 or right-click and select "Inspect."
  • Click the gear icon for Settings, then find "Available Toolbox Buttons."
  • Enable "Take a screenshot of the entire page" to add the camera icon to the toolbar.

Once enabled, clicking that camera icon triggers the same full-page capture as the context menu option. Choosing between "visible area" and "full page" matters: visible-area captures are faster for quick reference, while full-page captures are what you want for reviewing layout, long-form content, or anything that scrolls past the fold.

Using the Web Console :screenshot command for repeatable captures

Power users who need consistent filenames or want to skip the mouse entirely can use the Web Console instead. Press Ctrl+Shift+K to open it, then type :screenshot myfile.png --fullpage and hit Enter. The command captures the entire page and saves it to Downloads with the filename you specify, as documented in Firefox's DevTools reference.

A few flags make this command genuinely flexible:

  • --fullpage captures the entire scrollable page rather than just the viewport.
  • --filename sets a custom name instead of the browser's default.
  • --clipboard copies the image directly instead of writing a file.
  • --selector captures a single DOM element you specify, skipping the rest of the page.

The console command suits automation, stable filenames, and clipboard-based workflows where you're pasting straight into a document or chat. The context menu remains simpler for a one-off capture, so the console is worth learning mainly if you take screenshots often enough that the extra step pays off.

Pro Tip: Add --clipboard when you're about to paste a screenshot into a feedback tool or chat message. It skips the Downloads folder entirely.

Choosing an add-on for scrolling, element, and clipboard captures

When the built-in tool can't handle a page, a dedicated extension usually can. Add-ons listed on Mozilla's add-ons site typically offer four capture modes: full page, visible area, a selected region, and scrolling selection that stitches multiple frames together.

What makes a good add-on worth installing:

  • Support for inner scroll panels that the built-in tool often misses.
  • Clipboard output alongside file saving, so you can paste without extra steps.
  • Adjustable output quality and format, including PNG and JPEG.
  • A preview window before you commit to downloading, so you can confirm the capture looks right.

Before installing anything, run through a short checklist. Check that the extension requests only the permissions its features justify, confirm that image processing happens locally rather than on a remote server, and look at the update history to make sure it's compatible with your current Firefox version. Extensions that explicitly advertise handling for scroll containers and local-only processing, such as the SnapFold listing on Mozilla's add-ons site, tend to perform better on complex, app-like pages. Most extensions also let you set a custom keyboard shortcut from the about:addons page, which speeds things up once you've settled on one you trust.

Fixing cropped, truncated, or incomplete screenshots

Most cropped screenshots trace back to one of a few predictable causes, and each has a workaround.

  1. Inner scroll containers. Some pages place their actual scrolling behavior on a child element rather than the main document, which causes Firefox's full-page capture to grab only the visible slice. Mozilla's Bugzilla tracker documents this pattern on pages where a child element uses overflow:auto or where the html/body uses overflow:hidden.
  2. Lazy-loaded images. Content that loads as you scroll can appear blank or missing if the capture runs before the images finish loading. Scrolling through the page slowly once before capturing usually triggers the load in time.
  3. Historical height limits. Earlier Firefox versions capped full-page captures at certain pixel heights on extremely tall pages, which Bugzilla also documents.

When a page uses a child scroll container, Bugzilla outlines three practical fixes: capture the node that actually scrolls using Inspector's "Screenshot node" option or :screenshot --selector, use an extension built to expand inner panels and stitch the result, or trigger a print-media layout that reflows the page before capture. Each trades off convenience against fidelity, so pick based on how often you'll need to repeat it.

Always open the saved PNG afterward and check the bottom of the image and any embedded graphics. If the page was still loading when you captured it, just scroll through once and run the capture again.

Complete and clipped webpage screenshot comparison

Quick cheat sheet for saving a full page screenshot

Three workflows cover nearly every situation, from casual one-off captures to a repeatable routine.

  1. Built-in, no setup: right-click the page, choose "Take Screenshot," then "Save full page." The download starts automatically.
  2. Console, repeatable: press Ctrl+Shift+K, then run :screenshot myshot.png --fullpage. Add --clipboard if you'd rather copy than save.
  3. Add-on, one click: pin the extension's toolbar button for instant full-page capture, or right-click for a region or single element. Change the keyboard shortcut anytime from about:addons.

Why reliable screenshots matter for review workflows

A screenshot is only useful if it actually shows the whole page, because every piece of feedback anchored to it depends on that accuracy. When a capture is cropped or missing lazy-loaded sections, reviewers end up guessing at context instead of pointing at specifics. Full, reliable captures cut down on back-and-forth between designers, product teams, and clients, and they turn a screenshot from a static image into a dependable reference for the conversation that follows.

— Pinhub

Annotate and share your screenshots with Pinhub

Once you've got a clean full-page capture, the next step is turning it into feedback people can actually act on. We built Pinhub to let you upload screenshots, pin comments to exact pixels, and invite guest reviewers who can respond without creating an account. Every round of feedback is versioned, so nothing gets lost between revisions.

Usepinhub

If you're reviewing designs with a team or a client, start on our free plan at Usepinhub and see how much faster pixel-anchored comments move a review along.

FAQ

How do I take a screenshot of an entire webpage in Firefox?

Right-click anywhere on the page, select "Take Screenshot," then choose "Save full page" to download a PNG of the entire scrollable page, as described in Firefox's support guide. No extension is required for this built-in workflow.

Why is my Firefox full-page screenshot cut off?

This usually happens when a page scrolls inside a child element rather than the main document, or when images load late and get missed during capture. Bugzilla documents these truncation cases and recommends capturing the specific scrolling element or scrolling the page fully before taking the shot.

What does the :screenshot --fullpage command do?

Running :screenshot filename.png --fullpage in the Web Console captures the entire page, not just the visible viewport, and saves it under the name you choose. The DevTools documentation also lists --clipboard for copying instead of saving and --selector for capturing a single element.

How do I enable the screenshot camera button in Firefox DevTools?

Open DevTools, click the Settings gear, and check "Take a screenshot of the entire page" under Available Toolbox Buttons. This adds a camera icon to the toolbar that triggers the same full-page capture as the right-click menu.

Do I need an add-on to capture a full page in Firefox?

Not for most pages, since the built-in tool handles standard full-page captures without any installation. An add-on helps mainly when a page uses inner scroll containers or needs clipboard output and adjustable formats, features covered in extension listings on Mozilla's add-ons site.

Sources