Lute

Open-source language learning software, honestly reviewed. Based on the GitHub repository, official documentation, and community knowledge — not marketing copy.

TL;DR

• What it is: MIT-licensed Python/Flask web app for reading-based language learning — you import texts in a foreign language, click on unknown words, look them up, and track your vocabulary progress automatically [1].
• Who it’s for: Language learners paying $12–25/mo for LingQ (or similar SaaS) who want the same core loop — read, click, define, track — without a recurring bill or vendor lock-in.
• Cost savings: LingQ Premium runs ~$12.99–$24.99/mo. Lute self-hosted costs $0 for the software, runs comfortably on a laptop or a $5 VPS, and you own every word you’ve ever tracked [1][2].
• Key strength: Dead-simple setup (one pip install or Docker), persistent word tracking across all your texts, and full data ownership. Once you look up a word, it’s tracked everywhere — past and future texts included [1][2].
• Key weakness: No content library. LingQ gives you millions of pre-loaded lessons. Lute gives you a blank slate and expects you to bring your own texts. Also: 1,256 GitHub stars means a smaller community than SaaS alternatives, and independent third-party reviews are sparse [1].

---

What is Lute

Lute — short for “Learning Using Texts” — is a reading-based language learning environment. The premise is direct: you paste or import a text in a foreign language, the software renders it word-by-word, and you click on unfamiliar terms. A popup lets you look up the word in a dictionary of your choice, enter your own definition or translation, and set a status level: new, learning (stages 2–5), or known [2].

The critical mechanic is that this tracking persists across every text you ever read in that language. Look up “ephemeral” in a French article today, and the next time that word appears in a different text, it’s already highlighted at whatever level you left it. This is the same idea that made LingQ popular in the language-learning community — the “known words counter” goes up every time you genuinely encounter and review a term in real context, not in a flashcard deck divorced from reading [2].

The project is written in Python (Flask backend), runs as a local web server, stores everything in SQLite, and uses plain HTML/CSS/JavaScript on the front end [1]. There’s no cloud component, no account to create, no data sent anywhere. The codebase is MIT-licensed, which means you can fork it, modify it, or embed it without restriction [1].

At the time of this review: 1,256 GitHub stars, 119 forks, 57 releases with the most recent (3.10.1) published March 10, 2025, and 2,271 commits reflecting steady development since the v3 rewrite [1]. The project maintains an active Discord server and a full manual hosted at the GitHub Pages domain [1][2].

---

Why people choose it

Lute doesn’t have a wide body of independent press coverage — this is a tool discovered by word of mouth in communities like r/languagelearning, r/LearnJapanese, and r/selfhosted. The appeal is almost always the same story: someone paying for LingQ, hitting the free-tier word limit or the pricing tier wall, finding Lute, and realizing they can replicate the core reading workflow for free with full control over their data.

Versus LingQ. LingQ is the market benchmark for reading-based language learning. It has a large community content library (pre-imported podcasts, graded readers, user-submitted texts across 40+ languages), a mobile app, SRS review modes, and a polished interface with years of iteration [3]. It also limits the free tier to 20 saved LingQs — essentially unusable for serious study — and charges $12.99/mo for Premium or $24.99/mo for Plus [3]. Your vocabulary data lives on LingQ’s servers. If LingQ raises prices, changes the product, or shuts down, you lose your years of word history. Lute is the alternative that says: take the core reading loop, make it self-hosted, and let you own your data permanently.

The trade-off is real. Lute has no built-in content library. You bring your own texts — from news sites, Project Gutenberg, your own transcripts, wherever. LingQ has an enormous library, especially for popular languages like Spanish, French, German, and Japanese. For learners who know how to find input (and most serious language learners do), this matters less. For beginners who want guided “Level 1 lessons,” LingQ wins.

Versus Anki. Anki is the go-to SRS flashcard tool for vocabulary, but it’s a fundamentally different workflow. You build individual flashcards and review them in isolation. Lute is contextual: you encounter words inside actual texts, which is the environment where reading fluency develops. Many learners use both — Anki for drilling, Lute for reading. They don’t really compete.

Versus LWT (Learning With Texts). Lute v3 is effectively the modern successor to LWT, a PHP-based project that pioneered the same concept. LWT is older, less maintained, and harder to deploy. Lute v3 was purpose-built to replace it with a cleaner Python stack, better multilingual support, and active ongoing development [1][2].

---

Features

Based on the README and official manual [1][2]:

Core reading interface:

• Import texts as files or by pasting directly
• Word-by-word rendering with interactive lookup
• Click-to-define: opens a configurable dictionary popup (you point it at any URL-based dictionary)
• Status tracking: 1 (new) → 2–5 (learning stages) → 99 (known) → 0 (ignored)
• Words highlighted by status so unknown terms are visually prominent
• Persistent tracking across all texts in a given language — one lookup, tracked everywhere

