Open-source project
readest/readest avatar
readest/readest

Readest: A Cross-Platform Ebook Reader Built on Next.js and Tauri

Readest is a modern, feature-rich ebook reader designed for avid readers offering reliable cross-platform access, powerful tools, and an intuitive interface to elevate your reading experience.

24,354 stars1,578 forksTypeScriptAGPL-3.0

At a glance

What is it?
Readest is an open-source ebook reader that rewrites Foliate using Next.js 16 and Tauri v2, targeting macOS, Windows, Linux, Android, iOS, and the Web. It offers a wide feature set but carries an AGPL-3.0 license that may affect how you distribute it.
Who is it for?
Adopt Readest if you want a modern, actively maintained ebook reader that works across desktop, mobile, and web, and if you are comfortable with the AGPL-3.0 license. Do not adopt it if you need to embed the reader in a proprietary product or if you require a stable API for custom development, since the project is still evolving.
Can I use it commercially?
Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
Is it still maintained?
Yes. The repository last received commits 1 day 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 15, 2026, and from our analysis. They are not legal advice.

DEEP OPEN-SOURCE ANALYSIS

What Readest Solves and Who It Is For

Readest addresses a common pain point for avid readers: managing and reading ebooks across multiple devices without losing progress or annotations. The README positions it as a modern rewrite of Foliate, a popular GTK-based reader for Linux. Where Foliate is desktop-only, Readest expands to macOS, Windows, Linux, Android, iOS, and the Web, all from a single codebase. The target user is someone who reads EPUB, PDF, MOBI, or other formats and wants a consistent experience on a phone, a tablet, and a desktop. The project also targets users who need accessibility features like full keyboard navigation and screen reader support, which the README lists as implemented. If you are a developer who wants to contribute, the TypeScript codebase and the use of Next.js and Tauri may be familiar, but the AGPL-3.0 license is a significant consideration for any commercial use.

Architecture: Next.js 16 and Tauri v2

The README states that Readest is built with Next.js 16 and Tauri v2. This is an unusual combination: Next.js is a web framework, while Tauri is a desktop application shell that uses the system webview. The architecture likely splits the application into a frontend rendered by Next.js and a Tauri backend that provides native capabilities like file system access and window management. For mobile and web, the same Next.js frontend can be served, which explains the cross-platform reach. The README does not detail the data flow, but the presence of features like OPDS/Calibre integration and sync across platforms suggests a client-server model where the Tauri layer handles local file access and the Next.js layer handles UI and network calls. This design offers a trade-off: you get a consistent UI across platforms, but you depend on the webview's performance and consistency, which can vary, especially on older devices. The repository layout is not fully described, but the use of Tauri implies a Rust backend for the desktop shell, which is not evident from the README alone.

Getting Started: Installation and Setup

The README provides download links for mobile apps on the App Store and Google Play, and mentions platform-specific downloads for macOS, iOS, and iPadOS via the App Store, with TestFlight available for beta testers. For desktop, the README is truncated, but it likely offers installers for Windows, Linux, and macOS from the releases page. The latest release is v0.12.6, dated 2026-08-28. To run from source, you would need to clone the repository and install dependencies, but the README does not include explicit build commands in the visible portion. The documentation section is mentioned but not detailed. For a developer, the first step would be to check the repository's CONTRIBUTING or README for setup instructions, but the truncated content prevents me from giving exact commands. What is clear is that the project supports multiple formats, so you can open files directly or import them into the library. The README also mentions file association and 'Open With' support, which suggests that after installation, you can right-click an ebook file and open it in Readest.

Feature Set: From Annotations to Audiobooks

The README lists a long set of implemented features, which is the project's main selling point. You get multi-format support for EPUB, PDF, MOBI, KF8 (AZW3), FB2, CBZ, TXT, and Markdown. Reading modes include scroll and paginated views. Full-text search works within a book or across the library shelf. Annotations cover highlights, bookmarks, and notes, with an 'instant mode' for quicker interactions. Dictionary and Wikipedia lookup is built in, and you can import local packs, including Yomitan ZIP/RDICT. Parallel read lets you view two books side by side. There is code syntax highlighting, which is useful for reading technical manuals. Library management includes sorting and organization. OPDS and Calibre integration allow access to online catalogs. Translation via DeepL and Yandex works from a sentence to the whole book. Audiobook support and text-to-speech are implemented, including read-along narration with EPUB 3 Media Overlays. Sync across platforms covers book files, progress, notes, and bookmarks, and there is even sync with KOReader devices. Accessibility features include keyboard navigation and screen reader support. This is a feature-rich list, but the README does not specify the quality or stability of each feature, so users should test the ones they rely on.

Limitations and When It Is the Wrong Tool

One clear limitation is the license. AGPL-3.0 is a strong copyleft license, which means if you modify Readest and provide it over a network, you must release your source code. For a company that wants to integrate an ebook reader into a proprietary product, this is a non-starter. Another limitation is the reliance on Tauri and Next.js, which may introduce complexity for users who want a simple, self-contained app. The README mentions 'planned features' like AI-powered summarization and advanced reading stats, but these are not yet available, so if you need those, Readest is not the right tool today. The sync feature is a black box: the README says it syncs across platforms, but it does not explain the backend, whether it is self-hosted, or what data is collected. For privacy-conscious users, this is a concern. Also, the project is still under active development, with releases coming every few weeks, which means features may change or break. If you need a stable, long-term support version, you might prefer a more mature reader like Calibre, which has a different approach.

Alternative: Foliate and Calibre

The most direct alternative is Foliate, the project Readest rewrites. Foliate is a GTK-based reader for Linux, written in JavaScript, and it focuses on a clean, minimal interface. It does not have mobile or web support, and it does not offer sync across platforms. If you are a Linux user who wants a lightweight, native reader, Foliate may be a better fit. Another alternative is Calibre, which is a full-featured ebook manager and reader with a huge ecosystem of plugins. Calibre is desktop-only (with a web server option), and it uses a different architecture: a monolithic Python application with a custom Qt interface. Calibre is more powerful for library management and conversion, but it is heavier and less modern in its UI. Readest's advantage is its cross-platform reach and modern stack, but if you need deep metadata management or a stable, long-standing tool, Calibre is the safer choice. The README does not compare itself to these, but the difference in approach is clear: Readest bets on web technologies and a unified codebase, while Foliate and Calibre use native toolkits.

Maintenance and Upgrade Cost

The project is actively maintained, with the latest release v0.12.6 on 2026-08-28, and previous releases in July and August 2026. This cadence suggests a steady development pace. The README invites contributions and has a Discord and Reddit community, which indicates a support structure. The upgrade cost is low for end users, as they can download new releases from the App Store or the releases page. For developers who fork the project, the cost is higher: you need to track upstream changes, and the use of Next.js 16 and Tauri v2 means you must keep up with updates to those frameworks. The AGPL-3.0 license also imposes obligations if you distribute modified versions, so you must maintain a public source repository. The README does not provide a changelog or migration guide, so upgrading between major versions may require manual intervention. Overall, the maintenance burden is moderate, but the active release schedule is a positive sign for bug fixes and new features.

Editorial conclusion

Adopt Readest if you want a modern, actively maintained ebook reader that works across desktop, mobile, and web, and if you are comfortable with the AGPL-3.0 license. Do not adopt it if you need to embed the reader in a proprietary product or if you require a stable API for custom development, since the project is still evolving. Before adopting, verify that the sync backend meets your privacy expectations and that the platform-specific builds for your target OS are current, as the latest release is v0.12.6 from August 2026.

Official sources

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

Community notes