Free hosting

Host all your strings and translations for free. Bring them from any tool.

Import your source files and the translations you already have from Crowdin, Lokalise, Phrase or anything else. Glossa hosts unlimited strings, apps and languages at no cost, your own agent audits them for free over MCP, and you pay only when Claude translates something new.

Unlimited hosting, free

Every string, app, language and translation you have, for as long as you keep them. No hosted-word meter and no storage tier to outgrow.

Import your current translations

Push the files you already have in any of 12 formats, or one Glossa learns. Existing translations arrive as imported, and AI never overwrites them.

Audit them free with your agent

Your coding agent reads every translation over MCP or the CLI with the code that uses it, and corrects what is wrong. No AI words are counted.

Leave whenever you want

Pull every language back in its original format at any time. Your files stay in your repository; there is nothing to unlock and no export fee.

One prompt moves you over

Run one of these in your repository. Your agent installs the plugin or the CLI, exports from your current tool, imports every file in agent mode so nothing is billed, then audits and fills the gaps itself.

Claude Code

claude "$(curl -fsSL https://getglossa.dev/switch/any/prompt.txt)"

Codex

codex "$(curl -fsSL https://getglossa.dev/switch/any/prompt.txt)"

Or paste this prompt into any agent

Move our app's strings and existing translations from our current localization tool to Glossa (https://getglossa.dev), then audit them. Hosting, imports, exports and audits are free on Glossa; keep this move free by using agent mode, so nothing is machine-translated or billed.
1. Set up Glossa. In Claude Code run `/plugin marketplace add MeterApp/glossa-plugins` then `/plugin install glossa@glossa`; in Codex run `codex plugin marketplace add MeterApp/glossa-plugins && codex plugin add glossa@glossa`. That adds the Glossa MCP server and skills; sign in through the browser when asked. Without a plugin, use the CLI: `npx @meterapp/glossa login` opens my browser to sign in, and `npx @meterapp/glossa ops` lists every operation.2. Get the newest translations. If our localization tool holds translations that are not committed here yet, export every language from it first with its CLI or its download option, in a format Glossa reads (JSON, YAML, XLIFF, PO, Android XML, .strings, .xcstrings, ARB, .properties, RESX or CSV). Ask me for access if you need it; never commit or print API tokens.3. Find every translation file in this repository: the source language and every target language. List them with their locales and ask me only if the source language is unclear.4. Create one Glossa project per app with agent mode and its target languages, e.g. `npx @meterapp/glossa create_project --json '{"name":"Web","slug":"web","target_locales":["es","fr"],"translation_mode":"agent"}'`. Agent mode leaves missing strings for you instead of translating them with AI.5. Push each source-language file first, then every target-language file: `npx @meterapp/glossa push locales/en.json --project web`, then `npx @meterapp/glossa push locales/es.json --project web` (add `--locale` when the path does not name it). Existing translations are stored as imported, and AI never overwrites them.6. Check the import: `npx @meterapp/glossa pull --project web --out glossa-preview`, then diff glossa-preview against our files. Report every key, placeholder or plural that differs.7. Audit every target language for free with the codebase in view: page through `list_translations_for_audit` (MCP tool, or `npx @meterapp/glossa list_translations_for_audit --locale es --project web`), read the call sites in this repo, and correct wrong translations with `submit_translations`. Start with the flagged ones (placeholder_mismatch, glossary_miss, same_as_source).8. Fill the gaps yourself: `npx @meterapp/glossa missing --project web --locale es --out missing.json` lists untranslated strings with their file paths, glossary and rules; translate them and write them back with `npx @meterapp/glossa fill translations.json`.9. Save a .glossa.json with the project and source files so `npx @meterapp/glossa pull` and `npx @meterapp/glossa check` work from now on. Then summarize: files imported, translations per language, issues fixed and strings still missing. Leave our current localization tool's configuration and CI in place until I confirm the switch.

Pick the tool you are leaving

Each guide has that tool's export command, the prompt with it filled in, and what it charges for next to what is free here.

Switch from Crowdin

Priced by hosted words: source words × target languages.

Switch from Lokalise

Plans list hosted words, processed words and seats.

Switch from Phrase

Priced by Strings seats and managed words.

Switch from Transifex

Priced by AI-translated words; price on request.

Switch from POEditor

Priced by strings: terms plus translations.

Switch from Weblate

Hosted plans priced by hosted strings.

Switch from Tolgee

Priced by hosted words plus MT credits.

Switch from Localazy

Priced by source keys; languages unlimited.

Switch from Lingo.dev

A platform fee plus usage in tokens.

Switch from SimpleLocalize

Priced by translation keys, members and characters.

All of them in one table: Glossa compared with every alternative.

What is free and what is not

Free on every plan

Including Free, with no card.

Hosting unlimited strings, apps and languages, for as long as you keep them
Importing your existing translations from any tool, in any format
Exporting every language in its original format, any time
Audits, by your own agent over MCP or the CLI, or by run_audit
Translations your agent or your team writes, for your whole library
Strings shared across apps, translated once and reused

What you pay for

Only the words Claude translates for you.

When a project is in ai mode, Claude translates new strings with your glossary and rules. That is metered in source words × languages, once per string and language. Free includes 20,000 words a month; Cloud is $49 a month for 200,000.

In agent mode your own agent translates with list_missing_translations and submit_translations, and nothing is counted, even for your whole library. Pricing

Bring your strings over

Start free: import every file and translation you have, audit them with your agent and leave whenever you like.

Start for free Read the quickstart