{"id":188,"date":"2026-11-14T17:45:07","date_gmt":"2026-11-14T17:45:07","guid":{"rendered":"https:\/\/docs.latw.ai\/uncategorized\/latw-cloud-2\/"},"modified":"2026-11-14T17:45:07","modified_gmt":"2026-11-14T17:45:07","slug":"latw-cloud-2","status":"publish","type":"post","link":"https:\/\/docs.latw.ai\/pl\/latw-multilingual\/latw-cloud-2\/","title":{"rendered":"Translation Engine &#8211; LATW Cloud"},"content":{"rendered":"<p><em>Available in the free version (version 2.8.0 and later). Sending translations to LATW Cloud from<br \/>\nwp-admin is a <strong>PRO<\/strong> feature.<\/em><\/p>\n<p>LATW Cloud is LATW&#8217;s translation service. You connect your site to your LATW account, choose what to<br \/>\ntranslate in the LATW Cloud panel, and LATW Cloud translates it on LATW&#8217;s servers with an AI model<br \/>\nand writes the translations back into your site. Nothing runs on your server: no WP-Cron, no<br \/>\ntimeouts, no API key in WordPress.<\/p>\n<p>It works with the <strong>free version<\/strong> of LATW Multilingual &#8211; no PRO licence is needed.<\/p>\n<p><strong>It is a paid service, billed by LATW Cloud, not by this plugin.<\/strong> You pay with LATW Credits &#8211;<br \/>\nincluded in a LATW plan or bought in packs in LATW Cloud &#8211; or translate with your own AI provider key<br \/>\nthere if your plan allows it. The cost of every job is shown before it starts, per site, language and<br \/>\nmodel. Translating sends your content to LATW&#8217;s servers and to the AI provider of the chosen model &#8211;<br \/>\nsee <em>What is sent, and where<\/em> below.<\/p>\n<h2>What you need before you start<\/h2>\n<ul>\n<li>A <strong>LATW account<\/strong> at <a href=\"https:\/\/app.latw.ai\/\">app.latw.ai<\/a>. The <strong>Free<\/strong> plan connects one site and<br \/>\ntranslates with LATW Credits.<\/li>\n<li>The languages you translate into, set up in <strong>LATW Multilingual \u2192 Settings \u2192 Languages<\/strong>.<\/li>\n<li>A site <strong>LATW Cloud can reach from the internet over HTTPS<\/strong>. LATW Cloud calls your site to read what<br \/>\nneeds translating and to write the translations, so a site on your own computer, or a staging site<br \/>\nbehind a password, cannot use it.<\/li>\n<\/ul>\n<h2>Connecting the site<\/h2>\n<ol>\n<li>Go to <strong>LATW Multilingual \u2192 Settings \u2192 LATW Cloud<\/strong>. With LATW Multilingual PRO there is no such<br \/>\ntab: go to <strong>LATW Multilingual \u2192 Settings \u2192 AI<\/strong> and choose <strong>LATW Cloud<\/strong> as the <strong>Engine<\/strong> instead<br \/>\n(see <em>With PRO<\/em> below).<\/li>\n<li>Click <strong>Connect with LATW<\/strong>. A LATW window opens; sign in if you are asked to.<\/li>\n<li>Check that the window names this site, then click <strong>Authorize<\/strong>.<\/li>\n<li>The window closes on its own once LATW Cloud has reached the site. The page now says <strong>Connected<\/strong><br \/>\nand shows your plan, your LATW Credits balance, the model the site uses, its target languages and<br \/>\nits recent jobs.<\/li>\n<\/ol>\n<p>If your browser blocks the window, the page shows a link to open it instead.<\/p>\n<p>The <strong>model<\/strong>, <strong>LATW Credits or your own API key<\/strong>, the <strong>glossary<\/strong>, the <strong>budget limits<\/strong> and the<br \/>\n<strong>target languages<\/strong> are set per site in LATW Cloud &#8211; <strong>Open LATW Cloud<\/strong> takes you there.<br \/>\nWhen you connect, LATW Cloud starts from the languages enabled on the site; you can narrow them down<br \/>\nthere.<\/p>\n<p>Each LATW plugin connects on its own. If the site also runs another LATW plugin &#8211; LATW for Loco<br \/>\nTranslate, for example &#8211; that plugin is a second site in LATW Cloud and counts towards your plan&#8217;s<br \/>\nsite limit.<\/p>\n<h2>Translating<\/h2>\n<p>You start translations in LATW Cloud: open the site there, go to its <strong>Content<\/strong> tab, select what to<br \/>\ntranslate and the languages, and click <strong>Translate<\/strong>. LATW Cloud shows the price first, from the words<br \/>\nthat actually need translating. The Content tab offers what the plugin&#8217;s own screens do:<\/p>\n<ul>\n<li><strong>Posts, pages and custom post types<\/strong> &#8211; every content type switched on in <strong>Settings \u2192<br \/>\nTranslation \u2192 Content Types<\/strong>, one tab each.<\/li>\n<li><strong>Taxonomies<\/strong> &#8211; categories, tags and the other taxonomies switched on in <strong>Settings \u2192 Translation<br \/>\n\u2192 Taxonomies<\/strong>, one tab each.<\/li>\n<li><strong>Strings<\/strong> &#8211; the groups of the <strong>Strings<\/strong> screen: menus, widgets, theme options, blocks and the<br \/>\nrest.<\/li>\n<li><strong>Themes &amp; Plugins<\/strong> &#8211; the translation files of themes, plugins and WordPress itself. A language is<br \/>\noffered only for a theme or plugin that already has a translation file in it: add the language on<br \/>\nthe <strong>Themes &amp; Plugins<\/strong> screen first (<strong>Add language<\/strong>).<\/li>\n<\/ul>\n<p>You can translate whole items or, for Strings and Themes &amp; Plugins, pick single strings.<\/p>\n<h3>What is sent for each item<\/h3>\n<p>LATW Cloud gets exactly what is still to translate, as the plugin decides it:<\/p>\n<ul>\n<li><strong>Posts and pages<\/strong> are sent as segments &#8211; only the paragraphs, headings, button labels and other<br \/>\npassages that have no translation yet in that language (see <em>Translation Memory and Segments<\/em>).<br \/>\nText you wrote or corrected by hand is never sent and never replaced. Neighbouring translated<br \/>\npassages go along as context, so the wording stays consistent, but are not translated or billed.<br \/>\nElementor and Divi pages are sent as their texts; the layout never leaves the site. A post whose<br \/>\ntranslation is up to date is skipped, unless you choose <strong>Translate again<\/strong> in LATW Cloud.<\/li>\n<li><strong>Terms<\/strong> are sent whole: name, description and SEO texts. The slug is not sent; it is made from<br \/>\nthe translated name, as when you translate a term by hand.<\/li>\n<li><strong>Strings and theme\/plugin files<\/strong> are sent string by string &#8211; only those without an up-to-date<br \/>\ntranslation. Plural forms are sent once per grammatical form of the target language.<\/li>\n<\/ul>\n<p>Pages built with WPBakery, Beaver Builder, Oxygen, Bricks or Brizy cannot be translated automatically<br \/>\n(their layout would be damaged); LATW Cloud reports them as refused. Translate them by hand.<\/p>\n<h3>What you see on the site<\/h3>\n<p>Translations appear as soon as LATW Cloud writes them. Every write is listed on the <strong>History<\/strong><br \/>\nscreen with <strong>LATW Cloud<\/strong> as the model and a cost of $0.00 &#8211; LATW Cloud bills it, not your own key. A<br \/>\ntranslation of a post or term that the site could not accept &#8211; because the original was edited or<br \/>\ndeleted in the meantime &#8211; is listed there too, as failed, with the reason.<\/p>\n<p>A segment whose translation lost some formatting of the original (a link, bold text) is saved without<br \/>\nit; the History entry names it and the segment editor marks it, as for any automatic translation.<\/p>\n<h2>With PRO<\/h2>\n<p>With LATW Multilingual PRO, LATW Cloud is one of the translation engines, and the <strong>Settings \u2192 LATW<br \/>\nCloud<\/strong> tab is not shown: the connection &#8211; <strong>Connect with LATW<\/strong>, the plan, <strong>Test connection<\/strong>,<br \/>\n<strong>Disconnect<\/strong> &#8211; is in <strong>Settings \u2192 AI<\/strong>, when <strong>LATW Cloud<\/strong> is chosen as the <strong>Engine<\/strong>. While the<br \/>\nsite 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<br \/>\nThemes &amp; Plugins screens send their work to LATW Cloud as jobs, whatever engine is chosen under<br \/>\n<strong>Settings \u2192 AI<\/strong>. The message after Translate names the job (&#8220;Sent to LATW Cloud as job #1042&#8221;),<br \/>\nthe queue shows the items as in LATW Cloud, and <strong>Cancel<\/strong> works there. Automatic translation on save<br \/>\nand the MCP server are off while the site is connected. See <em>Translation Engine &#8211; AI Providers<\/em>.<\/p>\n<p>This works whether or not the PRO licence is active &#8211; LATW Cloud bills its translations itself.<\/p>\n<h2>What is sent, and where<\/h2>\n<p>Nothing is sent until you connect the site. After that:<\/p>\n<ul>\n<li><strong>When you connect:<\/strong> the site address, the address of its LATW Cloud endpoint, its languages, the<br \/>\nplugin version and the email address of the administrator who clicked <strong>Connect with LATW<\/strong>.<\/li>\n<li><strong>When you translate:<\/strong> LATW Cloud lists your content for its Content tab &#8211; titles, translation<br \/>\nstatus, word counts &#8211; and reads the text of the items you translate, then writes the translations<br \/>\nback. Every request between LATW Cloud and your site is signed with a key only the two of them know;<br \/>\nanything unsigned is refused.<\/li>\n<li><strong>On LATW&#8217;s side:<\/strong> the text goes to the AI provider of the model chosen for the site. LATW Cloud does<br \/>\nnot store your source texts: they are processed only while a translation runs, and a finished<br \/>\ntranslation is written straight back to your site. It is kept on LATW&#8217;s servers only if the site<br \/>\ncannot be reached at that moment &#8211; for up to 7 days, until it can be delivered &#8211; and then deleted.<br \/>\nCosts and job details are kept.<\/li>\n<\/ul>\n<p>The service is run by LATW at <a href=\"https:\/\/app.latw.ai\/\">app.latw.ai<\/a> &#8211; see the<br \/>\n<a href=\"https:\/\/llm-automatic-translation.top\/privacy-policy\/\">Privacy Policy<\/a> and the<br \/>\n<a href=\"https:\/\/llm-automatic-translation.top\/terms-of-service\/\">Terms of Use<\/a>. Disconnecting stops all of<br \/>\nthis.<\/p>\n<h2>Limitations<\/h2>\n<ul>\n<li><strong>Jobs are started in LATW Cloud.<\/strong> In the free version, nothing is sent from wp-admin, and there is<br \/>\nno &#8220;in LATW Cloud&#8221; state or Cancel button on the site &#8211; a job is followed and cancelled in the LATW<br \/>\nCloud panel.<\/li>\n<li><strong>Editing an item while it is being translated.<\/strong> In a post, a passage you changed meanwhile simply<br \/>\nstays to translate, and the rest of the translation is saved. A term, or a post field that is not<br \/>\nsplit into segments, that changed meanwhile ends the item with an error (&#8220;The original changed after<br \/>\nthe translation started&#8221;), and LATW Cloud does not translate it again by itself &#8211; start it again in<br \/>\nLATW Cloud.<\/li>\n<li><strong>A field that is not split into segments goes whole.<\/strong> Most fields are segments; a field that is<br \/>\nnot (some custom fields) is sent and billed in full each time it is translated.<\/li>\n<li><strong>The address must stay the same.<\/strong> LATW Cloud does not follow redirects. If you move the site to<br \/>\nanother domain, switch between <code>www<\/code> and no <code>www<\/code>, or move from HTTP to HTTPS, connect it again.<\/li>\n<\/ul>\n<h2>When LATW Cloud cannot reach the site<\/h2>\n<p><strong>Test connection<\/strong> (on the <strong>LATW Cloud<\/strong> tab, or with PRO in <strong>Settings \u2192 AI<\/strong>) asks LATW Cloud to call the site right now and tells you what came back.<br \/>\nThe usual causes:<\/p>\n<ul>\n<li><strong>A firewall or security plugin<\/strong> (Wordfence, Cloudflare, your host&#8217;s WAF) blocks the requests.<br \/>\nAllow requests to <code>\/wp-json\/latw\/v1\/cloud\/<\/code>. LATW Cloud has no fixed IP addresses to allow, but every<br \/>\nrequest it sends is signed, and the plugin refuses anything that is not.<\/li>\n<li><strong>The REST API is switched off<\/strong> or restricted to logged-in users. LATW Cloud needs it for the path<br \/>\nabove.<\/li>\n<li><strong>Password protection<\/strong> (basic auth) on the whole site.<\/li>\n<li><strong>The server clock is wrong.<\/strong> Signed requests are valid for five minutes either side, so a clock<br \/>\nthat is off by more than that makes every request fail.<\/li>\n<\/ul>\n<p><strong>&#8220;Connection lost&#8221;<\/strong> in the connection section means the site&#8217;s WordPress security keys changed &#8211; some security<br \/>\nplugins regenerate them &#8211; and the stored connection can no longer be read. Click <strong>Connect with<br \/>\nLATW<\/strong> again.<\/p>\n<p>If the site was disconnected in LATW Cloud, or connected again from a copy of the site (which replaces<br \/>\nits key), every admin page shows a notice that LATW Cloud no longer recognises the site, with<br \/>\n<strong>Connect again<\/strong> and <strong>Dismiss<\/strong>.<\/p>\n<h2>Disconnecting<\/h2>\n<p><strong>Disconnect<\/strong> in the connection section removes the connection from this site; LATW Cloud can no longer read or write<br \/>\nanything, and its jobs for the site stop. Translations already made stay on the site. To free the site<br \/>\nin your plan, remove it in LATW Cloud as well &#8211; disconnecting it there also disconnects the plugin.<\/p>\n<h2>Updating from PRO 2.7 or older<\/h2>\n<p>LATW Cloud used to be part of LATW Multilingual PRO. A site connected there stays connected after you<br \/>\nupdate both plugins &#8211; no new pairing. Until LATW Multilingual PRO is updated, its own LATW Cloud<br \/>\nconnection keeps working under <strong>Settings \u2192 AI<\/strong>, and the <strong>Settings \u2192 LATW Cloud<\/strong> tab asks you to<br \/>\nupdate PRO. Once PRO is updated the connection stays under <strong>Settings \u2192 AI<\/strong> and the tab goes away.<\/p>\n<h2>Developer reference<\/h2>\n<ul>\n<li>REST base: <code>\/wp-json\/latw\/v1\/cloud\/latw-multilingual\/<\/code> &#8211; <code>POST<\/code> only, every route signed with HMAC.<\/li>\n<li>To pair with another LATW panel (development, testing), put<br \/>\n<code>define( 'LATWM_CLOUD_URL', 'http:\/\/localhost:3000' );<\/code> in <code>wp-config.php<\/code>, or use the<br \/>\n<code>latwm_cloud_url<\/code> filter. <code>LATWMP_CLOUD_URL<\/code> from older PRO versions is still honoured.<\/li>\n<li>Options: <code>latwm_cloud_connection<\/code> (the secret is stored encrypted with a key derived from the site&#8217;s<br \/>\n<code>AUTH_SALT<\/code>; not autoloaded) and <code>latwm_cloud_lost<\/code>.<\/li>\n<li>The plugin keeps no record of LATW Cloud&#8217;s jobs. A document&#8217;s <code>source_hash<\/code> covers its fields that<br \/>\nare not segments; a write whose fields changed since the read is refused as <code>stale<\/code>, a segment the<br \/>\npost no longer has is skipped.<\/li>\n<li>Hooks for add-ons: <code>latwm_cloud_resource_handlers<\/code> (filter, name =&gt; <code>LATWM_Cloud_Handler<\/code>: what LATW<br \/>\nCloud can translate), <code>latwm_cloud_held_keys<\/code> (filter: strings a read leaves out),<br \/>\n<code>latwm_cloud_po_source_locale<\/code> (filter: the language a theme or plugin is written in, default<br \/>\n<code>en_US<\/code>), <code>latwm_cloud_local_settings<\/code> (filter) and <code>latwm_cloud_settings_saved<\/code> (action),<br \/>\n<code>latwm_cloud_connected<\/code> \/ <code>latwm_cloud_disconnected<\/code> (actions), <code>latwm_cloud_saved<\/code> (action<br \/>\n<code>$type, $id, $locale, $answer<\/code> after every write or refusal), <code>latwm_cloud_release<\/code> (filter, a job<br \/>\nended without translating the items), <code>latwm_cloud_tab_after<\/code> (action on the tab),<br \/>\n<code>latwm_cloud_settings_url<\/code> (filter: the admin page holding the connection). An add-on can show the<br \/>\nconnection on its own screen with <code>LATWM_Cloud_Admin::render_connection()<\/code> and<br \/>\n<code>LATWM_Cloud_Admin::enqueue_assets()<\/code> &#8211; LATW Multilingual PRO does so in Settings \u2192 AI and removes the<br \/>\ntab through <code>latwm_settings_tabs<\/code>.<\/li>\n<li>Writes go through <code>LATWM_Content_IO::save_post()<\/code> \/ <code>save_object()<\/code> with the origin <code>machine<\/code>; the<br \/>\n<code>latwm_translate_slug<\/code> filter (default off) decides whether a post&#8217;s translation gets a slug made from<br \/>\nits translated title.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>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&#8217;s translation service.\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_latwm_translated_slug":"","footnotes":""},"categories":[4],"tags":[],"class_list":["post-188","post","type-post","status-publish","format-standard","hentry","category-latw-multilingual"],"_links":{"self":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/188","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/comments?post=188"}],"version-history":[{"count":1,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/188\/revisions"}],"predecessor-version":[{"id":220,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/188\/revisions\/220"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=188"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=188"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=188"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}