Read Frog vs KISS Translator: How Two Open-Source AI Translation Extensions Challenge Bloated Paid Plugins
> Source: GitHub repositories, official docs, community reviews, public information on the Meituan Tabbit plagiarism incident
Overview
Read Frog and KISS Translator are two open-source browser translation extensions attacking the market from opposite directions: "AI language-learning assistant" and "minimalist translation tool." Both are ad-free, don't harvest data, and counter the increasingly bloated, closed-source, privacy-risky immersive translation plugins. Read Frog differentiates with 20+ AI models + context awareness + batched requests saving ~70% tokens; KISS Translator wins over technical users with minimalism + broad browser support + offline-first translation + a custom rules ecosystem.
Why alternatives are needed
Mainstream translation plugins (e.g., Immersive Translate) suffer from well-known pain points:
- Feature bloat — cluttered UI, high learning curve
- Token burn — every translation is an independent API call
- Privacy risk — terms of service collect nearly everything; an August 2025 data-leak incident
- Ads/commercialization — free tier limits, subscriptions
- Closed source — no auditing, no self-hosting, no customization
- Page lag — heavy DOM manipulation and injection
- Bilingual / pure translation modes — original + translation side by side, or direct replacement; mode switch re-translates without page refresh
- Context-aware translation — feeds page title + Markdown content summary to the AI for more accurate domain-specific, literary, and ambiguous translations
- Selection toolbar — Translate (streaming), Explain (per user level), Speak (Edge TTS); draggable, works across sites
- Custom prompts — dynamic tokens like
[TARGET_LANG],[INPUT],[TITLE],[SUMMARY]; multiple saveable templates - Batched requests (key differentiator) — merges multiple translation requests into a single API call, officially claimed to save up to 70% API cost; exponential-backoff retries with fallback to per-item requests
- 20+ AI providers via Vercel AI SDK: OpenAI, DeepSeek, Anthropic Claude, Google Gemini, xAI Grok, Groq, Mistral, Ollama (local), plus free options (Google/Microsoft Translate, DeepLX)
- YouTube bilingual subtitles inside the video player
- Edge TTS — completely free, 150+ voices, 80+ languages, sentence-aware chunking with preloading, auto language detection
- Broad support: Chrome / Edge / Firefox / Kiwi (Android) / Orion (iOS) / Safari / Thunderbird, plus a Tampermonkey/Violentmonkey userscript
- Translation services: Google, Microsoft, DeepL, DeepLX, NiuTrans, Baidu, Tencent, Volcengine; AI: OpenAI, Gemini, Claude, Ollama, DeepSeek, OpenRouter, AzureAI, CloudflareAI; Chrome BuiltinAI (offline); custom endpoints
- Coverage: bilingual page translation, input-box translation, selection translation with multi-service comparison, hover translation, YouTube subtitles (AI segmentation, merging, custom styling), vocabulary favorites
- Customization: automatic text-pattern detection (most sites need no rules), manual rules, custom translation styles, rich-text translation preserving links/styles, translation-only mode
- Offline translation (key differentiator): browser BuiltinAI (zero config), local models via Ollama (
http://localhost:11434), or local cache (24h validity) - Advanced: AI context memory, AI glossary, batch aggregation, cross-client sync via KISS-Worker (Cloudflare/Docker) or WebDAV, rule subscription/sharing, custom shortcuts
- Language learners → Read Frog (context explanations, TTS)
- Technical docs → KISS Translator (fast, glossary, offline)
- High-frequency translators → Read Frog (batch token savings)
- Privacy-sensitive users → KISS Translator (offline, local models, self-hosted sync)
- Mobile users / multi-device sync → KISS Translator
- Custom prompts → Read Frog; custom rules → KISS Translator
- Token savings: Read Frog's "70%" is a best case; savings depend on text distribution. KISS Translator reduces calls but publishes no percentage. Batching pays off most for short, fragmented texts.
- Not full replacements: neither supports PDF translation, EPUB translation, or AI text polishing; mobile experience is weaker than native apps.
- Open source ≠ automatically secure: users still manage their own API keys; extensions have high privileges; open source only helps if actual security review happens.
- Token economics: AI translation cost includes per-request overhead; batching short texts amortizes system prompts and HTTP overhead.
- Browser built-in AI is an emerging zero-key, offline path that may challenge third-party translation services.
- Decentralization: user-supplied keys, multi-provider support, and community rule ecosystems counter platform lock-in.
- When mainstream products bloat, precise tools win: Read Frog focuses on "web + AI + learning"; KISS Translator on "minimal + multi-scenario + offline." Read Frog may evolve toward a commercialized learning platform; KISS Translator toward "the uBlock Origin of translation."
Users increasingly want open, lightweight, controllable tools: auditable code, their own API keys, custom prompts/rules, and offline capability.
Read Frog: AI-driven language learning assistant
| Property | Info | |---|---| | Repo | https://github.com/mengxi-ream/read-frog | | Stars | ~5.6K (as of 2026-05) | | License | GPLv3 + commercial dual license | | Positioning | AI-powered immersive language learning extension |
Core features
Tech stack: TypeScript + React + Tailwind CSS + Vite + WebExtension API; IndexedDB (Dexie) storage; fully local, user-supplied API keys that never pass through the author's server.
The Meituan Tabbit plagiarism incident
| Date | Event | |---|---| | 2025-12-30 | Meituan's Tabbit team forked Read Frog code (no license declared at the time) | | 2026-01-02 | Author added GPLv3 | | 2026-03-02 | Tabbit browser launched; translation UI, option order, shortcuts, even internal filenames (read-frog-xxx.png) nearly identical to Read Frog | | 2026-03-02/03 | Author published accusations on Xiaohongshu/X; community backlash | | 2026-03-03 | Tabbit admitted forking pre-license, promised to remove the feature and open-source per community norms: https://github.com/Tabbit-Browser/read-frog | | Aftermath | Author granted Tabbit a free commercial license (limited to v1.21.3 and earlier) |
The incident highlighted the power of GPLv3 copyleft and a rising awareness of license compliance in the Chinese open-source community.
KISS Translator: the minimalist's choice
| Property | Info | |---|---| | Repo | https://github.com/fishjar/kiss-translator | | Developer | fishjar | | Philosophy | Keep It Simple, Smart |
Core features
Ecosystem
| Project | Purpose | |---|---| | kiss-translator | Main extension | | kiss-worker | Self-hosted sync service (Cloudflare/Docker) | | kiss-rules | Community rule subscription lists | | kiss-proxy | Translation endpoint proxy | | kiss-dictionary | Selection dictionary plugin |
Head-to-head
| Dimension | Read Frog | KISS Translator | |---|---|---| | Positioning | AI learning assistant | Minimalist translator | | AI models | 20+ (Vercel AI SDK) | 10+ incl. custom endpoints | | Batch requests | Yes, ~70% token savings | Aggregated sending | | TTS | Edge TTS (150+ voices, free) | None | | Offline | No | BuiltinAI / Ollama / cache | | Browsers | Chrome/Edge/Firefox | 7+ incl. mobile + userscript | | Sync | IndexedDB (Firebase planned) | KISS-Worker / WebDAV | | License | GPLv3 + commercial dual | Open source |
How to choose
Versus Immersive Translate
Compared to the closed-source incumbent, both tools are free, ad-free, run locally, support more AI models, and cut token costs through batching — while Immersive Translate uniquely offers PDF/EPUB translation and AI polishing. The 2025 data-leak incident accelerated user migration to open-source alternatives.
Reality check (anti-hype audit)
Takeaways
References
1. Read Frog GitHub: https://github.com/mengxi-ream/read-frog 2. KISS Translator GitHub: https://github.com/fishjar/kiss-translator 3. Meituan Tabbit incident writeup: https://blog.mzh.ren/zh/posts/2026/02/meituan-tabbit-plagiarize-read-frog/ 4. Tabbit's open-source fork: https://github.com/Tabbit-Browser/read-frog 5. Chrome Stats – KISS Translator: https://chrome-stats.com/d/jemckldkclkinpjighnoilpbldbdmmlh 6. KISS Translator userscript: https://greasyfork.org/