Discofork
Repository brief

gedoor/legado

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T12:55:04.617Z
3mo ago

gedoor/legado

Legado is an active, open source Android novel reader focused on highly customizable content sources and reading controls. It has a large user base and fork ecosystem, and the repository shows recent maintenance through March 2026. Forks are most interesting if they want to extend or tailor an Android reading app with custom source rules, subscription content, local TXT/EPUB support, and deep reading UI customization.

GitHub
Loading tags...
Stars45,399
Forks5,163
Default branchmaster
Last pushed2026-03-17T11:01:41Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if you want a more aggressive, source-centric Legado variant with better web rendering and extra rule capabilities. Stick with upstream if you prefer the simpler, more established baseline and want fewer fork-specific behaviors to account for.

Choose this fork if AI summaries are the main reason to use Legado. Choose upstream if you want the broadest compatibility, freshest fixes, and the least maintenance burden.

Choose this fork if your main pain point is backup, restore, or WebDAV sync reliability and you want an actively maintained Legado branch. Skip it if you want the broadest upstream feature set or the newest upstream changes immediately.

Choose this fork only if you specifically want its 2022 customizations and are prepared to maintain it yourself. If you want an actively evolving Android novel reader, upstream is the better fit.

Choose this fork if you want an actively developed, heavily customized Legado variant with extra workflow polish and some new playback/editor-oriented behavior. Choose upstream if you need maximum compatibility, simpler maintenance, or specific customization surfaces like the original welcome-page behavior.

Prefer this fork only if its specific reader tweaks solve a real problem for you. If you want the healthiest long-term Legado base, upstream is the safer choice because this fork is very small and far behind.

Choose this fork only if its custom workflow changes are important enough to justify a stale, heavily diverged codebase. For most adopters who want the latest Legado fixes and source compatibility, upstream is the safer default.

Choose this fork if you want Legado plus Reader Server syncing, app lock, and local-data hardening. Stick with upstream if you want the broadest compatibility and the least migration risk.

Choose this fork if you want a customized Legado derivative and can tolerate being far behind upstream. Avoid it if you need an actively maintained, upstream-aligned reader with the latest fixes and features.

Choose this fork if you want a Legado-based reader with rebranding and reduced Google dependency surface; skip it if you need maximum upstream feature parity or depend on Firebase/Google-service integrations.