Make your product multilingual.

Understand the workflow, get a first result, then connect the parts your product needs.

On this page

How EveryLocale fits

You keep writing your product's original text. EveryLocale prepares the other languages before your next release. Your app displays those prepared translations; a visitor never waits for an AI request to read a page.

For example, you change an English button from “Create a project” to “Create your first project.” Your build sends the change, EveryLocale translates and checks it, and the next app release includes the new wording. Unchanged translations are reused.

  1. Bring your text. Import a file or connect your build or publishing system.
  2. Translate and check. Your selected models translate changed text and review it in a separate request.
  3. Follow your approval rules. Clean results can approve automatically. Turn on human review when a person should check every result.
  4. Use the approved files. Build your app or let a connector publish the translated content.

A project groups a product's languages, text, and spending limit. A catalog is a language's messages file with approval information. A release is the complete approved set of files your app uses together.

Start with one small result

New to EveryLocale? The first-file walkthrough shows installation, model settings, the workspace buttons to use, and the JSON file you get back. You do not need to connect your entire app to try it.

Translate your first file

After that, the workflow guide explains review states, manual corrections, source changes, and spending.

Choose what to connect next

EveryLocale supplies translation, review, files, and integration helpers. Your app supplies its interface, routes, saved account preferences, and deployment. The guides show those connection points.

Make updates part of your release

Once a manual translation works, automate the same steps in GitHub Actions or your existing CI runner. Keep EveryLocale running on a persistent server. The runner needs a project access token; your model keys stay on the service.

The sequence is simple: send changed text, wait for approval, download all configured languages, then test and build the app. A translation that needs attention stops the new release. Your currently deployed app remains available.

Translation before your build
pnpm cli sync --project first-app --input source.json --locales de --wait --timeout 600
pnpm cli pull --project first-app --output locales

The file connection guide shows how to create source.json and set the access token. Then use the complete GitHub Actions workflow with your app’s checks and deployment.

Let people choose their language

A shared German page link should show German. A private dashboard should follow the person's saved language choice. Browser preferences can suggest another language; country must not silently choose it.

Your app needs a visible selector and the right language file for each page. The language integration guide explains the React controls, Remix and Next.js routing, Arabic direction, fonts, and keeping the same language while the page loads.

Make translated pages discoverable

Give each published language its own URL and complete page content. Search engines need to know which pages are translations of one another. EveryLocale's page registry helps generate those alternate links, canonical URLs, and sitemaps from one list of published pages.

Your application owns that published-page list. Include approved, available pages and return a real unavailable page when a translation does not exist. See public-page and search setup.

Know what needs your attention

Automatic approval accepts translations that pass structural checks and AI review. Material findings, provider failures, and exhausted budgets still need a person. You can inspect and correct approved wording, or choose a human gate for every result.

Generation and review both count toward the project's total spending limit. No provider changes automatically. See the costs you control, and set up backups and exception alerts before relying on unattended operation.

Reference when you need it