# The wallabag Android app is a client for a server you run yourself

> wallabag is a self-hosted read-it-later service, and this repository is its Android companion rather than a standalone reader, which means the app is only as useful as the instance behind it. The feature list is deliberately modest: font controls, themes, offline image caching and text to speech, with no advertising and no special permissions on modern Android.

**wallabag/android-app** — Android application to read your articles saved in your wallabag. You can also easily add new articles.

- Repository: https://github.com/wallabag/android-app
- Website: https://www.wallabag.org
- Stars: 591 · Forks: 279
- Language: Java
- License: GPL-3.0
- Published: 2026-10-22 · Updated: 2026-10-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/wallabag-android-app

## This is a client, and that shapes everything

The wallabag Android application allows you to put a link in your wallabag instance, letting you read your wallabag links offline.

That sentence is the whole product. The app does not have its own account system, its own storage of articles and its own sync. It talks to a wallabag instance that you host or that you sign up for at wallabag.it, and the article list you see belongs to that server.

The background is that wallabag is a self-hosted read-it-later app, and unlike other services it is free and open source. You can download it from wallabag.org and follow the instructions to install it on your own server, or you can sign up directly for wallabag.it if you would rather not run one.

The app therefore comes in two flavours of use, and the documentation is explicit about both. You can connect to your self-hosted wallabag instance, or you can connect to your wallabag.it account.

The second is worth pausing on, because it changes the privacy story without changing the architecture. Even when you sign up for the hosted instance, the app is still a client talking to a server, and the difference between the two is who runs that server.

There is also a detail in the licensing history that says something about the project's shape. The application was originally created by Jonathan GAULUPEAU and released under the GNU GPLv3, while wallabag itself is a creation from Nicolas Loeuillet released under the MIT License, the Expat License.

So this repository is a separate work with its own licence and its own history, attached to a server project with a different one. That distinction is not unusual in this world, where a client and a server evolve separately, but it does mean the app and the service have to be matched by version rather than assumed compatible.

The project is Java, GPL-3.0 licensed, with the last push on 2026-10-12 and releases 2.6.0 from 2026-06-01, 2.5.3 from 2024-05-24 and 2.5.2 from 2024-05-01. The homepage is wallabag.org and the app is on the Google Play Store and F-Droid.

## The feature list is short, and each item is about reading

The features the app provides are listed as seven bullets, and reading them tells you what the project considers its job.

You can connect to your self-hosted wallabag instance or connect to your wallabag.it account. The app supports wallabag 2.0 and higher, which is the compatibility statement. It is completely ad-free. You can increase and decrease the size of the font and switch between a serif or sans-serif font for a more comfortable reading experience. You can switch between numerous themes. There is the possibility to cache images locally for offline reading. Articles can be read via a text-to-speech feature. And it needs no special permissions on Android 6.0 and later.

Three of those deserve a bit more attention.

The font controls, including the serif and sans-serif switch, are unusual for an app of this kind and they say something about the audience. wallabag is a tool for reading long articles, often on a phone, and the difference between a serif and a sans-serif face over a long text is a real difference in comfort. That is a small feature that most read-it-later clients do not offer at all.

The text-to-speech support is the other one. It means the saved article is not only a thing you read but a thing you can listen to, which turns a queue of articles into something you can consume while doing something else, and it works on the content the app already has.

And the ad-free statement, alongside the open source licence, is worth noting as a design position rather than a feature. An app whose server side you host yourself has no reason to carry advertising, and for a service where you are reading things you saved for yourself, the absence is part of what the software is for.

The version floor of wallabag 2.0 and higher is the practical constraint. The app speaks the API of a 2.x server, so an older instance would not work with it.

## Offline reading is a cache, and the permission list explains it

The permissions section is written for Android versions prior to Android 6.0, and it lists four: full network access, view network connections, run at startup, read and write access to external storage.

The explanation for each one is short and specific.

The run at startup permission is only used if the auto-sync feature is enabled and is not utilised otherwise. That is a good example of a permission that looks alarming until you read where it is used.

The network access permissions are made use of for downloading content, and the external storage permission is used to cache article images for viewing offline.

So the permission set tells you what the app actually does on the network. It fetches article content from your wallabag instance, and the images are cached to external storage so they survive for offline viewing. The view network connections permission is the one Android requires for the network access permission in that era, which is a platform requirement rather than a feature of the app.

The caching behaviour is the interesting part for anyone who cares about offline reading. The app caches images locally, so the visual part of an article is available without a connection. The text itself comes from the server, so a cached article is a compromise rather than a full archive, and the extent to which an article reads offline depends on how much of it was fetched and cached on the last sync.

