Open-source project
lnreader/lnreader avatar
lnreader/lnreader

LNReader: An Open Source Light Novel Reader for Android With a Plugin Architecture

Light novel reader for Android. LNReader LNReader is a free and open source light novel reader for Android, inspired by Tachiyomi.

2,833 stars426 forksTypeScriptMIT

At a glance

What is it?
LNReader is a free, MIT-licensed Android app for reading light novels, built with TypeScript and inspired by Tachiyomi. Its plugin system separates content sources from the core app, but the documentation is thin on setup and usage details.
Who is it for?
Adopt LNReader if you want a free, open source light novel reader for Android with a plugin architecture that keeps content sources separate from the app. Do not adopt it if you need polished documentation, a stable API, or a large ecosystem of verified plugins.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on September 14, 2026, and from our analysis. They are not legal advice.

DEEP OPEN-SOURCE ANALYSIS

What Problem LNReader Solves and Who It Is For

LNReader addresses a specific gap for Android users who read light novels, a format that differs from manga or western ebooks. The app provides a dedicated reading experience with features likely tailored to this content, though the README does not list specific features. It is for readers who want to aggregate content from multiple web sources into one interface, similar to how Tachiyomi works for manga. The target user is someone comfortable with sideloading APKs and managing plugins, not a casual app store user. The project explicitly states it is inspired by Tachiyomi, which sets expectations for a similar extension-based model.

The Plugin Architecture: How Content Sources Are Handled

The core mechanism is the plugin system. LNReader itself has no affiliation with content providers, as stated in the README. Instead, plugins, hosted in a separate repository called lnreader-plugins, provide access to sources. This is a clean separation: the app handles reading, library management, and UI, while plugins handle scraping and parsing. The README directs plugin requests to that separate repository, indicating that the core team does not maintain sources directly. This design reduces legal and maintenance burden on the main project. However, it means the app's utility depends entirely on the community's willingness to write and update plugins. If a source changes its HTML structure, the plugin must be fixed, and there is no guarantee of timely updates.

Getting It Running: Installation and Requirements

Installation is straightforward if you are familiar with sideloading. The README points to the releases page on GitHub for the latest APK. There is also a build workflow via GitHub Actions, so you can build from source if you prefer. The only stated requirement is Android 7.0 or higher. There are no instructions for building locally in the README; it refers to CONTRIBUTING.md for that. The release history shows a recent v2.1.3 from August 2026, so the project is active. For users, the path is: download the APK, enable unknown sources, and install. For developers, the contribution guide is the entry point, but its contents are not covered in the provided material.

Language and Localization: Crowdin Integration

The project uses Crowdin for translations, which is a concrete sign of international user base. The README invites contributors to help translate the app. This is a practical feature for a niche reader app, as light novel readers are global. The integration with Crowdin means translations are managed externally, and the app can pull in strings from the community. This is a maintenance cost: every new feature or UI string must be added to Crowdin, and translators need to keep up. For users, it means the app is likely available in many languages, but the quality and completeness of translations depend on volunteer effort. The README does not list supported languages, so you cannot assume your language is covered.

A Real Limitation: Dependency on Community Plugins

The most significant limitation is the plugin dependency. Without plugins, LNReader is an empty shell. The README explicitly disclaims affiliation with content providers, which is legally prudent but practically risky. If a plugin breaks, you have no recourse from the core team. The plugins repository is separate, and while it exists, there is no guarantee of plugin quality or update frequency. This is the wrong tool if you want a curated, reliable content experience. Compare this to a proprietary reader that bundles sources; LNReader gives you control but also responsibility. You must be willing to troubleshoot plugin issues yourself or wait for community fixes. The documentation does not explain how to install plugins, which is a gap for new users.

Alternative: Tachiyomi and Its Approach

The obvious alternative is Tachiyomi, the project LNReader is inspired by. Tachiyomi is a manga reader, not a light novel reader, but it uses a similar extension model. The key difference is that Tachiyomi has a longer history, a larger community, and a more mature extension repository. Tachiyomi's extensions are also community-maintained, but the ecosystem is bigger, so you are more likely to find working sources. For light novels specifically, Tachiyomi may not have the same reader features, such as text reflow or font customization, which LNReader likely offers. If you read manga and light novels, you might use both apps. If you only read light novels, LNReader is designed for that, but you must verify that its plugins cover your sources. The alternative approach is to use a web browser or a generic ebook reader, but those lack the aggregation and tracking features that a dedicated app provides.

Maintenance and Upgrade Cost, and License Implications

The project is under active development, with three releases in the last month as of August 2026. This suggests regular fixes and feature additions. However, the maintenance cost for users is tied to plugin updates, not just app updates. Each app release may require plugin compatibility updates, and you must keep both app and plugins current. The license is MIT, which is permissive: you can use, modify, and distribute the code with minimal restrictions, as long as you preserve the copyright notice. This is good for developers who want to fork or contribute. For users, it means the app is free, but there is no warranty. The README does not mention any paid features or ads, so it is likely fully free. The absence of a formal support channel, other than Discord and GitHub, means you rely on community help. Check the CONTRIBUTING.md for build instructions if you plan to compile from source, as the README does not include them.

Editorial conclusion

Adopt LNReader if you want a free, open source light novel reader for Android with a plugin architecture that keeps content sources separate from the app. Do not adopt it if you need polished documentation, a stable API, or a large ecosystem of verified plugins. Before using it, verify that the plugins you need are maintained and that the app runs on your Android version, which must be 7.0 or higher. Check the release page for the latest APK and the plugins repository for source availability. The project is actively maintained as of August 2026, with recent releases, but its success depends on community-provided plugins.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Community notes

Community notes