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 — page delivery stays local and deterministic even if the translation service is slow or unreachable
PricingFree downloadThe WordPress.org download is free. Pro versions, add-ons or external services may cost extra.
CompatibilityRequires WordPress 6.4 and PHP 8.1.
SourceWordPress plugins · Nov 1, 2026
01 / Source details
Aboutthistool.
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 — page delivery stays local and deterministic even if the translation service is slow or unreachable.
The plugin is free. New customers can try the hosted translation service with a one-time allowance of 50,000 characters for one site, with no card required. Start the free Gloty trial or view translation plans and the one-time pack . Saved translations keep serving locally after the allowance is used; generating more translations needs available hosted allowance.
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.
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.
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.
Key Features:
38 languages — the set both AI engines’ vendors list as supported, each with the right hreflang code
Your database, your translations — stored locally in WordPress, never fetched remotely at render time
Fast on slow hosting — translations compile into a cache your server holds in memory, so serving a translated page costs no database queries once warm; it falls back to the database safely if your host cannot do that
Automatic page translation — captures page output, extracts translatable text, queues it for translation
Entity-aware — posts, pages, taxonomies, and template strings are tracked as distinct sources with stale detection
Edit any translation — review and correct translations from Gloty → Translations
Prepare a language before publishing it — translate in the background, check it over, then show it to visitors
Let someone correct translations without making them an administrator — optionally limited to one language
A different image per language — for screenshots, diagrams and packaging that carry words
The language switcher in your menu — as ordinary menu items your theme styles, plus a block
A sitemap of your translated pages — so search engines can actually find them
Translate content that loads after the page — load-more, AJAX filters and search panels
Manual edits are protected — machine sync never silently overwrites a human correction
Glossary — terms that must never be translated, or that must always render a specific way per language, promotable in one click from any translation you are looking at
01Install Gloty and connect your site to the Gloty translator service
02Add your target languages
03Gloty discovers translatable content from your posts, taxonomies, and template strings
04Translation runs in the background and the results are written to your database
05Visitors get translated pages under language-prefixed URLs (/fr/, /de/, …) and can switch languages from the switcher
Translation requires an external machine-translation service. See External services below for exactly what is sent and to whom.
Documentation: https://wp-shelf.com/gloty/docs/
External services
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.
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.
1. The Gloty translator service
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.
Service host: https://gloty-api.wp-shelf.com (overridable by defining the GLOTY_SERVICE_URL constant, for example to point at a self-hosted instance of the service).
What is sent: the source text to be translated (page, post, taxonomy, and template strings from your site), the source and target language codes, your site URL, and a per-site API token and license key used to identify and authenticate your site.
What is not sent: Gloty does not read text off your cart, checkout, order or account pages, because those are written about one customer rather than for every visitor, and it skips any string carrying an email address that is not your own. If a page of yours shows a customer’s details and you translate it, tell us — that is a gap, not a setting.
When: on connection verification, while dispatching queued translation batches, when polling for results, and when the service delivers results back to your site over a signed webhook.
Who: the Gloty translator service, operated by WP Shelf.
Terms of service: https://wp-shelf.com/terms
Privacy policy: https://wp-shelf.com/privacy
The Gloty service in turn passes your text to the AI translation engine it selects for the batch — OpenAI or Google Gemini. Their terms apply to that processing:
Google Gemini — https://ai.google.dev/terms / https://policies.google.com/privacy
2. WordPress.org translation packs
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.
Gloty does not send analytics, telemetry, or usage tracking anywhere. The optional browser page-view counter described in the changelog posts to your own site’s REST API and nowhere else: it is not an external request, it carries only the language of the page, and no third party is involved.
Filters
gloty_compiled_map_enabled
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 — return false 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.
Returning true forces it on where Gloty could not confirm OPcache is active — useful when opcache.restrict_api 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.
Defining GLOTY_DISABLE_COMPILED_MAP as true in wp-config.php disables it before any filter can run, and Gloty honours WordPress’s own DISALLOW_FILE_MODS constant without any configuration.
gloty_compiled_map_max_bytes
The largest cache file Gloty will write, in bytes. Default 8 MB. A translation set that would exceed it keeps using the database.
Source code
The admin interface is compiled from JavaScript sources before release. The uncompiled, human-readable sources for everything in build/ ship inside the plugin under src/ , together with the build configuration in webpack.config.js and package.json . The bundles are produced by @wordpress/scripts (webpack) via the build script in package.json ; no minified or obfuscated code is included without its source.
Security
Found a security issue? Please email hello@wp-shelf.com rather than opening a public support thread — a forum post is world-readable the moment you send it, on a plugin installed on other people’s sites. You will get an acknowledgement within 72 hours, and credit in the changelog unless you would rather not have it.
How do I review translations captured for one post or term?
Open Translations, find a row with a Post or Term context, and choose Review this post or Review this term in its row actions. The workspace groups the cached strings captured for that e
See it in action
Screenshots & previews.
Demo data: Every language on one screen: what is finished, what is still queued, and what went out of date when you edited the English. Italian is being translated in the background and is not shown to visitors yet. All of it is counted from your own database.Demo data: Every translation is a row you can read and correct in place. Machine output is marked Synced, a correction you typed is marked Manually Edited and a later sync never overwrites it, and a row whose English changed is marked Stale.Demo data: Which languages your visitors actually read, counted on your own site over 7, 30 or 90 days, with each language's shape beside its share. No cookie, no fingerprint, no IP address, and nothing sent anywhere.
02 / Source details
Gettingstarted.
01Upload the gloty folder to /wp-content/plugins/
02Activate the plugin through the ‘Plugins’ menu in WordPress
03Open WP Shelf → Gloty → Setup . New customers can start the free hosted trial: 50,000 characters once for one site, with no card required. Already have an account or license? Choose I already have an account or license , copy your Gloty key from the WP Shelf dashboard, and connect with that account’s email address.
04Add your target languages in Setup or under WP Shelf → Gloty → Languages
05Follow Setup to scan content and begin background translation. Review the translations before making a language public.
The setup guide covers each step in more detail: https://wp-shelf.com/gloty/docs/getting-started.html
03 / Source details
Frequently asked questions.
Do I need an account?
Yes, to generate translations with the hosted Gloty service. Open WP Shelf → Gloty → Setup to connect. New customers can start a one-time free trial of 50,000 characters for one site, with no card required. If you already have an account or license, choose I already have an account or license and use your Gloty key from the WP Shelf dashboard with that account’s email address. Without a connection, Gloty can still store, manage, and serve translations you already have, but it cannot generate new ones.
How much does it cost?
The plugin itself is free and GPL-licensed. The hosted service gives new customers 50,000 characters once for one site, with no card required. Paid monthly plans and a one-time translation pack are available for more work; see Gloty translation plans . 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.
Are translations stored on an external server?
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 — see External services above for exactly what is sent and to whom.
My language isn’t in the list. Can you add it?
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.
Does it work with page builders?
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.
Can I edit translations manually?
Yes. Go to Gloty → Translations, find the string, and edit it. Manual edits are marked as such and are never overwritten by later machine sync.
Does it support WooCommerce?
Yes. Gloty translates product titles, descriptions, attributes, and the cart and checkout pages, including WooCommerce’s AJAX cart fragments.
For orders placed through classic or block checkout, Gloty records the customer’s active language on the order and uses it when WooCommerce sends order emails, including later status updates. Email text uses installed WooCommerce language packs and translations already saved on your site; prepare the target language before relying on it for customer emails. Orders without a recorded Gloty language keep the site’s normal email language. Check custom email templates and extensions on your store; email delivery does not wait for fresh AI translations.
What happens to my translations if I deactivate Gloty?
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.
Will this slow my site down?
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.
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 — a fresh install, or just after an edit — pages are served from the database exactly as earlier versions did: correct, just not yet as fast.
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 → Issues. Nothing about this can make a page render incorrectly, only more slowly.
Where does Gloty write files?
Only one place: a gloty-cache folder inside your uploads directory, holding the compiled translation cache described above (with wp-content/cache/gloty 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.
Website LLMs.txt and LLMs-Full.txt Generator is an LLMs.txt generator and llms-full.txt generator for WordPress. It helps site owners generate, manage, preview, validate, and serve AI discovery files from published public content. Use it to create structured /llms.txt and optional /llms-full.txt end
EngageDock AI is a customizable floating contact widget for WordPress websites that want more leads and faster visitor communication. It helps small businesses turn website traffic into calls, texts, emails, and callback requests from one clean contact panel. Key Features: Click-to-Call – One tap ca
Altify AI is an auto ALT text and AI ALT text plugin for WordPress images. It helps generate descriptive image ALT text for accessibility and image SEO. Use bulk image ALT text tools for your Media Library, generate featured image ALT text automatically, and scale WooCommerce image ALT updates with
The Accepted Payment Methods plugin is a straightforward, lightweight solution that enhances your website by displaying visually appealing icons of the payment methods you accept. This plugin is ideal for a variety of websites, including e-commerce platforms, service-oriented websites, and informati
