Read-it-later apps solve a specific problem: you find an article you cannot read right now, you want to keep it, and you want to read it later without ads, pop-ups or a dead link. Wallabag is an open-source answer to that problem. This review looks at what the project says it does, what you need to run it, and who is likely to enjoy it.
This is a review of the project's public documentation and repository, not a hands-on benchmark. Where something is not stated in the sources, this article says so instead of guessing.
What wallabag is
According to its repository, wallabag is a web application for saving web pages to read later. The project says it extracts content from the page so you are not distracted by pop-ups. Its tagline also mentions saving and classifying articles.
Key facts from the project page:
- License: MIT, a permissive open-source license.
- Built with: the repository lists PHP and Symfony as its main technologies.
- Content extraction: it relies on Graby, php-readability and ftr-site-config to pull the readable part out of a page.
- Community: the repository shows 13.0k stars and 898 forks at the time the page was read, which is a rough signal of a large user base and not a measure of quality.
- Translation: managed through Weblate, a hosted translation platform.
- Documentation: hosted at doc.wallabag.org.
Two ways to run it
Self-hosting. You install wallabag on your own server. The repository says the requirements are listed in the documentation and that installation uses make install. Self-hosting means you control the data, you decide when to upgrade, and you are also the person who has to keep it patched and backed up.
Hosted at wallabag.it. The repository says you can create an account at wallabag.it instead of running your own server. This is the lower-effort route, and a sensible way to try the app before deciding whether to host it yourself.
Apps and extensions
The repository points to:
- an Android app and an iOS app, each in its own repository;
- a browser extension listed as wallabagger;
- a third-party GNOME app for Linux called read-it-later, which the page says is not maintained by the wallabag project.
The documentation's navigation also lists Android and iOS applications. The pages we read did not give details about how each app behaves, so test the one you plan to use before relying on it.
Moving in from other services
One of the most practical parts of any read-it-later tool is how easily you can bring your saved articles with you. The wallabag documentation's import section lists seven sources:
- Instapaper
- Readability
- Pinboard
- elCurator
- wallabag v2
- wallabag v1
If you are leaving Pocket or Instapaper, that list is the strongest argument for trying it. The documentation pages we read did not state which export formats wallabag offers for leaving, so confirm that before you commit a large library. A good rule is to export a small batch, re-import it somewhere else, and see what survives.
What we could not confirm
To keep this review honest, here are things the sources we read did not describe:
- the exact tagging workflow (the documentation lists a Tags page but the content we read had no details);
- how annotations work (a page exists under Articles, but no details were available to us);
- export formats;
- the server requirements in full.
If any of these decide the purchase for you, read the relevant page at doc.wallabag.org directly. Treat this article as a guide to what to check, not a replacement for the documentation.
Strengths
- Open and permissive. An MIT license and a public repository mean you can inspect the code and self-host it.
- Self-hosting or hosted. You can run it yourself or sign up at wallabag.it.
- Focused on reading. The project's aim is a distraction-free reading copy of the page, rather than trying to be a general knowledge base.
- Import list. Seven documented sources cover several of the services people most often leave.
- Apps and extension. Android and iOS apps and a browser extension are linked from the project.
Limitations
- You run the server. Self-hosting is a real commitment: updates, backups and security are your job.
- Plain reading focus. If you want AI tagging, semantic search or built-in page screenshots, other tools in this category emphasize those features. Wallabag's repository page does not list them.
- Documentation depth. Some behavior, such as annotations and export, needs the full docs to understand.
- Extraction is imperfect on any tool. Reader-mode extraction depends on how a site is built, and sites with unusual layouts can come out messy in any read-it-later app. Check a few of your usual sources.
Who should use it
Wallabag is a good fit if you:
- read a lot of long articles and want a clean reading queue;
- like open-source software and want the option to self-host;
- are migrating from Pocket, Instapaper or Pinboard and want a documented import path;
- do not need heavy automation around your saved links.
It is a weaker fit if you want one tool for bookmarks, notes, images and AI-assisted sorting, or if you do not want to maintain a server and would rather use a polished commercial app.
A sensible trial plan
- Create a test account on wallabag.it, or install it on a spare machine.
- Install the browser extension and save ten articles from sites you read often.
- Open them on your phone using the app for your platform.
- Import a small export from your current tool and check that titles and tags arrive intact.
- Decide after a week. If you still open the app daily, plan a proper self-hosted install with backups.
Verdict
Wallabag is an open-source read-it-later option with a clear import story and the choice of running it yourself or using the hosted service. Its main costs are the time to self-host and the need to verify details like export and annotations in the documentation. For readers who value control and a clean reading list, it is worth an afternoon of testing.
Sources
- wallabag repository: https://github.com/wallabag/wallabag
- wallabag documentation: https://doc.wallabag.org/
