globalize.now makes your app multilingual in three steps — and keeps it that way on every push.
Already have i18n set up? The scan detects locale files and an i18n library, skips the preparation, and connects your existing setup to auto-translate on push. See "I already have i18n. What does globalize.now do?"
Free to start. You get a €5 translation credit when you sign up — enough to translate a small-to-medium app across multiple languages before you need to add billing.
Step 1 — Sign up and create a project
Click Start free at globalize.now, then create a project in the app.
Step 2 — Connect your repo
Connect GitHub or GitLab and pick the repo. globalize.now scans the codebase and figures out where it stands: not internationalized yet, or already set up. That scan decides the path — you don't configure anything.
Step 3 — Preparation, translation, and push — all automatic
If the codebase needs it, globalize.now prepares it for multilingual support: extracts hardcoded strings into translation keys, sets up the right i18n library for your stack, and builds the language files. Translations run automatically right after, and everything is pushed to your repo for review.
Small projects finish in a few minutes; large codebases can take an hour or more — leave the page open and grab a coffee while globalize does the work.
From then on, every push that adds new text gets translated and delivered back as a pull request. You review and merge. No other manual steps, ever.
See the whole thing in 2 minutes: the getting-started video.
What you get at the end
-
All UI strings extracted and translated into your chosen languages
-
Locale files committed to your repo (you own the files, no vendor lock-in)
-
A language switcher in your app
-
Automatic translation on every push
-
The globalize skills installed for your coding agent, ready if you ever want to drive things from Claude Code or Cursor
Prefer working from your coding agent?
The same result is available from inside Claude Code, Cursor, or Codex using our skills and MCP server — the agent prepares your codebase locally and connects the repo from your editor. Start with "App, MCP, CLI, or skills — which one do I need?".