How to Capture a Full Webpage Screenshot on Ubuntu for Technical Documentation

To capture a full webpage on Ubuntu, use Firefox’s built-in screenshot tool: open the page, choose Take Screenshot from the page context menu, select Save full page, then download the PNG. This captures the document beyond the visible browser window. The Ubuntu desktop screenshot utility captures the screen, a window, or a selected area; it does not replace Firefox’s full-document capture for a page that scrolls. Mozilla’s screenshot guide documents full-page and visible-only capture; Ubuntu’s desktop screenshot guide describes the desktop capture modes.

1. Capture the full page with Firefox’s screenshot tool

1. Open the target webpage in Firefox on Ubuntu and wait for the content you need to appear.
2. Right-click an empty area of the page and choose Take Screenshot. If the context menu is inconvenient, use Ctrl+Shift+S.
3. Choose Save full page in the screenshot interface. Choose Save visible only when you want the current viewport rather than the entire document.
4. Select Download. Firefox saves the image to its configured download folder. The file is a PNG.
5. Open the saved image and inspect the top, middle, and bottom before attaching it to documentation. Give it a descriptive name such as checkout-flow-full-page.png.

Firefox can also select a page region or an automatically highlighted page part in this interface. Those are useful for a focused diagram or component, but they are not the right choice when the documentation needs the entire page. See Firefox screenshot instructions.

2. Use Firefox Developer Tools for a repeatable GUI workflow

Firefox Developer Tools has a full-page screenshot button. It may be hidden until enabled:

1. Open Developer Tools with Ctrl+Shift+I.
2. Open Developer Tools Settings.
3. Under Available Toolbox Buttons, enable Take a screenshot of the entire page.
4. Return to the toolbox and click the screenshot icon. Firefox saves the capture in its Downloads directory.

This approach is handy when you already use the Inspector or need to capture an individual DOM element. To capture one element, inspect it and use the element context menu’s Screenshot Node command. Mozilla documents both workflows in its Developer Tools screenshot guide.

3. Capture from Firefox’s Web Console

For a command-oriented workflow, Firefox’s Web Console provides the :screenshot helper. Open the console with Ctrl+Shift+K, then enter:

:screenshot --fullpage --filename=technical-docs.png

The --fullpage option includes content outside the browser window. Mozilla’s documented options include:

Option	Purpose	Example
--fullpage	Capture the entire webpage beyond the current window bounds.	:screenshot --fullpage
--filename	Choose an output name. Use a .png extension.	:screenshot --fullpage --filename=api-reference.png
--delay	Wait a number of seconds before capture, useful for a transient menu or hover state.	:screenshot --fullpage --delay=2
--dpr	Set device pixel ratio. Values over 1 produce a more pixel-dense, zoomed-in image; values under 1 produce a less pixel-dense image.	:screenshot --fullpage --dpr=2
--selector	Capture a matching element and its contents rather than the entire page.	:screenshot --selector=.article-content
--clipboard	Copy the capture to the clipboard. This prevents writing a file unless --file is also supplied.	:screenshot --fullpage --clipboard
--file	Force writing a file when using options such as --clipboard.	:screenshot --fullpage --clipboard --file --filename=page.png

For example, to capture a full page after a short delay at a higher pixel ratio:

:screenshot --fullpage --delay=1.5 --dpr=2 --filename=setup-guide.png

Firefox may append a full-page marker to the output filename. Avoid reusing a filename when you want to preserve earlier captures: a capture to the same filename can overwrite the previous file. The options and filename behavior are described in Mozilla’s Web Console helper reference.

4. Choose the right capture method

Method	Captures	Best for	Output location
Firefox context menu	Full page, visible viewport, region, or highlighted part	Quick one-off documentation images	Firefox’s configured download folder
Developer Tools screenshot button	Full page or inspected element	Captures while working in Developer Tools	Downloads
Web Console :screenshot	Full page or selected element, with options	Named captures, delay, device pixel ratio, or clipboard	Browser download location unless copied
Ubuntu Screenshot utility	Entire screen, a window, or selected screen area	Including desktop, app chrome, or other windows	Pictures/Screenshots according to Ubuntu help

If the deliverable must show the browser window or Ubuntu desktop itself, use the Ubuntu utility. If it must show webpage content below the fold without desktop chrome, use Firefox’s full-page feature. The desktop modes and save location are covered by Ubuntu Documentation.

5. Prepare a useful technical documentation capture

