How do paywalls work?

Understanding how a paywall is built explains why some articles open in a click and others never will. There are three common designs, from flimsiest to strongest.

Soft paywalls: a curtain over the text

The full article is already in the page HTML; a JavaScript overlay just covers it and disables scrolling. Because the text is present, a reader extractor — or even disabling JavaScript — reveals it easily. Many regional papers use this.

Metered paywalls: counting your reads

You get a set number of free articles, tracked by a cookie or browser-storage counter (sometimes server-side by account). Early free reads are fully delivered, so extraction and archives work well — until the meter trips and the page stops sending the body.

Hard paywalls: nothing without a login

The server checks your subscription before sending any article text, so the body is never in the page for non-subscribers. The WSJ, The Times and The Washington Post work this way, often with bot protection on top. No extractor can recover text the server never sent — only a pre-existing public archive can.

Why bot protection matters

Big publishers add Cloudflare-style checks and reverse-DNS verification to block the old "pretend to be Googlebot" trick that tools like 12ft.io relied on. That is why single-trick bypasses stopped working and archive-backed reading became the reliable approach.

Live success rates

Unlike other tools, RemovePaywall publishes how often it works for each outlet, measured from real use. See the live list.