That is a real limitation of the client-server arrangement, and it is the same limitation that any read-it-later client with a server component has. The alternative design, where the app holds its own copy of the articles, would give better offline behaviour but would need its own synchronisation story, and that is exactly what a server-backed design is avoiding.

## What is in the repository, and what the project asks from contributors

The top-level entries describe a conventional Gradle Android project. There is an app/ directory for the application module, a build.gradle and a settings.gradle at the root, gradle.properties, the gradle/ directory with the wrapper and the gradlew and gradlew.bat scripts, an icon/ directory, a readme/ directory holding the screenshots and the logo, and a fastlane/ directory for release automation.

The fastlane directory is worth noting, because it is the sign of a project that releases through more than one channel. The app is on both the Google Play Store and F-Droid, and those two channels have quite different signing and release processes, so automating both is not optional.

The contributing section is short and lists three ways to help. You can report bugs and make suggestions on the issue tracker. You can translate the app, through a Weblate project, and the documentation points out that you do not have to create an account for that. And you can write some code, following the code style used in the project to make a review process faster.

The translation route is the interesting one, because it is the lowest barrier contribution and it is the one that most affects the user base. An app for a self-hosted service has an audience that is self-hosters, and self-hosters are not uniformly English speaking, so localisation matters more here than it would for a consumer app with a marketing budget behind it.

The note about following the existing code style to speed up review is the standard request in a volunteer project, and it is a reasonable one. Wallabag is described as a free and open source project developed by volunteers, and that framing explains the shape of everything else in the repository, including the modest feature list and the permissive request for help.

The licence section says the application is released under GNU GPLv3 and that some of the used libraries are released under different licences.

## Where this fits against the browser and against the other clients

The comparison worth making is with using wallabag in a browser, since the web interface of a wallabag server is a complete reader on its own.

The browser version needs no installation, no store listing and no updates, and it works on any device you can open a page on. The Android app wins on the things a native app is good at: it is offline for cached images, it has text to speech for articles you want listened to rather than read, it has the font and theme controls tuned for a phone screen, and it avoids the browser's own chrome and address bar taking up a third of the display.

The cost of the native app is the thing the project is explicit about elsewhere. You need an account on a wallabag instance, which means you need an instance, which means either running a server or trusting wallabag.it. That is a much bigger commitment than installing a browser extension, and for a lot of people it is the deciding factor.

The second comparison is with the other read-it-later clients, whether Pocket, Instapaper or Readwise Reader. Those are generally free at the point of use, synchronise across devices without you thinking about it, and have reading modes that are more polished than this one. What they are not is something you host. The wallabag proposition is that the data lives on your server, so if the service disappears the archive is still there, and if you do not want a third party reading your reading history you have a way to avoid it.

That proposition has a cost, and it is the same cost the app's feature list implies. You are responsible for the instance, its backups and its upgrades. The app is a well-made client for that arrangement rather than a standalone solution.

So the honest framing is that this repository is the mobile half of a self-hosted system. It is well within its scope, it is ad-free and open source, and the question of whether it is the right choice for you is really a question of whether you want to run the server.

## Conclusion

Adopt the wallabag Android app if you already run or are willing to run a wallabag instance, since the app is a client and the server holds the data. Skip it if you want a read-it-later service with no infrastructure of your own and do not want to rely on the hosted wallabag.it option, and if you need cross-device sync beyond what the server provides. Verify first which wallabag version your instance runs, since the app supports wallabag 2.0 and higher, that you have a working account on the instance before installing, and how you want your reading data protected, since the app is GPLv3 while the underlying wallabag creation carries an MIT licence and the bundled libraries have their own terms.

## FAQ

### What do I need to use the wallabag Android app?

You need a wallabag account first, which you are going to use in the app. You can either connect to your own self-hosted wallabag instance, installing it on your own server following the instructions at wallabag.org, or connect to your wallabag.it account. The app supports wallabag 2.0 and higher.

### Does the wallabag Android app work offline?

There is the possibility to cache images locally for offline reading, and the external storage permission on Android versions before 6.0 is used to cache article images for viewing offline. The article content itself comes from your wallabag instance, so offline availability depends on what was fetched and cached on the last sync.

### What can I read aloud with the wallabag app?

Articles can be read via a text-to-speech feature. The app also lets you increase and decrease the font size and switch between a serif or sans-serif font, switch between numerous themes, and it is completely ad-free with no special permissions needed on Android 6.0 and later.

## Sources

- [License: GPL-3.0](https://github.com/wallabag/android-app/blob/master/LICENSE)
- [Project website](https://www.wallabag.org)
- [README](https://github.com/wallabag/android-app/blob/master/README.md)
- [Releases](https://github.com/wallabag/android-app/releases)
- [wallabag/android-app on GitHub](https://github.com/wallabag/android-app)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/wallabag-android-app