Built-in AI Translation using DeepL
Copy content and pages into another locale and DeepL translates them on the way. Every copy lands as a draft, so someone who reads the language looks it over before it goes live.
Localization
Running a site in two languages shouldn't mean doing the work twice
If you run a site in more than one language, you know the routine: copy the page into the other locale, paste every field into a translator, paste the result back, and repeat until lunch. Agility now does the copying and the first translation, and leaves the part that needs a person, reading it over, to a person.
How it works
Three steps, and the last one is yours
Pick your content: select items or a whole list and choose Copy to Locales, or open a page in the other locale and click Initialize Page, then tick Translate Content. DeepL translates the text, rich text, page components and custom fields on your own API key. Each locale gets a draft, and nothing goes live until you publish it.
What you get
Everything that used to be copy and paste
The locale tools, including the new Other Locales column and filter, are on for every instance, with or without DeepL. Install DeepL and they translate as they copy.
Copy to Locales
Copy one item, a selection or a whole list into one or more locales in a single step.
Save & Localize
Save an item and copy it to your other locales at the same time.
Pages in several locales at once
Initialize a page in every locale you need, with its components, title, menu text and meta description.
The DeepL panel
Translate a few fields in place from the editor's sidebar. Nothing is saved until you save the item.
Custom fields too
The text inside Power Fields Markdown and Block Editor content is translated, while IDs and Friendly URL fields are left alone.
Regional versions
Every language DeepL supports, including Canadian French, Latin American Spanish, Traditional Chinese, and Brazilian and European Portuguese.
What to check, and what you need
Machine translation is a strong first draft, not the final word, so we'd rather tell you where to look than have you find out later. Canadian French comes out Canadian, though. We're Canadian, so we checked.
- 01
URL slugs in plain text fields get translated
If your model keeps the slug in a plain text field, check it. A Power Fields Friendly URL field is left alone.
- 02
A page keeps its URL path
Its title, menu text and meta description are translated, so set a localized path yourself if you want one.
- 03
Code in body text can come back changed
Check any code samples or JSON pasted into rich text before you publish.
- 04
What you need
An instance with more than one locale, your own DeepL API key (API Free to try it, API Pro for real content; DeepL bills you directly, and its Translator and Write plans don't include API access), and an admin with two minutes. The setup guide shows where to find the key.
Questions about translating with DeepL
What teams usually ask before they turn it on.
Do I need my own DeepL account?
Yes. The app uses your DeepL API key, so translation runs on your DeepL account and DeepL bills you directly. We don't charge for DeepL. A DeepL API Free key works for trying it out.
Does translated content publish automatically?
No. Every translated copy is saved as a draft in its locale. You review it and publish it when it's ready, the same as any other change.
Which languages can I translate into with DeepL?
Any language DeepL supports that matches a locale on your instance. That's dozens of languages, including regional versions where DeepL has one: Canadian French, Latin American Spanish, Traditional Chinese, Brazilian and European Portuguese, and US and UK English.
Can I translate just one field?
Yes. Open the DeepL panel on the item, pick the fields you want, and translate. Nothing is saved until you save the item.
Can developers translate content from code?
Yes. The Management API has Initialize and Translate endpoints for pages, content items and content lists, and they run the same copy jobs the editor does. They're listed in the Management API reference.
Want to see it on your own content?
Bring a page you already run in two languages and we'll walk through what DeepL does with it, including the parts you'd still want a person to read.