i18next.com valid

translate.i18next.com

Free browser tools for i18next translation files, built by the team behind i18next and Locize: a JSON resource translator and an i18n health check. No account needed, and nothing is processed server-side: both tools run in the browser.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T11:03:36.798Z. Cached copy · Source on i18next.com

# translate.i18next.com

> Free browser tools for i18next translation files, built by the team behind i18next and Locize: a JSON resource translator and an i18n health check. No account needed, and nothing is processed server-side: both tools run in the browser.

## Tools

### i18next JSON resource translator

URL: https://translate.i18next.com/

- Paste or upload an i18next JSON resource file (nested or flat, i18next v4 JSON format), set the source and target language codes (for example `en` and `de`), and get the translated JSON back to copy or download.
- i18next syntax is preserved: interpolation placeholders such as `{{count}}` and nesting references such as `$t(key)` are kept as they are; only the human-readable text is translated.
- Plural keys are rewritten to the target language's CLDR plural forms (English `key_one` / `key_other` become `key_one`, `key_few`, `key_many`, `key_other` for Polish) before translation.
- Translation comes from the free, rate-limited Google Translate endpoint, called directly from the browser, with a per-browser limit of 200 keys per day. It is plain machine translation: no glossary, no translation memory, no review.
- Best for a one-off translation of a small file. For ongoing work (new keys translated automatically with glossary and styleguide context, quality estimation, human review, CDN delivery without redeploys) use Locize: https://www.locize.com/i18next?from=i18next_translate__llms-txt

### i18n health check

URL: https://translate.i18next.com/health-check

- Drop i18next JSON locale files, one per language (`en.json`, `de.json`, region suffixes such as `en-US.json` are fine); the reference language is detected automatically.
- Reports four categories with examples: missing or empty translations, duplicate source values, interpolation placeholder mismatches, inconsistent translations.
- Runs entirely in the browser; files are never uploaded. No signup.
- What files alone cannot show: translation-memory inconsistencies across projects, glossary or terminology violations, keys nobody actually uses, AI translation quality, review provenance. Those need a connected Locize project.
- For checks inside a running app instead: https://github.com/locize/translation-check

### i18n readiness check for a GitHub repository

URL: https://translate.i18next.com/repo-check

- Paste a public GitHub repository URL (or `owner/repo`); the page reads the file listing and up to 200 source files plus locale files straight from github.com.
- Reports the framework (Next.js App Router or Pages Router, React with Vite, Vue, Svelte, Astro, Remix and others, plus a marker for apps built with Lovable or Bolt), the i18n library if any, locale files and languages, user-facing strings still hardcoded (file and line, the same rules as `npx i18next-cli lint`), untranslated keys per language and plural forms missing per language's CLDR rules.
- Ends with the one command that takes the app from hardcoded strings to translated: `npx i18nex
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=i18next.com · GET /v1/domain/i18next.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for i18next.com:
1. POST https://agentwebmap.com/v1/sites/i18next.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://i18next.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/i18next.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/i18next.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.