Quickstart

This quickstart walks you through a full first setup — from creating a project to using translations in your app.

Step 1: Create a project

After signing in, create a new project.

Choose:

• A clear name (e.g. Web App, Marketing Site)
• A base language (your source language, often en)

The base language is where new keys usually start.

Step 2: Add languages

Add one or more target languages to the project (for example fr, de, es-ES).

When you add a language:

• Existing keys get empty values for that language
• Empty values do not count as strings until saved

This lets you prepare structure without increasing usage.

Step 3: Import or create keys

You can now add translation keys in two ways.

Import existing files

If you already have translation files:

• Choose your format (e.g. JSON)
• Upload the file(s)
• Review the detected keys and structure

Dot-notation keys are preserved and exported as nested objects.

Create keys manually

You can also create keys directly in the UI.

Example:

• Key: COMMON.SAVE
• Base language value: Save

Step 4: Add translations

For each language, you can:

• Enter translations manually
• Request AI suggestions per key
• Bulk translate an entire language

Suggestions don’t overwrite values unless you save them. Bulk translate can optionally replace existing values — use with care.

Step 5: Review usage

As you add translations, your string usage updates automatically.

Remember:

• 1 key × 1 language = 1 string
• Empty values don’t count
• History doesn’t count

You can always see current usage in the workspace.

Step 6: Use translations in your app

You have two common options:

Export files

Export translation files and bundle them with your app’s build.

Good when:

• Translations change infrequently
• You prefer build-time integration

Enable CDN delivery

Enable CDN delivery and fetch translations at runtime.

Good when:

• You want updates without redeploys
• You support many languages
• You want globally cached reads

Step 7: Iterate safely

As your app grows:

• Add languages gradually
• Review AI output before shipping
• Delete unused keys to reduce usage
• Rename keys carefully (update app references)

---

What’s next?

• Learn how strings & keys work under the hood
• Set up CDN delivery for production
• Explore auto-translate workflows
• Review plans & limits as usage grows