Skip to content

Translation Engine – LATW Cloud

On this page

With every other engine, translation happens on your own server: WP-Cron picks up the queue, your
server calls the AI provider with your API key, and the result is written into WPML. LATW Cloud is an
engine that moves that work to LATW’s servers. You translate exactly as before – the same buttons,
the same screens – but the translating, the retries and the waiting happen on LATW’s side, and the
result is written back into WPML.

What that buys you:

  • No WP-Cron and no timeouts. A job of a few thousand products runs in the background on LATW’s
    side, retries on its own, and does not depend on visits to your site.
  • No API key needed. Translate with LATW Credits – included in a LATW plan or bought in packs –
    or use your own OpenAI key in LATW Cloud if you prefer.
  • One dashboard for all your sites, with the cost of every job per site, language and model.

#What you need before you start

  • A LATW account at app.latw.ai.
    The Free plan connects one site and translates with LATW Credits.
  • WPML with Translation Management, as for any other engine.
  • A site LATW Cloud can reach from the internet over HTTPS. LATW Cloud calls your site to read
    what needs translating and to write the translations, so a site on your own computer, or a staging
    site behind a password, cannot use it.

#Switching to LATW Cloud

  1. Go to AI Translator → Settings → General and choose LATW Cloud as the Engine.
  2. Click Connect with LATW. A LATW window opens; sign in if you are asked to.
  3. Check that the window names this site, then click Authorize.
  4. The window closes on its own once LATW Cloud has reached the site. The engine section now says
    Connected and shows your plan, your LATW Credits balance, the model the site uses and its
    recent jobs.

While the site is connected, LATW Cloud is its engine and the Engine setting is locked. To use
another engine, click Disconnect first; the site then goes back to the engine it had before you
connected.

If your browser blocks the window, the section shows a link to open it instead.

The model, LATW Credits or your own API key, the prompt, the glossary, the website
description
, the budget limits, the target languages, the translation editor and what
happens to outdated translations are set per site in LATW Cloud (Site settings in LATW Cloud
opens them). While the site is connected, the plugin does not let you change them here:

  • Settings → General: Model, API key, Processing Mode, Reasoning Effort and Website Description
    disappear.
  • Settings → Translation: the Translation Prompt is replaced by a link to LATW Cloud, and the
    Target Languages are the ones set in LATW Cloud, shown but not editable. When you connect, LATW
    Cloud starts from the languages you had chosen here; after that you change them in the site’s
    settings in LATW Cloud, and the plugin follows. Your own choice comes back if you disconnect. The
    same goes for the Translation Editor and Outdated Translations (PRO): shown as set in LATW
    Cloud (Site settings → Plugin), not editable here.
  • Glossary (PRO): the entries can’t be edited or imported; Export CSV still works, and LATW
    Cloud’s glossary imports that file as it is (terms in another source language than the glossary’s
    are skipped). The entries are kept and apply again if you disconnect.
  • Settings → Automation (PRO): automatic translation is not available – see below.
  • Settings → MCP (PRO): the MCP server is off, so AI assistants can’t translate on the site past
    LATW Cloud’s settings. Your MCP settings and token are kept and work again if you disconnect.
  • Settings → Advanced: Manual Check Responses is not used – nothing waits for WP-Cron. Send
    Only Text
    still applies: LATW Cloud reads the text of each field with placeholders instead of its
    HTML, as described in What Gets Translated?, unless you turn it off.
  • Dashboard: Cost Statistics count only translations made on this server. LATW Cloud translations
    are billed in LATW Cloud, and the History screen shows “LATW Cloud” in their Cost column.

Each LATW plugin connects on its own. If the site also runs another LATW plugin – LATW for Loco
Translate, for example – that plugin is a second site in LATW Cloud and counts towards your plan’s
site limit.

#Translating

Nothing changes in how you start a translation. Everything the plugin can translate goes through
LATW Cloud once it is the engine:

  • Posts, pages and products – the Translate button, bulk translation and Translate Again on
    the Translations screen.
  • Categories, tags and other terms – the Taxonomy Translation screen.
  • Strings – the String Translation screen.

