Introduction
Getting started
Automatically translate your documentation with the Localizeflow GitHub App in under two minutes.
Getting started
Install the GitHub App and run your first automatic documentation translation in under two minutes.
Translate your docs site
Prepare and connect your Astro, Hugo, or Docusaurus documentation site for reliable automatic translations.
Troubleshooting & FAQ
Fix common issues such as missing repositories, missing translation pull requests, or static docs folder problems.
Localizeflow automatically translates your documentation and opens pull requests whenever the source file changes. This guide shows you how to install the Localizeflow GitHub App, connect a repository, prepare your docs structure, and run your first automated translation.
Prerequisites
- A GitHub account.
- Access to the GitHub organization or repository you want to translate.
- A Localizeflow account. You can create one using Sign in with GitHub in the next section.
Installing the Localizeflow GitHub App on a GitHub organization requires that you are an organization owner. If you are not an owner, share this page with an owner and ask them to complete the installation step for you.
Prepare your repository for translation
Before you start automatic translation, we recommend a one-time translation cleanup: This helps Localizeflow detect your source language correctly and avoid translating outdated or duplicate content.
For example, If you already have manually maintained translated copies of your docs (for example README.ko.md or a docs/ja/ folder), remove those translations before you start using Localizeflow so your default language remains the single source of truth.
Sign in and install the Localizeflow GitHub App
-
Visit localizeflow.com.
-
Select Continue with GitHub.

-
Select Sign in with GitHub.

-
Sign in with your GitHub account.

-
After logging in with GitHub, you’ll be redirected to Localizeflow’s account selection page. Select Install in new account to create your account and install the Localizeflow GitHub App.

-
Choose the account where you want to install the Localizeflow GitHub App — your personal account or an organization you manage.

Installing the Localizeflow GitHub App on a GitHub organization requires that you are an organization owner. If you are not an owner, share this page with an owner and ask them to complete the installation step for you.
-
Select the repositories you want Localizeflow to access, then choose Save.

-
You will be redirected to the Localizeflow home page.
If an organization owner installed the Localizeflow GitHub App, they can invite teammates from the Team page in the sidebar, either by sending email invitations or sharing an invite link.

To add more repositories later, select your account in the header and choose + Add more repositories.

Connect your repositories to Localizeflow
-
On the Localizeflow home page, select + Connect repositories.

-
Select one or more repositories you want to connect, then select Save. You can use the search bar to quickly find specific repositories.

-
Your connected repositories will now appear on both the Home page and the Repositories page.
-
To view all connected repositories, navigate to the Repositories page.

Start automatic translation
-
Select the repository you just connected.

-
On the repository detail page, select Edit at the bottom.

-
Configure your translation settings:
Basic settings (required for all repositories):
- Framework: Choose Generic Git repository for typical open-source projects, or Documentation site if you’re using Astro, Hugo, Docusaurus, or similar frameworks.
- Source language: The language your content is written in (default:
en). - Target languages: Select one or more languages you want to generate (for example
ko,ja,fr). - Target branch: The branch where translation pull requests will be opened. If empty, your repository’s default branch will be used.
Additional settings (only for Documentation site):
If you selected Documentation site, you’ll also need to configure:
- Translation groups: Define source and output folder mappings. For example:
- Source root:
src/content/docs/en→ Output root:src/content/docs/ - Source root:
src/content/blog/en→ Output root:src/content/blog/
- Source root:
Select Save.

Generic Git repository is the simplest option—just select your languages and you’re done. Use this for typical repositories with files like
README.md,CONTRIBUTING.md, ordocs/*.mdat the root or in simple folders.Documentation site requires translation groups to map your source language folder (e.g.,
docs/en) to the parent output folder (e.g.,docs/). Localizeflow will then createdocs/ko,docs/ja, etc. alongside your English content.See Translation configuration reference for all available options.
-
Select Start & Automate. Localizeflow will now automatically translate your documentation and open pull requests whenever the source changes.
