How to Capture Website Screenshots with Browser Extensions Disabled

You can capture a website without browser extensions by using a browser’s built-in screenshot tool, Developer Tools, or your operating system’s screen capture. For a full-page image, Firefox documents built-in full-page capture. Chrome DevTools documents an area capture workflow. If you only need what is currently visible, an operating-system screenshot is a practical fallback.

Pick the method based on what you need: a visible viewport, selected region, page element, or full page. A screenshot saves pixels; it is not the same as printing a page to PDF.

Choose a capture method

Need	Try	What to know
Full page, visible portion, region, or automatically selected page element	Firefox’s built-in Take Screenshot tool	Save the image or copy it to the clipboard. Mozilla’s instructions cover these capture types.
Selected area in Chrome	Chrome DevTools Command Menu	The documented area workflow requires DevTools to be docked.
Full page or one DOM element in Firefox	Firefox Developer Tools or Web Console	Enable the full-page button in Developer Tools settings, or use the :screenshot command.
Visible screen when browser tools are unavailable	Your operating system’s screenshot feature	This captures the visible screen; it does not automatically include content below the fold.
Repeatable captures, automation, or a file without local browser setup	A screenshot API	ScreenshotNeo is the first service to try: it removes common consent banners and only bills clean screenshots.

Capture a screenshot in Firefox

Use Firefox’s built-in screenshot interface

1. Open the page you want to capture.
2. Right-click an empty part of the page and choose Take Screenshot. You can also press Ctrl+Shift+S on Windows or Linux, or Command+Shift+S on Mac.
3. Choose a capture: drag a region, click a page element highlighted under the pointer, save the visible portion, or save the full page.
4. Choose Download to save an image or Copy to place it on the clipboard. Press Esc to cancel.

The selection interface also supports keyboard movement and resizing. Mozilla notes that moving the crosshair does not work on Wayland. See the Firefox screenshot guide for the current keyboard controls and save behavior.

Use Firefox Developer Tools for full-page or element captures

1. Open Developer Tools.
2. To show the full-page capture button, open Developer Tools settings and enable Take a screenshot of the entire page under Available Toolbox Buttons.
3. Click the screenshot button to save a full-page capture to Downloads.
4. To capture one element, open the Inspector, right-click its node in the HTML pane, and choose Screenshot Node.

Firefox’s Web Console also provides a :screenshot command for more control. Examples:

:screenshot --fullpage
:screenshot --selector "main article"
:screenshot --delay 2 --filename "menu-state.png"
:screenshot --dpr 2 --filename "retina.png"
:screenshot --clipboard
:screenshot --file --filename "page.png"

The command options include --fullpage, --selector, --delay, --dpr, --clipboard, --file, and --filename. The selector should identify one element. The delay is in seconds and can be fractional. A device-pixel ratio above 1 creates a higher-density image; below 1 creates a lower-density image. Use --file to force a file when combining options such as clipboard capture. Reusing a filename overwrites the previous image. See Firefox’s screenshot command documentation for option details.

Capture a selected area in Chrome

1. Open the page and open DevTools.
2. Keep DevTools docked to the browser window; Chrome documents that area capture does not work when DevTools is undocked.
3. Press Ctrl+Shift+P on Windows or Linux, or Command+Shift+P on Mac, to open the Command Menu.
4. Type screenshot and select Capture area screenshot.
5. Drag over the area of the page to capture. DevTools downloads the screenshot.

These steps capture a selected area. Do not assume this specific workflow creates a full-page image; use a browser method whose current documentation confirms the capture type you need. See Chrome’s Command Menu documentation.

When browser screenshot tools are blocked

First check whether the problem is limited to extensions. A browser can disable extensions while keeping its built-in screenshot UI or Developer Tools available. In a managed Edge installation, however, an administrator can enable the DisableScreenshots policy, which blocks screenshot keyboard shortcuts and extension APIs. Microsoft says Web Capture or methods outside the browser, such as an operating-system feature or another application, may still be available. The policy behavior depends on the managed setup, so check with your administrator if the remaining routes are unavailable. See Microsoft’s Edge policy documentation.

