How to Take a Screenshot of a Webpage Without Ads

To take a screenshot of a webpage without ads, first open a clean reading view if your browser offers one, then capture that view. Cleaning and capturing are separate steps: a screenshot command by itself does not necessarily remove ads. For an article-like page, try Firefox Reader View or simplified printing; for an automated screenshot, Chrome Headless can capture an image, but you must handle ad removal separately and inspect the result.

Choose the right output

Decide what you need before capturing:

Image of the visible screen: captures only what is currently in the viewport.
Full-page image: includes content below the fold, where the browser supports it.
Clean PDF: useful for reading or printing, but it is not an image screenshot.
Specific page element: useful when you need just an article, chart, or card.

Reader modes can remove surrounding material such as advertisements, navigation, and related content, but they may not be available on every page. They can also change the page’s original layout. If preserving the exact original appearance matters, review the saved capture: the browser guidance cited here does not establish a universal one-click way to remove ads while keeping every other visual detail unchanged.

Firefox: clean the page, then capture it

Use Reader View for an article-like page

Open the page in Firefox.
If the Reader View icon appears in the address bar, select it.
Review the simplified page and adjust its reading appearance if needed.
Capture the visible view or use Firefox’s screenshot tools for the full page or a particular element.
Open the saved image and check that the ads and any content you need are handled as expected.

Reader View is available only on pages Firefox can simplify. If its icon is absent, try simplified print formatting instead.

Use Simplified print formatting

Open the browser’s Print dialog.
Under More settings → Format settings, choose Simplified if the option is available.
Check the preview. Mozilla says this format strips clutter such as ads.
If you need a PDF, save the print output as a PDF. If you need an image, activate a clean reading view and use a screenshot tool; the print output itself is not an image screenshot.

Mozilla cautions that Simplified may not appear when a page cannot be simplified or when Reader View is already active. See Mozilla’s simplified printing instructions.

Capture a full page or element in Firefox

Firefox’s screenshot interface offers Save full page for the whole page and Save visible for the current viewport. Firefox Developer Tools can also capture a full page or an individual element. These capture choices determine the area saved; they are not documented as ad-removal features. Apply the clean view first when removing clutter is essential.

See Firefox’s screenshot instructions and the Firefox Developer Tools screenshot documentation.

Microsoft Edge: use Immersive Reader for clean print output

On a supported page, open Immersive Reader by selecting its address-bar icon. On Windows, Microsoft also documents F9 as a shortcut. Then open Print and inspect the preview for a clutter-free result. Microsoft describes this as a printing workaround and notes that “Immersive Reader may not be available for all websites.”

This documented workflow produces print output, such as a PDF. The Microsoft guidance cited here does not establish a full-page screenshot procedure in Edge, so do not assume that Immersive Reader’s print steps save an image. See Microsoft’s Edge printing instructions.

Chrome Headless: capture an image or PDF

Chrome Headless provides a repeatable command-line way to capture page output. Its screenshot option captures a rendered page; the documented flags do not claim to remove ads. To exclude advertisements, use an appropriate clean rendering or a separately configured page-cleaning approach, then inspect the capture.

Save a screenshot

chrome --headless --screenshot=page.png --window-size=1440,1200 --timeout=5000 https://example.com/article

--screenshot writes an image, --window-size sets the viewport dimensions, and --timeout sets the capture timing. Replace the URL with the page you want. A viewport-sized screenshot is not necessarily a full-page image; consult the current Chrome Headless command-line reference for the supported options in your installed version.

Save a PDF instead

chrome --headless --print-to-pdf=page.pdf --no-pdf-header-footer https://example.com/article

--print-to-pdf produces a PDF, not a screenshot image. --no-pdf-header-footer omits browser-added PDF headers and footers. The PDF command does not promise ad removal; check its output or use a supported simplified rendering first.

Optional extension route

PrintFriendly’s Chrome Web Store and Firefox Add-ons listings describe ad or clutter removal, PDF conversion, and full-page screenshot features. These are vendor and store listing claims, not independent compatibility tests. Treat an extension as an optional convenience, check that it supports your browser and page, and inspect its output. See the Chrome listing and Firefox listing.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Make one GET request to capture a page; its cleanup steps accept cookie or consent banners like a visitor and remove 60+ known consent platforms, newsletter popups, and chat widgets before the shot. Each cleanup step can be turned off. This is useful for removing those common interruptions, though it is not a general promise that every advertisement on every site will be removed.

