Wallabag versus Pocket and Instapaper for self-hosted reading

Mozilla shut down Pocket in July 2025, leaving millions of users without their primary tool for saving articles. While Instapaper remains the closest spiritual successor, it operates as a closed cloud service that charges $2.99 per month for premium features like full-text search and Kindle integration. For those seeking data sovereignty, Wallabag presents a self-hosted alternative that runs on your own infrastructure. This choice defines your relationship with your reading list: do you want a polished, managed experience from a third party, or do you want total control over your data at the cost of significant technical maintenance? The decision hinges on your willingness to manage a server stack against the convenience of a subscription.

The operational reality of self-hosting

Wallabag is a PHP application that requires a database backend, typically PostgreSQL, MySQL, or SQLite. Installing it via Docker Compose involves configuring environment variables such as SYMFONY__ENV__DOMAIN_NAME and SYMFONY__ENV__DATABASE_DRIVER. Users who attempt complex setups, like deploying on Kubernetes with external PostgreSQL clusters, often encounter errors where the installer tries to drop a non-existent SQLite file because the database_path parameter defaults to a local path even when using an external database. One user reported spending eight to ten hours over several days troubleshooting these configuration issues before realizing the instance was not reachable under a subpath. The default login credentials are wallabag / wallabag, which must be changed immediately for security. You also need to generate a Symfony secret using openssl rand -hex 32 to secure the session.

The mobile experience for Wallabag is less consistent than its web interface. While official apps exist for Android and iOS, some users describe the Android app as basic and outdated. Fetching errors can occur if the article parser fails to extract content from certain websites, a problem that does not affect all sources equally. If you choose the hosted option at wallabag.it, you avoid these setup headaches but still pay a subscription fee. The self-hosted route offers free access forever, but you become responsible for backups, updates, and fixing broken extraction rules. It is clearly a trade-off between financial cost and technical labor.

Feature parity and migration paths

Instapaper focuses on clean article parsing and offers fourteen different font choices, along with tilt scrolling for navigation. Its premium plan includes audio playback and unlimited highlights. Wallabag provides similar core functionality, including tagging, archiving, and full-text search. It supports exporting saved articles to EPUB, MOBI, PDF, CSV, or JSON formats, which is useful for sending batches to e-readers. Both services allow you to save articles via browser extensions for Firefox and Chrome, or by emailing links to a dedicated address.

Migration from Pocket is supported in Wallabag through an import menu that handles large volumes asynchronously using Redis. However, one user noted that migrating from Pocket to Wallabag was initially impossible due to missing CSV import features, forcing them to consider other cloud services like Raindrop.io. Instapaper also serves as a migration target, though it lacks the open-source flexibility of Wallabag. If your primary goal is to read long-form articles without ads, both tools strip formatting effectively. Wallabag adds automated tagging rules, such as assigning tags based on domain name or reading time, which saves manual effort. The question remains whether the freedom of self-hosting outweighs the friction of maintaining a server that Instapaper hides behind a simple login screen.