Frequently Asked Questions

Lokali FAQs

i18n coverage measurement, translation tools for Next.js / React / Vue, and how Lokali's GitHub Action fits into your release workflow.

Try the translation budget estimator → to see what your project would cost before you install anything.

i18n coverage is the percentage of source strings (typically keys in an en.json or default locale file) that have equivalents defined per target locale — e.g. coverage of 92% means 8% of strings are missing in that language. The inverse metric — hardcoded strings — counts user-facing literals in source code that were never extracted to the locale file at all. Run a free score and see which keys are missing at /audit.
Paste a public GitHub URL into /audit; Lokali scans your locale files, scores coverage per language, and lists hardcoded strings with line numbers. Results are cached for 30 days, and the open-source repo leaderboard lives at /audit/leaderboard ranking thousands of public repos.
Yes. Install the GitHub App, drop messages/en.json and messages/{fr,de,...}.json into your repo, and Lokali opens translation PRs against them automatically on every push. The framework-specific guide — folder layouts, .lokali.yml config, and PR examples — is at /for/nextjs, and the general quickstart is at /docs.
Yes. Lokali reads standard i18next JSON files (public/locales/{lng}/translation.json) and writes AI translations back via PR. See the React-specific notes and config tabs at /for/react, plus the shared /docs quickstart.
Yes. vue-i18n's standard src/locales/{en,fr,...}.json layout is supported out of the box. Walkthrough with folder conventions and the .lokali.yml config block is at /for/vue.
Yes — the Lokali i18n Coverage Check action runs on every PR and posts a coverage delta comment so you catch regressions before merge. Install it from the GitHub Marketplace at github.com/marketplace/actions/i18n-coverage-check, or read the full configuration guide at /i18n-coverage-github-action.
Once you install the GitHub App, signed-in users get a per-repo coverage dashboard at /dashboard — historical scores, language-by-language deltas, and the list of repos with the biggest recent drops. For unauthenticated score alerts, subscribe on /audit and Lokali will email you weekly when your number changes by more than 5 points.
Free for open-source and public repos — no string cap, no install fee. Private repos are priced per repo, not per seat or per string. Full current pricing, including team and enterprise tiers, is at /pricing.
A user-facing literal in your source code that was never extracted to the locale file — e.g. <button>Save</button> instead of <button>{t('save')}</button>. /audit lists them with file path and line number so you can extract them into your i18n catalog before Lokali picks them up.
Run a manual /audit before any major release and after pulling in new dependencies — coverage regressions often come from newly added components that hardcode literals. For continuous coverage, install the action from github.com/marketplace/actions/i18n-coverage-check so every PR posts a coverage delta comment automatically.

Ready to ship every language?

Install takes 30 seconds. First translation PR on your next push.