Languages in Scholarly

Scholarly keeps two language settings apart on purpose. One controls the language of the product itself, menus, navigation, buttons, settings. The other controls the language the AI writes in when it answers you or builds something.

Keeping them separate means you can run the interface in your own language while producing work in the language your colleagues, clients, or examiners read. It also means changing the interface never quietly changes the language of your next report.

App language

App language sets the language of Scholarly's interface: navigation, menus, settings, and buttons. It does not affect anything the AI writes.

1. Open Settings.
2. Go to the Appearance tab.
3. Under App language, choose your language.

The dashboard, marketing pages, and Help Centre support the same interface languages. Open App language to see the current list, or use the language menu on public pages. Arabic uses a right-to-left interface. New accounts start in a supported language from their browser preferences.

Your choice is saved to your account, so it follows you to any device you sign in on. The address you use stays the same, the app runs on the same links whichever language you choose, so bookmarks keep working and a link you send a colleague opens in whatever language they have chosen.

AI Language

AI Language sets the default language for new creations, including flashcards, quizzes, study guides, slides, podcasts, video lectures, and research reports. Chat replies follow the language of your latest message. The saved AI language is a fallback when that message has no clear language, such as a link or a number.

1. Open Settings.
2. Go to AI & Chat.
3. Under AI Language, pick a language. Use the search box to filter the list.

There are over 70 languages to choose from, plus Auto.

Auto

Auto is the default, and it is usually the right choice. Instead of forcing one language, Scholarly follows the material in front of it: a German contract produces German flashcards, a Japanese lecture recording produces a Japanese summary.

Pick a specific language when you want output in a language your source is not written in, for example, turning an English policy document into Spanish onboarding material for your team.

Changing the language for one creation

The account-wide AI Language is a default, not a lock. Most create windows have their own Language control in the Settings section, next to the model picker. Change it there to affect just that one creation and leave your default alone.

This is the quickest way to produce a one-off translation of a document you already have in your library.

How sources affect language

A few surfaces take their cue from the source material rather than a setting:

• PDF and video summaries follow the language of the source by default, rather than defaulting to English.
• Recordings keep their own language. A meeting recorded in Spanish, French, or German gets its transcript, summary, topics, and title in that same language.
• Practice exams on Auto follow the main language of the source.
• Read aloud picks a voice that suits the language of what it is reading, so a Japanese document is read in a natural Japanese voice.
• Generated titles and text inside creations follow the chosen output language where supported. Folder organisation suggestions follow the dominant language of the item titles. For a particular language in chat or an image request, say which language you want.

If you want any of these in a different language, set the language explicitly on that creation.

Emails

Account emails and checkout use your app language. Creation titles and previews keep the language of the work itself, so an English interface can still show a Spanish podcast title in a ready email.

Spoken languages: narration, podcasts, and read aloud

Anything Scholarly speaks aloud, video lecture narration, podcast hosts, a text-to-speech document, and read aloud, is narrated in the language the creation was made in. You do not pick a separate narration language; the creation's language decides it.

Every output language is spoken natively

The narration service receives the creation language along with the text. This helps it choose the right pronunciation for numbers, abbreviations, and words shared across languages. Pronunciation can still need review, especially names and specialist terminology.

The same voice is kept for each speaker throughout a video, episode, or document, so voices do not change between chapters.

No English creeping in

A podcast or lecture in another language stays in that language:

• Technical terms are translated rather than left in English.
• English filler, "okay", "exactly", "so", is dropped instead of being sprinkled through a non-English script.
• Numbers, dates, units, and abbreviations are written the way they are spoken in your language, so a currency amount or a percentage is read naturally.
• Where your field genuinely uses an English term, you hear the native term first, with the English said once for recognition, not every time.

Narrating from your own script

If you write a video lecture's narration yourself, the script's own language wins. The voice, the title, and the chapter headings all follow what you wrote, even when your account's language picker is set to something else.

Right-to-left languages

Arabic, Hebrew, and other right-to-left lectures are laid out right to left, not just translated. Headings start from the right edge, steps and timelines run right to left, punctuation lands on the correct side, and icons and markers sit beside their text rather than across the slide from it.

Captions

Captions follow the narration, so they are in the same language as the voice. See AI Video Lectures and Podcasts for how to turn them on and read along.

Recordings and read aloud

A meeting recorded in another language keeps it: the transcript, summary, action items, and title all come back in the language that was spoken. Read aloud picks a voice that suits the language of whatever it is reading, so a Japanese page is read in a natural Japanese voice.

Frequently asked

Does changing my app language re-translate my existing work?
No. Your existing chats, notes, and creations stay as they were written. App language changes interface text; the separate AI Language setting controls new AI output.

Can I have the interface in Japanese and my creations in English?
Yes, that is exactly what the two separate settings are for. Set App language to 日本語 and AI Language to English.

Why is my creation in a different language than I expected?
The most likely cause is Auto following your source. If a document is written in one language, Auto produces output in that language. Set the language explicitly on the creation to override it.

Is the interface available in more languages?
Yes. The dashboard, marketing pages, and Help Centre support the same interface languages. Use the language menu on public pages or Settings → Appearance in the app to see the current list. Changelog entries stay in English, and blog articles keep their published language. AI output supports more languages than the interface.

Can I narrate a video in a different language from the one it is written in?
Not as a separate setting, narration follows the creation's language. To get a lecture spoken in Spanish, set the language to Spanish on that creation, or write the narration script in Spanish and let the script decide.

Why did my podcast use English words in a non-English episode?
The script is instructed to use your selected language, though necessary names or technical terms can remain unchanged. If the narration uses the wrong language or distracting filler, tell us with a link to the episode.

Will my emails be in Japanese?
Yes, when your app language is Japanese. The title and preview of an existing creation keep the language of that creation.

Related

• Settings, every account preference in one place, including app and AI language.
• Recordings, how recorded meetings and calls keep their language.
• AI Video Lectures, narration language and captions.
• Turning Work Documents into Training Material, producing material in a language your team reads.