Lingvit

Native automated translation for Strapi 5

Connect Strapi 5 directly to Lingvit. The @lingvit/strapi plugin translates collection and single types automatically upon publishing, preserving relationships, rich text, and media.

What gets translated

  • Collection types and single types
  • Strapi native Internationalization (i18n) plugin compatibility
  • Blocks, Markdown, and CKEditor rich text fields
  • Component fields, dynamic zones, and repeaters
  • Automated lifecycle hooks on content publish and draft save
  • Content Manager UI badge and 1-click translate action
  • Media library metadata (alt text, captions)
  • Customizable glossary term protection

Setup guide

  1. Install the Strapi plugin

    Add the package to your Strapi 5 project dependencies.

    npm install @lingvit/strapi
  2. Enable the plugin in config/plugins.js

    Add the Lingvit configuration to your Strapi plugins file.

    module.exports = {
      'lingvit': {
        enabled: true,
        resolve: '@lingvit/strapi',
      },
    };
  3. Pair from the Strapi Admin Panel

    Go to Settings → Lingvit in the Strapi Admin Panel and enter your pairing code. Enable target locales to start translating content.

Frequently asked questions

Does it work with Strapi's built-in i18n plugin?

Yes. Lingvit creates and updates localized entries directly within Strapi's native i18n structure, so GraphQL and REST API queries remain standard.

What happens to relation fields?

Relations and media assets are linked to their corresponding localized versions or preserved from the source locale without duplication.

Can editors review before publishing?

Yes. You can configure Lingvit to create translations as drafts, allowing editorial review before publishing to production.

Does it support custom fields?

Yes. Any field registered in the content-type schema is localized according to its type definition.

Start translating your Strapi site

A monthly word generation allowance for new translations. Cached delivery uses no extra allowance.