OpenLang – Translate WordPress with AI | Multilingual Plugin

OpenLang is a free WordPress translation plugin for creating multilingual WordPress websites with automatic AI translation and full manual translation control.

Translate WordPress without manually creating a separate page for every language. OpenLang discovers visible frontend text at runtime, stores translations for reuse, and serves language-specific URLs with a frontend language switcher.

Use OpenLang when you need a multilingual WordPress plugin that combines automatic translation, manual translation editing, RTL support, Elementor language switching, translation caching, per-language typography, language-specific logos, CSV import/export, and per-language CSS and JavaScript.

All features included in this WordPress.org package are free to use and do not require a license key.

Translate WordPress with AI or Manually

OpenLang supports both automatic AI translation and manual WordPress translation in one workflow.

For manual translation, OpenLang discovers visible frontend strings and common translatable attributes while pages are rendered. Administrators can review detected strings and edit translations directly from WordPress admin.

For automatic translation, OpenLang can translate missing strings through its hosted AI translation service and save the returned translations for reuse. Automatic AI translation is enabled by default and can be disabled at any time under OpenLang > Settings.

This gives site owners the speed of automatic website translation while keeping manual control over important wording, brand language, and corrections.

WordPress Translation & Multilingual Features

• Translate visible WordPress frontend text discovered at runtime.
• Manage manual translations and detected strings from WordPress admin.
• Automatically translate missing strings with hosted AI translation.
• Create a multilingual WordPress website with multiple enabled languages.
• Configure a default website language.
• Serve language-specific URLs without manually duplicating every page.
• Add a frontend language switcher with local translation caching.
• Support both RTL and LTR page direction.
• Add an Elementor language-switcher integration.
• View translation coverage, runtime activity, analytics, and system status.
• Configure typography separately for each language.
• Use Google Fonts, system fonts, or uploaded WOFF, WOFF2, TTF, and OTF webfonts.
• Set a different website logo for individual languages.
• Import and export WordPress translations with CSV.
• Add Custom CSS and Custom JavaScript for each language.
• Use all included plugin features without license activation.

Multilingual WordPress without Duplicate Pages

OpenLang does not require administrators to manually create a separate WordPress page for every translated language.

Instead, the plugin detects frontend strings, stores their translations, and serves translated content through language-specific URLs. Visitors can switch languages from the frontend language switcher while OpenLang uses stored translations and local caching where available.

This workflow is useful for site owners who want multilingual website translation without maintaining duplicate page structures for every language.

Automatic AI Translation for WordPress

Hosted AI translation is enabled by default. When an enabled language has missing strings, OpenLang can send those strings to the managed translation service, receive translated text, and store the translations for use on the website.

Administrators can disable automatic AI translation under OpenLang > Settings and use OpenLang as a manual WordPress translation plugin instead.

Automatic translation requests are described in detail in the Privacy and External Services section below.

Elementor Language Switcher, RTL & Language URLs

OpenLang includes a frontend language switcher and an Elementor language-switcher integration for adding language selection to Elementor layouts.

Language-specific URLs are used when visitors switch languages. OpenLang also supports both RTL and LTR page direction, making it suitable for multilingual websites that need right-to-left as well as left-to-right layouts.

Per-Language Fonts, Logos, CSS & JavaScript

A multilingual website may need more than translated text. OpenLang lets administrators customize the visual presentation for individual languages.

Each language can use its own typography, Google Font, system font, uploaded webfont, website logo, Custom CSS, and Custom JavaScript.

Generated language-specific assets are stored under wp-content/uploads/vynlang/assets/.

Translation Management & CSV Import/Export

Detected WordPress strings can be reviewed and edited from the OpenLang translation manager.

Administrators can also import and export translation data with CSV, making it easier to review translations externally, move translation data, or maintain larger translation dictionaries.

Why Choose OpenLang?

OpenLang is designed for WordPress site owners who want a flexible translation workflow without locking core plugin features behind license activation.

• Free multilingual WordPress plugin with no license key required.
• Automatic AI translation for speed.
• Manual translation editing for accuracy and control.
• No need to manually duplicate every page for each language.
• Frontend language switcher and Elementor integration.
• RTL and LTR language direction support.
• Per-language typography and website branding controls.
• CSV translation import and export.
• Per-language CSS and JavaScript.
• Translation coverage and activity visibility.

Privacy and External Services

OpenLang works locally for manual translation management. Hosted automatic translation is enabled by default and can be disabled under OpenLang > Settings.

When enabled and missing strings need translation, OpenLang can send requests to:

A translation request can include source and target language codes, source strings and their MD5 dictionary hashes, the site URL and an MD5 hash of the site URL, and OpenLang and WordPress version numbers.

This build has no license activation system and does not require or transmit an OpenLang license key.

The public OpenLang REST dictionary endpoint is read-only. It returns locally stored translations and language assets; it does not call the hosted service and does not write translations to the database.

If automatic translation is enabled and a visitor requests a language whose current page still contains untranslated strings, OpenLang uses the normal language URL so translation can occur through the server-side page-rendering workflow.

If an administrator selects a Google Font, the visitor’s browser may load resources from https://fonts.googleapis.com and https://fonts.gstatic.com. Standard request information such as IP address, user agent, and requested font resource may therefore be sent to Google.

Google Privacy Policy: https://policies.google.com/privacy Google Terms: https://policies.google.com/terms

Service provider: Vynatics Privacy policy: https://vynatics.corsysltd.com/openlang/privacy-policy.html Terms: https://vynatics.corsysltd.com/openlang/terms-of-service.html Support: d.laeeq@corsysltd.com

Security

• Administrative data-changing actions require WordPress capability checks and nonces.
• The public translation REST endpoint is read-only and accepts only bounded, validated MD5 hash lookups.
• Managed translation requests require HTTPS and use WordPress safe HTTP requests with redirects disabled.
• Custom webfont uploads are limited to administrators who can upload files.
• CSV import is administrator-only, nonce-protected, limited to CSV files up to 10 MB, and does not execute uploaded content.
• CSV exports neutralize leading spreadsheet-formula characters in human-entered text fields.
• Custom code changes are administrator-only and nonce-protected; unfiltered JavaScript editing respects WordPress’s unfiltered_html capability.