Awesome Screenshot Stuck on Capturing Page: Fixes for Chrome
If Awesome Screenshot stays on “capturing page,” check for a page prompt first, then work through Chrome and extension troubleshooting in a safe order.
If Awesome Screenshot remains on “capturing page,” the message alone does not identify the cause. First check whether the page is waiting for an action, such as dismissing a cookie dialog or signing in. Then restart and update Chrome and the extension, re-enable the extension, and test in a clean Chrome profile if needed. These are diagnostic checks, not guaranteed fixes.
For the intended full-page workflow, click the Awesome Screenshot extension icon, choose Capture, then Full Page. The extension describes this as a full-page or scrolling screenshot. If that capture remains stuck, use the sequence below to separate a page-specific problem from a browser or extension problem.
1. Check whether the page is waiting for you
Before changing Chrome settings, look at the page being captured. A dialog or incomplete page action can keep the capture flow from continuing. Check for:
- A cookie or consent dialog, sign-in prompt, or modal covering the page.
- A loading indicator or a page that has not finished loading.
- A prompt that requires a choice, such as clicking Cancel or dismissing a dialog.
Complete or dismiss the prompt if appropriate, wait for the page to settle, and try Capture → Full Page again. If the page itself is blank or still loading, troubleshoot that page before treating the extension as the cause.
2. Restart Chrome and retry
- Close Chrome completely, then open it again.
- Return to the same page and retry the full-page capture.
- If the issue persists, restart the computer and try once more.
Awesome Screenshot’s general troubleshooting guidance recommends restarting the browser and computer for capture or recording functions that stop working. A restart can clear a temporary browser or extension state, but it does not establish the cause by itself.
3. Update Chrome and Awesome Screenshot
Check that Chrome and the extension are current, install available updates, then restart Chrome and retry. The installed extension version may differ from the current store listing; check the version in your own browser rather than assuming a particular version is installed. At the time of the research for this article, the Chrome Web Store listed Awesome Screen Recorder & Screenshot version 4.4.44, updated September 11, 2026.
Use the Awesome Screenshot Help Center for vendor troubleshooting guidance and the Chrome Web Store listing to check the extension listing.
4. Turn the extension off and back on
- Open Chrome’s Extensions menu and select Manage extensions.
- Turn Awesome Screenshot off.
- Turn it back on, return to the page, and retry the capture.
This re-enable check is a low-effort way to see whether the extension’s current state is involved. If Chrome shows that the extension is disabled by an administrator or policy, contact the person or team managing the browser rather than trying to bypass that restriction.
5. Test for a conflict in a clean Chrome profile
Another extension may interfere with capture. Create or open a separate Chrome profile, install or enable only Awesome Screenshot there, and try the same page. This follows the vendor’s clean-profile diagnostic guidance. If the capture works in the clean profile, a practical next step is to re-enable your other extensions one at a time and retry, so you can identify whether one of them changes the result.
If it still hangs in the clean profile, the cause may be specific to the page, Chrome, or the extension itself. A clean-profile result narrows the investigation; it does not prove which component is at fault.
6. Reinstall only if the earlier checks fail
If restarting, updating, re-enabling, and the clean-profile check do not help, remove Awesome Screenshot and install it again from the Chrome Web Store. Restart Chrome afterward and retry. Reinstallation is a later step because it takes more effort and may require setting up the extension again.
7. Decide whether the problem is page-specific
Try a second ordinary page using the same full-page workflow. Use the results to choose the next step:
| What happens | What it suggests | Next step |
|---|---|---|
| Only one page gets stuck | The issue may depend on that page’s prompt, loading state, or content. | Check for page actions and retry after it finishes loading. Record the affected page and where capture stops. |
| Several pages get stuck, but a clean profile works | An extension conflict or profile-specific state is more likely. | Re-enable other extensions methodically in the affected profile. |
| Several pages get stuck in a clean profile too | The problem is less likely to be caused only by another extension in the original profile. | Confirm updates, reinstall if not already tried, then report the issue with useful context. |
| The page itself is blank or incomplete | The capture may be reflecting a page load problem. | Resolve the page’s loading or sign-in requirement and retry. |
These interpretations are a troubleshooting aid, not confirmed diagnoses. The vendor’s general troubleshooting article identifies network issues, outdated software, a page action, and extension conflicts as possible areas to check; it does not identify one universal cause for the “capturing page” symptom.
8. Report a persistent failure with useful evidence
If the issue remains, contact Awesome Screenshot support and include enough detail to reproduce the problem:
- The Chrome and extension versions shown on your system.
- Whether the issue happens on one page or several, and the page URL if you can share it.
- The capture workflow you used and where it stopped.
- When it happened, including the time and time zone if practical.
- A screenshot of the stuck state or a shareable recording of the failure.
The Help Center’s troubleshooting index also lists focused guides for extension service-worker information, the captured page’s console, and an MHTML file. Collect diagnostic material if support requests it; most readers do not need to inspect browser logs as a first step. Start from the Awesome Screenshot Help Center.
Workarounds if you need the capture now
Awesome Screenshot’s troubleshooting guidance names its Windows or Mac desktop app, its website recorder, and its Edge add-on as possible alternatives when the extension remains unusable. Choose based on what you need: a full-page capture, a visible-region capture, or a way to continue in another browser. The available source material does not establish that these alternatives preserve every Chrome extension feature or resolve the underlying issue.
If you only need a quick manual record of what is visible, Chrome’s normal screenshot capability can capture the current view, but it is not the same as the extension’s documented full-page workflow. For automated website screenshots, an API can avoid relying on a Chrome extension running in your current profile.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request takes a URL and returns an image or PDF. This example saves a screenshot of Stripe as WebP; 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.webpimport 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}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and the response includes page-verdict and billing headers. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.
Create a free ScreenshotNeo account for 1,000 screenshots a month with no card.
Performance, reliability, and cost considerations
For a one-off capture, resolving the page prompt and restarting or updating Chrome are the simplest checks. A clean-profile test takes longer but gives useful evidence about extension conflicts. Reinstall only after those checks. If a deadline is close, the named desktop, web, or Edge alternatives may let you continue, though they may not behave exactly like the Chrome extension.
For repeated or automated captures, an API changes the workflow: your code sends a URL instead of depending on a human-operated browser extension. With ScreenshotNeo, only clean shots are billed; failed loads and other listed non-clean outcomes are not billed. Check the response’s X-Page-Verdict and X-Billed headers when deciding how to handle retries or record usage. The supplied product details list a 90-second timeout in the example above; production code should handle request errors and inspect the response before treating the body as an image.
Common errors and what to try
| Symptom | Likely area to check | Action |
|---|---|---|
| Capture waits while a prompt is open | The page may require an action before capture can continue. | Complete or dismiss the prompt, wait for the page, and retry. |
| Capture fails across pages in the original profile | Chrome state, an outdated extension, or an extension conflict. | Restart, update, re-enable the extension, then compare with a clean profile. |
| Capture works in a clean profile | Something in the original profile may conflict. | Re-enable other extensions one at a time and retry to isolate the change. |
| Capture still fails after reinstall | The issue may be page-specific or persist beyond the extension installation. | Try another page, record the versions and timing, and contact support with a screenshot or recording. |
| Chrome says the extension is managed or blocked | Browser policy or administrator settings. | Ask the browser administrator about the policy. |
FAQ
Does “capturing page” tell me what is broken?
No. The vendor’s general guidance lists several possible areas to check and does not name one definitive cause for this exact message.
How do I take a scrolling screenshot with Awesome Screenshot?
Click the extension icon, choose Capture, then Full Page. If it hangs, work through the checks above.
Should I reinstall the extension immediately?
No. Try the quicker checks first: check for a page prompt, restart, update, re-enable, and test a clean profile. Reinstall if those do not resolve it.
Which extension version should I have?
Check the version installed in your own Chrome. The Chrome Web Store listing showed version 4.4.44, updated September 11, 2026, when this article’s research was checked; that listing can change.
What if I need to send support diagnostic files?
Start with a clear description and screenshot or recording. The Help Center lists targeted guides for service-worker details, page-console information, and MHTML; gather those materials when support requests them.
Sources
- Awesome Screenshot Help Center: general troubleshooting, full-page capture instructions, and troubleshooting index.
- Awesome Screen Recorder & Screenshot on the Chrome Web Store: product listing and version information.
