What is Translate?

Translate rewrites the text layers of a template in another language with AI, before the image, PDF or video renders. The design, fonts, images and layout stay as they are; only the words change. It costs 1 AI credit per 100 words, and text Orshot has translated before is free.

Why use it#

• One design per market, not one per language. Keep a single set of templates and render each campaign, listing or report in the language of the market it goes to.
• No copy round-trips. Your feed, CRM or spreadsheet can stay in one language. Orshot translates at render time, so nobody pastes translated copy into dozens of layers.
• Typography stays correct. Translated text renders with the capitals, characters and line breaking its language expects.
• Pay per word, once. Repeat renders of the same text cost nothing, so a weekly job only pays for what changed.

Where it works#

Translate on every render#

Send translate with your render request. The template's text and your modifications are translated before the image, PDF or video is rendered.

{
  "templateId": <TEMPLATE_ID>,
  "translate": "el",
  "modifications": {
    "headline": "Bright apartment with sea views",
    "price": "€245.000"
  }
}

Translate single layers, or keep one as it is, with .translate on the parameter:

{
  "templateId": <TEMPLATE_ID>,
  "translate": "el",
  "modifications": {
    "headline": "Bright apartment with sea views",
    "agent_name": "Maria Papadopoulou",
    "agent_name.translate": false,
    "subtitle.translate": "de"
  }
}

On multi-page templates, add the page: "page2@title.translate": "hi".

For more control, pass an object:

"translate": {
  "to": "es-MX",
  "from": "en",
  "context": "real estate listing",
  "glossary": { "walk-in shower": "regadera tipo walk-in" },
  "strict": true
}

The response includes what the translation used:

"ai": { "type": "text:translate", "words": 142, "wordsCached": 30, "credits": 2 }

Dynamic URLs don't translate: they're public links, so translate and .translate keys are ignored on them. &lang= still works. Translate in the Studio instead, or render through the API.

Set the language without translating#

lang tells Orshot what language the text is in, so capitals and characters render the way that language writes them: Greek capitals drop their accents, Turkish i becomes İ, and Chinese and Japanese use their own character shapes. It never translates and costs nothing.

• Whole template: "lang": "tr" in the request, or Template Language in the template menu.
• One layer: "headline.lang": "tr", or the Language setting in the layer's API tab.

Language codes#

Use these codes for translate, lang, .translate and .lang. They're the languages in the Studio menus; the API also accepts any other standard language tag, such as fr-CA, es-AR, sw or ta.

Pricing#

Words are counted across every layer and page of one render or one Studio action. Chinese, Japanese and Thai count every 2 characters as one word. Every translation shows up in AI History with its words, languages and credits.

Good to know#

• Translations are often longer than the original (German runs about 30% longer than English). Set long layers to Fit so the text shrinks to its box. Renders warn you when a translated layer may not fit.
• Numbers, prices, URLs and {{inline parameters}} stay as they are, and bold or coloured words keep their formatting.
• Layers that use .prompt (AI-written text) aren't translated. Write the prompt in the language you want instead.