FireShot Not Working on a Website: Permissions and Fixes

If FireShot is not capturing a website, first identify what is failing: the extension may do nothing, capture only the visible viewport, omit content, show a permissions prompt, or fail to save. If you use Firefox, inspect that site’s special permissions in the address-bar Permissions panel and clear only a permission that should return to its default. Then confirm that FireShot is set to capture the visible area, a selected area, or the entire page as intended. These checks address different problems; changing a site permission is not a universal fix for every capture failure.

Firefox site permissions and FireShot’s extension permissions are separate. FireShot’s Firefox add-on listing includes permission to access data for all websites, while Firefox’s Permissions panel shows changed permissions for a particular site. Don’t treat one list as the other.

1. Identify the failure before changing settings

Write down the exact symptom and compare it with what you expected. A permission prompt, a viewport-only image, and a failed save point to different parts of the process.

Symptom	First check
The toolbar button or menu does nothing	Record the browser and FireShot versions, operating system, page, and any error text. Check whether the issue is limited to one site.
The image shows only what was on screen	Confirm that you chose entire-page capture rather than visible-area capture.
A permission prompt appears	Record the exact prompt and browser. In Firefox, inspect the affected site’s permissions separately from the extension’s permission listing.
Some page content is missing	Record which content is missing and whether visible-area and entire-page capture behave differently. The available FireShot sources do not establish a universal cause for site-specific missing content.
The capture appears to work but does not save	Record the output action, any error, and whether the problem happens on other sites too.

For any symptom, note the browser and its version, operating system, FireShot version and installation source, affected page, selected capture mode, and exact prompt or error. Version matters: the Firefox listing describes one release and notes a newer version 2 rollout through the developer’s site, so the listing alone does not identify the version you have installed.

2. Check FireShot’s capture mode

FireShot distinguishes among visible-area, selected-area, and entire-page captures. If the result contains only the viewport, check the mode first: a visible-area capture is expected to show only the area currently visible in the browser. To capture beyond it, choose the entire-page mode in your installed version. Interface names may differ because the available FireShot manual is legacy documentation.

1. Open the FireShot capture menu.
2. Choose the mode that matches the result you need: visible area, selected area, or entire page.
3. Capture the same page again and compare the result.
4. If the entire-page capture still fails, record whether visible-area capture works. That comparison is useful when reporting the problem.

3. Review Firefox permissions for the affected site

Firefox exposes changed special permissions in the address-bar Permissions panel. The icon may not appear when a permission remains at its default. Mozilla documents that clearing a permission entry with its X restores that permission type’s default. For other permissions, open Page Info through the site-information panel.

1. Open the affected website in Firefox.
2. Open the site-information panel from the address bar and look for the Permissions panel or icon.
3. Review the permissions shown for that site. Change only an entry that is relevant and should return to its default.
4. To restore a listed permission’s default, clear that entry using its X.
5. If the permission you need is not shown there, check Page Info through the site-information panel.
6. Retry the same FireShot capture mode and note whether the result changed.

Mozilla’s instructions explain how to inspect and reset Firefox site permissions; they do not say that resetting a site permission will fix all extension capture problems. If there is no relevant changed site permission, or clearing one makes no difference, keep troubleshooting the actual symptom rather than changing unrelated settings. See Mozilla’s Site Permissions panel instructions.

4. Keep site permissions and extension permissions separate

A per-site setting in Firefox controls a permission associated with that website. FireShot’s own permission list describes what the extension can access. The Firefox add-on listing names access to data for all websites among FireShot’s permissions. That listing does not mean every website has a separate FireShot-specific permission to toggle, and it does not explain every prompt.

A FireShot forum user reported a Chrome 129 prompt for additional privileges on certain pages while using FireShot 2.0.2.2 on macOS; the user said the prompt buttons did nothing but visible-area capture worked. This is one user’s report about Chrome, not an official diagnosis or evidence that Firefox users have the same cause. If your prompt resembles it, include the browser, extension version, operating system, exact prompt text, and whether visible-area capture works when you ask for help.

5. Retry in a way that isolates the cause

After checking the mode and any relevant Firefox site permission, make one controlled comparison:

1. Retry on the affected page with the mode you originally wanted.
2. If it fails, try visible-area capture on the same page and record whether it works.
3. If useful, try the same mode on another page to establish whether the failure is limited to one site.
4. Keep the exact error or prompt text. Do not infer that the site’s permissions caused the problem solely because it occurs on one site.

This comparison helps distinguish a mode mismatch from a site-specific failure or a broader extension problem. The available sources do not establish that FireShot works on every protected, dynamic, or unusual page, so report what you observed without assuming a compatibility cause.

6. Get useful help if it still fails

FireShot’s Firefox add-on listing directs users with technical issues to its support forum. Before posting, gather:

• Browser name and version
• FireShot version and installation source
• Operating system
• The affected page or site
• Desired and selected capture modes
• Exact prompt or error text
• Whether visible-area capture works and whether the issue is limited to that site
• What you checked in Firefox’s site permissions and the result

Use the FireShot Firefox add-on listing for its support direction and permission information. Avoid assuming an upgrade will fix a capture or permission failure: the sources describe additional Pro export and editing capabilities but do not establish that Pro resolves these problems.

Or skip the browser setup

If your goal is simply to capture a website, ScreenshotNeo is a website screenshot API and MCP server. A single request can return a PNG, JPEG, WebP, or PDF. It accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. AI agents can use its MCP server tools to take screenshots, get page information, and capture PDFs.

See the ScreenshotNeo API documentation. Example cURL request:

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}`);

Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed; an MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card.

Frequently asked questions

Why does FireShot capture only the visible part of a page?

Check whether you selected visible-area capture. FireShot provides separate visible-area, selected-area, and entire-page modes.

Does resetting Firefox site permissions always fix FireShot?

No. Mozilla documents how to inspect and reset site permissions, but the available sources do not show that doing so resolves every FireShot failure. Match the fix to the symptom.

Is FireShot asking for the same permissions Firefox lists for a website?

No. Firefox’s site permissions and the extension’s own permissions are separate layers. Record which browser displayed the prompt and its exact wording.

Where should I report a technical issue?

FireShot’s Firefox add-on listing directs technical questions to its support forum. Include your browser and extension versions, operating system, page, capture mode, prompt or error, and comparison results.