Make your app multilingual in minutes

Prompt your coding agent to discover globalize.now, then run npx 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 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 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 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.

Localization infrastructure is the automation layer that turns a codebase full of hardcoded UI copy into translation-ready structure: it finds user-visible strings, proposes stable identifiers, writes locale JSON, and keeps catalogs aligned whenever your team pushes code. globalize.now is that class of tooling aimed at AI-generated repositories—you bootstrap it with npx globalize-skills at the project root, then rely on Git push–driven sync so new literals do not silently pile up while engineers stay focused on shipping features.

Internationalization (i18n) is the engineering work of making UI text addressable: extracting literals, assigning translation keys, and wiring a runtime library that loads the right language per visitor. Localization (l10n) is supplying the translated phrases, tone, and regional formatting for each locale once those hooks exist. i18n must come first when JSX still embeds English. globalize.now automates the i18n slice for messy AI-built trees so the subsequent l10n work is mostly filling catalogs instead of hunting literals across components.

A translation key is a stable identifier such as checkout.submit_order that your i18n runtime resolves to the correct phrase for the active locale. Instead of leaving human copy inline, components call something like t("checkout.submit_order") while the strings live in JSON per language, which is how one UI serves many languages without forks. globalize.now generates and maintains those keys and locale files from existing hardcoded English so you are not hand-authoring every identifier.

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.