# globalize.now

## Key facts
globalize.now is AI-powered localization infrastructure that converts your codebase once — hardcoded UI strings become translation keys and locale files — then keeps translations in sync on every Git push. Setup is in-app: sign up, connect your GitHub or GitLab repo, approve the conversion (about 30 minutes, measured). Coding agents get a post-setup role via skills (`npx skills add globalize-now/globalize-skills`) and MCP. The team ships from the Lokalise alumni network (see /about); site copyright is dated 2026. Differentiators: one-connect in-app setup, Git-backed sync, agent skills + MCP, context-aware AI translation, 50+ locales with RTL, and integrations for Next.js, React, Vue, Vite, React Router, and CI/CD.

Longer path and page index: https://globalize.now/llms-full.txt

## What it does
- Converts a codebase once, in-app: hardcoded UI strings become translation keys and locale files, delivered as a PR you review
- Translates new strings on every Git push after that (GitHub or GitLab)
- Gives coding agents a post-setup role: skills keep new UI text keyed, MCP drives projects and sync
- Available in Claude's connectors directory (https://claude.ai/directory/globalize-now): from any Claude chat, translate locale files, add languages, manage glossaries and style guides, and connect a GitHub repo — OAuth sign-in, no API key
- Supports 50+ languages including RTL (Arabic, Hebrew)
- Works with Next.js, React, Vue, Vite

## Who it's for
- Solo developers and indie hackers using AI coding tools
- Vibe coders who built fast and now need to go multilingual
- Teams who want localization without manual work

