.po File Inspector
Paste a gettext .po file to see translated / fuzzy / untranslated counts and export CSV.
| Source | Translation | Status |
|---|---|---|
| Add to cart | In den Warenkorb | translated |
| Checkout | Kasse | fuzzy |
| Your order is complete | — | untranslated |
| Continue shopping | Weiter einkaufen | translated |
What a .po file is
.po (Portable Object) files are how gettext — the system WordPress uses for interface translation — stores strings. Each entry pairs a source string (msgid) with its translation (msgstr). Themes and plugins ship them so their UI can be localized.
What this inspector shows
- Translated — entries with a non-empty
msgstr. - Fuzzy — entries flagged
#, fuzzy, meaning a tool guessed the translation and it needs human review. - Untranslated — entries with an empty
msgstr. - Completion % — translated ÷ total, so you know how far a file is from done.
Everything runs in your browser — your file is never uploaded anywhere. Export a CSV to hand off to a translator or import elsewhere.
gettext vs. content translation
.po files cover interfacestrings (buttons, labels, error messages). They don't cover your posts, pages, or products — that's editorial content. A complete multilingual setup needs both. Gloty handles interface strings and content translation together, so you're not juggling .po files and a separate content workflow.
Gloty translates WordPress UI strings automatically, so you spend far less time managing .po files by hand.