Localization · checked 2026-10-13

Can I vibecode Crowdin?

YES· one-shottable

For one developer, Crowdin's job is a table of source strings and their translations, machine translation for the gaps, a translation memory, a few QA checks and the files written back into the repo. An agent builds that in one sitting on SQLite with DeepL or an LLM. What stays behind is the people side: outside translators and volunteers working in a browser, proofreading and voting, plus hundreds of integrations and the in-context editor. If you need translators in the loop, self-hosting Weblate or Tolgee is the shorter road.

$59/moprice

$708you'd save a year

one sittingbuild time

—people replaced it

Before you start

What you need on hand.

DifficultyIntermediate · Some system setup or keys.

TimeOne to two hours for the first version

Claude Code, Codex or CursorAny of them can run the prompt.
Node.js 22better-sqlite3 compiles a native module, so build tools must be installed.
A DeepL or LLM API keyOnly for filling empty cells; the editor works without one.
Your Crowdin exportsThe translations ZIP, a TMX of the translation memory and the glossary.

Before you buildCheck Crowdin Free first: one private project with 60,000 hosted words and Crowdin AI costs nothing if you translate alone. It stops being enough once outside translators need into a private project.

1. Install one agent: Claude Code, Codex, Cursor.
2. Make an empty folder and open it in the agent.
3. Paste the prompt below, press enter, and answer its questions as it builds.

The prompt

Build me a local translation workbench to replace Crowdin for my app's string files. Requirements:

- Node.js 22 + TypeScript: a Fastify server and a React UI built with Vite.
`npm start` serves everything on http://localhost:4700.
- Source of truth stays in my repo: LOCALES_DIR in .env points at a folder with en.json
and one file per target language. Also read nested YAML (`yaml`) and gettext .po
(`gettext-parser`), and write every file back in its original format and key order.
- Storage: better-sqlite3 in ./data/workbench.db for strings, edit history, a translation
memory (every approved source/target pair) and a glossary of terms per language.
- Editor: one row per key with the source text and a column per language; filters for
missing, outdated (source changed since approval) and failing QA; edit and approve inline.
- Fill gaps with DeepL (`deepl-node`) when DEEPL_API_KEY is set, otherwise any
OpenAI-compatible endpoint from .env. Show translation-memory matches (exact, then fuzzy
at 75% or more) before calling an API, and send glossary terms with every request.
- QA before export: placeholders ({name}, %s, {{count}}) and HTML tags must match the source,
ICU plurals must parse (`@messageformat/parser`), no leading or trailing space changes.
- XLIFF 1.2 export and import per language, so a hired translator can use their own CAT tool.
- Single user. No accounts, no telemetry, local-first: only machine-translation calls leave
the machine, and the README must say exactly what is sent.
- Out of scope: translator logins, comments and voting, Git host integrations, OTA delivery.
- README: setup, the .env keys, where the data lives and how to back it up.

Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.

Share on X

Max MiskowSponsoredAI agents, automations and MVPs, built for your company.Visit site ›

Then keep going

Next prompts, same folder.

The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Crowdin.

Add a Crowdin importer to the translation workbench in this folder. Requirements:

- A command `workbench import-crowdin` that takes three paths: the ZIP from
  Translations > Download as ZIP, a TMX file exported from Translation Memories,
  and a TBX or CSV glossary export.
- Unpack the ZIP (one folder per language code), match files to LOCALES_DIR by name,
  and print a summary of new, changed and identical strings before writing anything.
- Load every TMX unit into the translation memory with its languages; load glossary
  terms with their language and notes. Skip duplicates so running it twice is safe.
- Mark imported translations as approved, and list files it could not map.
- Update the README with the three Crowdin export steps.

Add Git sync to the translation workbench in this folder. Requirements:

- A command `workbench sync` that runs `git pull` in the repo that holds LOCALES_DIR,
  re-reads the source file and marks changed keys as outdated in every language.
- After I approve translations, `workbench sync --push` writes the files, commits them on
  a branch named l10n/YYYY-MM-DD and opens a pull request with the GitHub CLI (`gh pr create`).
- Never commit to the default branch directly; abort if the working tree has unrelated changes.
- A dry-run flag that prints the diff instead of committing.
- Update the README with the gh login step and an example cron line.

Add guest translator links to the translation workbench in this folder. Requirements:

- From the UI, create a link for one language: a random 32-byte token stored hashed in SQLite,
  with an expiry date and a revoke button.
- The link opens the same editor limited to that language, without settings, export or
  machine-translation buttons. Every guest edit is saved as a suggestion I approve.
- Guest routes only listen on a second port (GUEST_PORT in .env) so I can expose just that
  through a tunnel; the main UI stays on localhost.
- Rate-limit guest requests per token and log every edit with the token id.
- Update the README with how to expose the guest port through Cloudflare Tunnel.

What you lose

A browser editor where outside translators and volunteers can work
Proofreading, voting and approval steps between people
Ready-made sync with GitHub, GitLab, Figma and hundreds of other apps
The in-context editor and over-the-air updates for mobile apps
The translation vendor marketplace and Crowdin's shared memory

