Localization automation
for software teams

Automate localization. Keep your workflow.

Use doloc's translation API to send XLIFF, JSON, ARB, Android XML, or Properties files from a script or CI job. Get translated target files back in the same run, with existing translations, placeholders, and file structure preserved.

Start free See how it works

200 source texts free per month
Repository remains the source of truth
No platform setup

01 See exactly what comes back

localization-run ready

01 Input files

Source source.en.json

{
  "cart.title": "Your cart",
  "cart.pay": "Pay {{total}}"
}

Current target target.de.json

{
  "cart.title": "Warenkorb"
}

02 Curl request

curl --fail-with-body --silent --show-error --compressed \  https://api.doloc.io \  -H "Authorization: Bearer $API_TOKEN" \  -F source="@source.en.json" \  -F target="@target.de.json" \  -o target.de.json

03 Returned target

updated

Returned target target.de.json

{
  "cart.title": "Warenkorb",
Added line:   "cart.pay": "{{total}} bezahlen"
}

1 missing string translated · 1 existing entry preserved same request

01 Input files

Source + current target messages.de.xlf

<xliff version="1.2"
  xmlns="urn:oasis:names:tc:xliff:document:1.2">
  <file source-language="en" target-language="de">
    <body>
      <trans-unit id="workspace.name">
        <source>Workspace</source>
        <target state="translated">Arbeitsbereich</target>
      </trans-unit>
      <trans-unit id="workspace.create">
        <source>Create workspace</source>
      </trans-unit>
    </body>
  </file>
</xliff>

02 Curl request

curl --fail-with-body --silent --show-error --compressed \  https://api.doloc.io \  -H "Authorization: Bearer $API_TOKEN" \  --data-binary "@messages.de.xlf" \  -o messages.de.xlf

03 Returned target

updated

Returned target messages.de.xlf

<xliff version="1.2"
  xmlns="urn:oasis:names:tc:xliff:document:1.2">
  <file source-language="en" target-language="de">
    <body>
      <trans-unit id="workspace.name">
        <source>Workspace</source>
        <target state="translated">Arbeitsbereich</target>
      </trans-unit>
      <trans-unit id="workspace.create">
        <source>Create workspace</source>
Added line:         <target state="translated">Arbeitsbereich erstellen</target>
      </trans-unit>
    </body>
  </file>
</xliff>

1 missing unit translated · 1 existing unit preserved same request

01 Input files

Source app_en.arb

{
  "workspace": "Workspace",
  "createWorkspace": "Create workspace",
  "@createWorkspace": {
    "description": "Primary action"
  }
}

Current target app_de.arb

{
  "@@locale": "de",
  "workspace": "Arbeitsbereich"
}

02 Curl request

curl --fail-with-body --silent --show-error --compressed \  https://api.doloc.io \  -H "Authorization: Bearer $API_TOKEN" \  -F source="@app_en.arb" \  -F target="@app_de.arb" \  -o app_de.arb

03 Returned target

updated

Returned target app_de.arb

{
  "@@locale": "de",
  "workspace": "Arbeitsbereich",
Added line:   "createWorkspace": "Arbeitsbereich erstellen",
Added line:   "@createWorkspace": {
Added line:     "description": "Primary action"
Added line:   }
}

1 missing string translated · 1 existing entry preserved same request

01 Input files

Source values/strings.xml

<resources>
  <string name="cart_title">Cart</string>
  <string name="cart_pay">Pay %1$s</string>
</resources>

Current target values-de/strings.xml

<resources>
  <string name="cart_title">Warenkorb</string>
</resources>

02 Curl request

curl --fail-with-body --silent --show-error --compressed \  "https://api.doloc.io?sourceLang=en&targetLang=de" \  -H "Authorization: Bearer $API_TOKEN" \  -F source="@values/strings.xml" \  -F target="@values-de/strings.xml" \  -o values-de/strings.xml

03 Returned target

updated

Returned target values-de/strings.xml

<resources>
  <string name="cart_title">Warenkorb</string>
