Drupal is a registered trademark of Dries Buytaert

The AI Translate functionality of Drupal AI basically works. But for more complex websites it is not useful as it is.
At the moment it only offers a single prompt per language. But the prompt needs to be different for different contexts:

  • optional prompt per content type / bundle
  • different provider or model per content type / bundle
  • optionally disable AI translation per field
  • use full featured replacement tokens when creating prompts
  • access the current entity when rendering prompts in Twig

For example, you might automatically accept translations for the title and the body field, but you won't AI translations for the path alias.
Or you want to specify a different context like "food" or "computers" to get Apple translated correctly.

Some providers might be better suited for specific contexts or languages than others.

Furthermore, the token replacement is not sufficient. For example, if a content entity references a manufacturer entity, I want to add the instruction to the prompt that the manufacturer's name stored in a field of that entity must not be translated. Good examples are Zebra or Star or Brother or Citizen.
Therefore, AI Translate Plus fully integrates Core's replacement tokens based on the entity to be translated, including following entity references. And the entity and the same navigation is available from Twig when rendering the prompt. This way you can use taxonomy to narrow the context of your translation.

AI Translate Plus offers these features on top of AI Translate, a sub-module of Drupal AI.

Activity

Total releases
3
First release
Sep 2025
Latest release
3 months ago
Release cadence
30 days
Stability
0% stable

Release Timeline

Releases

Version Type Release date
1.0.0-beta1 Pre-release Nov 10, 2025
1.0.0-alpha1 Pre-release Sep 12, 2025
1.0.x-dev Dev Sep 12, 2025