Title: Gloty
Author: wpshelf
Published: <strong>August 4, 2026</strong>
Last modified: August 4, 2026

---

Search plugins

![](https://ps.w.org/gloty/assets/banner-772x250.png?rev=3634659)

![](https://ps.w.org/gloty/assets/icon.svg?rev=3634659)

# Gloty

 By [wpshelf](https://profiles.wordpress.org/wpshelf/)

[Download](https://downloads.wordpress.org/plugin/gloty.1.29.2.zip)

 * [Details](https://wordpress.org/plugins/gloty/#description)
 * [Reviews](https://wordpress.org/plugins/gloty/#reviews)
 *  [Installation](https://wordpress.org/plugins/gloty/#installation)
 * [Development](https://wordpress.org/plugins/gloty/#developers)

 [Support](https://wordpress.org/support/plugin/gloty/)

## Description

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.

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:**

 * **Your database, your translations** — stored locally in WordPress, never fetched
   remotely at render time
 * **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
 * **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
 * **SEO-friendly** — hreflang tags, translated meta, clean /fr/page/ URLs
 * **Language switcher** — floating widget, footer list, shortcode, or sidebar widget
 * **Optional browser-language redirect** — off by default, crawler-safe, remembered
   per visitor
 * **WooCommerce compatible** — products, cart, checkout, and store AJAX fragments
 * **Gettext integration** — translates WordPress, theme, and plugin UI strings
 * **AI translation engine** — OpenAI or Google Gemini, selected for you by the 
   service on every plan
 * **Background processing** — queued dispatch with webhook delivery and a polling
   fallback
 * **Developer extensible** — filters and a REST API

**How it works:**

 1. Install Gloty and connect your site to the Gloty translator service
 2. Add your target languages
 3. Gloty discovers translatable content from your posts, taxonomies, and template 
    strings
 4. Translation runs in the background and the results are written to your database
 5. Visitors 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://api-production-3261.up.railway.app` (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.
 * 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:

 * OpenAI — https://openai.com/policies/terms-of-use / https://openai.com/policies/
   privacy-policy
 * 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.

### 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.

## Screenshots

[⌊Dashboard showing translation statistics across languages⌉⌊Dashboard showing translation
statistics across languages⌉[

Dashboard showing translation statistics across languages

[⌊Translations screen for reviewing and editing individual translations⌉⌊Translations
screen for reviewing and editing individual translations⌉[

Translations screen for reviewing and editing individual translations

[⌊Settings page with translation and switcher options⌉⌊Settings page with translation
and switcher options⌉[

Settings page with translation and switcher options

## Installation

 1. Upload the `gloty` folder to `/wp-content/plugins/`
 2. Activate the plugin through the ‘Plugins’ menu in WordPress
 3. Go to **Gloty > Connection** and connect your site to the Gloty translator service
 4. Add your target languages under **Gloty > Languages**
 5. Visit your site — translations happen automatically in the background

The setup guide covers each step in more detail: https://wp-shelf.com/gloty/docs/
getting-started.html

## FAQ

### Do I need an account?

Yes. Producing translations requires a connection to the Gloty translator service,
set up under Gloty  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.

### How much does it cost?

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.

### 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.

### 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.

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.

### 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.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Gloty” is open source software. The following people have contributed to this plugin.

Contributors

 *   [ wpshelf ](https://profiles.wordpress.org/wpshelf/)

[Translate “Gloty” into your language.](https://translate.wordpress.org/projects/wp-plugins/gloty)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/gloty/), check out 
the [SVN repository](https://plugins.svn.wordpress.org/gloty/), or subscribe to 
the [development log](https://plugins.trac.wordpress.org/log/gloty/) by [RSS](https://plugins.trac.wordpress.org/log/gloty/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.29.2

 * First release on WordPress.org.

## Meta

 *  Version **1.29.2**
 *  Last updated **11 hours ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.4 or higher **
 *  Tested up to **7.0.2**
 *  PHP version ** 8.1 or higher **
 * Tags
 * [i18n](https://wordpress.org/plugins/tags/i18n/)[language](https://wordpress.org/plugins/tags/language/)
   [localization](https://wordpress.org/plugins/tags/localization/)[multilingual](https://wordpress.org/plugins/tags/multilingual/)
   [translation](https://wordpress.org/plugins/tags/translation/)
 *  [Advanced View](https://wordpress.org/plugins/gloty/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/gloty/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/gloty/reviews/)

## Contributors

 *   [ wpshelf ](https://profiles.wordpress.org/wpshelf/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/gloty/)