.po, .pot

Translate gettext PO files with AI

Import PO and POT catalogs with comments and fuzzy flags preserved, let AI translate them, review and export valid gettext files.

Used by WordPress, Django, C/C++, PHP and countless open source projects.

What a gettext PO/POT file actually holds

gettext is the oldest localization format still in wide use, and the most information-dense. A PO catalog carries not just strings but source references, translator comments, fuzzy flags and plural forms — metadata that tooling and human translators both depend on.

That richness is exactly what generic translation tools throw away. Paste a catalog into a text translator and you get back a wall of text with the msgid and msgstr structure dissolved, the references gone and the flags lost. The file is no longer a catalog; it is prose.

.po, .pot

#: templates/login.php:12
msgid "Welcome back!"
msgstr ""

#: templates/login.php:15
msgid "Save changes"
msgstr ""

What goes wrong when gettext PO/POT files are translated badly

These are the failures that reach production, because none of them look like errors until they do.

Fuzzy flags get dropped

A fuzzy entry is one gettext knows may be stale. Lose the flag and the translation looks approved, so nobody ever revisits a string that has since changed.

Plural forms need the right header

Each language declares its plural rule in the catalog header. Copy an English header into a Polish catalog and the wrong form shows for most numbers.

Source references disappear

The #: lines tell a translator where a string appears. Without them, ambiguous words like "Post" or "Order" have to be translated blind.

The header entry gets translated

The entry with an empty msgid is the catalog header, not a string. Translate it and tooling stops reading the file correctly.

How GetTranslated handles it

Automatic format detection on upload: no configuration needed.
AI translations guided by your glossary, tone of voice and project context.
Every AI suggestion is marked for human review before it ships.
Export in the same format you imported, ready for your next release.
1

Import your gettext PO/POT file

2

AI translates with your glossary

3

Review and approve every string

4

Export and ship

Want to see it on your own file first?

Paste a gettext PO/POT file into the free tool and get the translated version back straight away — no account, no email address.

Open the free gettext PO/POT translator

Frequently asked questions

Are comments and references preserved?

Yes. Everything that is not a translation — references, translator comments, flags — is carried through import and export untouched.

Can I start from a POT template?

Yes. A POT file is a catalog with empty translations, which is the natural starting point: import it once and generate a PO for every language you ship.

Are fuzzy entries handled?

Yes. Fuzzy strings are imported as needing review, which is precisely what the flag means, and they surface in the review queue rather than shipping silently.

Start for free

500 keys free forever. No credit card.