1. Try the browser’s own screenshot interface or Developer Tools, if your organization allows them.
2. If you need only the visible screen, use the operating system’s screenshot feature. The exact shortcut depends on the operating system and is not the same as a full-page browser capture.
3. If you need a webpage image rather than a screen image, use an authorized screenshot service or ask your administrator which method is permitted.
4. If you need a document layout, browser printing or PDF export may help, but the result is a document and may differ from a pixel-faithful screenshot.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request returns an image or PDF. Cookie banners, newsletter popups, and chat widgets are removed before capture; bot checks, blank pages, and failed loads are never billed. AI agents can take screenshots through its MCP server. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. See the ScreenshotNeo website and API documentation.

cURL

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

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)

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}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

Replace YOUR_API_KEY with your key. The Node.js example uses top-level await and writes the response body to a file. Check the response headers and API documentation when handling page verdicts or billing programmatically.

Sign up free for 1,000 screenshots a month, with no card required.

Quality, performance, and reliability

• Wait for the page state you need. A screenshot can capture a loading placeholder, animation frame, or consent dialog if the page has not reached the intended state. For manual capture, wait for visible content to settle; for automation, use a documented wait condition or delay.
• Plan for lazy-loaded content. A full-page capture may not show images or sections that load only after scrolling. Scroll through the page before capture when needed, then verify the result.
• Keep the capture scope small. A selected region or element is easier to inspect and generally produces a smaller image than a very long full-page capture.
• Check pixel density. Higher device-pixel ratios produce more detail and larger files. Choose a scale appropriate for the intended display or document.
• Preserve the intended state. Responsive layout, authentication, geolocation, time zone, cookies, and personalization can change what appears. If the browser session matters, capture within that session; a remote API may see a different session unless configured accordingly.
• Keep a fallback. If one built-in route is blocked by policy or does not offer the needed capture scope, use another approved route. An operating-system screenshot is useful for visible content but does not replace full-page capture.

Troubleshooting

Symptom	Likely cause	What to try
Screenshot shortcut does nothing	The shortcut may be intercepted, unavailable, or blocked by a managed-browser policy.	Open the browser menu or Developer Tools directly. In Edge, ask whether DisableScreenshots is enabled; Microsoft documents that it blocks screenshot shortcuts and extension APIs.
Chrome says area capture is unavailable or does not start	DevTools may be undocked.	Dock DevTools to the browser window and run Capture area screenshot from the Command Menu.
Firefox does not show a full-page screenshot button	The optional Developer Tools button may not be enabled.	Open Developer Tools settings and enable Take a screenshot of the entire page under Available Toolbox Buttons, or use the built-in Take Screenshot interface.
Capture contains a banner, popup, or chat panel	The page displayed those elements when captured.	Dismiss them manually if permitted, or use a capture workflow that handles these elements. ScreenshotNeo removes common consent banners, newsletter popups, and chat widgets before capture.
Part of the page or images are missing	The capture was limited to the visible viewport, or content loads lazily or after interaction.	Choose full-page capture when available; scroll to trigger lazy content, wait for it to load, and capture again.
Firefox saved over an earlier screenshot	The same filename was reused.	Choose a unique --filename for each capture. Firefox warns that capturing again to the same filename overwrites the earlier file.
The result looks blurry or is unexpectedly large	Pixel density or capture dimensions differ from what you need.	Adjust the viewport or Firefox --dpr option; use a smaller capture area when full detail is unnecessary.
Capture shows the wrong page state	The page was still loading, or a menu, animation, or personalized state changed.	Wait for the intended state, use a deliberate delay where supported, and capture again. For repeatable captures, control the page state and viewport.

Frequently asked questions

Can I take a screenshot without installing anything?

Yes. Use browser features already included in Firefox or Chrome, or your operating system’s screenshot function for visible-screen capture.

Will an operating-system screenshot capture the whole webpage?

Usually it captures the screen area currently visible. Use a browser’s full-page feature when you need below-the-fold content.

Does a screenshot include interactive content?

It records the page’s rendered appearance at the moment of capture. Menus, hover states, videos, and personalized content may require you to set up the desired state first.

Can I use these methods in a managed browser?

Availability depends on organization policy. Edge’s screenshot policy can block shortcuts and extension APIs; ask your administrator which capture methods are allowed.