After you click Translate, the message says which LATW Cloud job the work became (“Sent to LATW Cloud
as job #1042”). The items show In LATW Cloud in the Active Translation Queue and on the
Taxonomy and String Translation screens, and Cancel works as for any other engine. When the translation is written back it
appears on the History screen like any other, at $0.00 – LATW Cloud bills it, not your own API
key.

What gets translated follows the same rules as with every engine: a missing translation is
translated in full, and an outdated one the way you set under AI Translator → Settings →
Translation → Outdated Translations
(PRO; see Updating Outdated Translations). Translate Again
always translates the whole page.

You can also start translations from LATW Cloud itself: open the site there, go to its Content
tab, select posts, pages or products and click Translate. The same rules apply.

#Automatic translation

Automatic translation after a save (PRO) is not available while the site is connected to LATW
Cloud – it is coming to LATW Cloud in a later version. Nothing is translated on its own, and the
latwaitrp_translate_post / latwaitrp_translate_post_now developer actions do nothing. Your
Automation settings are kept and apply again if you disconnect. To cap spending, set the budget
limits
in the site’s settings in LATW Cloud.

#What is sent, and where

Nothing is sent until you connect the site. After that:

  • When you connect: the site address, its WPML languages, the plugin version and the email
    address of the administrator who clicked Connect.
  • When you translate: LATW Cloud is told which items and languages, then reads their text from
    the site and writes the translations back. For its Content tab it also lists your posts, pages and
    products – titles, translation status, word counts. Every request between LATW Cloud and your site
    is signed with a key only the two of them know; anything unsigned is refused.
  • On LATW’s side: the text goes to the AI provider of the model chosen for the site. LATW deletes
    it 7 days after the job finishes; costs and job details are kept.

Disconnecting stops all of this; the site then translates with the engine it had before you connected.

#Limitations

  • The address must stay the same. LATW Cloud does not follow redirects. If you move the site to
    another domain, switch between www and no www, or move from HTTP to HTTPS, connect it again.
  • Translations still waiting in the queue when you switch to LATW Cloud are not sent to it: they
    fail with a note saying so. Start them again.
  • In LATW Cloud’s Content tab you see posts, pages and products. Terms and strings are translated
    from this plugin’s screens.

#When LATW Cloud cannot reach the site

Test connection in the engine section asks LATW Cloud to call the site right now and tells you
what came back. The usual causes:

  • A firewall or security plugin (Wordfence, Cloudflare, your host’s WAF) blocks the requests.
    Allow requests to /wp-json/latw/v1/cloud/. LATW Cloud has no fixed IP addresses to allow, but
    every request it sends is signed, and the plugin refuses anything that is not.
  • The REST API is switched off or restricted to logged-in users. LATW Cloud needs it for the
    path above.
  • Password protection (basic auth) on the whole site.
  • The server clock is wrong. Signed requests are valid for five minutes either side, so a clock
    that is off by more than that makes every request fail. LATW Cloud says by how much it is off.

If LATW Cloud refuses a translation – not enough credits, no API key chosen for the site, a plan
limit – the message after Translate says why, and the items are marked as failed with that reason.

“Connection lost” in the engine section means the site’s WordPress security keys changed – some
security plugins regenerate them – and the stored connection can no longer be read. Click Connect
with LATW
again.

#Disconnecting

Disconnect in the engine section removes the connection from this site; LATW Cloud can no longer
read or write anything, and nothing can be translated until you connect again or choose another
engine. Translations already made stay on the site. To free the site in your plan, remove it in LATW
Cloud as well – disconnecting it there also disconnects the plugin.

#Developer reference

  • REST base: /wp-json/latw/v1/cloud/latw-ai-translator-for-wpml/ – POST only, every route
    signed.
  • To pair with another LATW panel (development, testing), put
    define('LATWAITR_CLOUD_URL', 'http://localhost:3000'); in wp-config.php, or use the
    latwaitr_cloud_url filter.
  • The engine id is latw-cloud. Rows translated by LATW Cloud carry that provider and the status
    cloud while LATW Cloud works on them. They go through latwaitr_translated_strings and fire
    latwaitr_translation_saved like any other translation.