Native Drupal translations, produced by Lingvit

Lingvit plugs into Drupal's Translation Management Tool as a translation provider. Jobs are translated through your Lingvit project and written back as real entity translations — the structure Drupal's own multilingual stack, search engines and accessibility audits already understand.

Get started View all integrations

What gets translated

Nodes, taxonomy terms, media and any translatable content entity TMGMT sources

Titles, plain-text and formatted text fields (markup preserved, only visible text is translated)

Paragraphs and other entity-reference-revision content via TMGMT's content source

Continuous jobs: new and edited content is translated on save

TMGMT review and acceptance workflow, or auto-accept

Native language paths, hreflang and sitemaps — nothing runs in the visitor's browser

Setup guide

1
Install TMGMT and the Lingvit translator module
Add the Translation Management Tool and the Lingvit translator module to your site, then enable them together with the content translation module.
```
composer require drupal/tmgmt drupal/lingvit_tmgmt
drush pm:enable tmgmt tmgmt_content content_translation lingvit_tmgmt
```
2
Generate a pairing code
In the Lingvit dashboard open your project → Integrations → Drupal and generate a pairing code. It is valid for a few minutes and works once.
3
Connect the provider
In Drupal go to Configuration → Regional and language → Translation providers → Lingvit, paste the pairing code and press Connect. The site receives its own credential; the code is never stored.
4
Send jobs, or let continuous jobs do it
Pick Lingvit as the provider on any TMGMT job, or create a continuous job for the content types you want kept in sync. Review translations in TMGMT or enable auto-accept to publish them straight away.

Need the full platform overview? Browse the use case guides →

Frequently asked questions

Is this a JavaScript widget?

No. The Drupal integration is server-side only: TMGMT hands Lingvit the source text, Lingvit returns the translation, and TMGMT saves it as a native entity translation. Visitors get ordinary Drupal pages in their language, with Drupal's own language paths and hreflang.

What happens to markup in body fields?

Formatted text is split into its visible text runs before translation and reassembled afterwards, so tags, attributes, links and embedded media stay exactly where they were. Elements marked translate="no" are left untouched.

Can editors review before anything is published?

Yes. Lingvit is an ordinary TMGMT provider, so the usual review, accept and reject flow applies. Turn on the provider's auto-accept option when you would rather publish immediately.

What about Drupal 7 or sites where modules cannot be installed?

Use Lingvit's language subdomains instead: point fr.yoursite.com at Lingvit with one DNS record and the French version is served at the edge, with no module involved. That path works for any Drupal version.

Where is the credential stored?

In the translator's configuration, like every TMGMT provider key. Sites that export configuration should override it from settings.php so it never lands in version control; the module's README shows the one-line override.

What gets translated

Nodes, taxonomy terms, media and any translatable content entity TMGMT sources

Titles, plain-text and formatted text fields (markup preserved, only visible text is translated)

Paragraphs and other entity-reference-revision content via TMGMT's content source

Continuous jobs: new and edited content is translated on save

TMGMT review and acceptance workflow, or auto-accept

Native language paths, hreflang and sitemaps — nothing runs in the visitor's browser

Setup guide

Install TMGMT and the Lingvit translator module

Add the Translation Management Tool and the Lingvit translator module to your site, then enable them together with the content translation module.

composer require drupal/tmgmt drupal/lingvit_tmgmt
drush pm:enable tmgmt tmgmt_content content_translation lingvit_tmgmt

Generate a pairing code

In the Lingvit dashboard open your project → Integrations → Drupal and generate a pairing code. It is valid for a few minutes and works once.

Connect the provider

In Drupal go to Configuration → Regional and language → Translation providers → Lingvit, paste the pairing code and press Connect. The site receives its own credential; the code is never stored.

Send jobs, or let continuous jobs do it

Pick Lingvit as the provider on any TMGMT job, or create a continuous job for the content types you want kept in sync. Review translations in TMGMT or enable auto-accept to publish them straight away.

Frequently asked questions

Is this a JavaScript widget?

What happens to markup in body fields?

Can editors review before anything is published?

Yes. Lingvit is an ordinary TMGMT provider, so the usual review, accept and reject flow applies. Turn on the provider's auto-accept option when you would rather publish immediately.

What about Drupal 7 or sites where modules cannot be installed?

Where is the credential stored?

Native Drupal translations, produced by Lingvit

What gets translated

Setup guide

Frequently asked questions

Start translating your Drupal site

Native Drupal translations, produced by Lingvit

What gets translated

Setup guide

Frequently asked questions

Start translating your Drupal site