# Translator configuration

> Choose Google or Yandex as the translation service of the N1ED Translator, set its API key and the default languages, and show its buttons on the toolbar.

Source: https://n1ed.com/docs/configuration/translator  
Section: Configuration > Translator  
Updated: 2026-11-13  
Every page of n1ed.com has a Markdown copy at its URL + `.md` (`index.md` after a URL that ends in `/`); all of them are in one file: https://n1ed.com/llms-full.txt

The Translator translates the selected text of your content right in the editor, with Google Translate or Yandex Translate. Its settings are in the **Translate** section of your [Dashboard](https://n1ed.com/dashboard)'s **Settings** tab: the service, its API key, and the languages it starts with. The Translator is a part of the Premium plan.

![Translate section of the N1ED Dashboard: service, API keys, languages](https://n1ed.com/img/screenshots/docs/widgets/config-editor/config-editor-translator.png)

*Configuring Translator*

The Translator's buttons are hidden on the toolbar of new API keys. To show them, click **Translate** in the copy of the toolbar in the **N1ED → Toolbar** row and check **Show on the toolbar**, and do the same for the two buttons next to it (see [UI, toolbar and widgets](https://n1ed.com/docs/configuration/ui-and-widgets#modern-toolbar)).

When you use the Translator you can change the languages on the fly right from its buttons: one swaps the two languages, the other one opens the languages for the rest of the session. What you set here is where every session starts.

The translation is requested from the browser of the user who edits, so the API key is visible to anyone who can open the editor page. For Google, restrict the key to the Cloud Translation API and to the address of your website in the Google Cloud Console.

## Translation API provider

Specify which service will be used to translate texts in your content. They have a bit different language sets and terms of use. Google uses the Cloud Translation API (Basic), Yandex the Yandex Translate API v1.5 with its `trnsl.` keys. Write the value in lower case.

- **API parameter:** `Translator.provider`
- **Type:** `string`
- **Default:** `yandex`
- **Valid values:** `google`, `yandex`
- **Dashboard:** Settings → Translate → Services → Default translation service

## Yandex API key

API key for using Yandex Translate engine. [Get a Yandex API key](https://yandex.com/dev/translate/)

- **API parameter:** `Translator.yandexAPIKey`
- **Type:** `string`
- **Dashboard:** Settings → Translate → Services → Yandex Translate API key

A configuration without this key uses our demo key, and the Dashboard shows it in the field. A field you empty stays empty.

## Google API key

API key for using Google Translate engine. [Get a Google API key](https://console.cloud.google.com/)

- **API parameter:** `Translator.googleAPIKey`
- **Type:** `string`
- **Default:** `""`
- **Dashboard:** Settings → Translate → Services → Google Translate API key

## Source language

Default source language Translator will use on load. Use a language code here. The two services use a few different codes (Google `zh-CN`, `iw`, Yandex `zh`, `he`): pick them in the Dashboard, which lists the codes of the service you chose.

- **API parameter:** `Translator.langFrom`
- **Type:** `string`
- **Default:** `en`
- **Dashboard:** Settings → Translate → Languages → From

## Target language

Default target language Translator will use on load. Use a language code here.

- **API parameter:** `Translator.langTo`
- **Type:** `string`
- **Default:** `de`
- **Dashboard:** Settings → Translate → Languages → To
