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
Serving those pages is built to be cheap. Gloty compiles your translations into a PHP cache file that your server's OPcache holds in shared memory, so once it is warm a translated page view costs no database queries for translation at all, and the translations take almost no memory in the request. That is aimed squarely at ordinary shared hosting with no object cache, which is where a translation plugin normally slows a site down most. Where the technique is unavailable, Gloty serves from the database instead and the page is still correct.<\/p>\n\n
The picker offers 38 languages, each with the right hreflang code emitted for it. That list is deliberately shorter than it could be: it is the set both AI engines' vendors say their models support, rather than every language code in existence. A translation you cannot judge the quality of is worth less than one you can, so Gloty offers the ones where the engines are known to be strong, and every translation it produces is editable by hand.<\/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 Whether Gloty may compile your translations into a PHP cache file for OPcache to hold in memory. The value passed in is Gloty's own verdict on whether the server can benefit \u2014 return Returning Defining The largest cache file Gloty will write, in bytes. Default 8 MB. A translation set that would exceed it keeps using the database.<\/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 gives you a one-time free allowance to try it 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 Ask and we will look at it. The list is the set of languages the AI engines' own vendors say their models support, which is why it is shorter than the language list you may have seen on other plugins. Adding one means checking that the current engines actually handle it rather than just producing confident-looking output, so it is a real answer rather than an automatic yes.<\/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 Serving a translated page is designed to cost nothing extra. Gloty compiles your translations and your glossary into a PHP cache file kept in your server's OPcache, so once it is warm a page view runs no database queries to translate, makes no remote call, and holds the translations in shared memory rather than copying them into every request.<\/p>\n\n The cache is written in the background, never during a visitor's page view, and rebuilds within about a minute of a translation changing. Until it exists \u2014 a fresh install, or just after an edit \u2014 pages are served from the database exactly as earlier versions did: correct, just not yet as fast.<\/p>\n\n If your host has no OPcache, if the uploads directory is not writable, or if a cache file is ever damaged, Gloty notices and serves from the database instead, and reports it under Dashboard \u2192 Issues. Nothing about this can make a page render incorrectly, only more slowly.<\/p><\/dd>\n Only one place: a \n
\n
External services<\/h3>\n\n
\n
https:\/\/gloty-api.wp-shelf.com<\/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
Filters<\/h3>\n\n
gloty_compiled_map_enabled<\/h4>\n\n
false<\/code> to switch the feature off entirely, in which case translations are served from the object cache, a transient, or the database, exactly as in earlier versions.<\/p>\n\nadd_filter( 'gloty_compiled_map_enabled', '__return_false' );\n<\/code><\/pre>\n\ntrue<\/code> forces it on where Gloty could not confirm OPcache is active \u2014 useful when opcache.restrict_api<\/code> hides the OPcache status from plugin code. Do not force it on where OPcache is genuinely off: every request would then compile the cache file from source, which is slower than the database read it replaces.<\/p>\n\nGLOTY_DISABLE_COMPILED_MAP<\/code> as true in wp-config.php<\/code> disables it before any filter can run, and Gloty honours WordPress's own DISALLOW_FILE_MODS<\/code> constant without any configuration.<\/p>\n\ngloty_compiled_map_max_bytes<\/h4>\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
My language isn't in the list. Can you add it?<\/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
Will this slow my site down?<\/h3><\/dt>\n
Where does Gloty write files?<\/h3><\/dt>\n
gloty-cache<\/code> folder inside your uploads directory, holding the compiled translation cache described above (with wp-content\/cache\/gloty<\/code> as a fallback if uploads is not writable). The folder carries an index.php and .htaccess so the files are not browsable, and each file refuses to output anything if requested directly. Deactivating the plugin deletes them; uninstalling removes the folder too, and only ever removes files Gloty can prove it wrote.<\/p><\/dd>\n\n<\/dl>\n\n\n1.32.3<\/h4>\n\n
\n
1.32.2<\/h4>\n\n
\n
1.32.1<\/h4>\n\n
\n
1.32.0<\/h4>\n\n
\n
gloty_compiled_map_enabled<\/code> filter, and Gloty respects DISALLOW_FILE_MODS<\/code>.<\/li>\n1.31.0<\/h4>\n\n
\n
https:\/\/gloty-api.wp-shelf.com<\/code>. Sites already connected are moved across automatically on the next admin page load; a self-hosted or staging URL you set yourself is left untouched. No action needed, and nothing about how translation works has changed.<\/li>\n<\/ul>\n\n1.30.1<\/h4>\n\n
\n
1.29.2<\/h4>\n\n
\n