A technical check before your next localization release.
For plugin and theme developers, PO file maintainers, localization QA teams and translation agencies. Inspect an existing catalog for placeholder differences, missing plural translations and structural issues before handing it off.
Free PO File Check
Your upload is processed in server memory and is not saved on our server.
Translation QA before release
A translated string can look readable while losing a variable, changing markup or leaving a required plural form empty. PO Reviewer gives you a focused technical check alongside the editing and translation tools you already use.
Bring your gettext PO file from an existing workflow. Inspect entry-level findings, decide which differences need correction, and use your normal release checks before shipping a WordPress plugin or theme.
The free workflow
The free checker makes no AI request. You can inspect technical findings without purchasing a review.
Start in your browser without creating an account. Bring an existing PO catalog from your WordPress plugin, theme or gettext workflow.
Select a UTF-8 .po file. The technical check starts when you choose it. Confirm the source and target language options; the checker uses the target language header where available.
Read the source, current translation and entry/line reference. Plural findings identify the affected form. Review each finding before deciding what needs attention.
Illustrative technical findings
These PO entry excerpts come from a synthetic, non-customer catalog. Each reproduces the finding shown using the free checker’s technical rules.
PO entry excerpt
msgid "Hello %s"
msgstr "Merhaba"Checker finding
Placeholder, tag, entity or shortcode tokens differ; inspect this translation.
The source contains %s, but the translation drops it. Check that the variable is preserved before releasing the catalog.
PO entry excerpt
msgid "%d file"
msgid_plural "%d files"
msgstr[0] "%d dosya"
msgstr[1] ""Checker finding
Required plural form is empty.
This example’s catalog header declares nplurals=2. The second required form, msgstr[1], has no translation.
PO entry excerpt
msgid "<strong><em>Save</em></strong>"
msgstr "<strong><em>Kaydet</strong></em>"Checker finding
HTML tags are not correctly nested.
Both tags are present, but their closing order has changed. The inner em element must close before the outer strong element.
What the checker covers
Formatting can be intentional; inspect each finding in context. Required plural forms follow the catalog header; the checker does not certify that a plural rule is correct for a language. A clean technical check does not establish linguistic accuracy.
Free limits: 1 MiB, 10,000 entries, up to six plural forms and 16 KiB per text field. The first 250 findings are shown; counts include all findings. Large or invalid catalogs can be rejected by the checker’s resource limits.
Optional AI quality review
Public paid checkout is not yet open
Technical checks compare structure. The optional AI quality review examines meaning, fluency and consistency in existing translations. Inspect AI findings and suggestions, make the final decisions, then export an editable PO, compiled MO or ZIP package. Empty entries remain visible for human translation.
Priced per eligible file, from USD $10. The exact price is calculated and displayed before purchase. One-time payment. No subscription. See your price before checkout.
One eligible file, up to 1,000 active entries and 200 KiB, subject to the processing limit. Eligibility is checked before payment. Larger files are never silently reviewed in part. Applicable tax is shown at checkout.
When public checkout opens, the paid workflow requires sign-in and email verification, payment, backend-confirmed review, human approval and export. If you continue, the selected file and review options are saved only on your device for up to two hours to bridge sign-in and checkout. Paid AI processing sends the needed strings to OpenAI. AI suggestions require human judgment.
Check your file free