Gloty translates your WordPress site with AI machine translation, then stores every translation in your own database and serves it from there. Rendering a translated page never calls a remote service \u2014 page delivery stays local and deterministic even if the translation service is slow or unreachable.<\/p>\n\n
Producing a translation does require an external service, because machine translation is not something WordPress can do locally. Gloty sends the text that needs translating to the hosted Gloty translator service, which translates it and returns the result to your site in the background. The results land in your WordPress database, are editable by hand, and keep serving with no further external calls.<\/p>\n\n
Key Features:<\/strong><\/p>\n\n How it works:<\/strong><\/p>\n\n Translation requires an external machine-translation service. See External services<\/strong> below for exactly what is sent and to whom.<\/p>\n\n Documentation: https:\/\/wp-shelf.com\/gloty\/docs\/<\/p>\n\n Gloty cannot produce translations without an external machine-translation service, because machine translation is not something WordPress can do locally. This section describes every external request the plugin makes, what it sends, and when.<\/p>\n\n Nothing is sent anywhere until you have connected your site and translation has been triggered (by a scan, a Translate action, or scheduled background dispatch). Serving an already-translated page makes no external request at all.<\/p>\n\n 1. The Gloty translator service<\/strong><\/p>\n\n All translation work is performed by the hosted Gloty translator service. The plugin does not contact machine-translation providers directly; it sends work to the Gloty service, which selects and calls the translation engine on your behalf and delivers the results back to your site.<\/p>\n\n The Gloty service in turn passes your text to the AI translation engine it selects for the batch \u2014 OpenAI or Google Gemini. Their terms apply to that processing:<\/p>\n\n 2. WordPress.org translation packs<\/strong><\/p>\n\n When you enable a language, Gloty asks WordPress.org to install the official WordPress and plugin language packs for that locale, using WordPress core's own updater. This is the same request WordPress itself makes and sends no site content.<\/p>\n\n Gloty does not send analytics, telemetry, or usage tracking anywhere.<\/p>\n\n The admin interface is compiled from JavaScript sources before release. The uncompiled, human-readable sources for everything in The setup guide covers each step in more detail: https:\/\/wp-shelf.com\/gloty\/docs\/getting-started.html<\/p>\n\n\n Yes. Producing translations requires a connection to the Gloty translator service, set up under Gloty \u2192 Connection. There is a free tier. Without a connection, Gloty can still store, manage, and serve translations you already have, but it cannot create new ones.<\/p><\/dd>\n The plugin itself is free and GPL-licensed. Translation runs through the Gloty service, which has a free tier with a monthly character allowance and paid plans for higher volume and more sites. Every plan translates on the same AI engines. Your existing translations continue to serve regardless of plan or status, because they live in your own database.<\/p><\/dd>\n Your translations are stored in your own WordPress database, and translated pages are served from there with no external call. However, producing a translation in the first place does send the source text to an external machine-translation service \u2014 see External services<\/strong> above for exactly what is sent and to whom.<\/p><\/dd>\n Yes. Gloty captures translatable text from rendered output as well as from WordPress entities, so it works with Elementor, Beaver Builder, Divi, and other page builders.<\/p><\/dd>\n Yes. Go to Gloty \u2192 Translations, find the string, and edit it. Manual edits are marked as such and are never overwritten by later machine sync.<\/p><\/dd>\n Yes. Gloty translates product titles, descriptions, attributes, and the cart and checkout pages, including WooCommerce's AJAX cart fragments.<\/p>\n\n Order emails are not translated. They are sent outside the page rendering that Gloty works through, so a customer who ordered in German still receives the confirmation in your site's source language.<\/p><\/dd>\n Deactivating stops translated URLs from being served but leaves all data in place. Deleting the plugin runs an uninstall routine that removes Gloty's tables and options, so export anything you want to keep first.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
External services<\/h3>\n\n
\n
https:\/\/api-production-3261.up.railway.app<\/code> (overridable by defining the GLOTY_SERVICE_URL<\/code> constant, for example to point at a self-hosted instance of the service).<\/li>\n\n
Source code<\/h3>\n\n
build\/<\/code> ship inside the plugin under src\/<\/code>, together with the build configuration in webpack.config.js<\/code> and package.json<\/code>. The bundles are produced by @wordpress\/scripts<\/code> (webpack) via the build<\/code> script in package.json<\/code>; no minified or obfuscated code is included without its source.<\/p>\n\n\n\n
gloty<\/code> folder to \/wp-content\/plugins\/<\/code><\/li>\n\n
Do I need an account?<\/h3><\/dt>\n
How much does it cost?<\/h3><\/dt>\n
Are translations stored on an external server?<\/h3><\/dt>\n
Does it work with page builders?<\/h3><\/dt>\n
Can I edit translations manually?<\/h3><\/dt>\n
Does it support WooCommerce?<\/h3><\/dt>\n
What happens to my translations if I deactivate Gloty?<\/h3><\/dt>\n
1.29.2<\/h4>\n\n
\n