Skip to content

Translation Engine – LATW Cloud

On this page

Available in the free version (version 2.8.0 and later). Sending translations to LATW Cloud from
wp-admin is a PRO feature.

LATW Cloud is LATW’s translation service. You connect your site to your LATW account, choose what to
translate in the LATW Cloud panel, and LATW Cloud translates it on LATW’s servers with an AI model
and writes the translations back into your site. Nothing runs on your server: no WP-Cron, no
timeouts, no API key in WordPress.

It works with the free version of LATW Multilingual – no PRO licence is needed.

It is a paid service, billed by LATW Cloud, not by this plugin. You pay with LATW Credits –
included in a LATW plan or bought in packs in LATW Cloud – or translate with your own AI provider key
there if your plan allows it. The cost of every job is shown before it starts, per site, language and
model. Translating sends your content to LATW’s servers and to the AI provider of the chosen model –
see What is sent, and where below.

#What you need before you start

  • A LATW account at app.latw.ai. The Free plan connects one site and
    translates with LATW Credits.
  • The languages you translate into, set up in LATW Multilingual → Settings → Languages.
  • 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.

#Connecting the site

  1. Go to LATW Multilingual → Settings → LATW Cloud. With LATW Multilingual PRO there is no such
    tab: go to LATW Multilingual → Settings → AI and choose LATW Cloud as the Engine instead
    (see With PRO below).
  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 page now says Connected
    and shows your plan, your LATW Credits balance, the model the site uses, its target languages and
    its recent jobs.

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

The model, LATW Credits or your own API key, the glossary, the budget limits and the
target languages are set per site in LATW Cloud – Open LATW Cloud takes you there.
When you connect, LATW Cloud starts from the languages enabled on the site; you can narrow them down
there.

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

You start translations in LATW Cloud: open the site there, go to its Content tab, select what to
translate and the languages, and click Translate. LATW Cloud shows the price first, from the words
that actually need translating. The Content tab offers what the plugin’s own screens do:

  • Posts, pages and custom post types – every content type switched on in Settings →
    Translation → Content Types
    , one tab each.
  • Taxonomies – categories, tags and the other taxonomies switched on in Settings → Translation
    → Taxonomies
    , one tab each.
  • Strings – the groups of the Strings screen: menus, widgets, theme options, blocks and the
    rest.
  • Themes & Plugins – the translation files of themes, plugins and WordPress itself. A language is
    offered only for a theme or plugin that already has a translation file in it: add the language on
    the Themes & Plugins screen first (Add language).

You can translate whole items or, for Strings and Themes & Plugins, pick single strings.

#What is sent for each item

LATW Cloud gets exactly what is still to translate, as the plugin decides it:

  • Posts and pages are sent as segments – only the paragraphs, headings, button labels and other
    passages that have no translation yet in that language (see Translation Memory and Segments).
    Text you wrote or corrected by hand is never sent and never replaced. Neighbouring translated
    passages go along as context, so the wording stays consistent, but are not translated or billed.
    Elementor and Divi pages are sent as their texts; the layout never leaves the site. A post whose
    translation is up to date is skipped, unless you choose Translate again in LATW Cloud.
  • Terms are sent whole: name, description and SEO texts. The slug is not sent; it is made from
    the translated name, as when you translate a term by hand.
  • Strings and theme/plugin files are sent string by string – only those without an up-to-date
    translation. Plural forms are sent once per grammatical form of the target language.

Pages built with WPBakery, Beaver Builder, Oxygen, Bricks or Brizy cannot be translated automatically
(their layout would be damaged); LATW Cloud reports them as refused. Translate them by hand.

#What you see on the site

Translations appear as soon as LATW Cloud writes them. Every write is listed on the History
screen with LATW Cloud as the model and a cost of $0.00 – LATW Cloud bills it, not your own key. A
translation of a post or term that the site could not accept – because the original was edited or
deleted in the meantime – is listed there too, as failed, with the reason.

A segment whose translation lost some formatting of the original (a link, bold text) is saved without
it; the History entry names it and the segment editor marks it, as for any automatic translation.

#With PRO

