Project details #️⃣

Project icon & name #️⃣

Change your project name or icon anytime to keep things organized. This is what you’ll see in your project list and what team members will recognize.

The icon resolution has to be minimum 72x72px and max 3072x3072px, maximum file size is 5MB. You can also generate a random project icon.

Project URL slug #️⃣

Each project gets a unique URL like https://localazy.com/p/my-example-project. You can customize the URL slug to match your project name or branding.

Tone of voice (formality) #️⃣

Setting a tone of voice will help your contributors keep the language consistent and is highly recommended before ordering translation services or running machine translations.

Translation interface #️⃣

These settings control how translators interact with your content and what languages they can work with.

Languages available as source #️⃣

Here you can add languages that contributors can select as source language on the translation/review screen. This won’t change your project’s actual source language, but allows your contributors to select another languages from your project. If the translation is not available, the actual source language wil be displayed.

This can be helpful if your team has for example, English as source, but your team is German and your translators prefer to translate from German.

Preferred source language #️⃣

Here, you can set a preferred language that will be displayed to translators in the translation session instead of the default source language.

Preferred sequence in translate/review session #️⃣

• Default - Based on upload order.
• Alphabetically - Based on key name alphabetical order.
• Alphabetically (Head-Tail) - Based on key name alphabetical order, with head-tail logic.

How does head-tail sort work? If your keys follow nested structures, for example: head.middle.tail

1. First, keys are sorted alphabetically by their head (first segment)
2. Then, within each head group, they’re sorted by their tail (last segment)
3. All the middle segments are completely ignored during sorting

Define plurals #️⃣

Localazy handles plural forms automatically based on language rules defined in CLDR definition, but you can define custom plural handling if your internationalization library requires specific formats.

Machine translations #️⃣

Configure how automated translation suggestions work in your project.

Community translations (ShareTM) #️⃣

Enable this to anonymously collaborate with other projects and exchange translations.

In return for offering your translations anonymously, your contributors will see aggregate suggestions from other projects, sorted by most-used. This allows you to get crowdsourced translations for your project without inviting external contributors.

Learn more about ShareTM

Machine translation suggestions #️⃣

Turn this on to get automatic translation suggestions when translators are working. These appear as suggestions, not final translations, so your team maintains control over quality.

Disabling this option won’t prevent project owners from using bulk machine translation or automations.

Publishing #️⃣

Control how your translated content gets delivered to your applications.

Manage releases #️⃣

Here you can manage your Releases. Set up release management to control when translations get published to your apps. You can create release tags and control which content goes live when.

Learn more about Releases

Publish unapproved translations for selected languages #️⃣

By default, Localazy only exports approved translations and untranslated keys fallback to your source language. Here, you can select languages for which you want to publish unapproved translations instead. The latest version is used.

This is useful for applying machine translation and relying on human reviewers to refine the final results. Your translations are available immediately, but the review workflow ensures they are validated afterwards.

Import and export #️⃣

Configure how content flows in and out of your project.

Key clustering #️⃣

When enabled, keys with identical content get automatically grouped together. This reduces duplicate translation work and keeps your project organized.

Learn more about Key Clusters

Content generation #️⃣

This relates to Export Aliases feature. Create path aliases for organizing exported files and keys differently than how they’re stored in Localazy. This helps match your development workflow without reorganizing the entire project.

Learn more about Export Aliases

Permissions #️⃣

Control who can access what parts of your project.

Project type #️⃣

• Public: Anyone can find and contribute to your project. Ideal for crowdsourcing and volunteer projects.
• Private: Only invited team members can access the project - recommended for most projects.
• Secret: Project is completely hidden from search and public listings (available in the Business plan)

Default language permissions #️⃣

Related to the Language Permissions feature. Define the initial language permissions for new members joining hte project here.

• New members can access all languages – Project members can see and contribute to any language in the project.
• Restrict new members from any access – Project members won’t see any project languages, until they are assigned some languages.

Learn more about Language Permissions

Default public project permissions #️⃣

Set the baseline permissions for new contributors joining your public project. You can choose between Translator and Trusted Translator (their translations skip review process).

Learn more about Project roles

Public description #️⃣

Here, you can fill in your project description and add links to your website or app stores.

This is mostly used by public projects to inform contributors about what is the project about.

Advanced settings #️⃣

Project source language #️⃣

The base language used as the foundation for all translations. To change it, click on the pencil icon.

• Set another fully translated language as the new source: Select this option if you already have another language that is fully translated and you want to switch its place with the current source language. You can choose any fully translated language in your project and the previous source language will continue to be treated as a normal Localazy language.
• Transfer the current source content to a new source language: Select this option to preserve the current source content but change the source locale code. You can either choose a blank language or an existing hidden language. When changing the source to a language that is currently hidden, its data is purged first.

Sometimes, it happens that your source files are in en_GB but you would like to use simply en while keeping the content intact. Select the second option to preserve the current source content but change the source locale code.

Clear project data #️⃣

Remove all translation data while keeping the project settings and contributors intact. This is useful when starting fresh or removing test content.

Delete project #️⃣

Permanently remove the entire project and all its data. This action cannot be undone!