globalize.now

Make your app multilingual

Set it up once. Translations land on every push.

Make my app multilingual

€5 free credit · no card · 30-minute setup

wanderstay · main
49s

Done — 10 strings, 3 languages

49s

Done — 10 strings, 3 languages

messages/de.json · messages/es.json · messages/fr.json

A real run, recorded — August 2026. Total: 49s.

4.8 on G2Built by Lokalise alumni

WHAT MAKES US DIFFERENT

Where developers actually work.

Most localization tools live outside your workflow. We live inside it — connect your repo once and every push gets translated.

Connect

Your repo, not a dashboard.

Pick your GitHub or GitLab repo in the app — that's the whole setup. Prefer your editor? Drive it from Claude Code, Cursor, or Codex.

Prepare

Your codebase, as it is.

We scan, do the i18n groundwork, and translate. Already on next-intl, i18next, or @lingui? We skip setup and go straight to sync.

Ship

Your Git workflow, every push.

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

Works with Next.js · React · Vite · Cursor · Lovable · Claude Code · Codex · GitHub · GitLab

PRICING

Start free. Then pay for the characters you translate.

No per-seat charges, no per-language charges, no surprises. Top up when you grow.

Billed by the characters we translate, shown to you in plain English. Before any translation runs, we show you the exact math for your codebase.

“Because it's painful stuff.”

Tomas Franc · ex-Lokalise Lead Solutions Architect · ★ 5.0 on G2

“Works in the background on every commit, with great results!”

Charlie Day · Co-founder, Pretty Prompt · ★ 4.5 on G2
EARLY ACCESS

What's included

PER WORKSPACE

€5 translation credit on signup, no card required.

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

Start free →
  • Pay only for the characters you translate
  • Unlimited languages incl. — 50+ on day one
  • CLI, API & GitHub sync
  • Context-aware AI glossary
  • Priority support during early access

See full pricing →

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

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.
Sign up at globalize.now, create a project, and connect your GitHub or GitLab repo. That is the whole setup. We scan the codebase, and if it has no translation wiring yet we offer to prepare it for multilingual support — the i18n groundwork — in one click. Conversion and translation then run on their own, and everything is pushed to your repo for you to review. After that, every push gets translated.
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 keep translations in sync on every Git push so collaborators always edit structured locale data instead of fragile JSX. See how globalize.now handles idioms, plurals, and RTL →
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.
Billing counts translated characters — the rendered text we generate across your target languages, not source-code bytes. What each plan includes in its base fee, and the rate beyond it, differ per plan and are set out in full on the pricing page. Either way you are billed on output you can see, not on repository size or seats.
Yes. Add the lovable-i18n skill to your Lovable workspace, then prompt Lovable: Set up i18n for my project using the lovable-i18n skill. It detects your stack, installs Lingui, scaffolds PO catalogs, and wraps your strings. Connect the repo to globalize.now and every push opens a translation PR — keep building in Lovable as normal. See the full Lovable setup guide →

Got questions? Browse the docs →

Ready to make your app multilingual?

Make my app multilingual

€5 free credit · no card · 30-minute setup