FireShot Not Working in Firefox? How to Troubleshoot It

If FireShot is not working in Firefox, first identify what is failing: the toolbar icon may be hidden, the extension may be disabled, a capture may be blank or incomplete, or the image may fail to save. Check the extension’s enabled state and toolbar pin, review its permissions, then use Firefox Troubleshoot Mode to check for conflicts. If you only need a screenshot right now, Firefox has a built-in screenshot option.

These symptoms have different fixes. Work through the section that matches what you see; you do not need to reinstall FireShot as the first step.

1. FireShot’s icon is missing

Open Firefox’s Extensions button and look for FireShot. Extensions that are not pinned may be listed in the extensions panel rather than directly on the toolbar.
If FireShot appears there, open its menu and choose Pin to Toolbar.
If it does not appear, open the Add-ons Manager, find FireShot, and check whether it is enabled. Enable it if necessary.
If FireShot is enabled but still missing, restart Firefox and check the Add-ons Manager again.

Firefox’s toolbar controls can change between releases. Mozilla’s guide to the Extensions button explains how to find and pin extensions.

2. The icon is there, but capture fails or looks wrong

Check permissions for the site

FireShot’s Mozilla Add-ons listing requests access to website data and downloads; it also lists access to the clipboard and tabs among its optional permissions. Open FireShot’s Permissions and data section in the Add-ons Manager and review its access. If the extension cannot access a page, it may not be able to capture it. Mozilla explains how to manage extension permissions.

Test for a conflict with another add-on

Start Firefox in Troubleshoot Mode, which temporarily disables extensions and some other customizations.
Try the same page and capture action. If the problem goes away in Troubleshoot Mode, an extension or customization may be involved.
Return to normal mode. Disable other extensions one at a time, then test FireShot again to isolate a conflict. Also check whether changing the theme affects the issue.

Troubleshoot Mode is a diagnostic step. It does not establish that FireShot itself is the cause, and a successful test there does not identify which other extension or customization is responsible.

Update the add-on and restart Firefox

In the Add-ons Manager, open the gear menu and choose Check for Updates. Install any available update, then restart Firefox and retry the same capture. Mozilla recommends keeping automatic add-on updates enabled. If the problem began after a Firefox update, note the browser version when reporting it.

3. The screenshot is blank, incomplete, or fails on one site

First compare the same capture on a second ordinary web page. If FireShot works there, the issue may be specific to the original site or its page behavior. If it fails on several sites, check permissions, updates, and extension conflicts using the steps above.

FireShot’s version history records improvements for cases such as long captures, sticky or fixed elements, iframes, infinite-scroll pages, and scripts that block capture. Those release notes do not guarantee that every current Firefox version or dynamic site will work. For a long or lazy-loaded page, wait until its content has loaded and test again; compare a full-page capture with a visible-area capture if the extension offers both.

Do not treat a blank or partial capture as proof of a general FireShot outage. Record the site, the capture type, and whether the problem repeats in Troubleshoot Mode. These details help distinguish a page-specific issue from a local configuration problem.

4. Capture works, but the file is not saved

Check whether Firefox is prompting for a download location or showing a blocked-download notice.
Open Firefox’s downloads list to see whether the file completed, failed, or is still in progress.
Review FireShot’s download permission in the Add-ons Manager.
Try saving to a different writable folder and check that the destination has enough free space.
If the capture can be copied but not downloaded, review clipboard permission as well.

These checks help separate a capture problem from a browser download or filesystem problem. The FireShot listing includes downloads among its required permissions.

5. Check FireShot’s Firefox compatibility carefully

The Mozilla Add-ons listing identifies FireShot version 1.12.18 as the current listed version and says it supports Firefox 77.0 and later. The version history dates that release to June 5, 2023. That compatibility statement is not a guarantee for every later Firefox release, website, or capture type.

The listing’s release notes mention batch mode, all-tabs capture, and PDF metadata in that release. Earlier notes describe fixes and improvements involving very long captures, fixed elements, iframes, infinite scrolling, and capture-blocking scripts. Treat these as release-note details, not proof that a particular issue is fixed in your setup.

Mozilla Add-ons user ratings and FireShot support-forum posts are not a diagnosis of your particular problem. Forum topics show that users have reported different issues, but do not establish how common a failure is or prove a universal cause.

6. Use Firefox’s built-in screenshot option as a temporary workaround

If you need an image immediately and FireShot remains unavailable, Firefox’s built-in screenshot feature may be enough. Mozilla Support describes opening the page context menu and choosing Take Screenshot, or using Ctrl+Shift+S on Windows and Linux. Toolbar customization may also let you add the screenshot control. Current labels and availability can vary by Firefox version or settings; see the Mozilla Support discussion about the screenshot control.

A browser’s built-in option is a useful fallback for a quick capture. If you need the extension’s particular capture or export behavior, continue with FireShot troubleshooting or report the issue to its developer.

7. Report a persistent FireShot issue

FireShot’s Mozilla Add-ons listing directs users with technical issues to its official support forum. Include:

Firefox version and operating system
FireShot version
The affected website, if you can share it
Whether the icon is missing, capture fails, the image is incomplete, or saving fails
The capture type and exact error message, if any
Steps to reproduce the issue and whether it occurs in Troubleshoot Mode

A clear report helps the developer distinguish a browser-version issue, a site-specific failure, a permissions problem, and a download issue. Avoid including private page content or credentials in a public report.

Or skip the browser setup

For a screenshot from code, ScreenshotNeo is a website screenshot API and MCP server. Its API returns an image or PDF from one GET request. Cookie and consent banners, newsletter popups, and chat widgets are removed before capture; each cleanup step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits cost nothing, with the page verdict and billing status returned in headers. AI agents can use its MCP tools, including take_screenshot, get_page_info, and capture_pdf. See the ScreenshotNeo API documentation for request options.

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

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)

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(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

Replace YOUR_API_KEY with your key. In Node.js environments without Bun.write, use your runtime’s file-writing API to save the response body. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000, and every feature is available on every plan. Sign up for free and get 1,000 screenshots a month with no card.

Performance, reliability, and cost notes

For FireShot: troubleshooting is fastest when you repeat the same page and capture type after each change. That makes it easier to see whether pinning, permissions, an update, or a conflict test changed the result.
For dynamic pages: wait for the content you need to appear before capturing. Infinite scrolling and lazy-loaded images can make a capture differ from the currently visible viewport.
For reliability: keep Firefox and extensions updated, and retain the browser version and reproduction steps when reporting a recurring issue. Compatibility statements and old release notes are not guarantees for every current site.
For ScreenshotNeo: clean screenshots are billed; bot checks, blank pages, timeouts, failed loads, and cache hits are not. The response includes X-Page-Verdict and X-Billed headers. Plans range from 1,000 free monthly shots to paid tiers, and yearly billing gives two months free.

FAQ

Does reinstalling FireShot usually fix a missing icon?

Check the Extensions panel and Add-ons Manager first. The icon may simply be unpinned or the add-on may be disabled.

Does “Firefox 77 and later” mean FireShot is guaranteed to work today?

No. It is the compatibility statement on the listed add-on build, not a guarantee for every newer browser release or website.

Is Firefox’s screenshot feature the same as FireShot?

It is a built-in fallback for taking screenshots. It may not provide the specific capture or export workflow you use FireShot for.

Can ScreenshotNeo capture a page without a Firefox extension?

Yes. It accepts a URL through its screenshot API, and it also provides an MCP server for AI agents. The API and its options are documented at screenshotneo.com/docs.