Why people still pay

Teams pay because developers, translators and reviewers meet in one place: new strings arrive from the repo on their own, translators get context, memory and glossary in the browser, and finished languages go back as pull requests. Swapping that for files passed around by email feels like a step backwards once a few languages are live.

Moatcollaboration integrations switching costs

Do the math

Crowdin or your own copy?

Over

Your usage

Count my time3h ×$/h

Crowdin, 1 yr$708

Your own copy, 1 yr$35running + build session

You keep$673pays for itself in the first month

Estimate · Runs on your machine. Machine translation is the only running cost: DeepL's free API tier or a few cents of LLM tokens per thousand strings. The build is token usage on your agent plan.

Leaving Crowdin

Take your data, then cancel.

1 · Take your data out of Crowdin

1Translations: open the project, go to the Translations tab, expand Download as ZIP and click Build & Download. The ZIP has one folder per language code.
2Translation memory: open TM from your profile (or project Settings > Translation Memories), click View Records, then Download as TMX, XLSX or CSV.
3Glossary: open Glossaries, click View Records, then Download as TBX (v2 or v3), CSV or XLSX.
4String-based projects can't use the ZIP download; build target file bundles there instead.

2 · Cancel Crowdin

1Open Account Settings > Billing to see what your plan is using.
2To drop to Free, first remove managers (Free has no manager seats) and anything else above Free limits, then switch the plan to Free.
3Card subscriptions run through FastSpring: crowdin.onfastspring.com/account, with the email you bought with, shows the subscription and the next charge.
4If the downgrade stays blocked, email support@crowdin.com with your project URL.

Only the project owner and managers can download the translation memory and glossary, so export before you remove manager roles.
Annual card plans renew on their own; Crowdin emails two months and one month before, and FastSpring a day before the charge. Invoice-paid plans don't renew automatically.
Crowdin refunds on request if you cancel within 30 days of signing up.
The ZIP holds only the translated files: comments, screenshots and task history stay behind, so note what you need first.

Checked 2026-10-13 against Crowdin's docs: 1, 2, 3, 4, 5, 6, 7

The escape hatch

Don't feel like building it? These are already free.

WeblateOpen sourceGit-connected translation server with memory, glossary, checks and reviews; free hosting for libre projects.★ 6.1k · active Oct 2026 · docker to self-host
WebVisit ↗TolgeeOpen sourceTranslation platform with in-context editing in your running app; Apache-licensed core, some enterprise parts paid.★ 4.1k · active Oct 2026 · docker to self-host
WebVisit ↗PontoonOpen sourceMozilla's own translation platform for volunteer communities, built around version-control sync.★ 1.7k · active Oct 2026 · self-host, real ops
WebVisit ↗

All 5 free alternatives to Crowdin ›

The numbers

Crowdin pricing

Plan	Monthly	Annual, per month	What you get
Free	$0	$0	60K hosted words, 1 private project, unlimited public projects, 1 integration, 3 file formats, 1 branch.
Pro	$59	$50	60K hosted words, 2 private projects, 2 integrations, 5 file formats, 2 branches, unlimited translators; no manager seats.
Team	$179	$150	100K hosted words, 5 managers, unlimited private projects, 3 integrations, 15 file formats, in-context editor, webhooks.
Team+ (Crowdin Enterprise)	—	$450	500K hosted words, 5 managers, unlimited integrations, project groups, advanced workflows, data residency.
Business	custom	—	Custom hosted words, 10 managers, SSO, SCIM, teams, unlimited activity history.

Free tier: 60,000 hosted words, one private project, one integration, three file formats; outside translators only on public projects.
Billing: Monthly or annual for Pro and Team (annual is two months free); Crowdin Enterprise plans are annual only. Card subscriptions run through FastSpring and renew automatically; wire transfer only for annual plans. Prices exclude VAT and other taxes.
Hidden costs: Hosted words are source words times target languages, so every new language eats the quota (500 words in 10 languages count as 5,000). Extra hosted words and managers are paid add-ons. Machine and professional translation are prepaid through a Managed Balance. Over-the-air delivery is free up to 1M requests and 10 GB, then $3 per 1M requests and $2 per 10 GB.
Source: crowdin.com

Also on the list

Lokalise$169/mo · LocalizationYES

Airtable$24/mo · DatabasesYES

Carrd$1.58/mo · Website buildersYES

Questions

Crowdin, briefly

Not answered here? Tell us and we'll add it.

Ask a question ›

Free covers 60,000 hosted words, one private project and unlimited public ones, with Crowdin AI included.

Yes. An AI coding agent such as Claude Code, Codex or Cursor can build a usable personal version in one session with the prompt on this page, running on your own machine.

About $59 a month on the Pro plan, $708 a year (checked 2026-10-13).

A browser editor where outside translators and volunteers can work; Proofreading, voting and approval steps between people; Ready-made sync with GitHub, GitLab, Figma and hundreds of other apps; The in-context editor and over-the-air updates for mobile apps; The translation vendor marketplace and Crowdin's shared memory. If any of those matter to you, keep paying.