Added line:   <string name="cart_pay">%1$s bezahlen</string>
</resources>

1 missing string translated · 1 existing entry preserved same request

Illustrative request. Use your own files to evaluate the output.

Works with the files already in your repository

JSON XLIFF 1.2 XLIFF 2.0 ARB Android XML Properties

Angular React Intl / FormatJS Android Flutter GitHub Actions IntelliJ IDEA

Integrates with your framework

02 Add one translation step

From extracted copy to updated localization files.

Add doloc's translation API after extraction. doloc returns the updated translations in the same script or CI run, then your existing workflow continues.

1

extract
Keep your current setup

Generate source and target files with the framework tooling you already use.
2

request
Call doloc

Send the files from a local script or CI job with one synchronous API request.
3

release
Continue with your checks

Receive updated target files ready to ship. Inspect the diff when useful, then release as usual.

Ready to add the translation step? Follow the quickstart with commands for your file format.

View setup guide

03 Built around software delivery

Localization stays where engineering happens.

Use automation for routine UI copy while keeping the option to review ambiguous, legal, regulated, or brand-critical text.

Repository-native

Repository remains the source of truth. Keep using your extraction tooling, tests, diffs, and release controls.

On demand

Updated target files return in the same script or pipeline run. There is no project queue or handoff.

Context from existing translations

Existing target translations guide terminology and style for the new routine UI copy.

Review where it matters

Routine UI copy returns ready to test and ship with the release. Legal, regulated, ambiguous, and brand-critical text may still require review.

04 Where doloc fits

Automation, not another workspace.

doloc is for software teams whose localization process already lives in the repository. Choose a translation management platform like Crowdin, Lokalise, or Weblate when people and approvals need a shared workspace.

Compare operating models

Choose repo-native automation when…

Developers own localization files in the repository.
Routine UI copy should return during the same script or CI run.
Existing translations provide terminology and style context.
Diffs, tests, and release controls already provide oversight.

Choose a localization workspace when…

Translators need assignments, comments, or approval stages.
Teams need screenshot review or a visual editing workspace.
Vendor management and central governance are required.
Localization runs as a managed project with handoffs.

05 Preserved file structure

Your format in. Your format back.

Send the localization format your application already produces, including XLIFF 1.2, XLIFF 2.0, JSON, ARB, Android XML, and Properties. doloc updates the target file while retaining its format and surrounding structure, so your existing tooling can keep using it.

01 .json

JSON

Supports nesting and keeps formatting

Format guide

02 .xlf

XLIFF 1.2

Handles states and uses notes

Format guide

03 .xlf

XLIFF 2.0

Handles states and uses notes

Format guide

04 .arb

ARB

Supports metadata

Format guide

05 .xml

Android XML

Supports placeholders and plurals

Format guide

06 .properties

Properties

Keeps surrounding structure

Format guide

Integration guides Angular React Intl / FormatJS Android Flutter GitHub Actions IntelliJ IDEA

06 Predictable scope

Pay for source text, not every target language.

200 source texts free · Hobby from €12/month · Unlimited requests and target languages

Pro: 10,000 source texts for €45/month.

See pricing

07 Directly accountable

Built and maintained by Daniel Schreiber

Founder & Software Engineer

Daniel is a software engineer and open-source maintainer focused on developer tooling and localization workflows. He created doloc to make localization a natural part of software development—not another platform teams have to manage.

LinkedIn GitHub

08 Try the actual workflow

Start with one file. Keep everything else.

Start free Read the documentation

Automate localization. Keep your workflow.

From extracted copy to updated localization files.

Keep your current setup

Call doloc

Continue with your checks

Localization stays where engineering happens.

Repository-native

On demand

Context from existing translations

Review where it matters

Automation, not another workspace.

Choose repo-native automation when…

Choose a localization workspace when…

Your format in. Your format back.

JSON

XLIFF 1.2

XLIFF 2.0

ARB

Android XML

Properties

Pay for source text, not every target language.

Built and maintained by Daniel Schreiber

Start with one file. Keep everything else.