13ft Ladder

Open-source paywall proxy, honestly reviewed. Not a SaaS replacement. A single-purpose Python script with 4,000 stars and a narrow, useful job.

TL;DR

• What it is: A self-hosted Python/Flask server that impersonates GoogleBot to fetch the full content of paywalled articles — a more private, self-controlled version of the now-defunct 12ft.io [README][3].
• Who it’s for: Developers and technically comfortable founders who occasionally hit a paywall on an article they need to read, and don’t want to pay $20/mo for a journalism subscription they’ll use once.
• Cost: $0 for the software (MIT license). $5–10/mo for the VPS you run it on. No SaaS equivalent still operating at scale [README][3].
• Key strength: Actually works on sites that 12ft.io struggled with, because you control the server and can update it when things break [README].
• Key weakness: A single-trick tool with no active development apparent from the commit history, operating in an increasingly hostile legal and technical environment. Publishers have been hardening their paywalls specifically against this class of tool [3].

---

What is 13ft Ladder

The name is a joke: 12ft.io was a popular public paywall-bypass service named after the expression “show me a 12-foot ladder and I’ll get over any 10-foot paywall.” 13ft Ladder is one foot higher — it’s the self-hosted version, built as a direct replacement after 12ft.io became unreliable and eventually went offline [README][3].

The mechanism is simple and the README doesn’t hide it: the server pretends to be Googlebot, Google’s web crawler. When you paste a paywalled URL into the interface, 13ft makes the HTTP request using a Googlebot user-agent string. Publishers let Googlebot through their paywalls so their content gets indexed by search engines — so the full article comes back, and 13ft serves it to you.

That’s the entire product. There’s no dashboard, no subscription management, no team features. It’s a Python Flask app with a text input and a submit button. The GitHub repository has 4,111 stars, 218 forks, and 71 commits — numbers that suggest it found a real audience without growing into a platform [merged profile].

What makes it worth considering over just using archive.today or a browser extension is that you run it yourself. Your IP, your logs, your instance. If the tool breaks because publishers updated their anti-bot logic, you can update your own copy. You’re not waiting for a public service to fix itself [README].

---

Why people choose it

The third-party coverage on 13ft Ladder the software is thin — most search results for “13ft” lead somewhere unrelated. What exists paints a consistent picture.

The 12ft.io gap. In 2025, 12ft.io stopped working reliably and was eventually taken offline after major publishers pursued legal pressure around copyright circumvention [3]. The service had been widely used by researchers, students, and occasional readers who needed to access one article without committing to a subscription. When it went dark, users started looking for alternatives — and self-hosted tools like 13ft Ladder moved from niche to practical fallback [3].

The self-hosted advantage. CYCHacks [3] categorizes 13ft among tools for “technically inclined users” who want “maximum control, privacy, and flexibility.” That framing is accurate. A public paywall-bypass service is a target — publishers can block its IP range, DMCA it, or pressure its hosting provider. A private instance on your own VPS running under your own domain is much harder to shut down centrally. The trade-off is that you have to run it.

The simplicity. The README is honest about the use case: “I do want you to support the creators you benefit from, but if you just wanna see one single article and move on with your day then this might be helpful” [README]. This is not a tool for wholesale content harvesting. It’s for the moment you hit a paywall on a specific article you actually need.

Publisher countermeasures are winning. CYCHacks [3] is direct about the trajectory: paywalls have started blocking Googlebot and crawler user-agents specifically. Some sites verify login tokens. Others use browser fingerprinting and dynamic content loading that a server-side fetch can’t replicate. 13ft works well for older-style paywalls (Medium, early NYT implementation) and less well for sophisticated modern ones [3]. The README itself mentions NYT and Medium specifically — these are the original use cases. Publications that have invested more in their paywall infrastructure will defeat this approach.

---

Features

This is a short section because there aren’t many:

Core:

• Web interface: paste URL, get full article without paywall [README]
• Googlebot user-agent spoofing — the single mechanism behind everything [README]
• Ad blocking as a side effect (the page served back strips a lot of the surrounding page cruft) [README]
• Works with websites that 12ft.io didn’t, according to the project description [README]

Deployment options:

• Docker Compose (simplest path — three commands from zero to running) [README]
• Standard Python script via pip install
• venv setup with configurable host/port via Flask environment variables [README]
• Available on DockerHub as wasimaster/13ft and ghcr.io [README]

Browser integration:

• Bookmarklet support: a one-line JavaScript snippet that redirects the current page URL through your 13ft instance [README]
• Works in Chrome; instructions are documented in the README with step-by-step setup [README]

