How do metered paywalls count article reads?

Metered paywalls typically set a cookie in your browser when you read each article. When you visit an article page, JavaScript checks for this cookie and compares the count against the monthly limit. If the limit is exceeded, the paywall overlay is shown.

Why do paywalls sometimes disappear when I scroll?

Some paywalls are implemented as sticky position CSS elements or modal dialogs. These can be dismissed or bypassed by scrolling if the page content loads underneath them. Some browser extensions exploit this by removing the overlay element from the page DOM.

What is browser fingerprinting in paywall context?

Browser fingerprinting creates a unique identifier based on your browser settings, fonts, screen resolution, timezone, and other characteristics. Some advanced paywalls use fingerprinting to track readers even when cookies are cleared, making private browsing mode less effective.

Why can Google's crawler read paywalled articles but I can't?

Publishers want their content indexed in search engines for traffic. They configure their servers to show full content to known search engine crawlers (identified by their user-agent strings) while showing the paywall to regular visitors. This is sometimes called the "first click free" model.

Home / Guide / How Paywalls Work

How Paywalls Work — A Technical Explanation

Understanding how paywalls are implemented technically helps explain why some bypass methods work on certain publications and not others. This guide walks through the main technical approaches publishers use to restrict content.

Client-Side Paywalls (Soft Paywalls)

Client-side paywalls send the full article content to your browser and then use JavaScript to restrict access. The article text exists in your browser's memory and in the page HTML — it is simply hidden by a CSS or JavaScript overlay.

This approach is simpler and cheaper for publishers to implement and works well for metered systems. However, it is inherently bypassable because the content is already delivered to the browser. Methods that work against client-side paywalls include:

Browser reader mode (extracts content from the DOM before overlay renders)
Disabling JavaScript (removes the overlay entirely)
Browser developer tools (manually deleting the overlay element)
Certain browser extensions that remove overlay elements

Server-Side Paywalls (Hard Paywalls)

Server-side paywalls check your subscription status before the article content is sent to your browser at all. If you are not a subscriber, the server sends only the article summary or the first few paragraphs, not the full text. No amount of JavaScript manipulation on the client can reveal content that was never sent.

The Wall Street Journal and the Financial Times use primarily server-side restrictions for their most valuable content. Web archives are effective against these because archives captured the content when it was publicly sent to crawlers.

Cookie-Based Metering

The most common paywall implementation for major newspapers is cookie-based metering. When you read an article, JavaScript writes a cookie recording that visit. On subsequent article visits, JavaScript reads the cookie to check your article count against the monthly limit.

Why this is bypassable: cookies are stored per-browser-session. A private browsing window starts with no cookies, making you appear as a new reader with a fresh article count.

Login-Based Paywalls

Some publications require you to log in to read any content, even free content. The subscription check happens server-side against your account. Bypassing these requires either a subscribed account or accessing archived content from when the article was publicly crawlable.

Browser Fingerprinting

Advanced paywall systems collect a "fingerprint" — a combination of your browser version, installed fonts, screen resolution, timezone, and dozens of other characteristics — to identify your browser even if cookies are cleared. This makes private mode less effective since your fingerprint does not change between regular and private sessions unless you use a fingerprint-blocking tool.

How Web Archives Bypass All of These

Web archives work by preserving a copy of the article as it appeared when first crawled publicly. Crawlers are typically granted access as search engine bots (because publishers want their content indexed). The archived copy contains the full article and is stored permanently, unaffected by any paywall the publisher later implements or tightens.

Access Articles Through Web Archives

Frequently Asked Questions

How do metered paywalls count article reads?: Metered paywalls typically set a cookie in your browser when you read each article. When you visit an article page, JavaScript checks for this cookie and compares the count against the monthly limit. If the limit is exceeded, the paywall overlay is shown.
Why do paywalls sometimes disappear when I scroll?: Some paywalls are implemented as sticky position CSS elements or modal dialogs. These can be dismissed or bypassed by scrolling if the page content loads underneath them. Some browser extensions exploit this by removing the overlay element from the page DOM.
What is browser fingerprinting in paywall context?: Browser fingerprinting creates a unique identifier based on your browser settings, fonts, screen resolution, timezone, and other characteristics. Some advanced paywalls use fingerprinting to track readers even when cookies are cleared, making private browsing mode less effective.
Why can Google's crawler read paywalled articles but I can't?: Publishers want their content indexed in search engines for traffic. They configure their servers to show full content to known search engine crawlers (identified by their user-agent strings) while showing the paywall to regular visitors. This is sometimes called the "first click free" model.