How to Fix Full-Page Screenshots Not Working in Firefox
Fix missing, broken, or unsaved Firefox full-page screenshots with a symptom-based checklist and a browser-free API option.
Firefox has a built-in full-page screenshot tool. Open the page, right-click an empty area, choose Take Screenshot, then choose Save full page. You can also press Ctrl + Shift + S on Windows or Linux, or Command + Shift + S on macOS. If the command is missing, the capture fails, or the file cannot be saved, use the matching fix below.
Mozilla documents this workflow in Firefox Help. Interface names can vary by Firefox version.
1. Take a full-page screenshot in Firefox
- Open the page you want to capture.
- Right-click an empty part of the page and select Take Screenshot, or use the keyboard shortcut.
- In the capture toolbar, select Save full page.
- Select Download to save an image, or Copy to place it on the clipboard.
Save visible captures only the current viewport. Use Save full page when you need content below the fold.
2. If “Take Screenshot” is missing
Try the other entry points
- Right-click an empty area of the webpage and look for Take Screenshot.
- Press Ctrl + Shift + S (Windows/Linux) or Command + Shift + S (macOS).
- Open More Tools → Customize Toolbar. Add the Screenshot button to the toolbar, then select Done.
Check the screenshot preference
Mozilla Support troubleshooting discussions identify extensions.screenshots.disabled as a possible cause when the feature disappears. Enter about:config in the address bar, accept the warning, search for that preference, and check whether it is explicitly set to true. If so, restore the default value (normally false) and try again. Change only this preference; do not modify unrelated settings.
Check whether Firefox is managed
If the preference is locked or cannot be changed, open about:policies. An enterprise policy may disable screenshots. On a managed computer, your administrator may need to change that policy.
3. If the capture panel opens but full-page capture fails
Test another ordinary website
Capture a simple public page. If that works, the original site is probably the limiting factor. Mozilla Support guidance notes that some frameset pages, pages with special permissions to modify Firefox, and Firefox’s own internal pages are unsupported. A failure on one site does not prove that Firefox screenshots are broken everywhere.
Check the page type
- Do not use Firefox’s internal pages such as
about:pages as your compatibility test. - Try the page in a normal tab rather than a special browser surface or extension view.
- If the page is built from frames or embeds, capture the individual frame URL when possible.
Separate page failures from browser failures
- Capture a basic article page.
- Capture the target page in a private window.
- Disable extensions temporarily and retry.
- Compare the result across another ordinary site.
These checks identify scope; they do not guarantee a fix for every page.
4. If the screenshot succeeds but you cannot find or use it
- Select Download in the capture interface. The file goes to Firefox’s configured download folder.
- Select Copy and paste into an image editor or document.
- Check Firefox’s download settings if no file appears where expected.
- Make sure the clipboard destination accepts images; some applications accept only text.
5. A symptom-based troubleshooting checklist
| Symptom | Likely cause | What to do |
|---|---|---|
| No Take Screenshot command | Toolbar removal, disabled preference, or policy | Use the shortcut, customize the toolbar, inspect about:config, then check about:policies. |
| Shortcut does nothing | Focus is in another control, shortcut conflict, or feature disabled | Click the page first, use the context menu, then test the preference and policy checks. |
| Panel opens but Save full page fails | Page compatibility or unsupported browser page | Test an ordinary site and capture a frame or public URL separately. |
| Only the visible viewport is captured | Save visible was selected | Open the capture panel again and choose Save full page. |
| Download is missing | Unknown download folder or blocked file handling | Use Download again and inspect Firefox’s configured download location. |
| Copy does not paste an image | Destination does not accept image clipboard data | Use Download or paste into an image-capable editor. |
| Works on some sites only | Site-specific compatibility | Compare with an ordinary page; investigate frames, special permissions, and internal pages. |
6. Reliability and practical limits
Firefox’s built-in tool is convenient for occasional manual captures. Its behavior depends on the page being rendered in the browser and on the page type. A site-specific failure, an internal Firefox page, a frameset, or an organization policy can prevent capture. Mozilla Support forum guidance describes screenshots as working on almost all web pages while noting exceptions; treat that as troubleshooting guidance rather than a formal guarantee.
For repeatable work, record the URL, Firefox version, operating system, whether the failure occurs on all sites, and whether the installation is managed. This information quickly separates a browser-wide configuration problem from a page compatibility problem.
7. Or skip the browser setup
ScreenshotNeo captures a URL through one API request, so you do not need to open Firefox or manage browser automation. Before capture it accepts cookie and consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response reports the result in X-Page-Verdict and X-Billed headers.
See the ScreenshotNeo API documentation for all options, including full-page capture, lazy-image loading, CSS-selector element capture, device presets, custom viewports, retina scale, dark mode, custom CSS and JavaScript, waits, blocked resources, headers, cookies, user agents, timezone, geolocation, transparent backgrounds, resizing, caching, signed links, asynchronous jobs, webhooks, bulk capture, usage, and PDF output.
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,
)
r.raise_for_status()
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}`);
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));
ScreenshotNeo has an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 shots each month without a card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
8. FAQ
Can Firefox save a full page as an image?
Yes. Open Take Screenshot and choose Save full page, then download or copy the result.
Why can I capture one site but not another?
The failing page may use an unsupported frameset, special permissions, or a Firefox internal page. Compare it with an ordinary website to confirm the scope.
What if my company controls Firefox?
Inspect about:policies. A policy may disable screenshots, and only an administrator may be able to change it.
Is an extension required?
No. Firefox includes the feature. Extensions are optional and are not required by the documented workflow.
Where does Firefox put the downloaded image?
It uses Firefox’s configured download location. The Download action in the capture panel saves the image there.


