Do I need to leave the Lovable editor?

No. Setup happens entirely through a Lovable skill and the Globalize.now web dashboard. No CLI, no local environment.

I don't see a Skills page in Lovable

Skills are managed by workspace owners or admins. Ask your workspace owner to add lovable-i18n once. Every project in the workspace inherits it.

Will it break my live Lovable preview?

No. The default locale stays English and locale files live in your repo. Your preview keeps working while translations populate.

What if I keep editing in Lovable after setup?

Every push from Lovable to GitHub triggers Globalize.now to open a translation PR. Merge it and the new strings ship translated.

What library does it use?

Lingui v6. One PO catalog per locale at src/locales/{locale}/messages.po, compiled at build time by @lingui/vite-plugin. Works on both Lovable stacks: Vite SPA and TanStack Start (SSR).

I already have react-i18next / next-intl in my project

The skill stops and asks before doing anything. It will not silently migrate. Either keep your existing library (in which case this skill doesn't apply) or remove it first, then re-run the skill so it can set up Lingui cleanly.

Globalize.now charges a small workspace fee plus per-translated-character usage. New accounts get €5 of free credit on signup.

The skill import URL fails. What now?

Lovable's Import from GitHub for skills is currently broken (a Lovable bug). Use the zip instead: download lovable-i18n.zip from https://globalize.now/lovable-i18n.zip and upload it via Settings → Skills → Add → Upload a ZIP. Or paste the SKILL.md manually.

Community setup guide · powered by the lovable-i18n skill

Make your Lovable app multilingual in minutes

Add the lovable-i18n skill and the globalize MCP, all inside Lovable. Translations land on every push. No CLIs, no leaving the editor.

Get started Read the FAQ

Works insideLovableGitHubglobalize.now

Powering localization for

Pretty PromptNextKSRajaride

What is this guide?

A three-part workflow that lives entirely inside Lovable and GitHub.

Add the skill

Install lovable-i18n once on your Lovable workspace. Every project gets it.

Lovable wires up Lingui

Detects your stack (Vite SPA or TanStack Start), adds Lingui v6, wraps your strings in <Trans> macros, and scaffolds a PO catalog per locale.

Stay translated on every push

A GitHub Action extracts new strings into the catalogs. Globalize.now opens a translation PR. Merge and ship.

Built for your stack

Next.jsReactViteTanStack StartLovableCursorClaude CodeCodexVS CodeGitHubGitLab

Before you start

Prerequisites

Three quick checks. Two minutes total.

Lovable project connected to GitHub
Open the + menu in chat → GitHub → Connect project.
A globalize.now account
Free signup with €5 credit, no card required.
Workspace owner or admin in Lovable
Required to add a skill once for the whole workspace.

Setup

Five steps from English-only to 50+ languages

1
Connect your Lovable project to GitHub
In the Lovable editor, open the + menu in the chat input → GitHub → Connect project. Authorize the Lovable GitHub App, pick the org, and create the repository.
Skip if your project is already connected. You can verify under the + menu → GitHub.
2
Add the lovable-i18n skill by uploading the zip
The skill teaches Lovable exactly how to internationalize your project the way Globalize.now expects.
Open Skills in your Lovable workspace settings, click Add, and upload the lovable-i18n.zip.
Download the skillDownload
https://globalize.now/lovable-i18n.zip
You only do this once per workspace. Every project in that workspace can now use the skill.
Lovable's Import from GitHub for skills is temporarily broken, so upload the zip for now.
Can't upload a zip? Paste the skill manually.
Open the lovable-i18n SKILL.md, copy its contents, then in Lovable go to Settings → Skills → Add → Create new skill and paste it in.
New to Lovable skills? Read the Lovable Skills docs.
3
Add the globalize MCP
Connect Globalize.now as a custom MCP inside Lovable.
In Lovable, open Connectors → Custom MCP and add the globalize MCP. Authenticate with an API key you create in the MCP tab of your globalize.now dashboard.
MCP URL
https://api.globalize.now/mcp
4
Ask Lovable to set it up
Open any project in the workspace and paste this into the Lovable chat:
Lovable prompt
Use the lovable-i18n skill and the globalize MCP to set up i18n and translate my app.
Lovable will detect your stack (Vite SPA or TanStack Start), then ask one short question: source language, target languages, whether to put the locale in the URL, and whether to add the GitHub Action. Reply go to accept all defaults.
It then installs @lingui/core, @lingui/react and the Vite plugin, wires the provider, scaffolds one PO catalog per locale, wraps every hardcoded UI string in Lingui macros, and drops a language switcher in. The MCP connects your repo and translates on every push.
5
Review, merge, and keep building
Lovable syncs to GitHub automatically. Review the diff in the Lovable code view or directly on GitHub, then merge to your default branch.
That's the loop. Every push triggers Globalize.now → translation PR → merge → translated app ships. Nothing else to do.

The loop

How a single push becomes 50+ languages

Runs automatically after the one-time setup. Nothing else to wire up.

Edit in Lovable

Push to GitHub

Action extracts strings

globalize.now

Translation PR

Merge

Multilingual app

You edit in Lovable. Lovable pushes to GitHub. Globalize.now opens a translation PR. You merge. Your preview is multilingual.

What makes us different

Where developers actually work

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

Inside your AI agent

Installs as a Lovable skill. The agent does the work. We just give it the playbook. No separate dashboard. You connect the skill and the MCP once, then prompt.

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 Lingui, next-intl, or react-i18next, the skill stops and asks before changing anything.

50+ languages, RTL included

Pick any combination in the Globalize.now dashboard.

EnglishSpanishFrenchGermanItalianPortugueseDutchPolishSwedishNorwegianDanishFinnishCzechSlovakHungarianRomanianGreekTurkishRussianUkrainianBulgarianSerbianCroatianSlovenianEstonianLatvianLithuanianJapaneseKoreanChinese (Simplified)Chinese (Traditional)VietnameseThaiIndonesianMalayFilipinoHindiBengaliTamilTeluguMarathiGujaratiPunjabiArabicRTLHebrewRTLPersianRTLUrduRTLSwahiliAfrikaansZuluCatalanBasque

From the field

What early users are saying

Real React apps. Real i18n debt. What early builders tell us.

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.

Charlie Day

Co-founder · Pretty Prompt

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

Tomas Franc

Founder · NextKS · ex-Lokalise Lead Solutions Architect

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

Verified user

Leisure, Travel & Tourism · Small business

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.

Early access

€20/month

Per workspace · over 4M 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 including RTL
CLI, API & GitHub sync
Context-aware AI glossary
Priority support during early access

FAQ

Lovable-specific questions

Ready to ship your Lovable app in 50+ languages?

Add the skill once. Translations follow forever.

Create a globalize.now account View the skill on GitHub