GitHub: Automate File Translation with the Localize GitHub Integration

Easily connect the Localize dashboard to your GitHub repository to automate and simplify content workflows between GitHub and your Localize project.

Localize Your GitHub Projects with Localize

Translate your GitHub-hosted documentation, wikis, and static sites automatically. Localize helps your developer community and customers understand your project in any language — without extra configuration or manual updates.
Auto detect new content for translation
Utilize MTs, your translators, or our LSP's
Support for numerous language pairs

Localize vs react-i18next and react-intl

React-i18next and react-intl are popular open-source libraries for internationalizing React apps.
They give developers precise control, but every string needs to be wrapped in code,
every language needs its own resource file, and translation updates usually mean a new build.

Localize handles translation at runtime, so your team doesn't have to manage string extraction or translation files.
React-i18next / react-intl
Localize
Setup
Install the library; wrap strings in t() or<FormattedMessage>, configure locales
Paste one JavaScript snippet
Translation files
JSON or message files per language, kept in your repo
None. Content is managed in the dashboard
New or changed strings
Extract, send to translators, merge, redeploy
Detected automatically as they render
Dynamic content
(Dynamic generation source)
Not handled natively and must be translated as content is detected
Detected when it renders
Who manages translations
Mostly developers
Anyone on the team, in a no-code dashboard
Translation sources
Depends on how you translate your content
AI translation, human translators or language service providers
Deploying Changes
Done via your CI/CD
Automatic from our snippet

Which should you choose?

Choose a library if you want every string defined in code and have engineering time for ongoing i18n maintenance.
Choose Localize if you want to launch new languages in days and let non-developers manage translations.

Get up and running with the React integration guide, the developer docs and live customer support.
Setup

Add Localize to your react app in 3 steps

How the React Integration Works

Step 1

Paste our snippet into the <head> of your index.html or layout file.

Replace YOUR_PROJECT_KEY with the key from your Localize dashboard. See the full list of options in our Library API docs.

Step 2

Let users switch languages from your own React component.

Localize ships a built-in language widget. If you want the switcher to match your design system, call Localize.setLanguage from any component.

Step 3

Load your app and approve phrases. Open your app, choose a target language, and browse your pages.

Localize picks up new content as it renders and sends it to your dashboard. You approve the phrases there, and they go live in your app without a redeploy.
Q&A

Frequently Asked Questions

Is the Localize GitHub Integration secure?

Yes. The integration is powered by a GitHub App which safely gatekeeps personal information and account access.

Does the integration have access to my GitHub credentials?

The Localize GitHub integration stores a GitHub-generated authentication token that allows Localize to access your specified repo. We do not have access to personal credentials.

How does Localize detect changes to our source phrases?

Each time a change is committed to your source file within the configured branch, GitHub will notify Localize. Localize will then re-import this updated file and create or update phrases as needed.

When do my translations get committed to my GitHub repository?

Since everyone’s workflows are different, we let you choose between delivery options. You can always press the Deliver Now button to send the most recent translations to your repository within your GitHub account. Localize can also check for updates on a schedule that you configure and will automatically upload if new translations are detected.

How will my translations appear in my GitHub repository?

When Localize delivers new translations a pull request is opened against the latest commit on your configured branch. This commit will contain one file of translations per language configured in the project. This gives you control to approve and merge on your schedule.

Can I see a history of when Localize downloaded my source phrases?

Yes. You can see a running history listed on your file import/export page. If for any reason Localize cannot process your source file, detailed errors will be displayed to help you troubleshoot.

Join the 40,000+ Users Who Trust Localize to Power Translations

Ready to translate your website and content faster?

Talk to an expert today to find out how you can translate your website in minutes, not months.