Book and text management:

• Group texts into “books” (chapters of a novel, episodes of a podcast transcript, etc.)
• Import full EPUB files
• Progress tracking per book
• Multiple languages simultaneously — each has its own word database

Audio support:

• Sentence-level audio playback if you supply an audio file alongside the text
• Useful for listening + reading comprehension in the same interface

Dictionary integration:

• Configurable dictionary links per language
• Supports multiple dictionaries simultaneously (one popup per term)
• Works with any dictionary that accepts a URL parameter (Wiktionary, DeepL, Jisho, Linguee, etc.)

Term and phrase tracking:

• Tracks multi-word phrases, not just single words
• Image associations for terms
• Tags for organizing vocabulary

Plugin system:

• Official plugin support for extending behavior [1]
• Documented plugin API in the wiki

Infrastructure:

• Python 3.x, Flask, SQLite (single file database — easy to back up)
• Docker support (Dockerfile and docker-compose in the repo) [1]
• pip-installable: pip install lute3 && lute and it runs
• Runs on macOS, Linux, Windows
• Can be deployed to a server for remote access via a browser

What’s missing compared to LingQ: mobile app, community content library, built-in SRS review mode (though you can export to Anki), social features, and managed cloud hosting. These are conscious omissions, not gaps — Lute is explicitly a self-hosted single-player tool [2].

---

Pricing: SaaS vs self-hosted math

Lute self-hosted:

• Software: $0 (MIT license) [1]
• Local use: $0/mo — runs on your laptop, no server needed
• Remote access: $5–6/mo for a minimal VPS (Hetzner, Contabo), though most users just run it locally
• Data storage: SQLite file on your machine — no ongoing cost

LingQ for comparison:

• Free tier: 20 saved LingQs (words). Essentially unusable for serious study after week one.
• Premium: ~$12.99/mo
• Plus: ~$24.99/mo
• Annual billing reduces this somewhat; prices are subject to change [3]

Concrete math: A language learner spending one year on LingQ Premium pays roughly $155. On Lute, they pay $0 (local) or ~$60–72 if they want a dedicated VPS for remote access from multiple devices. Over five years — a realistic language-learning timeline for C1 fluency — the gap becomes $775 vs. $0–360.

More importantly, all your vocabulary data stays with you regardless. LingQ has changed pricing and removed features before. Your Lute SQLite database is a file you back up to Dropbox and never lose.

Data caveat: LingQ pricing quoted here reflects training data from this review and may have shifted. Check current rates before making a decision [3].

---

Deployment reality check

Lute is one of the simpler self-hosted tools to get running. The README and manual describe two paths [1][2]:

Local install (simplest):

pip install lute3
lute

Open a browser to http://localhost:5001. That’s it. No database to configure, no environment variables, no nginx. SQLite is bundled. Most users run this on their own laptop and never need anything more.

Docker (for server deployment): Docker and docker-compose files are included in the repository [1]. If you want to access Lute from your phone or multiple machines, spin up a $5 VPS, clone the repo, run docker-compose, and point a subdomain at it. You’ll want a reverse proxy (Caddy is the simplest) and HTTPS. This is a 30–60 minute project for anyone who’s done basic server setup before.

What can go sideways:

• SQLite in Docker: if you mount volumes incorrectly, database writes don’t persist across container restarts. The documentation covers this, but it trips up Docker newcomers.
• Audio sync: sentence-level audio requires you to supply a properly timed audio file alongside your text. This isn’t automatic — you need to source or create aligned audio, which adds friction for audio-heavy learners.
• Large texts: importing a 300,000-word novel works, but the initial parsing and word-status lookup on first load can be slow depending on your hardware. SQLite is fast enough for personal use but isn’t designed for multi-user workloads.
• Language support: Lute handles space-delimited languages well (European languages, Russian, etc.). Japanese and Chinese require the MeCab morphological analyzer or similar external parser for word segmentation [2]. This is documented but adds a setup step for CJK learners.

For non-technical users: the local pip install path is genuinely accessible to anyone comfortable with a terminal. If “open a terminal and type a command” is a blocker, this tool isn’t for you yet — or have a technical friend handle the one-time setup.

---

Pros and cons

Pros

• Free forever. MIT license, no SaaS tier, no word limit, no account required [1]. Your reading habit isn’t capped by what you’re willing to pay this month.
• Data ownership. SQLite file on your machine. Back it up, migrate it, inspect it — it’s plain SQL. No vendor can delete your vocabulary history.
• Simplest setup in the category. pip install lute3 && lute and you have a working tool. Compared to most self-hosted projects, the onboarding friction is minimal [2].
• Language-agnostic. One install supports as many languages as you want to learn simultaneously, each with independent word tracking [2].
• Persistent word tracking across texts. The core mechanic — words remembered everywhere — is the same loop that makes LingQ valuable, without the subscription [2].
• Plugin system and active development. 57 releases, active Discord, MIT license — this is a maintained project with a real community [1].
• Bring-your-own-content. No restrictions on what you read. News articles, novels, subtitles, your own transcriptions — anything text-based.

