Awesome Screenshot Chrome Extension Not Working: How to Fix It

If the Awesome Screenshot Chrome extension is not working, first identify what fails: the icon is missing, the extension is disabled, the popup opens but capture fails, only Full Page or Selected Area is unavailable, or recording fails. Then check whether the problem happens on every site or only one. A capture mode that fails on a Chrome settings page or another restricted page may be blocked by Chrome rather than broken.

Work through these steps in order: restart Chrome and update it and the extension; test a normal website; check the extension’s enabled state and site access; toggle or reinstall the extension; then test in a clean Chrome profile for conflicts.

1. Identify the failure

Before changing settings, note the exact symptom and where it occurs. This helps distinguish an extension problem from a page restriction or a recording permission issue.

Icon missing: Look in Chrome’s Extensions menu. The extension may be installed but not pinned.
Extension disabled or marked unsupported: Inspect its status in Manage extensions. A work or school administrator may also control whether it can run.
Popup opens, but no screenshot is produced: Try a regular public website and check the extension’s site access.
Only Full Page or Selected Area is unavailable: Check whether the current page is a Chrome internal page, the Chrome Web Store, browser settings, or another extension.
Screenshot is wrong on one site: Record the page URL and the capture mode. If the mode is available but the result is incorrect, send the URL to the vendor through extension Feedback or its website.
Recording fails but screenshots work: Check whether setup granted the requested camera and microphone permissions. These permissions are relevant to recording, not a universal fix for screenshots.

2. Restart Chrome and install updates

Save any open work, close Chrome, and reopen it. If the problem continues, restart the computer and try again.
Open Chrome’s About page from the browser menu and let Chrome check for and install available updates. Restart Chrome if prompted.
Open Chrome’s Extensions page and check that Awesome Screenshot is current. Update it if an update is available, then restart the browser.
Test the same operation on an ordinary website, such as a page you can access without signing in.

A browser or extension update can fix a stale or incomplete installation. If the failure is limited to one page or one capture mode, continue to the page restriction checks before reinstalling.

3. Check whether Chrome restricts the page

Chrome restricts extensions from running scripts on some browser-controlled pages, including URLs beginning with chrome://, browser settings, the Chrome Web Store, and other extensions. Awesome Screenshot identifies these as cases where Full Page or Selected Area may not be available. That behavior does not by itself mean the extension installation is damaged.

Try the capture on a normal website. For a restricted page, the vendor suggests using Visible Part or Entire Screen & App Window and cropping afterward. Its desktop app is another software workaround for selected-area capture. If a mode is available but captures a particular website incorrectly, provide that site’s URL to the vendor.

4. Confirm the extension is enabled and allowed on the site

Open Chrome’s Extensions menu, then choose Manage extensions. You can also open the extensions management page from Chrome’s menu.
Find Awesome Screenshot and confirm its enabled switch is on.
If it fails only on certain websites, inspect the extension’s site access setting. Chrome lets extensions be allowed on the current site, selected sites, or all sites. Choose the access level appropriate for the sites where you use it.
If Chrome marks the extension unsupported or offers a repair action for a corrupted extension, follow the browser’s available prompt. Restart Chrome and retry.
If this is a work or school device and the setting is controlled or the extension is blocked, contact your administrator. Organization policy can restrict extensions.

If the icon alone is missing, open the puzzle-piece Extensions menu and pin Awesome Screenshot so it appears in the toolbar. Pinning changes visibility; it does not grant access to a site that the extension is not allowed to use.

5. Toggle the extension, then reinstall if needed

In Manage extensions, switch Awesome Screenshot off, wait a moment, then switch it back on.
Restart Chrome and try again.
If it still fails, remove the extension and install the latest version from its official Chrome Web Store listing. Complete any setup prompts, then restart Chrome.
For recording problems, follow the setup prompts for camera and microphone access if the feature requires them. Do not assume those permissions will fix screenshot capture failures.

Reinstalling can repair a damaged extension installation, but it will not make a Chrome-restricted page available to extension scripts or override an administrator’s policy.

6. Test for a conflict with another extension or profile setting

Create a new Chrome profile, install only Awesome Screenshot, and try the same page and capture mode. This is the vendor’s suggested way to investigate extension conflicts.

It works in the clean profile: Another extension or a profile-specific setting may be interfering. In your regular profile, disable other extensions and re-enable them one at a time, testing after each change.
It still fails in the clean profile: The cause may be the page, browser, extension state, or a managed-device restriction. Keep the exact page, error, and capture mode recorded for support.

Do not change multiple extensions at once while isolating a conflict; testing one change at a time makes the result easier to interpret.

7. Give support evidence they can use

If the steps above do not resolve the issue, send Awesome Screenshot support a concise report. Include:

The Chrome version and operating system.
The affected page URL, if the failure is site-specific.
The exact symptom and capture mode, including whether screenshots, Full Page, Selected Area, or recording fails.
The error message and when it appears.
Whether the extension is enabled, whether the device is managed, and whether the problem reproduces in a clean profile.
A screenshot or shareable recording of the failure, if possible. Keep the cursor visible and show when the error occurs.

The vendor also lists its desktop app, website recorder, and extension for another browser as software workarounds. Choose based on whether the issue is Chrome-specific, whether you need browser-only or desktop capture, and whether installing software on your device is allowed. The cited guidance does not establish feature parity or pricing for these alternatives.

Or skip the browser setup

If you need a screenshot of a website rather than a fix for this particular extension, ScreenshotNeo provides a screenshot API and MCP server. A single GET request returns an image or PDF. See the ScreenshotNeo API documentation for options and configuration.

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 and change the target URL. ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.

Performance, reliability, and cost considerations

For the browser extension, first test a normal page and a clean profile so you do not spend time reinstalling when Chrome is blocking the requested mode. Keep a record of whether the failure is repeatable and which page triggers it; that evidence narrows the diagnosis. The support guidance does not promise that any one troubleshooting step resolves every failure.

For API captures, ScreenshotNeo bills clean shots only: bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. Review the response’s X-Page-Verdict and X-Billed headers when diagnosing a request. Choose a plan based on expected monthly volume: Free has 1,000 shots, Starter is $5 for 3,000, Growth is $15 for 15,000, Pro is $39 for 60,000, Scale is $99 for 250,000, and Business is $249 for 1,000,000. Yearly billing gives two months free. Every feature is on every plan.

Frequently asked questions

Why is the extension icon missing after installation?

It may be hidden in Chrome’s Extensions menu. Open that menu and pin Awesome Screenshot. If it is absent from Manage extensions too, check whether installation was blocked or removed.

Why is Full Page disabled only on one tab?

The tab may be a Chrome-controlled page or another restricted page. Test on a regular website; use a visible or full-screen capture with cropping where the extension cannot run its page scripts.

Should I grant camera and microphone access to fix screenshots?

Those permissions are relevant to recording and setup prompts. They are not a general remedy for still screenshot failures.

What if a clean profile does not help?

Record the URL, error, Chrome version, and capture mode, then send the evidence to the vendor. A clean profile helps rule out many profile-specific conflicts but does not identify every possible cause.