Loco Translate & Poedit friendly
Outputs standard gettext PO files with valid headers and clean msgid/msgstr pairings.
Supported formats:.po.pot
Translate WordPress plugins and WooCommerce themes in PO and POT format
Upload your gettext PO or POT files from Loco Translate or WP CLI. Translate admin strings and frontend notices without corrupting PHP printf placeholders.
Drop your PO file here
Up to 2 MB, five files a day. Nothing to install, no account.
Built for WordPress developers and agency teams
WordPress strings frequently contain %s, %1$s, %d, and <a> tags. AI Glot locks these placeholders to prevent fatal PHP errors.
Printf placeholder security
Positional arguments like %1$s and %2$d are never corrupted or omitted.
WooCommerce & checkout readiness
Translate checkout notices, shipping messages, and email templates with appropriate e-commerce terminology.
Fast plugin internationalization
Prepare your WordPress.org plugin for global translation benchmarks in minutes.
Localize WordPress plugins and themes in 3 steps
Compatible with Loco Translate, WP-CLI, and Poedit.
Upload your .po or .pot file
Upload the language template exported from your WordPress theme or plugin.
Upload PO file →product-catalog.csvwebsite-content.xlsxmobile-app.xliffcourse-subtitles.zip
Review translation plan
Check that PHP printf tags like %s, %1$d, and HTML formatting are recognized.
Review strings →How to translate this file?
Translate into German and Spanish. Keep product names in English, use our glossary, and make the copy sound natural for e-commerce.
Glossary applied
Translation planReadyUpdated
LanguagesEN → DE, ES
Scope742 cells
Volume8,490 words
Existing translationsKeep unchanged
Start translation
Refine your instructions
Drop into wp-content/languages
Download translated PO files, compile MO with Poedit or WP CLI, and deploy.
Download PO file →fr-FR
de-DE
es-ES
ja-JP
website-content_localized.xlsx
WordPress translation FAQ
How do I translate a WordPress plugin or theme using PO/POT files?
Export your .pot language template or .po file from Loco Translate or WP-CLI, translate it in AI Glot, and place the resulting .po and .mo files in wp-content/languages/plugins/.
Are PHP printf placeholders like %s, %d, and %1$s protected?
Yes. All printf specifiers (%s, %d, %1$s, %2$d) are locked as code tokens to prevent PHP fatal errors or string evaluation crashes.
Does AI Glot preserve gettext plural forms (nplurals=...; plural=...;)?
Yes. The appropriate plural formula for each target language (e.g. Polish with 3 plural forms, French with 2) is automatically written to the PO header.
Are HTML tags inside translatable strings preserved?
Yes. Tags like
<a>, <strong>, and <span> are kept intact with identical attribute values and nesting order.Why is AI Glot better than Poedit Pro or Loco Translate auto-translation?
Built-in translation in Poedit or Loco Translate uses generic translation APIs that lack context. AI Glot understands WordPress terminology (dashboard, nonce, permalink, taxonomy) for professional localization.
Can I compile the translated PO file into binary MO format?
Yes. The output is a standard gettext PO file that compiles instantly into .mo using Poedit, msgfmt, or WP-CLI (wp i18n make-mo).
Does AI Glot support WordPress Gutenberg block translations?
Yes. Both PHP gettext PO files and Gutenberg block JSON translation dictionaries are fully supported.
Can I test translating a WordPress PO file for free?
Yes. Upload your .po or .pot file into the free tool above to translate sample strings up to 25 000 tokens free.
Make your WordPress plugins and themes multilingual
Your first 5,000 words free