Make your app multilingual in minutes

Set it up once. Translations land on every push.

Make my app multilingual

What is globalize.now?

Make your app multilingual in minutes — and keep it that way automatically.

Add the skills

Paste one prompt into Cursor or Claude Code. It makes your codebase translation-ready.

It hooks into globalize

Your text becomes locale files you own, right in your repo.

Every push stays translated

New text is translated and synced automatically. Nothing breaks, no manual steps.

BUILT FOR YOUR STACK

Next.js

React

Vite

Cursor

Claude Code

Codex

VS Code

GitHub

GitLab

How does globalize.now work?

Two paths. One outcome. Pick whichever describes your codebase today.

NO YET

ALREADY HAVE

NO YET

Full setup.

No translations wired up yet? We install everything, find your English text, and translate it. Then we keep new content in sync.

Step 01
Install in your terminal
One command. Nothing in your codebase changes. It just gives your agent a playbook to read.
$npx skills add globalize-now/globalize-skills --all
What to expect
- One prompt installs the skills, then the agent makes your codebase ready for languages. It's more than a single line of code, and that's what saves you the manual rewrite.
- It does change your code to make this work. You see the plan first and approve before anything changes.
- After setup, translation runs automatically on every push. You're only charged for new text, never just for shipping.
Step 02
Tell your agent to set up multilingual
In Cursor, Claude Code, or Codex. The agent detects your framework, installs the right translation library, and wires up every piece of English text in your UI.
Your prompt
Set up i18n for my project
Step 03
Your text becomes translatable
Every piece of English text gets wired to a translation file. Spanish, German, Arabic. Whichever languages you need are ready to fill in.
Step 04
Translations land on every push
Open a PR with new text? Translations land in the same PR before you merge. Push straight to main? We open a follow-up PR with translations. Either way, translations ship with your code, not behind it.

Both paths end at the same loop: a PR you review, you merge. We never push to main directly. No manual exports, no review queues.

Was this helpful?

WHAT MAKES US DIFFERENT

Where developers actually work.

Most localization tools live outside your workflow. We live inside it.

Inside your AI agent.

We install as a skill into Cursor, Claude Code, or Codex. The agent does the work. We just give it the playbook. No separate dashboard. No second tool to learn.

Inside your Git workflow.

Every push to main triggers a PR with translations ready to review. No review queue. No export button. No separate role to hire.

Inside your existing codebase.

Framework detection on first run. If you already have next-intl, react-i18next, i18next, or @lingui, we skip the destructive setup and go straight to sync. Other tools assume you're starting from zero.

LANGUAGES

50+ languages on day one ( included)

50+ languages including Arabic, Hebrew, Persian (), Chinese, Japanese, Hindi, and more.

Show all 50+ languages

AfrikaansArabicBengaliBulgarianCatalanChineseCroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrenchGermanGreekGujaratiHebrewHindiHungarianIndonesianItalianJapaneseKannadaKoreanLatvianLithuanianMalayMalayalamMarathiNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishTamilTeluguThaiTurkishUkrainianUrduVietnamese

Got questions? Browse the docs →

From the field

What early users are saying.

Real React and Next.js apps. Real i18n debt. What early builders tell us.

Charlie Day

Co-founder · Pretty Prompt

“I just want translation to be automatic so language no longer becomes a barrier. This is exactly what I was looking for, works in the background on every commit, with great results!”

Tomas Franc

Founder · NextKS · ex-Lokalise Lead Solutions Architect

“A big relief to developers, they can rely on AI to do this stuff for them. Because it's painful stuff.”

Verified User

Leisure, Travel & Tourism · Small business

4.5

I tried to do it with Claude and Lovable before but ended up breaking the code. With globalize it was super easy.

Verified on G2Read on G2

Using globalize.now? Tell us what you think.

PRICING

€20 a month. Plus the translations you actually use.

One plan. No tiers, no surprises, no enterprise sales call. Top up when you grow.

Billed by what we actually process (tokens), shown to you in plain English. The €5 signup credit covers over 1,000,000 characters (roughly 150,000 words). A typical SaaS with ~10,000 translation keys across 5 locales lands comfortably inside the €20 plan; larger apps top up at the same per-character rate. Before any translation runs, we show you the exact math for your codebase.

EARLY ACCESS

What's included

€20/mo

PER WORKSPACE · OVER 4,000,000 CHARACTERS · ~600,000 WORDS

€5 translation credit on signup, no card required.

Need more? Top up at the same per-character rate. No plan switch required.

Start free →

