Q: What is your refund policy?

We do not offer refunds. Please read <a href="/terms-and-conditions">Terms &amp; Conditions</a> of Localazy before purchase.

Q: How can I help build the shared translation memory?

You can help build the ShareTM by allowing your project’s translations to be shared. In your project settings on Localazy, you can enable the ShareTM option, which will make your translations available to other projects. By doing so, you contribute to a richer and more diverse translation database, benefiting all users. <blockquote> Learn more about <a href="/docs/general/what-is-localazy-sharetm">ShareTM</a> </blockquote>

Question 1

What is the maximum possible length of translation text?

Accepted Answer

There is no hard limit at the moment, but it’s recommended to keep the size of each individual item under 4kB. This corresponds to 4,000 characters encoded as UTF-8 and 2,000 characters encoded as UTF-16. Uploading longer texts won’t yield any errors, but might get refused by some external translation engines integrated in Localazy.

Question 2

Why are the recent changes or new translations not downloaded?

Accepted Answer

If you come across this issue, it is likely because you have exceeded your account’s source key limit or the changes you made haven’t been published yet. To resolve this, please go to the Billing section of your account to check your source key limit and consider upgrading if necessary. Additionally, you can visit your Project Activity Stream to verify if the project has been published.

Question 3

What is your refund policy?

Accepted Answer

We do not offer refunds. Please read Terms & Conditions of Localazy before purchase.

Question 4

How can I ensure the best translation quality for my product?

Accepted Answer

While many digital product makers choose machine translations for the very start (and it’s a standard best practice for early stages of development where MT-pre translate is a rational decision), they often forget that machine translation alone yields subpar results.

It’s vital to focus on the highest possible quality of translation when it comes to product interfaces and product marketing. But enlisting professional translators is not a silver bullet solution. You need to be diligent and prepare a sound basis for successful localization.

These are best practices to ensure the best translation quality:

Read how to Make your translators happy to cooperate
Prepare your glossary
Prepare your style guides
Upload screenshots of your product to improve the context
Make sure there are multiple rounds of quality assurance. You can e.g., follow the first round of translations with proofreading.
Perform thorough localization testing

Question 5

What is the difference between hidden and deprecated source keys?

Accepted Answer

In Localazy, every key can be in different states, which makes it invisible from the translation process.

Hidden: Hidden keys are not available to translators, but other than that, they are processed the same way as all the others. They are also exported in the output file.

Keys are automatically marked hidden under certain circumstances - when the source language translation is empty or when they are linked to another one using our Duplicity Linking feature.

Deprecated: Deprecated keys are invisible in the translation process and are not exported in the output file. Under certain circumstances, they can be exported for our Android/iOS SDK when the update is required from the older version of the app. If the key reappears in the input data, it’s restored along with its complete state (context, translation, contributors, etc.)
Deleted: Deleted keys are removed with all their data - comments, translations, screenshot linking, contributors’ history, etc. Once the key is deleted, it’s no longer counted against the key limit, and it’s impossible to restore it.

Question 6

Should I delete deprecated keys?

Accepted Answer

If you are running over the source key limit, you can consider deleting deprecated keys. However, be sure that deleted keys are no longer necessary for your project, as you cannot restore them if needed, and all the associated data is also deleted.

It’s not only about the translations you can easily store and restore if needed when using deprecated keys instead of deleting them, but also about context information, comments, user interactions, etc. Once the key is deleted, it’s no longer counted against the key limit, and it’s impossible to restore it.

Question 7

How to delete a language from my Localazy project?

Accepted Answer

You can either disable or delete a language if you no longer need it.

Disabling a language hides it from the translation interface but retains all translations and keys. On the other hand, deleting a language completely removes it from the project, optionally including all translations, keys, and associated metadata.

To delete a language in Localazy:

Go to the language list of your project and use the three dots menu next to the language you want to delete.
Hover your cursor over the three dots to reveal several options, including the “Delete language” option.
Click and confirm.

It’s important to note that deleting a language is permanent and can’t be undone. It’s recommended to double-check and ensure that the language deletion is intentional and necessary. Disabling a language may be a better option if you are unsure whether you’ll need the language in the future.

Question 8

How to cooperate with an external translation agency when I am using Localazy?

Accepted Answer

When working with external translators or agencies that are used to their own solution for translating, you may need a few extra features - language statistics and import/export.

You can find both of them in a single place - in our console. As you may already know, the console is our place for features that are relevant to a small subset of our users only and for features that are still being heavily improved over time. We are committed to making Localazy better every single day, so your feedback is welcomed. Feel free to share all your suggestions with us!

