Skip to main content
All CollectionsBest Practices for Spinach.io
Language Translation and Output
Language Translation and Output

Select your primary speaking and summary language

Karin Sharon avatar
Written by Karin Sharon
Updated over 3 months ago

Spinach has enhanced quality when you select the primary language you speak and can also send summaries in your native language.

What Languages Are Supported?

We currently support Afrikaans, Albanian, Amharic, Arabic, Armenian, Assamese, Azerbaijani, Bashkir, Basque, Belarusian, Bengali, Bosnian, Breton, British English, Bulgarian, Cantonese, Catalan, Chinese, Croatian, Czech, Danish, Dutch, English, Estonian, Faroese, Finnish, French, Galician, Georgian, German, Greek, Gujarati, Haitian Creole, Hausa, Hawaiian, Hebrew, Hindi, Hungarian, Icelandic, Indonesian, Italian, Japanese, Javanese, Kannada, Kazakh, Khmer, Korean, Lao, Latin, Latvian, Lingala, Lithuanian, Luxembourgish, Macedonian, Malagasy, Malay, Malayalam, Maltese, Maori, Marathi, Mongolian, Myanmar, Nepali, Norwegian, Nynorsk, Occitan, Pashto, Persian, Polish, Portuguese, Punjabi, Romanian, Russian, Sanskrit, Serbian, Shona, Sindhi, Sinhala, Slovak, Slovenian, Somali, Spanish, Sundanese, Swahili, Swedish, Tagalog, Tajik, Tamil, Tatar, Telugu, Thai, Tibetan, Turkish, Turkmen, Ukrainian, Urdu, Uzbek, Vietnamese, Welsh, Yiddish, Yoruba

Default Setting For All Meetings

Do you speak another language in your meetings but want your summaries sent in English?

  1. Go to Settings

  2. Select the language you speak in the meetings

  3. The summary will be translated to English with a higher accuracy.

Do you want your summaries sent in your native language?

  1. Go to Settings

  2. Select the language you speak in the meetings

  3. Select the language you want the summary output in

Customize Per Meeting Series

You can change the language for each meeting:

  1. Go to your Spinach dashboard

  2. Navigate to the Meetings tab

  3. Click on the meeting

  4. Select the language you want that meeting sent in.

Did this answer your question?