Ship Global Apps Fast
Automate your internationalization process. Connect your repository, scan for hardcoded strings, and let AI translate your app to 18+ languages in minutes.
Scan Results: src/components/Hero.tsx
Found 12 hardcoded strings. Select targets to translate.
hero.title
“Ship Global Apps Fast”
hero.subtitle
“Automate your internationalization...”
hero.cta
“Start For Free”
Companies around the globe use i18n
Why is i18n still a nightmare?
You know the drill. Wrapping strings, syncing JSON files, hoping nothing breaks. It drains weeks from every sprint.
Extracting and wiring i18n keys takes weeks of tedious, error-prone work that no developer enjoys.
Translation files become an unmanageable mess of nested JSON that's impossible to keep in sync.
Every new language means more delays, more context-switching, and more missed deadlines.
Existing tools either cost a fortune or simply don't translate -- there's no middle ground.
Built for bootstrap i18n, not TMS overhead
Detect hardcoded strings, generate assets, merge with confidence.
Hardcoded String Detection
Find real user-facing copy across components and templates without wasting time on config or implementation noise.
Cultural Mode Translation
NewAdapts tone, formality, and emotional register per locale — pt-BR gets warm and conversational, de-DE gets dense and privacy-first, ja-JP gets soft and indirect.
Merge-Ready Pull Requests
Create translation artifacts in a branch and open a reviewable GitHub PR instead of juggling locale files manually.
Framework-Aware Coverage
Start with modern frontend stacks and template-heavy codebases where localization debt usually appears first.
Suggested Key Mapping
Every string is mapped to a suggested key, file path, and line reference so the integration step stays predictable.
AI Refactor Hand-Off
Generate an integration prompt for Copilot, Cursor, Claude, or ChatGPT to wire the translated strings back into the code.
How i18nPilot gets you from zero to i18n
Connect the repository
Sign in with GitHub and pick the codebase you want to internationalize. i18nPilot starts from the repo you already have.
Scan real product copy
The scanner detects user-visible strings, maps their locations, and proposes i18n keys instead of making you hunt through files manually.
Open a Pull Request
Choose target languages, generate the translation files, and open a reviewable GitHub PR with the locale assets ready to merge into your codebase.
Finish the refactor with AI
Use the generated integration prompt in your coding assistant to replace hardcoded strings with the right i18n calls in the codebase.
Finish the integration work without doing it all by hand
Generate assets, then let AI wire them back in. Exact context. Zero guesswork.
Framework-Aware
Detects common i18n patterns and gives your assistant instructions tailored to the stack already present in the repository.
Exact Code Context
Every detected string carries file path, line reference, and suggested key so the replacement step is concrete instead of guesswork.
Works with Your AI Stack
Use GitHub Copilot, Cursor, Claude, or ChatGPT to accelerate the code changes after the scan and translation pass.
## i18nPilot Integration Prompt
# Framework: next-intl
# Languages: es, fr, de, ja, pt-BR
### Translation Files
Place these files in your project:
+ messages/es.json
+ messages/fr.json
+ messages/de.json
### String Replacements
| File | Line | Replace | With |
|------|------|---------|------|
| Hero.tsx | 14 | "Welcome" | t("hero.welcome") |
| Nav.tsx | 8 | "Sign in" | t("nav.signIn") |
### Framework Setup
Install next-intl and configure...
Why teams use i18nPilot first
A strong fit for product teams that need to unlock multilingual shipping before they adopt a heavier localization stack.
Sarah Chen
@sarahc
“i18nPilot saved us weeks of manual work. The AI translations are surprisingly accurate.”
Alex Rivera
@arivera
“The GitHub integration is flawless. It's like having a full-time localization team.”
David Kim
@dkim
“We launched in 5 new countries in one day. Unbelievable tool.”
Sarah Chen
@sarahc
“i18nPilot saved us weeks of manual work. The AI translations are surprisingly accurate.”
Alex Rivera
@arivera
“The GitHub integration is flawless. It's like having a full-time localization team.”
David Kim
@dkim
“We launched in 5 new countries in one day. Unbelievable tool.”
Sarah Chen
@sarahc
“i18nPilot saved us weeks of manual work. The AI translations are surprisingly accurate.”
Alex Rivera
@arivera
“The GitHub integration is flawless. It's like having a full-time localization team.”
David Kim
@dkim
“We launched in 5 new countries in one day. Unbelievable tool.”
Sarah Chen
@sarahc
“i18nPilot saved us weeks of manual work. The AI translations are surprisingly accurate.”
Alex Rivera
@arivera
“The GitHub integration is flawless. It's like having a full-time localization team.”
David Kim
@dkim
“We launched in 5 new countries in one day. Unbelievable tool.”
Elena Silva
@esilva
“Best i18n tool I've used. The context-aware translation is a game changer.”
Mark Johnson
@markj
“Extracting strings manually is a thing of the past. i18nPilot does it all automatically.”
Lisa Wong
@lisaw
“The JSON export is perfectly formatted. Dropped it into my Next.js app and it just worked.”
Elena Silva
@esilva
“Best i18n tool I've used. The context-aware translation is a game changer.”
Mark Johnson
@markj
“Extracting strings manually is a thing of the past. i18nPilot does it all automatically.”
Lisa Wong
@lisaw
“The JSON export is perfectly formatted. Dropped it into my Next.js app and it just worked.”
Elena Silva
@esilva
“Best i18n tool I've used. The context-aware translation is a game changer.”
Mark Johnson
@markj
“Extracting strings manually is a thing of the past. i18nPilot does it all automatically.”
Lisa Wong
@lisaw
“The JSON export is perfectly formatted. Dropped it into my Next.js app and it just worked.”
Elena Silva
@esilva
“Best i18n tool I've used. The context-aware translation is a game changer.”
Mark Johnson
@markj
“Extracting strings manually is a thing of the past. i18nPilot does it all automatically.”
Lisa Wong
@lisaw
“The JSON export is perfectly formatted. Dropped it into my Next.js app and it just worked.”
Pricing for the bootstrap phase of localization
Use credits when you need to scan, translate, and generate reviewable translation assets. Ideal for teams solving the first i18n rollout without committing to a heavy recurring platform.
v2 Launch Special
Use code PILOT at checkout for 70% off all credit packs!
PILOTStarter
For side projects and small apps
10 credits · $0.27/credit
- 10 credits
- All 18+ languages
- JSON, PO, YAML export
- GitHub Pull Requests
- ~1-2 continuous pushes
Growth
For growing teams and products
50 credits · $0.17/credit
- 50 credits
- All 18+ languages
- JSON, PO, YAML export
- GitHub Pull Requests
- ~8 continuous pushes
Scale
For large codebases and agencies
200 credits · $0.12/credit
- 200 credits
- All 18+ languages
- JSON, PO, YAML export
- GitHub Pull Requests
- ~33 continuous pushes
How credits work
Credits are consumed for scan and translation work. Project size and string volume determine total cost.
| Project Size | Strings Detected | Credits Used |
|---|---|---|
| Small | Up to 50 strings | 1 |
| Medium | 51 - 200 strings | 3 |
| Large | 201 - 500 strings | 5 |
| XL | 501 - 1,000 strings | 10 |
| Enterprise | 1,000+ strings | 20 |
Credits never expire. Use them to bootstrap new repositories, validate rollout scope, and generate the initial localization assets quickly.
Continuous Localization Cost
Each push to a repo with continuous localization enabled consumes approximately 6 credits (1 scan + translation for 5 languages with ~10 changed strings). Actual cost varies by the number of changed strings and target languages.
Starter
Starter covers ~1-2 pushes
Growth
Growth covers ~8 pushes
Scale
Scale covers 33+ pushes (daily pushes for a month)
Frequently Asked Questions
Everything you need to know about i18nPilot