Learn more about Language Statistics

Exporting content for use by external tools #️⃣

Some translation agencies are used to work with their own solution. There are numerous reasons for it - e.g., it helps them to calculate rewards for their translators and contractors. We are prepared for it, and you can easily export all your texts or only the untranslated ones as a CSV file, which any agency should easily be able to use.

Please note that we don’t recommend this for a variety of reasons - it adds extra manual work, and you also need to ensure that the agency has all the necessary context information in order to provide a high-quality translation. You wouldn’t need to care about it while using Localazy directly.

However, if there is no other way around it, here are a few simple steps on how to do it:

Add the required language to your project
Export your project as a CSV file using the Import/Export option in the Console
Exchange the file with your translation agency
Import the file back to Localazy
And that’s it!

Learn more about CSV Import/Export

Question 9

How to change the source language of my project in Localazy?

Accepted Answer

Watch the video #️⃣

Step-by-step explanation #️⃣

To change the source language of your project in Localazy, follow the steps outlined below:

Navigate to the Project Settings - General Settings
Scroll down to Advanced Settings
Find the field Project source language and click on the ✏️ pencil icon.

Localazy project settings - advanced settings

A modal window appears asking you how and to which language you would like to change the source language.

You have two options here.

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 swtich 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 the normal Localazy language.

Localazy - set another fully translated language as the new source

Transfer the current source content to a new source language #️⃣

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 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.

Localazy - transfer the current source content to a new source language

Question 10

Is it possible to manage multiple folders in one Localazy project?

Accepted Answer

Yes, absolutely. You can have multiple files in different folders uploaded to the same project.

You can include files by their exact path or by using standard path wildcards ? (single character), * (anything except path separator), ** (anything including path separators).

You can control files you want to upload with exclusion rules and conditions.

Example:

"upload": {
    "type": "json",
    "files": "modules/**/en.json"
  }
 
}

The above configuration will scan for files named en.json in all subfolders of the modules folder.

Question 11

How does the ShareTM feature work?

Accepted Answer

The ShareTM feature allows for the sharing of translation memories across public projects within Localazy. When you translate your project, the system automatically compares your texts with the ShareTM database and provides you with translation suggestions from other projects that have opted in.

This accelerates the translation process and improves the consistency of translations.

For more details, you can read more about ShareTM

Question 12

How can I help build the shared translation memory?

Accepted Answer

You can help build the ShareTM by allowing your project’s translations to be shared. In your project settings on Localazy, you can enable the ShareTM option, which will make your translations available to other projects.

By doing so, you contribute to a richer and more diverse translation database, benefiting all users.

Learn more about ShareTM

Question 13

Can I opt out of ShareTM if my project is sensitive?

Accepted Answer

Yes. If your project contains sensitive information and you do not want its translations to be shared within ShareTM, you can opt out. In the project settings on Localazy, you have the option to disable the ShareTM feature, ensuring that your translations remain private and are not shared with other projects.

For more details, read more about ShareTM

Question 14

How does Localazy help prevent broken placeholders in translations?

Accepted Answer

Localazy automatically identifies and highlights placeholders within your source text, making them visually distinct for translators.

When translating, placeholders like variables, HTML tags, and formatting codes appear specially marked, preventing accidental modification. Our system also performs validation checks that detect if a placeholder is missing or modified in the translation, alerting translators immediately rather than letting errors slip through to your application.

For developers, this means far fewer runtime crashes and formatting issues caused by broken placeholders in translated text. You won’t need to manually verify that every %s, {variable}, or HTML tag has been preserved correctly across dozens of languages - Localazy handles this verification automatically, letting you focus on building your product rather than debugging localization issues.

Question 15

What types of code elements and placeholders does Localazy recognize?

Accepted Answer

Localazy’s placeholder detection system works with virtually all common placeholder formats used in software development. This includes HTML/XML tags, React-style JSX elements, iOS and Android string format specifiers (%s, %d, etc.), ICU MessageFormat patterns ({name}), JavaScript template literals, printf-style formatting, and custom variable patterns specific to different frameworks and languages.

The system is designed to be framework-agnostic, so whether you’re using Angular, React, Vue, iOS Swift, Android Kotlin, or any other technology stack, Localazy will automatically recognize your code elements. This flexibility means you don’t need to modify your existing code patterns or add special markup for Localazy to understand what needs protection during translation.

If the placeholders in your project are not supported, feel free to contact us, we constantly expand the detection with new syntax.

General

💡 Enough theory, try Localazy now! 🚀