EPICWP AI Translation for Polylang

Yes. The plugin sends your content to OpenAI with your own API key and nothing else is needed: no account with us, no subscription. Create the key at https://platform.openai.com/api-keys with billing enabled; a ChatGPT subscription is not the same thing: the API is billed separately by usage.

The plugin is free and has no usage limits; OpenAI bills you per token for the GPT-5.4 Nano model, which comes to well under one cent per language for a typical 1,000-word post. Long pages and many languages add up in proportion, and your OpenAI usage page shows the exact amounts.

The free edition translates one post, page or term at a time from the editor, with OpenAI; the Pro edition adds bulk translation, page builders, WooCommerce, custom fields, SEO meta, Polylang strings, more AI providers and premium support. The full comparison is in the Free vs Pro section above. Both editions share their settings and translation records, so upgrading keeps everything.

For posts, pages and custom post types: the title, the content, the excerpt and the slug; for terms: the name, description and slug. Block editor markup and classic editor HTML keep their structure. Custom fields are not sent to the AI in the free edition; Polylang's own custom fields synchronisation copies them, and the Pro edition lets you decide per field whether it is translated, copied or ignored.

Yes. Tick as many target languages as you like in the AI Translation box and one run creates all of them. Translating every item of a post type in one go is a Pro feature.

Yes, both, from Polylang 3.7 onwards. The plugin uses Polylang's languages and translation links and adds no language system of its own. It is not affiliated with Polylang.

Content written in the block editor or the classic editor is translated in every edition. In the free edition, Elementor and Bricks layouts are copied unchanged into the translation, so the translated page opens in the builder with the original text for you to translate there; the Pro edition translates Elementor and Bricks layouts in place. Other page builders are not supported.

In the Pro edition, yes: product content and the WooCommerce product fields are translated in place. The free edition is not built for shops: when Polylang lists products as translatable it translates a product's title, description, short description and slug only, and leaves prices, attributes and variations alone.

In the Pro edition, yes. It translates ACF fields, custom fields you mark as translatable, and SEO meta for Yoast SEO, Rank Math, All in One SEO, SEOPress, Slim SEO, Squirrly SEO, The SEO Framework and SEO Engine Pro. The free edition leaves custom fields and SEO meta to Polylang's own synchronisation.

No. The translation is published as soon as it is written, with the same status as the original, and you review or correct it in the editor afterwards. Only published content is translated; a draft or private post waits until you publish it.

Open it and translate again: only the fields that changed since the last translation are sent to OpenAI, the rest is kept. Tick Force re-translation to redo everything, or only the fields you select, for example after changing your instructions.

Not with the free edition, which translates one post, page or term at a time into as many languages as you like. Bulk runs across post types and taxonomies, and the upcoming Auto-Translate 24/7, are part of the Pro edition.

The language card shows the error and the Support tab logs it, and nothing half-finished is written. Each item is retried up to three times when the cause is temporary (a rate limit, a slow response); when your OpenAI account is out of credit the run stops with a clear message. Fix the cause and start the translation again.

Your content goes to the OpenAI API only when you start a translation, and nowhere else: the plugin has no telemetry and sends nothing to us. OpenAI states that data sent through its API is not used to train its models unless you opt in; its terms and privacy policy are linked in the External services section. Your API key is stored in your WordPress database like any other setting, and logs stay on your server in wp-content/uploads/pllat-logs.

Not in the free edition, which uses OpenAI's GPT-5.4 Nano model. The Pro edition lets you pick any supported OpenAI model and adds Anthropic Claude, Google Gemini and OpenRouter.

No. Translations run as background jobs on your server and only when you start them; nothing runs on the front end and nothing changes for your visitors. Before a run, the plugin sends one request to your own site address to check that background jobs can run; if your host blocks loopback requests or WP-Cron, the preflight check tells you what to fix.

No. EPICWP AI Translation for Polylang is an independent plugin by EPIC WP and is not developed by, endorsed by or affiliated with the makers of Polylang. It requires Polylang to be installed.

Post in the support forum for this plugin on WordPress.org. The Support tab under Languages > AI Settings has the error log you can quote in your post. Pro customers get priority support through the support desk on our website.