Shiori vs wallabag

Editor take

Pick wallabag for a reading flow on phones with EPUB export. Choose Shiori for offline copies in a single binary.

Editor

Pros and cons

Each app's own strengths and weaknesses, plus the specs where Shiori and wallabag differ.

Shiori

Pros

  • One Go binary or one container
  • Offline archive and reader mode
  • Pocket and Netscape imports
  • CLI, REST API and web page
  • Users and per-account logins

Cons

  • Pocket import keeps links only
  • Browser extension still beta
  • No native mobile app

wallabag

Pros

  • Extracts article text for reading
  • Official Android and iOS apps
  • Imports Pocket and Omnivore archives
  • Tags, annotations and EPUB export

Cons

  • iOS client is closed source
  • Android app rules out 2FA
  • Paywalled sites need your login

Shiori vs wallabag: specs side by side

Every spec for both apps in one table. Values in bold are where one app has the edge, and amber ones are worth a second look before you install.

Spec
PriceAdvantage: FreeFree + Paid
LicenceMITMIT
Web UIYesYes
iOS–Yes
Android–Yes
DockerYesYes
Linux packageYesYes
WindowsYes–
macOSYes–
Tech stackGoPHP
Docker Containers1 (app only)2 (app + Redis)
DatabaseSQLiteSQLite
Architecturex86 + ARMx86 + ARM

Common questions

Which has official mobile apps?

wallabag. Shiori has none, only a web page, CLI and an extension.

Which keeps a full page copy?

Shiori can keep the readable content or a full archive; wallabag extracts article text for reading.

Sources: Shiori docs and wallabag docs. Versions checked: Shiori 1.8.0, wallabag 2.6.14.

Updated