Software Localization

Localize software at the speed of your commits

Connect a repository once and WordBeam keeps strings, branches and releases in sync. Engineers never export a file by hand, and translators never touch a line of code.

 

Get Started See pricing


Two-way repo sync  ✓ 16+ formats  ✓ 100+ languages

Image
16+
file formats
< 30s
commit to editor
0
keys ever broken
98%
less manual export
Dev-first

Built into your pipeline, not bolted on

CLI & REST API

Trigger pushes, pulls and status checks from CI with one command.

Two-way sync

New keys flow in on every commit; confirmed translations return as a clean pull request.

Branch processing

Each feature branch gets its own scope and merges back automatically when it ships.

Placeholder & ICU protection

Variables, ICU plurals and HTML tags are locked as non-editable tokens, a translator physically cannot break a build.

Every resource format

DOCX, XLSX, XLIFF, JSON, IDML, PO, SRT and more parsed natively, with new formats always in development.

Pipeline

From commit to translated release

1

Connect your repo

Authorise GitHub, GitLab or Bitbucket (coming soon) and point WordBeam at your resource files.

2

Translate in context

Strings arrive with screenshots and developer comments; TM and QA run as you type.

3

Ship every language

Confirmed translations return as a PR on the same branch, ready to merge and deploy.

Formats

CSV DOCX DOCX bilingual XLSX IDML JSON MQXLIFF MXLIFF PO PPTX SCC SDLXLIFF SRT TSV TXT XLIFF

Functionals

AI translate (GPT, Claude, Grok, DeepL) Auto tag placement with AI Translation memory Term base QA check + AI proofread
Why teams switch

Continuous beats batch

String files over email

  • Engineers export and re-import by hand
  • Placeholders break silently in the build
  • Each release starts translation from zero
  • No idea which strings actually changed

WordBeam repo sync

  • Strings sync automatically on every commit
  • Tokens are locked and validated
  • TM fills repeats so releases get faster
  • Only changed strings are queued
How it works

From source to shipped in four steps

1

Push your resource files

JSON, XLIFF, PO, IDML and more formats parse automatically, with new ones always in development.

2

Strings route to translators

New and changed keys are detected on every commit.

3

QA runs on every keystroke

Placeholders, variables and HTML are validated inline.

4

Pull localized files back

Merge translated bundles straight into your branch.

FAQ

Questions, answered

Which file formats are supported?

CSV, DOCX, DOCX bilingual, XLSX, IDML, JSON, MQXLIFF, MXLIFF, PO, PPTX, SCC, SDLXLIFF, SRT, TSV, TXT and XLIFF, with new formats always in development. Structure and comments are preserved on round-trip.

Will it break my variables or placeholders?

No. Interpolation tokens, ICU plurals and HTML tags are locked and validated, so a translator cannot accidentally remove or reorder them.

Can I automate this in CI?

Yes. The CLI and REST API let you push source strings and pull translations as a build step, with branch-aware syncing.

How does it handle new strings between releases?

Each commit is diffed against the last sync, so only new or changed keys are sent for translation, and untouched strings stay frozen.

See WordBeam in action

Translate faster, keep more of every word