This guide takes you from a new account to your first exported translation file, using only the web app. If you work from a code repository, you can also use the CLI or connect GitHub or GitLab.
New to the terms? Read Core concepts first.
1. Create your project #
After you sign up, you land on Projects. Choose New project and fill in:
- Project name: for example
Mobile App. - Description: optional.
- Source language: the language your texts are written in.
- Target languages: the languages you translate into. Optional, you can add them later.
Choose Create project. You become the manager of the project, and it starts with a protected main branch.
static/screenshots/new-project.png2. Add keys #
Open the project’s Editor and choose New key. Fill in:
- Key name: for example
checkout.discount_label. Use dots to group keys. - Source text: optional. A key without source text cannot be translated yet.
You can also bring in existing texts: import a file (JSON, YAML, XLIFF, Gettext and more) or push them from your repository with the CLI.
3. Translate #
In the editor, pick the target language at the top, select a key in the list on the left, type the translation and choose Submit for review. Save draft keeps your work without sending it to a reviewer.
static/screenshots/editor-overview.pngRead more in The translation editor.
4. Review #
By default a translation must be approved before it counts as translated. Open Review, look at each submitted translation and choose Approve or Request changes.
By default people cannot approve their own translations. If you are the only person in the project, turn on Allow self-review under Project settings → Workflow, or turn off Require review before publishing so that submitting publishes straight away. See Workflow.
5. Invite your team #
Invite colleagues under Organization settings → Members, then give them access to the project under Project settings → Members, or through a team. See Inviting people.
6. Get the translations out #
Open Project settings → Import & export, choose a format, a branch and the languages, and choose Download. To fetch translations automatically from a build, use the CLI or the API.
What’s next #
- Branch workflows: translate a feature in isolation and merge it back.
- Translation memory and the glossary: reuse earlier work and keep terminology consistent.
- Webhooks: get notified when keys or translations change.