Skip to converter

ARB translations to Gettext PO Converter.

Convert ARB translations to Gettext PO privately. Move ordinary app and software text translations into a new file with no source upload.

Featured resources

App or project

NGSpeak: Language Learning App

Learn English and Bengali with 160 offline-first lessons across CEFR A1–C2, including speaking, writing, pronunciation practice, and progress tracking.

Download Now

Convert your file

INPUTARB translations
OUTPUTGettext PO
Files stay on your device

Up to 25 MiB · Compatible data and documents · Local conversion

Choose a compatible source file to begin.
Private processingYour source file stays in your browser
Original stays intactDownload a new output file
Real formatsUnsupported conversions show an error

STEP BY STEP

How to convert ARB translations to Gettext PO

  1. Choose a source file. Select a real ARB translations file from your device.
  2. Run the local converter. The converter checks the input and processes it locally using the appropriate browser engine.
  3. Download the result. Save the generated Gettext PO file. Your original file is unchanged.

FORMAT GUIDE

Why convert ARB translations to Gettext PO?

Help move simple app labels, menu text and interface messages between translation tools and readable tables.

  • Reviewing interface translations in a spreadsheet.
  • Preparing simple Android and Apple localization strings.
  • Exchanging singular gettext messages with another localization editor.

UNDERSTAND YOUR FILES

ARB translations vs. Gettext PO: what changes?

Input · ARB translations

ARB translation files are JSON objects of message keys and strings. Locale and placeholder metadata are not handled by this simple converter.

Output · Gettext PO

Gettext PO stores translated text messages. This tool supports simple singular entries without contexts, plural forms, flags or comments.

Help move simple app labels, menu text and interface messages between translation tools and readable tables. Choosing an output format changes how another app reads the file; it does not restore detail missing from your source.

Before you share the output

Check column headings, escaped characters, delimiters and empty values. Data type information and spreadsheet formulas may not survive a plain-text format change.

Your files and privacy

Your selected file is converted on your device. You can download the new file while keeping the original unchanged.

Some formats work differently across browsers and devices. Check the converted result before using it for important work. Advertising and other optional website services may have separate privacy practices.

Format compatibility and limitations

Only plain singular UTF-8 text messages are supported. The two required table columns are key and value, in that order. Gettext plural messages, message contexts, flags and comments are rejected. Android input accepts plain string resources, but not plurals, string arrays, styled text or resource references; Android output requires valid Android resource names. Apple .strings input must be UTF-8 without comments. ARB supports simple key-to-string objects without locale, placeholder, or comment metadata. All unsupported structures cause an error rather than silently losing data. Keep the originals and verify every translated message in its target application.

Actual output behavior depends on the input file, your browser, device resources and the converter engine. Check important files before sharing or replacing them.

HELP & ANSWERS

ARB translations to Gettext PO questions

What table structure do I need?

Use exactly two columns: key and value, in that order. Keep each identifier unique.

Will plurals, comments or placeholders survive?

No. Only plain singular UTF-8 text messages are supported. The two required table columns are key and value, in that order. Gettext plural messages, message contexts, flags and comments are rejected. Android input accepts plain string resources, but not plurals, string arrays, styled text or resource references; Android output requires valid Android resource names. Apple .strings input must be UTF-8 without comments. ARB supports simple key-to-string objects without locale, placeholder, or comment metadata. All unsupported structures cause an error rather than silently losing data. Keep the originals and verify every translated message in its target application.

Are my translation files uploaded?

No. Conversion happens in your browser; your originals remain on your device.