Making the web multilingual
The web was built in English — but 75% of internet users prefer content in their native language. We built Lingvit because the existing solutions either require rebuilding your entire app (i18n libraries) or charge per word on your site (translation widgets). Neither is right.
What we believe
Translation should be automatic by default
A script tag before </body> can add runtime translation without rebuilding the application. Verify representative pages and review important copy before publishing.
Pricing should follow usage, not penalize you for having content
Word-count pricing punishes sites with lots of content for simply existing. We charge for translations served, not for words stored.
RTL languages deserve first-class support, not an afterthought
Arabic, Hebrew, Persian, and Urdu together represent hundreds of millions of users. Lingvit flips the full layout direction automatically — margins, padding, flex order, everything.
How Lingvit works
You add one script tag to your site. Lingvit's widget uses a MutationObserver to discover all text nodes — including content added after initial load by JavaScript frameworks. Translations are produced automatically and stored for reuse, so cached delivery does not use your monthly allowance again.
Pay only for new translations
Lingvit uses word-based subscription plans with a monthly allowance for new translations. Stored and cached translations can be served repeatedly without using your allowance again, making the same delivery model practical for small products and larger teams.
Learn more
Pricing
current subscription plans and billing details.
Documentation
installation guide, dashboard reference, and API.
Features
full feature list: caching, glossary, review, and RTL.
Integrations
WordPress, Shopify, React, Next.js, and more.
Languages
30+ supported languages with per-language pages.
Blog
guides on multilingual SEO, i18n comparisons, and localization strategy.