Cons

• No content library. LingQ has years of curated, graded content for major languages. Lute has none. You source your own reading material [2]. For beginners who don’t know where to find appropriate input, this is a real barrier.
• No mobile app. Browser-only. Using it on a phone requires either a remote server setup or browser-based access to localhost (awkward). LingQ’s mobile apps are a genuine advantage for reading on the go.
• No built-in SRS/review mode. You track words as you read, but there’s no built-in flashcard review loop. You’d export to Anki for that layer [2].
• Niche community. 1,256 stars is small. The Discord is active but not large. Third-party tutorial content is thin compared to LingQ, which has a massive YouTube community [1].
• CJK setup requires extra steps. Japanese and Chinese word segmentation requires an external dependency (MeCab). This is documented but adds friction for learners of the most-requested languages [2].
• No cloud-hosted option. If you want LingQ’s “just works in a browser anywhere” experience without running a server, Lute doesn’t offer that. You either run it locally or manage your own VPS.
• Single-user design. No multi-user support, no sharing. Built for one person’s language learning, not a team tool.

---

Who should use this / who shouldn’t

Use Lute if:

• You’re already paying LingQ or a similar reading platform $10–25/mo and the bill bothers you.
• You have your own sources for reading material — news, books, podcasts with transcripts.
• You want your vocabulary database to be yours, forever, regardless of what any company does.
• You’re learning a European language, Russian, or any space-delimited language (setup is trivial).
• You’re comfortable with a terminal, or have 30 minutes and a guide to set up a pip environment.

Skip it (stay on LingQ or similar) if:

• You’re a beginner who needs a curated content library to find appropriate texts at your level.
• You primarily learn on mobile and need a polished app experience.
• You rely on built-in SRS review loops and don’t want to manage a separate Anki setup.
• You’re learning Japanese or Chinese and aren’t comfortable installing MeCab or similar tools.
• You don’t want to manage any infrastructure, even the trivial pip install path.

Skip it (use Anki instead) if:

• Your primary learning method is vocabulary drilling, not reading. Anki is a different tool solving a different problem.

---

Alternatives worth considering

• LingQ — the direct SaaS comparison. Larger content library, mobile apps, managed cloud, active community. Costs $12–25/mo with data ownership trade-off [3].
• LWT (Learning With Texts) — the older PHP predecessor Lute was built to replace. Still works, less actively maintained, harder to deploy.
• Readlang — SaaS reading-based learning tool. Simpler than LingQ, limited language support.
• Vocabsieve — another open-source vocabulary tool, more focused on Anki integration and dictionary lookups than a full reading interface.
• Anki — not a reading tool, but often used alongside Lute. Anki handles SRS review; Lute handles reading. Many serious learners use both.
• Clozemaster — SaaS, focuses on cloze (fill-in-the-blank) vocabulary in context rather than free reading. Cheap but narrower in method.

For someone escaping a LingQ bill, the realistic shortlist is Lute vs. staying on LingQ’s free tier with supplemental tools. If you have intermediate-to-advanced reading ability in your target language and can source your own content, Lute is the clear choice. If you’re a complete beginner who needs the training wheels of a curated library, LingQ’s early-stage value is harder to replicate.

---

Bottom line

Lute solves one problem well: it takes the reading-based vocabulary tracking loop that LingQ commercialized and makes it free, self-hosted, and yours forever. It won’t replace LingQ if you depend on LingQ’s content library or mobile apps. But if you’re past the beginner stage, already sourcing your own reading material, and paying $150–300/year for a platform that could change its pricing or terms at any time, Lute is a direct substitute for the features you actually use. The setup is genuinely simple — a pip install and a browser — and the data model (a SQLite file you own) is as durable as it gets. The 1,256 GitHub stars reflect a niche tool rather than a broken one; language learners who find it tend to stick with it.

If the setup is the blocker — whether for Lute or any other self-hosted tool in this vein — that’s what upready.dev handles: one deployment, you own the infrastructure, no recurring dependency on someone else’s cloud.

---

Sources

1. LuteOrg/lute-v3 — GitHub repository (README, license, release history, contributor stats). https://github.com/LuteOrg/lute-v3
2. Lute v3 Manual (official documentation, feature descriptions, installation guide). https://luteorg.github.io/lute-manual/
3. LingQ Pricing Page (subscription tiers for comparison). https://www.lingq.com/en/pricing/