Self-hosting extras:

• systemd service configuration provided in the README for persistent deployment [README]
• Apache reverse proxy config example included [README]
• Configurable bind address and port [README]

What it doesn’t have:

• No user authentication (anyone who can reach the URL can use it — important for public-facing deployments)
• No rate limiting in the default config
• No history, bookmarks, or saved articles
• No API
• No mobile app

The simplicity is the point. This is not a platform. It’s a proxy with a text box.

---

Pricing: SaaS vs self-hosted math

There is no SaaS version of 13ft Ladder. 12ft.io, the closest equivalent, is defunct [3]. RemovePaywalls.com and similar services exist as free public tools, but they’re not the same architecture and carry the same reliability risks as 12ft.io [3].

13ft self-hosted:

• Software: $0 (MIT license)
• VPS: $4–8/mo on Hetzner or Contabo (a 1 vCPU, 2GB RAM box is more than enough for a Python Flask app used by one person)
• Domain (optional): $10–15/year if you want a clean URL instead of a raw IP
• Time: 15–30 minutes to deploy if you know Docker

The comparison isn’t really SaaS pricing. The tool replaces the occasional $20–$30 single-article subscription or the $5/mo “archive access” charge some publications push. If you’re hitting paywalls several times a week across different publications, having a working instance saves you from the friction of making that decision each time. Concrete savings depend entirely on how often you actually hit paywalls.

The honest caveat: if you’re hitting the New York Times or Washington Post paywall multiple times per week because you genuinely read those publications, this is the wrong tool. Buy the subscription and support the journalism. If you hit a random paywall twice a month on an article someone linked you, the math is clear.

---

Deployment reality check

Docker Compose deployment is genuinely three commands [README]:

git clone https://github.com/wasi-master/13ft.git
cd 13ft
docker compose up

That’s it. The app runs on port 5000 by default. Add a Caddy or nginx reverse proxy for HTTPS, and you have a working private instance.

What can go wrong:

• Publisher countermeasures: this is the biggest real-world issue. Sites that check for Googlebot verification (Google actually pings back to confirm a crawler is legitimate) will reject the spoofed user-agent. The README mentions this works for sites “that 12ft.io doesn’t work with,” but it also inherits the fundamental limitation of the approach — if the publisher blocks the technique, there’s nothing to configure your way around [3].

• No authentication by default: the default config has no login. If you point a domain at this and don’t restrict access, it’s an open proxy. Either run it on a private network, add HTTP basic auth at the reverse proxy level, or bind it to localhost and access via SSH tunnel.

• Dependency on Googlebot behavior: the entire tool depends on publishers continuing to grant Googlebot full content access. As more publishers implement hard paywalls that don’t exempt any crawler, the tool’s effective coverage will narrow [3].

• Maintenance: the commit history suggests this is not actively developed. 71 commits over the project lifetime is sparse. If a major publishing platform changes their anti-bot logic, a fix depends on whether the maintainer is still engaged.

• Legal gray area: CYCHacks [3] dedicates several paragraphs to the legal question. The tool circumvents technological access controls, which potentially implicates copyright law in several jurisdictions. The tool’s README acknowledges this indirectly by encouraging readers to support creators. Running a private instance for personal use is lower risk than running a public service — 12ft.io’s takedown came after it became a high-visibility public proxy, not because the underlying technique was new [3].

Realistic setup time for a developer: 10–20 minutes. For someone following a guide who knows Docker but hasn’t done Flask deployments: 30–60 minutes including the reverse proxy.

---

Pros and cons

Pros

• Zero cost. MIT license, runs on any VPS with Docker. No subscription, no per-article pricing, no account [README].
• Private. Your instance, your logs. A public paywall-bypass service logs every URL you request. Your own instance doesn’t share data with anyone [README].
• Simple deployment. Three Docker commands to a working instance is about as low-friction as self-hosted tools get [README].
• Survives public service shutdowns. When 12ft.io went offline, self-hosted users kept running [3]. You’re not dependent on a third-party service staying alive.
• Bookmarklet integration. One-click redirect from any page through your instance is a genuinely useful workflow [README].
• Honest about its purpose. The README doesn’t pretend this is something it isn’t. Small codebase (71 commits), single purpose, no enterprise edition upsell [README].

Cons

