How to Print a Web Page Without Ads, Menus or Cookie Banners (2026)
You find an article worth keeping, press Ctrl+P, and the preview shows the website instead of the article: a header that eats the first page, a menu down the left edge, an ad parked in the middle of the second paragraph, and the text itself squeezed into a narrow column. PrintClean is a browser extension that turns the page you are reading into a clean sheet — the article only — and then prints it or saves it as PDF through the print dialog you already know.
This guide covers the usual workarounds and where they stop, how PrintClean decides what to keep, what batch mode does with pages behind a login, and the exact line between the free version and Pro. It also states the privacy model and the permissions plainly, because a tool that reads your pages should have nothing to hide about how it does it.
Why printing a web page prints the whole website
A web page is designed for a screen, an ad inventory and a navigation tree — not for a sheet of paper. When you print it, the browser lays out everything the page contains: the sticky header, the side menu, the cookie banner, the share bar, the related-articles rail, the newsletter box and the comment section. Some sites ship a print stylesheet, but it is usually the first thing cut when deadlines loom, so the printed result is three pages of furniture around one page of text.
The article itself fares worst. On screen it sits in a column sized for the layout; on paper that column stays narrow, often around sixty characters wide, while the margins fill with things you never wanted to read. What you wanted was a document. What you got was a photograph of a website, in ink.
The usual workarounds, and where they stop
Most people try the same four things, and each one stops a step short:
- Browser reader mode. It hides clutter for reading on screen, which is genuinely useful — but it is not built for paper. Type controls are limited, the print result depends on the browser, and it is not offered on every page.
- Copy-paste into Word. You get the text, but figures, tables and captions rarely survive the trip, and you end up re-typesetting the document by hand. For anything with a code block or a data table, this is where the afternoon goes.
- Screenshot to PDF. A screenshot is pixels, not text: you cannot select it, search it or reflow it, the file is large, and the line breaks are frozen at whatever width your window happened to be.
- Online print-friendly services. These work by sending the URL — and sometimes the page content — to someone else's server. For a public article that may be acceptable; for an internal document or a subscription page you are logged in to, it is a privacy decision disguised as a convenience.
None of these is wrong. They just are not the same thing as deciding what belongs on the sheet and rebuilding it as a document worth putting on paper.
Finding the article: a scoring pass, not a site list
PrintClean's first job is to find the part of the page that is actually the article. It runs a scoring pass over paragraphs and their containers: paragraph length, comma density — prose has commas, link lists and navigation do not — and a decay by ancestor level, so a distant wrapper earns less credit than the block that holds the text directly.
Semantics help but do not decide: article and main elements and common class names act as tie-breakers, not as a lookup table of known sites. That is why the extractor works on sites it has never seen, rather than only on a curated list.
A final tightening pass then walks downward, so a wrapper never wins over its own text. Without it, a big container that happens to hold the article — plus a sidebar — could outscore the article itself. With it, you get the body of the article, not the div that happens to contain it.
A whitelist clone, not a screenshot
Once the article is found, PrintClean rebuilds it as a whitelist clone in a detached document. This is the part that separates it from both reader modes and screenshot tools: the result is real text, real tables, real code blocks — selectable, searchable, reflowable — not a picture of them.
The whitelist decides what survives. Scripts, styles, forms, navigation, share bars, related rails, newsletter boxes and anything hidden with CSS are dropped. Tables, quotes, code blocks, figures and captions are kept. Hidden blocks are dropped deliberately: content a site hides with CSS is rarely something you wanted on paper.
Nothing is changed on the original page. The clone is built in a detached document, so the site you are reading is untouched — no injected styles, no removed nodes, no layout shift. And because the on-screen sheet and the printed sheet are the same document, what you preview is exactly what the printer produces.
Type and paper: the settings that matter
A clean extraction is only half the job; the sheet also has to read well. PrintClean lets you set the font size from 13 to 26 px, choose between three line heights, and set the measure — the width of the text column — in pixels. The point is to make the sheet read like a book page instead of a browser window, at whatever size your eyes and your printer prefer.
For the paper itself: A4 or Letter, three margin presets, an optional header and footer carrying the date and the source URL — so a printed article can still be cited months later — optional grayscale for a cheaper print, and images on or off when you want a text-only draft. Whether the article runs one page or ten, it starts at the top of the paper.
From there it is the system print dialog: print, or save as PDF. There is no proprietary export pipeline and no account in the way — the same dialog you use for everything else, fed a document that is finally worth printing.
Batch mode, including pages behind a login
Sometimes one article is not the unit of work. You want an archive of pieces to read away from the screen, or a set of pages you have to hand in. Batch mode takes up to three addresses — fifty with Pro — and produces one document with each article starting on a new page.
Two details make it more than a loop. First, each address is fetched from the reader page itself, with your session cookies, so pages behind a login you are already signed in to work; your credentials never go anywhere new. Second, a page that refuses the request, times out or turns out not to be HTML is marked in place instead of breaking the batch. You get the document with the failures labelled, not an error dialog and nothing to show for it.
These fetches are also the only network requests the free add-on ever makes — and they go to the sites you listed, nowhere else. More on that below.
Free and Pro, exactly
The free version is a complete tool, permanently: single-page clean print with every typography setting, A4 and Letter, all three margin presets, header and footer, grayscale, images on or off, and batch up to three addresses. Nothing is time-limited and nothing is disabled after a trial, because there is no trial.
Pro is for volume and for sites that need hand-tuning. It raises batch mode to fifty addresses and adds selectors: per-site rules — hide this, keep that — remembered per domain, with the most specific domain winning, plus global selectors that apply to every site. Rules can be exported and imported as one JSON file, so a set you tuned on one machine travels to another.
The licence is an optional one-off purchase. One key activates two browsers, validation is throttled to about every two hours and cached for offline use, and a failed check never locks you out. If you print one article at a time and the extractor behaves on your sites, you may never need it.
Privacy and permissions, plainly
Pages are read and typeset on your device. No article text is uploaded anywhere: no analytics, no telemetry, no advertising identifiers, no tracking pixels. The extracted article is held in the extension's session storage — memory only, cleared when the browser closes — and deleted the moment the reader has rendered it. This add-on never writes page text to disk.
Without a licence key, the add-on makes no network request at all, except the pages you explicitly ask it to fetch in batch mode; those go to the sites you listed and nowhere else. With Pro, the only request is the licence check: the key, a random installation identifier and basic browser metadata, sent to api.annmax1983.com. Nothing about the pages you print.
The permissions are equally short. storage holds settings, the licence cache and the temporary article payload. activeTab and scripting let the toolbar icon read the tab you clicked — and only that tab. Host access is used for exactly two things: injecting the extractor into the clicked tab, and fetching the addresses you paste in batch mode. No content script is registered, so nothing runs on a page until you ask for it.
Where to get it — and the small print
PrintClean is coming soon for Chrome, Microsoft Edge and Firefox, so there is no store link yet; the product page and the licence checkout are the places to follow. It requires Firefox 140 or later and is built on Manifest V3. Extraction, typography and printing all work offline — the only things that ever need the network are the batch fetches you request and, with Pro, the licence check.
Two honest caveats. Extraction is heuristic: most articles come out right on the first click, but complex layouts can need a nudge — that is what the per-site keep/hide selectors (Pro) are for. And PrintClean prints the article, not interactive app state: a dashboard, an editor or a canvas is not an article, and no extractor should pretend otherwise.
FAQ
Is PrintClean just the browser's reader mode?
No. Reader modes hide things for on-screen reading. PrintClean decides what to keep, rebuilds it as a whitelist clone in a detached document, and hands you a page you can print or save as PDF. The on-screen sheet and the printed sheet are the same document, and the original page is never modified.
Does PrintClean upload the pages I print?
No. Pages are read and typeset on your device. The extracted article is held in the extension's session storage — memory only, cleared when the browser closes — and deleted the moment the reader renders it. There is no analytics or telemetry, and without a licence key the add-on makes no network request at all, except the pages you explicitly fetch in batch mode.
Can it print pages behind a login?
Yes, in batch mode. Each address is fetched from the reader page itself with your session cookies, so pages you are logged in to work. A page that refuses, times out or is not HTML is marked in place instead of breaking the batch.
What does the free version include?
Free, permanently: single-page clean print with every typography setting, A4 and Letter, all three margin presets, header and footer with date and source URL, grayscale, images on or off, and batch up to three addresses. Nothing is time-limited and nothing is disabled after a trial.
What does Pro add?
Pro raises batch mode to fifty addresses and adds per-site selectors (hide this, keep that, remembered per domain, most specific domain wins), global selectors for every site, and rules bundles exported and imported as one JSON file. The licence is a one-off purchase; one key activates two browsers, validation is throttled to about every two hours, and a failed check never locks you out.
Does it work on every site?
Extraction is heuristic, so most articles work on the first click, but complex layouts may need per-site keep/hide selectors, which are a Pro feature. PrintClean prints the article, not interactive app state such as dashboards or editors. It requires Firefox 140 or later (Manifest V3), and extraction, typography and printing work offline.
More guides in the VKT blog; questions to [email protected].
