🌍 Translation Open source Privacy ★★★★
Lingva Translate
Privacy frontend for Google Translate
Overview
Lingva scrapes/proxies Google Translate so users avoid direct Google contact—similar quality, modest privacy gain.
Account-free web UI; AGPL self-host possible.
Google engine dependency remains—instances can break on Google changes; interim tool not long-term Google exit.
Scores
Privacy 4/5
Ease of use 5/5
Features 3/5
Value 5/5
Google Translate — comparison
Same engine, less direct tracking—no Google account history; fundamental Google reliance remains.
Pros
- ✓ Google Translate–level quality
- ✓ IP not sent directly to Google
- ✓ Free, no account
- ✓ Self-hostable
Cons & caveats
- − Still depends on Google engine
- − Trust Lingva operator or self-host
- − Public instance availability varies
- − No camera or voice translation
Best for
- Better privacy without losing Google quality temporarily
- Self-hosted internal translation proxy
- Quick ad-hoc web translation
Not ideal for
- Long-term production dependence
- Fully offline translation
- Complete Google independence
Specs
- Pricing
- Free — Free; self-host free under AGPL.
- Difficulty
- Easy
- Data location
- Public instance server or your self-host; Google receives proxied requests.
- Platforms
- Web · Self-hosted
Googleに直接アクセスしないオープンソース自己ホスト可軽量UI
Migration from Google Translate
- 1 Bookmark lingva.ml or trusted instance
- 2 Replace Google Translate URLs with Lingva
- 3 Disable Google Translate browser extension
- 4 Self-host Docker instance for stability if needed
Setup steps
- 1 Open lingva.ml or self-host with Docker
- 2 Select source and target languages
- 3 Enter text and translate
- 4 Self-host: docker run -p 3000:3000 lingva/lingva