AumCreate

FREE TOOLS

Compile .po to .mo without installing anything

WordPress reads .mo at runtime; .po is the file people edit. Turning one into the other normally means installing gettext or downloading Poedit just to press Save. Drop the file here and get it back straight away — it is never uploaded.

  • Nothing is uploaded. Your language file is parsed, compiled and saved on your own machine.
  • Both directions. .po or .pot in, .mo out — or drop a .mo and get an editable .po back.
  • Every translated string is checked for placeholders that went missing or appeared from nowhere.
  • A .mo carries no comments, no source references and no fuzzy flags — those are dropped when it is compiled, not by us. Decompiling gives back less than the original .po had.

Drop a .po, .pot or .mo file

The file is never uploaded

Files do not leave the browser. Nothing is sent to a server.

Measured output

  • Entries in the .po

    581

  • With a translation

    565

  • Written to the .mo

    565

  • Left untranslated

    16

Measured on a real theme language pack. Every translated entry reaches the binary and nothing else does: untranslated and fuzzy entries are omitted, which is what gettext specifies and what lets WordPress fall back to the original English. The count on the right was read back out of the compiled .mo, not reported by the compiler.

100 KB .po → 44 KB .mo