Skip to content
English
  • There are no suggestions because the search field is empty.

Languages and Translations

Learn how to enable automatic translations and view them across your project and exports.

You can enable automatic translation with the click of a button. Through that functionality, the application will work in practically any language.


In the project setting switch on the toggle to enable the translations of your text. You can choose between DeepL and Google Translate.

CleanShot 2025-07-20 at 10.42.58@2x


Text to analyze will be translated into the main language selected during upload.

We strongly recommend setting this to the same language you'll create your topic collection in.


When to use it?

We strongly recommend turning on automatic translations in the following cases:

  • You have a multilingual text to analyze with different languages in the same dataset (e.g. the topic collection will be in English but the texts are in Chinese, English, German, etc.);
  • Your text to analyze is in a language that is not supported by Caplena (see supported languages);
  • You need your topic collection to be in a different language than the text to analyze;
  • You don't speak the language the texts to analyze are in and thus require translations πŸ™‚.

Supported Languages

Caplena supports a range of languages out of the box, check out this list for details.

Caplena works best on languages for which we have a lot of data, specifically Western European languages. This doesn't mean other languages won't work at all, but such datasets might need a bit more manual fine-tuning from your side.

Fees for automatic translation services are already included in your subscription and your Ad-Hoc credits, no additional charges incur for translations.


Google Translate & DeepL

DeepL is a newish player with very good translation quality, however only a limited set of languages is supported (click on "Supported languages" during the upload process to learn more). Anecdotally, we've found DeepL to yield a bit better results.

If you choose DeepL we will use DeepL for supported languages and fallback to Google Translated for the languages that are only supported by Google Translate. For a list of supported languages, see below.

Language Google Translate DeepL
Afrikaans βœ“  
Albanian βœ“  
Arabic βœ“  
Bulgarian βœ“ βœ“
Chinese (Simplified) βœ“ βœ“
Chinese (Traditional) βœ“  
Czech βœ“ βœ“
Danish βœ“ βœ“
Dutch βœ“ βœ“
English βœ“ βœ“
Estonian βœ“ βœ“
Finnish βœ“ βœ“
French βœ“ βœ“
German βœ“ βœ“
Greek βœ“ βœ“
Hungarian βœ“ βœ“
Indonesian βœ“ βœ“
Italian βœ“ βœ“
Japanese βœ“ βœ“
Latvian βœ“ βœ“
Lithuanian βœ“ βœ“
Malay βœ“  
Polish βœ“ βœ“
Portuguese βœ“ βœ“
Punjabi βœ“  
Romanian βœ“ βœ“
Russian βœ“ βœ“
Slovak βœ“ βœ“
Slovenian βœ“ βœ“
Spanish βœ“ βœ“
Swedish βœ“ βœ“
Thai βœ“  
Turkish βœ“ βœ“
Vietnamese βœ“  
...and more βœ… via Google Translate  

Language Determination

The selected translator (Google Translate or DeepL) automatically detects the source language when importing. This works well for most text, but single-word entries may be detected incorrectly. To ensure accuracy, you can specify a language ID in the import, which forces the correct source language to be used. See below how to add a language ID.

Automatic Detection

By default, the platform identifies the source language of each entry and only translates it if it differs from your project's main language.

Determine Source Language via ID

If you know the source language of your content, you can add a dedicated column to your file using standard ISO 639-1 language codes (e.g., en for English, de for German, ja for Japanese). This column will be recognized during the data upload and used to determine the source language automatically. Make sure of the following:

  • Columns Type: When uploading, make sure the column containing language codes is set to Source language as its column type. Caplena may automatically identify it as a regular Text column, if that happens, you can adjust it manually before confirming the upload (see screenshot above). 
  • Countries with Multiple Languages: If your data comes from a multilingual country (such as Switzerland or Belgium) and you are not sure which language a specific entry is in, you can leave that entry blank. Caplena will fall back to automatic detection for that row.
  • ISO 639-1 Language Codes: Make sure language codes follow the ISO 639-1 format exactly; they must be lowercase. Watch out for common mix-ups:
    • Japanese is ja, not jp
    • Austrian German is de, not the country code at
  • Refer to the full list of ISO 639-1 codes if you are unsure.


Translation Visibility in the App

You can view and work with both original and translated texts within various parts of the Caplena interface.

 Fine-Tuning View

CleanShot 2025-07-20 at 11.01.19

  • See both the translated and original text for each comment.

  • Use the toggle β€œSee original / See translated” in the bottom-right corner of each comment.

  • By default, the translated version is shown for consistency across languages.

 Visualizations

CleanShot 2025-07-20 at 11.04.04

  • All charts (e.g., bars, tiles) are interactive.

  • Click on a chart element to open the verbatim browser, showing all comments behind that topic.

  • Within the verbatim browser, you can easily switch between original and translated versions.

 Data Export

CleanShot 2025-07-20 at 11.19.18

  • Translations are included by default in data exports.

  • Under Advanced Export Options, you can:

    • Change the position of the translation column

    • Exclude translated texts entirely, if needed