Over 4M characters / ~600,000 words per month
Unlimited languages incl.
CLI, API & GitHub sync
Context-aware AI glossary
Priority support during early access

Comparing globalize.now to Lokalise, Phrase, or Crowdin? See how we stack up →

FAQ

Frequently asked questions

Google Translate bolts a rough machine-translation layer on top of your live page. You don't control the wording or how it reads, and it sits over your UI rather than being built into it. globalize translates the real text in your codebase into locale files you own, in your repo. You get editable, AI-quality translations, a proper page per language (better for SEO), and nothing breaks when you ship.

Prompt your coding agent to discover globalize.now, then run npx skills add globalize-now/globalize-skills from your project root. That command installs agent-side i18n skills so the agent can scan your AI-generated codebase for hardcoded UI strings, generate translation keys and locale files, and keep translations auto-synced on every Git push with no manual exports, no review queues, and no extra dashboard work.

No—you can stay entirely inside Cursor, Claude Code, or whatever AI coding environment you already use. Open the unguided setup flow and follow three agent prompts in order—after running npx skills add globalize-now/globalize-skills, use Set up localization for my project and Convert my app—so your editor never becomes a side quest while your repository gains translation keys, locale files, and continuous auto-sync on every push.

npx skills add globalize-now/globalize-skills installs curated localization skills into your agent so it knows how to analyze an AI-generated codebase, extract hardcoded UI text into translation keys, scaffold locale files, and keep translations aligned on every Git push. You still steer prompts, but the agent gains repeatable guardrails instead of improvising i18n architecture from scratch.

If explanations wander, stop and rerun npx skills add globalize-now/globalize-skills to refresh the skills, then issue Set up localization for my project so the agent rescans components, and Convert my app so new translation keys merge back into your repo with CI watching every Git push. Finish by asking for a simple language switcher so you can verify locale JSON immediately, still without manual exports or translator review queues.

Yes—you can translate every string yourself after Set up localization for my project because that phase is free and already leaves you with translation keys plus locale files checked into Git. If you later connect billing, globalize continues translating automatically on each push for new UI you ship, giving you auto-sync on every Git push without forcing human approval steps on every release.

Billing counts translated characters—the rendered text we generate across target languages—not source-code bytes. Each workspace includes 100,000 translated characters monthly in the base fee, with additional bundles billed at €0.001 per thousand characters applied consistently so everyone on the team sees predictable totals tied to actual output.

Translations pause when you cross the monthly translated-character allowance, but your application keeps serving the last synced locale JSON exactly as before, so nothing crashes at runtime. You receive an in-product heads-up, upgrade whenever you are ready, and new strings resume translating automatically on the next Git push after capacity resets or your plan expands.

Yes. globalize.now is infrastructure: it scans repositories, normalizes literals, and emits the locale bundles your process already versions in Git. Runtime libraries such as i18next, next-intl, or react-intl answer how browsers and servers load, pluralize, and swap messages at request time. The two layers stack cleanly—configure the runtime once, let globalize.now continue extracting and syncing on every Git push so collaborators always edit structured locale data instead of fragile JSX. See how globalize.now handles idioms, plurals, and RTL →

Yes. Connect Claude Code to your GitHub repo, run the globalize skills once to set up i18n and extract your strings, then let globalize auto-translate on every push. After that, keep building in Lovable as normal — your translations stay in sync automatically. Lovable handles the UI, globalize handles the languages.

In your repo. globalize.now generates locale files and commits them to your GitHub or GitLab branch like any other code change. The translation process runs on our end, but the output lands in your codebase and stays there. You own the files.

For best results, run the i18n step with Claude Opus. It handles complex codebases and edge cases better than lighter models. The skills work with any Claude model, but Opus gives you the cleanest extraction and key generation.

Yes. Open a new branch locally before you start. The agent will make changes to your codebase and you want those isolated from main until you have reviewed them.

Yes. Make sure your branch is pushed to GitHub or GitLab and up to date before connecting to globalize.now. If the remote is behind your local, the agent will not see your latest code and the extraction will be incomplete.

Guided mode walks you through each step and lets you confirm decisions along the way. It is built for developers who want visibility and control over what the agent does. Unguided mode runs the full process automatically using best-practice defaults. No decisions required. If you want to plug in and get a working i18n setup without touching the details, start with unguided.

If npx skills add globalize-now/globalize-skills fails (for example on Windows), you can download the skills folder as a zip directly from our website. Extract it and place it in your project's .claude/skills directory, then continue with setup as normal.

Ready to make your app multilingual?

Make my app multilingual

Make your app multilingual in minutes