Localization automation

Stop maintaining locale files by hand

autoglot keeps app localization files current across 30+ languages. Use it from GitHub Actions, an npm build, or the API without replacing your existing i18n framework.

What is app localization automation?

App localization automation connects translation to the same source files and development events that already drive a build. When source text changes, the localization workflow identifies the affected strings, translates them, validates protected syntax, and updates the target-language files.

autoglot supports Xcode String Catalogs, Android XML string resources, JSON, YAML, PO, and POT files, so applications keep their native localization format and runtime integration.

terminal
# Translate JSON locale files
npx @autoglot/cli src/locales/en.json --lang es,fr,de

# Translate a PO file with project terminology
npx @autoglot/cli messages/en.po --lang de,it,ja --project myorg/my-app

# Translate an Xcode String Catalog
npx @autoglot/cli Localizable.xcstrings --lang fr,ja,ko

# Translate Android string resources
npx @autoglot/cli app/src/main/res/values/strings.xml --lang de,es,ja

Use the workflow that fits your app

The same translation service is available from repository automation, JavaScript tooling, and a REST API.

  1. 01

    GitHub Actions

    Run localization when source files change and keep repository translations synchronized.

  2. 02

    npm and build scripts

    Translate locale files before a build with @autoglot/cli or the Next.js integration.

  3. 03

    REST API

    Submit localization files and target languages from an existing service or internal tool.

  4. 04

    Agent skills

    Give coding agents project-specific instructions for working with iOS or React localization.

Works with the files your app already uses

No translation-management export format is required between autoglot and the application.

Xcode String Catalogs

Translate .xcstrings for SwiftUI, UIKit, AppKit, and other Apple-platform projects.

Android XML

Translate Android strings, plurals, and arrays into locale-specific values directories.

JSON

Preserve nested locale keys and interpolation used by i18next, next-intl, and React Intl.

YAML

Translate nested YAML locale files without changing their application-facing format.

PO and POT

Localize gettext catalogs while retaining message identifiers and structured metadata.

Frequently asked questions

Do I need to replace my i18n library?
No. autoglot translates localization files; your app continues using Xcode localization, i18next, next-intl, gettext, or its existing runtime.
Can the same project use more than one file format?
Yes. Translation jobs can include multiple supported localization files, and each result retains the format expected by the app.
Are variables and plural messages supported?
Yes. autoglot protects common platform placeholders and validates structured plural messages before accepting translated output.
Can this run during a build?
Yes. The npm CLI and Next.js integration support build-time localization, including a timeout that can fall back to compatible completed translations.

Related guides and documentation

Android app translation

Automate strings.xml localization for Android apps.

React app translation

Automate JSON localization for React, Next.js, and common i18n libraries.

Web localization overview

Choose between Next.js, build-time, CLI, and API integrations.

Supported languages

Review the 30+ available target languages and accepted language codes.

Automate your app localization

Start with one successful translation, then connect the workflow that fits your project.