How to Capture a Full-Page Screenshot with Nimbus Screenshot in Chrome

To capture an entire webpage with Nimbus Screenshot in Chrome, open the page, open Nimbus Screenshot, and choose Entire page. When the capture finishes, Nimbus opens it in its editor; make any edits, then click Done to reach the save or sharing options. Nimbus also supports starting a capture from its toolbar button, the page context menu, or a configured hotkey. Nimbus Screenshot help guide.

Capture the entire page

1. Open the webpage you want to capture in Chrome and wait for its visible content to load.
2. Start Nimbus Screenshot from its extension control. Depending on your setup, Nimbus documents the extension button, context menu, and configured hotkeys as capture entry points.
3. Choose Entire page. This mode is for the webpage as a whole, including content beyond the current viewport.
4. Wait for the capture to complete. Nimbus says the result opens in its editor.
5. Optionally crop or annotate the image, then click Done and choose a save or sharing option.

If you prefer to bypass editing, Nimbus describes an action-after-capture setting that can be configured before starting the capture. The exact menu layout may vary; consult Nimbus’s current help if the labels differ. The procedural details here follow Nimbus vendor documentation and tutorial material, not independent verification of the current Chrome interface. Nimbus’s full-page screenshot tutorial.

Choose the right scrolling mode

Mode	Use it for
Entire page	The full webpage, extending beyond the visible browser area.
Capture scroll fragment	An internally scrolling region within a page, such as a chat window, service panel, or task window.

Use Entire page when the target is the site page itself. Use Capture scroll fragment when you want the contents of a scrollable panel embedded in that page. Nimbus says the fragment option appears when it detects an internal scrollable object. Nimbus guide to Capture scroll fragment.

Permissions and saving

Nimbus’s Chrome permissions help says website data access is needed to take page screenshots, and download access is used to save images to a computer. This is Nimbus’s explanation of its permissions; it is not an independent security assessment. If you are reviewing an extension’s access, read the permission prompt and the vendor’s explanation before installing or using it. Nimbus’s permissions explanation.

Common problems and fixes

• The capture only contains the visible screen: Confirm that you selected Entire page, rather than a visible-area capture mode.
• You need the contents of a panel, but got the full site: Try Capture scroll fragment for the internally scrolling region. Nimbus says this option depends on detecting a scrollable object.
• The editor appears when you wanted a direct save: Nimbus documents an action-after-capture setting. Configure it before the next capture if you want to skip the editor.
• You cannot save the result locally: Check whether Chrome or the extension has the download access Nimbus says is used for saving images.
• A control name or location differs from these steps: The research material does not establish the current extension version or present-day menu layout. Check the current Nimbus help guide rather than assuming an older tutorial matches your interface.

Or skip the browser setup

If you need repeatable captures from code, ScreenshotNeo is a website screenshot API: one GET request takes a URL and returns an image or PDF. Its capture flow accepts cookie and consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before the shot; each cleanup 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. ScreenshotNeo also offers an MCP server with screenshot tools for Claude, Cursor, and other MCP clients. Details and options are in the ScreenshotNeo API documentation.

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

Free includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for ScreenshotNeo and get 1,000 free screenshots a month, with no card required.

FAQ

Does Entire page capture an internally scrolling chat panel?

It is intended for the webpage as a whole. For a scrollable object inside the page, use Capture scroll fragment if Nimbus detects it.

Can I edit the screenshot before saving?

Yes. Nimbus says the capture opens in its editor; after edits, click Done to continue to save or sharing options.

Can I start a capture without opening the extension menu?

Nimbus documents the toolbar button, context menu, and configured hotkeys as additional ways to start a capture.