## Key pages
- https://globalize.now/en/ — Homepage: product overview, demo, features, supported languages, pricing, and FAQ for AI-generated apps.
- https://globalize.now/en/install/ — Get-started guide: the in-app setup (connect your repo, approve the conversion, ~30 minutes) plus the agent path for post-setup sync.
- https://globalize.now/en/pricing/ — Pricing page: Trial (14 days, €5 credit), Indie (€5/mo), Starter (€20/mo) and Team (€249/mo) plans, all priced per workspace, with competitor price comparison, billing explainer, cost calculator, and pricing FAQ.
- https://globalize.now/en/developers/ — Developer integration reference for Cursor, Claude Code, Codex, Copilot, and other AI coding tools, plus the MCP server (https://api.globalize.now/mcp) and the Claude connector.
- https://globalize.now/en/vibe-coders/ — Guide for non-technical builders who need multilingual apps without hand-writing i18n code.
- https://globalize.now/en/integrations/ — Index of integration guides (Cursor, Claude Code, Next.js, Lovable) with HowTo, FAQPage, WebPage, and ItemList schema.
- https://globalize.now/en/integrations/cursor/ — Using globalize.now with Cursor: extract hardcoded UI strings, generate keys and locale files, sync on Git push.
- https://globalize.now/en/integrations/claude-code/ — Using globalize.now with Claude Code: agentic workflow with npx skills add globalize-now/globalize-skills and Git-backed locale sync.
- https://globalize.now/en/integrations/next-js/ — Using globalize.now with Next.js: prepare keys and locale files for next-intl or other runtimes before runtime wiring.
- https://globalize.now/en/integrations/lovable/ — Using globalize.now with Lovable: lovable-i18n skill, Lingui PO catalogs, and Git-push translation sync for multilingual Lovable apps.
- https://globalize.now/en/compare/ — Index of structured product comparisons (Lokalise, Crowdin, i18next, lingo.dev) with FAQPage and WebPage schema.
- https://globalize.now/en/compare/lokalise/ — globalize.now vs Lokalise: TMS vs localization infrastructure for AI-generated codebases.
- https://globalize.now/en/compare/crowdin/ — globalize.now vs Crowdin: community TMS vs automated extraction and Git sync.
- https://globalize.now/en/compare/i18next/ — globalize.now vs i18next: infrastructure vs runtime library (complementary stack).
- https://globalize.now/en/compare/lingo-dev/ — globalize.now vs lingo.dev: repo-side i18n structure vs translation API engine.
- https://globalize.now/en/compare/phrase/ — globalize.now vs Phrase Strings: key-based string management with seat-capped plans vs Git-committed catalogs priced per character.
- https://globalize.now/en/compare/locize/ — globalize.now vs locize: the i18next team's hosted CDN backend vs the same catalogs committed into your own repository.
- https://globalize.now/en/blog/ — Blog index with articles on AI localization, i18n automation, and vibe-coding internationalization.
- https://globalize.now/en/blog/globalize-nimdzi-language-technology-radar/ — Nimdzi vetted globalize and listed it on its Language Technology Radar under localization for developers and localization-specific LLM tools; what the Radar is (1,100+ products, 756 companies, 11 categories), how vetting works, and why code-native localization is its own category.
- https://globalize.now/en/blog/crowdin-i18n-agent-skill-vs-globalize-now/ — Crowdin's i18n-setup agent skill compared with globalize.now, dated from commit history: Crowdin's seven phases delegate code changes to Lingui's skills, end in a Crowdin project and leave translation off by default; globalize.now runs i18n conversion and translation as one job and delivers a pull request. Timeline: lingui/skills Jan 2026, crowdin/skills Feb 2026, globalize-skills 29 Mar 2026, Crowdin i18n-setup 28 Aug 2026.
- https://globalize.now/en/blog/localize-bolt-app-without-a-dashboard/ — How to localize a Bolt.new app without a dashboard: push the Vite and React project to GitHub, keep translation catalogs as committed files, and let globalize.now convert once and translate new catalog units on push.
- https://globalize.now/en/blog/make-replit-app-multilingual/ — How to make a Replit app multilingual without a dashboard: connect the repository that Agent checkpoints already create, keep catalogs in Git, cover the Express server's strings, and pull translated pull requests back into Replit.
- https://globalize.now/en/blog/nextjs-16-i18n-middleware-to-proxy/ — Next.js 16 renamed the middleware file convention to proxy and next-intl moved locale reading to next/root-params; what to change in AI-generated App Router i18n, and why the locale files are unaffected.
- https://globalize.now/en/blog/lovable-i18n-skill/ — How to import the lovable-i18n skill into a Lovable workspace, which MCP connection it needs, and why it commits Lingui catalogs to your repository instead of running a translation widget.
- https://globalize.now/en/blog/localize-base44-app-without-a-dashboard/ — How to make a Base44 app multilingual using its two-way GitHub sync: catalogs as committed files, a merge to main as the delivery step, and why entity content needs its own language field.
- https://globalize.now/en/blog/globalize-now-claude-connector/ — globalize.now is live in Claude's connectors directory (24 Sep 2026): how to add it with an OAuth sign-in, eight things to ask it (translate files, add languages, glossary, per-language style guides, connect a GitHub repo, Markdown/HTML content, mobile string files), and what it does not do.
- https://globalize.now/en/blog/localization-growth-playbook-then-and-now/ — What localizing a product actually earned, using the one well-documented case: Smallpdf's reported 60% rise in monthly search users across 17 languages, what the 2017 translation loop cost to run, who is running the same play in the localization category today, and what the work takes now.
- https://globalize.now/en/blog/growth-tactics-one-founder-can-finish/ — A sorting test for growth tactics: does the work end, or does it become a standing job? Uses OneSky's Smallpdf case study for the team-shaped version of localization, a solo developer's published GA4 numbers across four languages for the version one person finished, and Localazy's roughly 14,000-page matrix as the tactic that stayed team-shaped.
- https://globalize.now/en/blog/agents-md-i18n-rules/ — The ten i18n rules to put in AGENTS.md, .cursor/rules, CLAUDE.md or Copilot instruction files so a coding agent stops hardcoding strings, where each tool reads them, why inline completions never do, and what enforces the rule when the file cannot.
- https://globalize.now/en/blog/lovable-knowledge-i18n-rules/ — Which of Lovable's three instruction surfaces to put i18n rules in, why knowledge dilutes in long chats while a root AGENTS.md does not, and what the lovable-i18n skill writes there.
- https://globalize.now/en/blog/globalize-now-lovable-select-partner/ — Announcement: globalize.now became an official Lovable Select Partner on 6 October 2026; what the status means, how a Lovable app is made multilingual with one skill, one connector and one prompt, and the RajaRide result (3 to 24 languages).
- https://globalize.now/en/blog/keep-ui-copy-consistent-across-codebase/ — How to keep UI copy consistent across a codebase: keep every user-visible string in one catalog in the repo, reference by key, review copy changes as diffs, block new literals with a lint rule, and keep a one-screen style-guide file that people and AI coding agents both read.
- https://globalize.now/en/blog/localization-roi-without-enterprise-budget/ — How to judge localization ROI when there is no budget to model: why the agency forecast has no denominator at one-person scale, what the return looked like when a team paid for it (OneSky's Smallpdf case study), how uneven it is when nobody funds it (a solo developer's published GA4 figures across four languages, one of which returned 7 pageviews), what the cost actually is (a second solo site cut twenty-one languages to six on quality, not traffic), and the two-locale, reversible test to run instead.
- https://globalize.now/en/blog/added-japanese-brazilian-portuguese-31-euros/ — First-party receipt: adding Japanese and Brazilian Portuguese to the whole globalize.now website, 1,782 interface strings and 61 blog posts (about 130,000 source words), translated in one job (8 minutes of translation, 27 of automated QA, 72 minor flags) for about €31, plus the Next.js routing work behind it (pt-BR served at /pt-br/) and what is still unreviewed.
- https://globalize.now/en/blog/translation-files-out-of-sync/ — Why locale files drift apart: missing and orphaned keys, merge conflicts in generated data, and review latency are routing failures rather than translation failures, and generating keys where the code is written removes the round-trip.
- https://globalize.now/en/blog/code-native-product-copy/ — Code-native product copy: what it is, what copy drift is, and why keeping UI text consistent and keeping it localization-ready are the same problem in a codebase.
- https://globalize.now/en/blog/what-is-copy-drift/ — Copy drift: user-visible text diverging from its approved source across surfaces and over time, with no single source of truth. What causes it, why nothing catches it, and how to prevent it in a codebase.
- https://globalize.now/en/blog/localize-v0-app-without-a-dashboard/ — How to localize a v0 app without a dashboard: v0 writes UI text directly into the Next.js components it generates, and the GitHub branch it already commits to is the hand-off point, so translation catalogs can live in the repository instead of behind a runtime widget.
- https://globalize.now/en/blog/github-copilot-i18n/ — How to add i18n to an app built with GitHub Copilot: custom instructions reach chat, agent mode and the coding agent but are not applied to inline autocomplete, which is why a repository with a clear i18n rule still accumulates hardcoded English, and what closes that gap.
- https://globalize.now/en/blog/stop-ai-agents-rewriting-ui-copy/ — How to stop AI coding agents rewriting your UI copy: why agents treat product copy as editable prose, why rule files only reduce the frequency, and how keying UI text into a source locale file turns a silent reword into a reviewable change.
- https://globalize.now/en/blog/next-intl-vs-react-i18next-vs-lingui/ — next-intl vs react-i18next vs Lingui in 2026: next-intl for the Next.js App Router, react-i18next for the largest ecosystem, Lingui for compile-time extraction and PO catalogs — and why all three still need a separate layer to produce keys and locale files.
- https://globalize.now/en/about/ — Team background and credibility for the globalize.now company.
- https://globalize.now/en/blog/we-ran-globalize-now-on-globalize-now/ — Dogfooding report: translation bugs found when globalize.now localized its own marketing site.
- https://globalize.now/en/blog/how-to-globalize-your-app/ — Five-prompt pipeline to go from hardcoded English to synced locale files and a language switcher.
- https://globalize.now/en/blog/why-globalize-your-app/ — ROI and timing case for globalizing English-first AI-built products before i18n debt compounds.
- https://globalize.now/en/blog/best-localization-tools-vibe-coding-2026/ — Layered map of localization tools for vibe-coded apps in 2026.
- https://globalize.now/en/blog/globalize-now-vs-lokalise-vs-crowdin/ — Comparison of globalize.now with Lokalise and Crowdin for AI-generated app localization.
- https://globalize.now/en/blog/how-to-localize-ai-generated-app/ — Step-by-step guide to localizing an app built with AI coding tools.
- https://globalize.now/en/blog/3-stages-of-localization-ai/ — Historical stages of localization and how AI shifts the third wave.
- https://globalize.now/en/blog/ai-code-broke-localization/ — Essay on why traditional TMS assumptions fail for AI-generated codebases.
- https://globalize.now/en/blog/make-lovable-app-multilingual/ — Durable Lovable multilingual setup: locale files, a real i18n library, and Git-push translation sync.
- https://globalize.now/en/blog/lovalingo-shutting-down-migration-guide/ — Lovalingo closes August 31, 2026: what breaks, the preservation export, clean removal steps, and migration to repo-owned Lingui PO catalogs (three months of usage free for migrators).
- https://globalize.now/en/blog/lovable-i18n-vs-lovalingo-vs-weglot/ — Three-way comparison for Lovable app localization: runtime widgets (Lovalingo, Weglot) versus committed locale catalogs.
- https://globalize.now/en/blog/weglot-alternative-for-lovable/ — Weglot alternative for Lovable apps: repo-committed Lingui PO catalogs versus a client-side translation widget.
- https://globalize.now/en/blog/lovable-tanstack-start-i18n/ — i18n for Lovable's TanStack Start SSR stack: server-rendered locale routes from committed catalogs.
- https://globalize.now/en/blog/lovable-app-translations-break-on-every-push/ — Why Lovable app translations break on every push, and the versioned-with-the-code fix.
- https://globalize.now/en/compare/lovalingo/ — globalize.now vs Lovalingo comparison (note: Lovalingo closes August 31, 2026 and has stopped new signups).
- https://globalize.now/en/blog/what-is-icu-messageformat/ — ICU MessageFormat explained: plurals, gender, and variables in one translatable string, and where it breaks in AI-generated apps.
- https://globalize.now/en/blog/what-is-software-localization/ — What software localization includes beyond translation, how it differs from internationalization, and avoiding i18n debt in AI-generated apps.
- https://globalize.now/en/blog/localize-claude-code-app/ — How to localize an app Claude Code generated without leaving the agent: skill install, i18n wiring, translations as PRs on every push.
- https://globalize.now/en/blog/seo-translation/ — SEO translation: adapting pages, keywords, and metadata so translated pages actually rank, plus the technical layer search engines require.
- https://globalize.now/en/blog/lovable-vite-i18n/ — Add i18n to a Lovable app on the classic Vite + React SPA stack with committed Lingui PO catalogs that sync on every push, no runtime widget.
- https://globalize.now/en/blog/lovable-language-switcher-hreflang/ — Give each Lovable locale its own crawlable URL, wire the switcher to navigate, and emit reciprocal hreflang so translated pages get indexed.
- https://globalize.now/en/blog/lovalingo-alternatives-after-shutdown/ — Lovalingo closes August 31, 2026: comparison of the realistic alternatives for Lovable apps, from committed catalogs you own to runtime widgets that rent your languages back.
- https://globalize.now/en/blog/cheapest-localization-tool-small-saas/ — Entry prices for thirteen localization tools verified on 7 August 2026, what each one meters, and what the billing unit does at 10,000 keys across 5 locales.
- https://globalize.now/en/blog/cheapest-way-to-localize-saas-2026/ — The zero-cash routes priced honestly: every hosted free tier and where it stops, self-hosted Tolgee, and what hand-extracting strings really costs.
- https://globalize.now/en/blog/lovalingo-export-translations/ — Lovalingo closes August 31, 2026: request your preservation export, convert the bundles into Lingui PO catalogs committed to your repo, and keep them synced on every push.
- https://globalize.now/en/blog/localize-database-content-lovable-app/ — Why a translated Lovable UI still renders English Supabase rows, the two Postgres patterns for localized database content, how to query them with fallback, and why a runtime widget is not a durable fix.
- https://globalize.now/en/blog/lovable-app-english-after-lovalingo-closes/ — What breaks in a Lovable app when Lovalingo closes on August 31, 2026: a DevTools outage simulation to run today, what no export can give back, and how to move translations into repo-committed catalogs first.
- https://globalize.now/en/blog/localization-moving-upstream-dev-loop/ — Positioning essay: the real shift in localization is position, not translation quality — out of the export-translate-import round-trip and into the dev loop, shipping as a localized pull request.
- https://globalize.now/en/blog/cursor-keeps-adding-hardcoded-strings/ — Why Cursor re-adds hardcoded strings after i18n setup, and the three-layer fix: AGENTS.md instruction, the no-literal-string ESLint rule in CI, and automated extraction and translation on every push.
- https://globalize.now/en/blog/does-localizing-your-app-help-seo/ — How localization affects SEO: Google assigns a page's language from its visible content, why non-English search is underserved, and the five steps that make translated pages rank.
- https://globalize.now/en/blog/lovable-app-rtl-arabic/ — Why a Lovable app translated into Arabic still renders left-to-right: set dir from the locale tag, swap physical Tailwind utilities for logical ones, and gate physical utilities in review so a regenerated component cannot reintroduce them.
- https://globalize.now/en/blog/localize-lovable-app-without-a-dashboard/ — How to keep a Lovable app's translation workflow entirely in the repository: committed locale catalogs, a strict compile step, and sync on every Git push, with no dashboard your coding agent cannot reach.
- https://globalize.now/en/blog/ai-localization/ — What AI localization means beyond machine translation: string extraction, key generation, locale files and continuous sync run by the coding agent, with translations arriving as pull requests.
- https://globalize.now/en/blog/website-localization/ — The seven steps to localize a website in dependency order, the four-layer tool stack, what it costs, and how a coding agent does the internationalization a localization team used to do.
- https://globalize.now/en/blog/why-localization-software-gets-expensive-as-you-scale/ — The three cost multipliers in legacy localization pricing: editor seats, hosted or processed words, and tier gates, with 2026 Lokalise and Crowdin figures and what a per-workspace usage model removes.
- https://globalize.now/en/blog/translate-lovable-app/ — The two ways to translate a Lovable app compared: a runtime widget that swaps text after the page paints, or Lingui PO catalogs committed to your repo and rendered server-side, and which one survives a vendor shutdown.
- https://globalize.now/en/blog/best-way-to-localize-a-lovable-app/ — Why committed Lingui PO catalogs beat a runtime translation widget for a Lovable app on speed, indexability and ownership, with the four-step setup and a side-by-side comparison.
- https://globalize.now/en/blog/localization-growth-cases-we-verified/ — The full evidence audit behind our localization growth posts: four published cases that survived a check, the status given to each (one vendor retelling, one of our own measurements of a third party, two first-party solo developers), the verification standard applied, the figures cut and why (undated, paywalled, or from a non-matching window), a case whose own numbers contradict its headline, a locale that returned 7 pageviews in 22 days, and the four questions to ask of the next localization claim you read.
- https://globalize.now/en/blog/one-prompt-translation-coding-agent-checks/ — Seven checks for an app a coding agent translated in one prompt: text overflow, plural forms, variables, terminology, tone, missing keys and drift, with a script that checks keys and variables.
- https://globalize.now/en/blog/lovable-github-sync-translation-prs/ — How Lovable's single-branch two-way GitHub sync, the lovable-sync parking branch and branch protection interact with a translation pull request, and when a PO catalog conflict can happen.
- https://globalize.now/en/blog/two-localization-growth-plays/ — The two growth plays that both get called localization, sorted by whose demand they harvest: a generated matrix of language pair pages (measured on one vendor at 757 conversion pages, 1,705 language pair pages and about 14,000 indexed URLs, with 4,859,220 of summed United States keyword volume on its detected top 500 terms) versus translating the product you already own (60% growth in monthly search users in the best documented vendor case, and 748 against 7 pageviews across four locales in a solo developer's own GA4 figures). Includes why the matrix play is unfinishable alone, how to read your own analytics to pick, and the recurring cost of proving locale quality.
- https://globalize.now/en/blog/nextjs-i18n-strings-outside-components/ — Where Next.js App Router strings escape t(): generateMetadata, Server Actions and Zod errors, not-found and error pages, share images, manifest, sitemap and route handlers, with the next-intl call for each.

## Pricing
Starter is €20/mo per workspace with unlimited projects and languages. Includes about 4,000,000 characters (roughly 600,000 words) per month, then token-based usage at the same per-character rate. No per-seat and no per-language charges. An Indie plan at €5/mo carries no included volume and bills all translation as usage. A Team plan at €249/mo is in early access and is booked through a demo rather than self-serve checkout. €5 signup credit, no card required. CLI, API, and GitHub sync included. 50+ languages including RTL. Lovalingo migrators (service closing August 31, 2026): first three months of usage free.

## How to get started
Sign up at https://app.globalize.now, connect your GitHub or GitLab repo, and approve the conversion — about 30 minutes to a multilingual app.
Already set up? Give your coding agent the skills: npx skills add globalize-now/globalize-skills
Then prompt your agent: "Connect globalize.now to my repo"

## Company
https://globalize.now/en/about/ — Team and background.

## Contact
sales@globalize.now
support@globalize.now

# Last updated: 2026-08-23