• Shrinking effectiveness. Modern hard paywalls defeat the Googlebot impersonation approach. Publishers have been upgrading their systems specifically in response to tools like this [3].
• No authentication. Default config is an open proxy. Requires manual security hardening before any public-facing deployment [README].
• Sparse maintenance. The commit history doesn’t suggest active development. Issues that emerge when publishers update their systems may go unfixed [merged profile].
• Legal risk is real. Operating a self-hosted paywall bypass tool is not clearly legal in all jurisdictions. The technique that got 12ft.io taken down is the same one this tool uses [3].
• No mobile experience. The web interface works in a mobile browser technically, but it was clearly designed for desktop. No app, no sharing extension [README].
• Single mechanism, single point of failure. The entire tool depends on Googlebot exceptions. When that exception disappears for a given publisher, that publisher’s content stops being accessible. There’s no fallback strategy built in [README][3].
• Minimal documentation. The README covers setup but not troubleshooting, not which sites work well, not what to do when it fails on a specific site [README].

---

Who should use this / who shouldn’t

Use 13ft Ladder if:

• You’re a developer or technically comfortable founder who occasionally hits paywalls and finds it annoying, but not annoying enough to subscribe to six publications.
• You care about the privacy angle — you don’t want a third-party service logging every article URL you read.
• You’re comfortable with Docker and basic reverse proxy setup, or you’re willing to learn.
• You understand the legal gray area and accept it for personal use.

Skip it if:

• You want something that works on all paywalled sites reliably. The coverage has real gaps, particularly on publications that have hardened their paywalls since 2023 [3].
• You’re not comfortable with Docker or Linux server administration. The setup is simple but it’s not a web app you sign up for — it’s infrastructure you run.
• You’re looking for a team tool. No authentication means you either secure it yourself or it’s a private-use-only tool.
• You’re in a jurisdiction with strict anti-circumvention laws and want no legal exposure at all.
• You actually read the publications you’re bypassing regularly. Just subscribe.

Use a browser extension (Bypass Paywalls Clean) instead if:

• You want zero server maintenance and client-side installation is acceptable.
• You don’t need the privacy guarantee of your own infrastructure.

Use Archive.today instead if:

• You need archived versions of articles and don’t mind a public service.
• The articles you’re accessing have already been archived by someone else.

---

Alternatives worth considering

• Bypass Paywalls Clean — browser extension, community-maintained, client-side, no server required. Works by disabling paywall scripts and spoofing crawlers at the browser level. More flexible than 13ft for some sites, less private [3].

• Archive.today / archive.is — public archival service. Stores snapshots of pages, often without paywalls. Useful for previously archived content. Doesn’t help for new articles not yet archived [3].

• RemovePaywalls.com — public tool that fetches articles from archival sources. No setup required, works in browser. Third-party service with same reliability risks as 12ft.io had [3].

• smry.ai — open-source tool that fetches articles and optionally generates AI summaries. Useful if you need the gist rather than the full text [3].

• Wallabag — self-hosted read-it-later service that can sometimes capture full article content at save time. Not a paywall bypass specifically, but useful for articles you can access intermittently.

• Ladder (other projects) — several other self-hosted paywall proxies exist on GitHub under names like “ladder” and “readability-server.” Same general approach as 13ft, similar limitations [3].

The realistic question for most people isn’t “13ft vs. something else” — it’s “self-hosted vs. a browser extension.” If you want your own infrastructure and care about privacy, 13ft is the simplest entry point. If you want zero maintenance, Bypass Paywalls Clean is the practical alternative.

---

Bottom line

13ft Ladder is a 71-commit Python script that does one narrow thing: helps you read an article you hit a paywall on, without paying for a subscription you don’t need. It’s MIT-licensed, takes 15 minutes to deploy with Docker, and runs on a $5 VPS. The tradeoff is that it operates in a legal gray area, depends on publishers continuing to exempt Googlebot from their paywalls, and has no meaningful development activity to keep pace with publisher countermeasures. It’s not a platform, not a team tool, not a content pipeline. It’s a personal utility for the specific frustration of hitting a paywall on an article you actually need to read. If that’s your problem, this solves it — for now, on the sites that haven’t hardened their paywalls past the point this technique can reach.

---

Sources

1. CYCHacks — “Best 12ft Ladder Alternatives (2026): Best Tools to Bypass Paywalls Safely & Legally”. https://www.cychacks.com/best-12ft-ladder-alternatives/

Primary sources:

• GitHub repository and README: https://github.com/wasi-master/13ft (4,111 stars, MIT license)
• DockerHub image: https://hub.docker.com/r/wasimaster/13ft
• GitHub Container Registry: https://github.com/wasi-master/13ft/pkgs/container/13ft