Is my private repository exposed when using i18nPilot?

No. i18nPilot uses the GitHub token from your own OAuth session to read your code. We never store your source code on our servers. The scan runs ephemerally and only the detected hardcoded strings are kept, never the full file contents.

What if my project has never had internationalization (i18n)?

That is exactly the ideal scenario. i18nPilot scans your codebase for hardcoded strings, suggests i18n keys, translates them with AI, and creates a Pull Request with all the locale files ready to use. You go from zero to multilingual in minutes.

Which frameworks does i18nPilot support for i18n automation?

i18nPilot supports Next.js, Vite, React CRA, Angular, Nuxt, Vue, SvelteKit, Remix, Astro, Gatsby, Django, FastAPI, Flask, Express, NestJS, Rails, Laravel, and Spring. The scanner auto-detects the framework and adapts the output format accordingly.

How does credit consumption work in i18nPilot?

Each translation operation costs 1 credit regardless of the number of target languages. A scan is free. Buy a credit pack and start translating right away. Credits never expire.

Can I review the AI translations before merging?

Absolutely. i18nPilot creates a standard GitHub Pull Request. You can review every file, request changes, edit translations, or ask your team to review before merging, just like any other PR.

What file formats does i18nPilot generate?

i18nPilot auto-detects your existing i18n structure. It supports JSON, TypeScript, and JavaScript locale files. If your project already has locale files, the new translations follow the same format and directory structure.

What is i18n and why does my SaaS need it?

i18n (internationalization) is the process of designing software so it can be adapted to different languages and regions without engineering changes. SaaS products that localize see up to 1.5x higher conversion rates in new markets and reach 3x more users globally.

How is i18nPilot different from i18next or other i18n libraries?

i18next is a runtime translation library -- you still need to manually extract strings, create keys, and manage translation files. i18nPilot automates the entire pipeline: it scans your code, extracts strings, generates keys, translates with AI, and creates a PR with ready-to-use locale files. It complements i18next by doing the tedious setup work for you.

How do I extract i18n keys from my GitHub repository?

Connect your GitHub account to i18nPilot, select a repository, and click Scan. The tool automatically parses your source code, identifies hardcoded user-facing strings in JSX, templates, and server code, then generates structured i18n keys and translation files.

Does i18nPilot work with Next.js and next-intl?

Yes. i18nPilot has first-class support for Next.js with next-intl. It generates locale JSON files in the correct directory structure, creates the proper configuration, and produces an AI integration prompt that tells your coding assistant exactly how to wire each string using useTranslations hooks.

Sign In | i18nPilot

i18nPilot

Welcome back

We request repo access to scan your code for translatable strings. We never modify your code without your explicit approval.

Automate your i18n from start to finish

Connect your repository, let our AI handle the translation keys, and ship global products in a fraction of the time.

Smart Detection

Scan codebases for hardcoded strings instantly.

AI Semantic Keys

Generate context-aware keys instead of hashes.