WPML: How to Disable Automatic Translation Permanently

You turn off automatic translation in WPML—then a newly published page still appears in the translation queue, or WPML keeps inviting you to translate it. It feels like the setting did nothing. Usually, though, WPML is not ignoring you; more than one automation setting can be in play, and the one you changed may not be the one still triggering translations.

The answer to wpml how to disable automatic translation depends on how your site is configured: Translate Everything, Translate Some, automatic translation on publish, and work already waiting in a translation queue can each produce a different “it’s still translating” symptom. There is also one expectation worth setting early: turning automation off stops future actions—it does not erase translations WPML has already created.

First, Check Which WPML Translation Mode Is Active

Why Translate Everything keeps translating new content

If WPML translates a newly published post moments after you save it, that is usually not a rogue background process. It is doing exactly what Translate Everything is designed to do: automatically send eligible posts, pages, and later updates into the translation workflow.

This distinction matters because cancelling one translation job does not disable the rule that created it. Publish another article, edit a product description, or update a page title, and WPML may create a fresh job again. For anyone searching wpml how to disable automatic translation, the permanent fix starts with changing the site-wide mode—not with pausing or deleting individual translations.

Translate Some works differently. It leaves translation decisions in your hands: you choose which content to send, when to send it, and which languages need a version. That is the mode to use when automatic translation costs, editorial review, or selective localization are concerns.

How to confirm whether WPML is using automatic translation

Open WPML’s Translation Management area or its Settings screen and find the translation mode currently selected. The wording can vary slightly between WPML versions, but look specifically for the choice between Translate Everything and Translate Some. If Translate Everything is active, switching modes is necessary before new content stops entering automatic translation.

Also review the translation jobs or queue before assuming the setting failed. Jobs created while Translate Everything was enabled can remain pending, in progress, or waiting for completion after you change modes. Those existing jobs may still appear to be “automatic” even though WPML is no longer creating new ones.

In short, verify the global mode first, then inspect and cancel or complete any queued work you no longer want. That two-part check prevents the most common mistake: turning off future automation while overlooking translations already scheduled.

How to Turn Off WPML Automatic Translation

Switch from Translate Everything to Translate Some

The setting that matters most is WPML’s translation mode. In your WordPress dashboard, open WPML settings or setup options and change Translate Everything to Translate Some. Labels and menu locations can vary slightly between WPML versions, but the principle is the same: Translate Everything creates translations when content is published or updated; Translate Some returns that decision to you.

This is the essential answer to wpml how to disable automatic translation. Save the change before leaving the page. From then on, an editor or translation manager must deliberately send content for translation.

Cancel or remove translations already in the queue

Changing modes prevents new work, but it may not stop jobs WPML created earlier. Check WPML’s Translation Management area, translation basket, and any pending or in-progress jobs. Cancel or remove items where WPML provides that option, especially articles updated shortly before you changed the setting.

Otherwise, a queued job can still run and make it appear that automatic translation remains enabled.

Check credits and assigned translators

Translation mode and translation workflow are separate controls. Review automatic translation credits, any connected translation service, and assigned translators or workflow rules. A translator assignment does not necessarily mean WPML will translate every new post, but an active workflow can still create jobs when content is sent to translation.

If you use LATW AI Translator for WPML, remember that it is an add-on to WPML, not a replacement for its workflow. Confirm that no WPML job is being submitted before checking the selected AI engine or API key.

Test the change safely

Create a low-risk draft or make a minor update to a test post, then save it. Confirm that WPML does not automatically generate translation jobs or new language versions. If the front end still shows an older translated page, clear your site, plugin, CDN, and browser caches before assuming the setting failed.

What Happens to Existing Translations and How to Translate Manually

Existing translated posts will remain published

Disabling automatic translation is not a reset button. It stops WPML from creating new automated translation jobs, but it does not delete translations that already exist. Published pages, posts, products, translated metadata, and the language relationships WPML created all stay in place unless you remove them yourself.

Translation credits already used are generally not returned simply because you change modes or turn automation off. Think of the setting as closing the tap, not reversing the water already used. This is often the point missed in searches for wpml how to disable automatic translation: your live multilingual content remains intact.

Update translations only when you choose

Switching to Translate Some gives editors control over each job. When a source page changes, WPML may mark its translation as needing an update, but it will not automatically translate that update. You can leave it pending, assign it to a translator, or open the translation yourself when the revised content is ready.

• Select only the posts, pages, products, or strings that need attention.
• Assign work to an internal editor or external translator.
• Review and publish the updated translation on your own schedule.

This approach is particularly useful for sites where a small wording change should not trigger paid work across six languages.

Avoid unexpected translation costs going forward

Manual control works best with a few guardrails. Before sending content, review WPML’s translation basket and remove items added by mistake. Check the estimated credit cost before confirming a batch, especially after a large import or site-wide edit. Limit translation-management permissions so only designated editors can initiate jobs.

If you still want machine assistance while keeping WPML, LATW AI Translator for WPML is an alternative translation engine for existing WPML installations. It uses your own provider key and sends content directly to the selected AI or translation API, rather than relying on WPML’s credit system. WPML remains the required multilingual framework; LATW does not replace it.

A Lower-Cost Option for WPML Translation Automation

Use LATW AI Translator for WPML when you want more control

Turning off WPML’s automatic translation does not mean returning to slow, copy-and-paste localization. For site owners searching wpml how to disable automatic translation, the real goal is often simpler: keep WPML’s multilingual structure, but decide exactly what gets translated, when, and at what cost.

LATW AI Translator for WPML is built for that use case. It is an add-on, not a replacement for WPML: you need an active WPML installation, which continues to handle languages, URLs, translation relationships, and the rest of the multilingual framework. LATW plugs into WPML’s existing translation workflow and provides a different automation engine.

Instead of relying on WPML’s credit-based automatic translation, you can select supported AI or machine-translation providers and use your own API keys. Content travels directly from WordPress to the chosen provider, without an intermediary LATW server. That gives teams clearer control over provider choice and translation spending, while the translation history and cost details make it easier to see what a job actually used.

The practical advantage is restraint. You can translate selected pages manually through the workflow, send a defined batch when a campaign is ready, or use optional bulk translation for larger backlogs—without switching on blanket site-wide automation. A glossary helps keep brand terms, product names, and recurring calls to action consistent across jobs. For agencies and content-heavy sites, that balance of automation and editorial control is often more useful than simply translating everything by default.

Keep Translation Decisions in Your Hands

To permanently stop WPML from translating new or updated content automatically, move away from Translate Everything, cancel any translation jobs that are still queued, and make one small test update to confirm nothing new is sent for translation. Your existing translated pages remain intact; this change controls only what happens next.

From there, you can choose a workflow that matches the content’s importance: translate key pages manually, review translations before publishing, or automate only the items you explicitly select. Translation should follow your publishing process—not silently take it over.