Release Notes

DeepL Translation Support

DeepL is now the default translation provider for the Translate Into Another Language workflow and the Word Add-In Translate screen in US and EU workspaces.

Release Date
Aug 5, 2026
Categories
Agents
General Availability Access
Regional Availability
US, EU

What’s New

Harvey has integrated DeepL as our default translation provider for the Translate Into Another Language workflow in Harvey’s web application, as well as the Translate screen in Harvey for Word. In US and EU workspaces, translations in these surfaces now route to DeepL automatically.

Key features include:

  • Automatic source language detection, so you only need to select a target language when translating a document
  • Improved translation quality across a wide range of languages, including major European languages, Japanese, Korean, and Chinese

Why It Matters

The DeepL integration improves translation quality across a wider range of languages, giving you more accurate, consistent results for the languages you rely on.

How To Use

Translate a document via the Workflow agent

  1. From the Library tab, navigate to Workflows in Harvey.
  2. Open the Translate Into Another Language pre-built workflow.
  3. Upload the document(s) you want to translate.
  4. Select your target language from the dropdown.
  5. Select Run.

Translate a document via the Word Add-In

  1. Open the Harvey Word add-in.
  2. Navigate to the Translate screen.
  3. Select your target language.
  4. Select Submit.

FAQs

Q: What happens if my target language isn't supported by DeepL?

The translation will return an error. If DeepL translations are not available, Harvey does not currently fall back automatically to other machine translation methods. If a specific language is a priority for your team, contact your Harvey Customer Support Manager.

Q: What data does DeepL receive when I translate a document?

Only what's needed to perform the translation. Harvey sends the document itself, along with limited translation-related information such as the source language, target language, and filename. Harvey does not send any additional workspace or customer identifiers to DeepL.

Q: How does DeepL handle our data and content?

DeepL processes documents solely to perform the requested translation. DeepL is contractually prohibited from using customer data or content to train its AI models, and customer data and content are deleted after processing in line with Harvey’s zero data retention standards.

Q: How are translations processed for AU workspaces?

Workspaces that have selected Harvey's Australian processing region will continue to use Harvey's pre-existing translation infrastructure provided by Microsoft Azure.