Translation management

Translations that keep up with your code

Manage your strings in Linguiqo, your team translates them, and the finished files go back to your repository as a commit or a pull request. When a source string changes, you see at once which translations need another look.

A sample workspace, ready in seconds. No email, no card, deleted after two hours.

  • €0for every extra team member
  • Every featurein every plan, Free included
  • 12 formatsfrom gettext to xcstrings
  • Data in the EUGoogle Cloud in Belgium
  • 14 days freeon your first paid plan

How it works

From Linguiqo straight into your repository

Connect GitHub, GitLab, Azure DevOps or any host that speaks plain git. Your strings live in Linguiqo, and the finished files reach the repository with one confirmation instead of a manual export.

1

You add strings in Linguiqo

Create a key in the app, paste a whole list or upload a file. Strings that turn up in the repository's files are picked up too: after a push through a webhook, or at the half-hourly check.

2

The team translates

Translators work in the editor with the glossary, the memory and the screenshots in front of them. Every string carries the context its developer wrote.

3

Translations go back

Linguiqo writes the files that changed, the source language included, as a commit or a pull request. You see the exact list first, and nothing is sent until you confirm.

Linguiqo is where your strings live, so nobody keeps the source language file up to date by hand: Linguiqo writes it along with the translations. A change that turns up directly in a file never overrides what you edited or removed in the app.

What you get

Everything the work actually needs

From the first string to the release, with no spreadsheets, no files sent back and forth and no guessing what is done.

An editor, not a grid

Keyboard-driven, with the right plural forms for every language and screenshots that show where each string appears.

Twelve quality checks

A translation with a missing placeholder or broken markup can't be approved.

Machine translation on your key

Your OpenAI or DeepL account.

Glossary and memory

OpenAI gets your glossary with every request, and a quality check flags translations that stray from it.

Your whole team, and your agency

Live presence, no collisions. Translators see only their languages.

API, CLI and webhooks

Automate it end to end.

Pricing

Your whole team, every feature, and AI at cost

You pay only for the size of your project: a slot is one string in one target language. Users, features and the Git connection cost nothing extra.

Free

€0 / month

  • 1,000 slots
  • 1 project
  • 2 team members

Medium

€49 / month

or €490 a year

  • 50,000 slots
  • Unlimited projects
  • Unlimited team members

Large

€99 / month

or €990 a year

  • 100,000 slots
  • Unlimited projects
  • Unlimited team members

Every team starts on the free plan. The first paid plan you choose is free for 14 days.

The same project, priced elsewhere

500 source terms translated into 2 languages – 1,000 translations

5,000 source terms translated into 2 languages – 10,000 translations

25,000 source terms translated into 2 languages – 50,000 translations

50,000 source terms translated into 2 languages – 100,000 translations

LinguiqoFreeSmallMediumLarge €0€9.90€49€99
Hosted Weblate10k10k160k160k €39€39€95€95
CrowdinFreeProTeamTeam+ €0€45€136€136+
POEditorStartPremiumEnterpriseEnterprise $17$136$221$221+
LokaliseExplorerExplorerExplorerExplorer $149$149$149$149

Prices per month from each vendor's public pricing page on 26 September 2026, at their cheapest published billing and the cheapest plan that holds this volume, before tax; seat, project and feature limits differ by vendor. Linguiqo is shown at plain monthly billing – billed yearly it drops to €8.25, €40.83 and €82.50. POEditor counts terms and translations together; Crowdin sells words, assumed here at two words per term; a plus sign means the vendor's largest listed plan is not enough.

Detailed comparison with each tool →

Frequently asked questions

Didn't find your answer? Write to us at hello@linguiqo.com.

What is a slot?

One term in one target language. A project with 500 terms and three target languages uses 1,500 slots. The source language does not count, and neither do archived terms.

What happens when a project outgrows its plan?

Adding strings and languages, and importing new ones, pause until there is room or the plan grows. Translating never stops, and nothing is deleted.

Do I need my own OpenAI or DeepL key?

Only for machine translation. It runs on your own key, so you pay the provider directly and we add nothing on top. Without a key everything else works, and no text is sent to any translation service.

Is there a free trial of the paid plans?

Yes. The first paid plan a team chooses is free for 14 days, and you can cancel before it ends. The free plan has no time limit at all.

Where is my data stored?

In the European Union: the service, the database and the file storage run in Google Cloud in Belgium. Your content is never used to train AI models.

Can I leave and take my translations with me?

Yes. Every language exports to a file at any time, and the API and CLI export everything at once. Cancelling stops the next renewal, and the period you paid for runs to its end.

See it with real data

The demo is the real app with two projects, five languages and strings that still need work. Connecting a repository and inviting people come with your own account.

No email address, no card, no confirmation. It disappears after two hours.