How to capture a full-page screenshot with Awesome Screenshot in Chrome
Capture an entire webpage in Chrome with Awesome Screenshot, use its shortcut, and troubleshoot restricted pages or incomplete captures.
To capture a full-page screenshot with Awesome Screenshot in Chrome, open the webpage, click the Awesome Screenshot extension icon, choose Capture, then choose Full Page. The documented default shortcut is Alt+Shift+F. You can annotate the result if useful, then save or finish using the options available in your extension version.
Capture a full webpage in Chrome
- Open the webpage you want to capture in Chrome and wait for the content you need to appear.
- Click the Awesome Screenshot icon in Chrome’s toolbar.
- Select Capture.
- Select Full Page. The extension scrolls through the page to capture beyond the currently visible viewport.
- Annotate the screenshot if needed, then save or finish using the choices shown in your version of the extension.
If the extension icon is missing, click Chrome’s puzzle-piece Extensions menu. Find Awesome Screenshot and pin it to the toolbar for easier access.
Use the full-page shortcut
Awesome Screenshot documents Alt+Shift+F as the shortcut for Capture > Full Page. To change it, open the extension’s Options and choose Set shortcuts, or visit chrome://extensions/shortcuts in Chrome and edit the extension shortcut there. Shortcuts can conflict with other extensions or system shortcuts, so choose a combination that is available in your setup.
Install Awesome Screenshot
- Open the Awesome Screenshot listing in the Chrome Web Store.
- Click Add to Chrome, then confirm with Add extension.
- Open the webpage you want to capture and follow the steps above.
Chrome may place the extension under its puzzle-piece menu after installation. Pin it if you want its icon to remain visible on the toolbar.
When Full Page is unavailable
Chrome restricts extension access to some pages. Awesome Screenshot says Full Page and Selected Area may be unavailable on Chrome internal pages such as chrome:// pages, the Chrome Web Store, settings pages, and other extensions’ pages. This is a browser security restriction, so changing the shortcut or repeating the same capture usually will not make those pages accessible.
For a restricted page, try Visible Part to capture what is on screen, or Entire Screen & App Window and crop the result afterward. The vendor also points to its Windows and Mac desktop apps for certain cases.
Alternatives for a full-page image or document
If you do not need Awesome Screenshot’s annotation or sharing workflow, the vendor documents two other options:
- Chrome DevTools: open DevTools, use the command menu, and select Capture full size screenshot. This is an option for producing a full-page image; the exact DevTools interface may vary by Chrome version.
- Print to PDF: use Chrome’s print dialog and choose Save as PDF when a document is more useful than an image. Check the print preview, since page breaks and print styles can change the layout.
Troubleshooting
| Problem | Likely cause | What to try |
|---|---|---|
| The extension icon is not visible | Chrome has placed it in the Extensions menu. | Open the puzzle-piece menu and pin Awesome Screenshot. |
| Full Page is missing or unavailable | The target is a browser-restricted page, such as a Chrome settings page or the Web Store. | Use Visible Part or capture the screen or app window, then crop. Consider a desktop app for applicable cases. |
| The shortcut does nothing | The shortcut may have been changed, may conflict with another shortcut, or Chrome may not have focus on an ordinary webpage. | Check chrome://extensions/shortcuts, assign an available shortcut, and try the extension menu workflow. |
| A full-page capture fails or is incomplete on a normal webpage | The page or extension may have encountered a capture-specific issue. | Confirm Full Page is available, then contact Awesome Screenshot support with the page URL. The vendor may ask for page-console and extension service-worker console information. |
Do not send console information unless support requests it. A restricted page and a capture failure on a normal site are different cases; the former is imposed by browser access rules.
Or skip the browser setup
ScreenshotNeo captures a webpage through one API request and returns an image or PDF. Its browser-based capture accepts cookie banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before the shot; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server provides screenshot tools for Claude, Cursor, and other MCP clients.
Example with cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
The same request in 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)
And in 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}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));
See the ScreenshotNeo API documentation for request options. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for 1,000 free screenshots a month, with no card.
FAQ
Does Full Page capture content below the fold?
Yes. Choose Full Page to capture the entire webpage rather than only the visible viewport.
Can I use a different shortcut?
Yes. Change the extension shortcut in its Options or on Chrome’s extensions shortcuts page.
Why can I not capture a Chrome settings page?
Chrome limits extension access to internal and other restricted pages. Use a visible-screen capture or another documented fallback.
What should I send support if a normal page capture fails?
Start with the page URL. Awesome Screenshot may request console details to investigate the failure.