For a PNG, JPEG, WebP, or PDF and the available capture options, see the ScreenshotNeo documentation.

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

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com/article"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://example.com/article'
});
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);

Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed; response headers report the page verdict and billing status. The MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for 1,000 free screenshots a month, with no card required.

Options for a more controlled capture

For code-driven workflows, distinguish the options that change what is rendered from those that change what is saved. A capture tool may let you choose full-page versus viewport output, a CSS element, viewport or device dimensions, and image format. A page-cleaning mode changes the rendered content. Do not treat one category as a substitute for the other.

Full page versus viewport: use full-page capture for content below the fold; use viewport capture when you need the visible composition.
Element capture: target the article or component when surrounding page content should be excluded. Confirm that the chosen element contains all required text and images.
Wait conditions: wait for a meaningful selector or page readiness when content loads asynchronously. A fixed delay can help with simple pages but may be too short or waste time on fast pages.
Image versus PDF: use an image for sharing or image processing; use PDF for print-like pagination and text documents.
Ad handling: use a reader/simplified view or a documented cleanup feature, and inspect the result. Hiding ad containers with custom rules can alter layout or miss ads served through unfamiliar markup.

ScreenshotNeo supports full-page capture with lazy images loaded, CSS selector element capture, device presets and custom viewports, custom CSS and JavaScript, click-before-capture, hide selectors, wait-for-selector/delay/network-idle, blocking ads/trackers/requests/resource types, headers, cookies, user agent, authorization, timezone and geolocation, transparent backgrounds, image resizing, caching with a chosen TTL, signed links, async jobs with signed webhooks, bulk capture of up to 100 URLs per call, usage API, and an OpenAPI spec. Its API accepts parameter names used by other screenshot APIs to make switching easier. Consult the documentation for exact parameter names and supported values.

Troubleshooting

Symptom	Likely cause	What to do
Reader View or Immersive Reader is missing	The browser cannot simplify that page, or the site does not support the mode.	Try Firefox Simplified printing if available, use a different page-cleaning method, or capture and manually review the result.
The screenshot still contains ads	The capture command saved the page as rendered; capture alone does not establish ad removal.	Activate a supported clean view before capturing, or use documented cleanup controls. Inspect the image at full size.
The result is only a viewport	The selected command or control captures the visible area.	Choose a full-page option where available, or use a tool that supports full-page capture. Check that lazy-loaded content appears.
Some article content disappeared	Reader mode or simplified formatting omitted content it did not identify as part of the article.	Compare with the original page. Use a different capture route or include the missing content through a supported element or page capture.
Chrome Headless output is blank or incomplete	The page may need more time, interaction, or a different viewport; dynamic content may not have rendered when capture ran.	Adjust `--timeout` and `--window-size`, then inspect the saved output. For interactive pages, use a browser automation workflow that can wait for the required state.
A PDF is produced when an image was needed	Print output and screenshot output are different deliverables.	Use Firefox’s screenshot controls or Chrome’s `--screenshot` option for an image.
ScreenshotNeo returns a bot check, blank page, timeout, or failed load	The target did not yield a clean, usable page capture.	Check the target URL and page availability. Read the response’s `X-Page-Verdict` and `X-Billed` headers to understand the outcome; these failure cases are not billed.

Performance, reliability, and cost

Local browser capture avoids per-shot API pricing, but it depends on the browser, machine resources, network, and page behavior. Large full-page pages take longer and produce larger image files. Dynamic pages can change between runs; use a stable wait condition and a consistent viewport when repeatability matters. Reader modes are convenient for supported article pages but are not universal.

For automated or repeated work, account for page-load variability, timeouts, and failures. Capture only the area you need, choose a suitable output size, and avoid waiting an arbitrary long time when a more specific ready condition is available. With ScreenshotNeo, only clean shots are billed; bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. Plans are Free: 1,000 per month; Starter: $5 for 3,000; Growth: $15 for 15,000; Pro: $39 for 60,000; Scale: $99 for 250,000; Business: $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan.

FAQ

Can a screenshot tool remove ads by itself?

Not necessarily. A capture tool records rendered content unless it provides and applies a cleanup feature. Reader or simplified modes are separate from capture.

Will a clean reader view preserve the original design?

Usually the goal is a simpler reading presentation, so it may change layout and styling. Compare the output with the source page if visual fidelity matters.

Should I save an image or a PDF?

Choose an image when you need a screenshot asset. Choose PDF for printing or document-like reading. A PDF can be clean without being a screenshot image.

Is Firefox Simplified available on every page?

No. Mozilla says the option may not appear if the page cannot be simplified or Reader View is already active.