With LATW Multilingual PRO, LATW Cloud is one of the translation engines, and the Settings → LATW
Cloud
tab is not shown: the connection – Connect with LATW, the plan, Test connection,
Disconnect – is in Settings → AI, when LATW Cloud is chosen as the Engine. While the
site is connected, LATW Cloud is the engine for translations you start in wp-admin too: the Translate buttons, the bulk actions and the Taxonomies, Strings and
Themes & Plugins screens send their work to LATW Cloud as jobs, whatever engine is chosen under
Settings → AI. The message after Translate names the job (“Sent to LATW Cloud as job #1042”),
the queue shows the items as in LATW Cloud, and Cancel works there. Automatic translation on save
and the MCP server are off while the site is connected. See Translation Engine – AI Providers.

This works whether or not the PRO licence is active – LATW Cloud bills its translations itself.

#What is sent, and where

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

  • When you connect: the site address, the address of its LATW Cloud endpoint, its languages, the
    plugin version and the email address of the administrator who clicked Connect with LATW.
  • When you translate: LATW Cloud lists your content for its Content tab – titles, translation
    status, word counts – and reads the text of the items you translate, then writes the translations
    back. 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 Cloud does
    not store your source texts: they are processed only while a translation runs, and a finished
    translation is written straight back to your site. It is kept on LATW’s servers only if the site
    cannot be reached at that moment – for up to 7 days, until it can be delivered – and then deleted.
    Costs and job details are kept.

The service is run by LATW at app.latw.ai – see the
Privacy Policy and the
Terms of Use. Disconnecting stops all of
this.

#Limitations

  • Jobs are started in LATW Cloud. In the free version, nothing is sent from wp-admin, and there is
    no “in LATW Cloud” state or Cancel button on the site – a job is followed and cancelled in the LATW
    Cloud panel.
  • Editing an item while it is being translated. In a post, a passage you changed meanwhile simply
    stays to translate, and the rest of the translation is saved. A term, or a post field that is not
    split into segments, that changed meanwhile ends the item with an error (“The original changed after
    the translation started”), and LATW Cloud does not translate it again by itself – start it again in
    LATW Cloud.
  • A field that is not split into segments goes whole. Most fields are segments; a field that is
    not (some custom fields) is sent and billed in full each time it is translated.
  • 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.

#When LATW Cloud cannot reach the site

Test connection (on the LATW Cloud tab, or with PRO in Settings → AI) 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.

“Connection lost” in the connection 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.

If the site was disconnected in LATW Cloud, or connected again from a copy of the site (which replaces
its key), every admin page shows a notice that LATW Cloud no longer recognises the site, with
Connect again and Dismiss.

#Disconnecting

Disconnect in the connection section removes the connection from this site; LATW Cloud can no longer read or write
anything, and its jobs for the site stop. 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.

#Updating from PRO 2.7 or older

LATW Cloud used to be part of LATW Multilingual PRO. A site connected there stays connected after you
update both plugins – no new pairing. Until LATW Multilingual PRO is updated, its own LATW Cloud
connection keeps working under Settings → AI, and the Settings → LATW Cloud tab asks you to
update PRO. Once PRO is updated the connection stays under Settings → AI and the tab goes away.

#Developer reference

  • REST base: /wp-json/latw/v1/cloud/latw-multilingual/ – POST only, every route signed with HMAC.
  • To pair with another LATW panel (development, testing), put
    define( 'LATWM_CLOUD_URL', 'http://localhost:3000' ); in wp-config.php, or use the
    latwm_cloud_url filter. LATWMP_CLOUD_URL from older PRO versions is still honoured.
  • Options: latwm_cloud_connection (the secret is stored encrypted with a key derived from the site’s
    AUTH_SALT; not autoloaded) and latwm_cloud_lost.
  • The plugin keeps no record of LATW Cloud’s jobs. A document’s source_hash covers its fields that
    are not segments; a write whose fields changed since the read is refused as stale, a segment the
    post no longer has is skipped.
  • Hooks for add-ons: latwm_cloud_resource_handlers (filter, name => LATWM_Cloud_Handler: what LATW
    Cloud can translate), latwm_cloud_held_keys (filter: strings a read leaves out),
    latwm_cloud_po_source_locale (filter: the language a theme or plugin is written in, default
    en_US), latwm_cloud_local_settings (filter) and latwm_cloud_settings_saved (action),
    latwm_cloud_connected / latwm_cloud_disconnected (actions), latwm_cloud_saved (action
    $type, $id, $locale, $answer after every write or refusal), latwm_cloud_release (filter, a job
    ended without translating the items), latwm_cloud_tab_after (action on the tab),
    latwm_cloud_settings_url (filter: the admin page holding the connection). An add-on can show the
    connection on its own screen with LATWM_Cloud_Admin::render_connection() and
    LATWM_Cloud_Admin::enqueue_assets() – LATW Multilingual PRO does so in Settings → AI and removes the
    tab through latwm_settings_tabs.
  • Writes go through LATWM_Content_IO::save_post() / save_object() with the origin machine; the
    latwm_translate_slug filter (default off) decides whether a post’s translation gets a slug made from
    its translated title.