1. Set the page state first. Sign in if the target content requires it, navigate to the relevant state, and wait for charts, images, or code samples to render.
2. Choose scope deliberately. Use full page for a complete procedure, a selected element for a specific panel, or visible capture for a viewport-specific behavior.
3. Check overlays. Dismiss menus and unrelated transient overlays where possible. If a banner or menu is the subject of the documentation, keep it visible intentionally.
4. Review legibility. A very long page can become a tall image whose text is difficult to read at normal display size. For a readable guide, capture meaningful sections separately when a single tall image is not useful.
5. Check sensitive information. Look for personal data, private account details, tokens, or internal URLs before sharing the screenshot.
6. Use a descriptive filename. Include the feature or procedure and, when useful, a version or date. Confirm the file is the expected PNG and not an older capture.

6. Troubleshooting

Symptom	Likely cause	Fix
Take Screenshot is missing from the context menu.	The menu was opened over a control, image, or embedded content, or the UI differs in the installed Firefox version.	Right-click an empty page area or use Ctrl+Shift+S. Try the Developer Tools button or the Web Console route if needed.
Only the visible area was captured.	Save visible was selected.	Repeat and select Save full page, or run :screenshot --fullpage in the Web Console.
The Developer Tools screenshot icon is absent.	The toolbox button is disabled by default.	In Developer Tools Settings, enable Take a screenshot of the entire page under Available Toolbox Buttons.
The image has a generic name or the wrong name.	The default command filename was used, or an existing filename was reused.	Pass a unique --filename=.... Check Downloads and avoid overwriting an earlier capture.
The screenshot went to the clipboard rather than a file.	--clipboard was supplied without --file.	Use --file --filename=page.png as well, or rerun without --clipboard.
A menu or hover state disappeared before capture.	The capture started before the transient state was ready.	Use --delay=1 or another suitable delay, then trigger the state before the capture. For manual capture, wait until the desired state is visible.
The capture is huge or text looks too small.	The page is long, or a high device pixel ratio created more pixels than needed.	Use the default ratio or a lower --dpr; consider capturing sections separately for documentation readers.
Some content is blank or missing.	The content had not loaded, requires interaction, or appears only after scrolling or waiting.	Wait for the page to finish rendering, perform the required interaction, scroll through the relevant lazy-loaded areas, then capture and inspect the result. A delay can help with known transient rendering, but it does not guarantee every page has loaded.
Screenshot controls behave differently on Ubuntu.	Firefox version, desktop session, or settings can affect controls. Mozilla currently notes a keyboard crosshair limitation on Wayland for region selection.	Use the full-page action or Web Console instead of relying on crosshair region selection; verify the saved file after capture.

7. Performance, reliability, and file handling

Browser capture is a manual operation and uses the page as rendered in your current Firefox session. Long pages and high device pixel ratios create larger images, so use a sensible pixel ratio and verify that the resulting image remains readable and manageable for the documentation system. A delay is only a fixed wait; it is not proof that every image or asynchronous component has completed loading. Review captures when the page is dynamic or when completeness matters.

For repeatable manual work, use a consistent viewport, page state, filename convention, and capture method. Keep original screenshots when they are source material for documentation, and record the page URL and capture date alongside them if your process requires traceability. These are workflow recommendations; the cited Firefox and Ubuntu documentation describes the capture controls and locations, not a guarantee that every website renders identically.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. One GET request can return a webpage screenshot as PNG, JPEG, WebP, or PDF. For a full-page capture, the API accepts screenshot options, including full-page capture. See the ScreenshotNeo API documentation.

cURL:

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

Python:

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)

Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

Before capture, ScreenshotNeo accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server exposes take_screenshot, get_page_info, and capture_pdf for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Every feature is on every plan.

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

FAQ

Does Ubuntu’s built-in screenshot tool capture a whole webpage?

It captures the screen, a window, or a selected screen area. For the entire scrollable webpage without desktop chrome, use Firefox’s full-page capture.

Where does Firefox save the screenshot?

The screenshot interface downloads to Firefox’s configured download folder. The Developer Tools screenshot documentation specifies Downloads. The Web Console helper can also copy to the clipboard when requested.

Can I capture just one element?

Yes. Use the Developer Tools Inspector’s Screenshot Node command, or pass a CSS selector to Firefox’s :screenshot helper.

Can I include a menu or hover effect?

Yes. Open the desired state and use the Web Console’s --delay option when a short wait is needed before capture.

Which format does Firefox produce?

The documented Firefox screenshot workflows save PNG images. ScreenshotNeo also offers JPEG, WebP, and PDF output.