PixGlory

Unlike a generic media-offload plugin, PixGlory pairs the offload with a guided migration for

your existing library, a live connection you can watch from your PixGlory dashboard, and

one-click WebP delivery that runs entirely on PixGlory’s servers, never on yours.

• Guided migration, not just new-upload offload. A read-only scan finds everything eligible

first; nothing is copied or changed until you say go. Migration then runs in resumable batches

(safe to close the page, safe if your host interrupts it, never restarts from scratch) and

rewrites every reference it finds: post content, page-builder layouts including Elementor’s

JSON-based storage, and other plugins’ serialized settings. Files are uploaded exactly as

WordPress generated them, and references switch to the PixGlory URL only once each upload is

confirmed.

• Connection-first, watchable from your dashboard. Once connected, this site shows up live on

your PixGlory dashboard’s Integrations screen: connection status, when it last checked in, and

a running count of the files it has sent, so you can confirm the plugin is doing its job

without digging through WordPress admin.

• One-click WebP delivery, zero re-encoding on your server. Run an optimisation batch from

your PixGlory dashboard, and every visitor whose browser supports WebP is served it

automatically through real content negotiation at the same URL, generated entirely on

PixGlory’s servers. Your WordPress site never runs an image conversion.

• Free to start. PixGlory has a free plan this plugin works with; paid plans raise the

storage and bandwidth limits, with no separate purchase needed for offload or migration.

com ) with a free plan and

paid plans for higher limits. This plugin is a client for that service: it does not do any image

processing or delivery on its own. An account is required (creating one is free), and use of the

service is governed by PixGlory’s Terms of Use.

With a connection key from your PixGlory organization, this plugin also:

• Pushes newly uploaded images to PixGlory’s storage and worldwide CDN after WordPress finishes

generating its own local size variants. The upload itself is never delayed or blocked by this;

the push to PixGlory happens afterward, in the background.

• Optionally rewrites your site’s image URLs to serve confirmed uploads from PixGlory instead of

your own server, once PixGlory has confirmed a working URL for that image and not before.

• Never re-encodes or resizes anything on your server. What gets uploaded is exactly the file

WordPress already generated.

• Never deletes original files from your server. Local copies always stay in place.

• Degrades silently: if PixGlory cannot be reached, or your account is over its quota, uploads

keep working normally and images keep rendering from your own server.

• Migrates your existing media library, at your own pace, in the background: scans your site

first (nothing is copied or changed until you start it), then copies files in resumable

batches and rewrites the links that point at them (post content, page-builder layouts, and

other plugins’ settings) to the PixGlory URL only after each file is confirmed uploaded.

Nothing is ever re-encoded. Pause and resume any time; your originals are never touched.

What data is sent where. No request to PixGlory is made until you paste a connection key on

the PixGlory admin menu and press Connect (this is your explicit consent). See “External services”

below for the exact hosts, when each request fires, and what it carries.

Migration of an existing library

0. Open the Migration tab, scan your site (read-only), review what was found,

and start the migration. It runs in the background in resumable batches: safe to close the page,

safe if your host interrupts it, and never restarts from scratch. Nothing is re-encoded: your

existing files are uploaded exactly as they are, and their references are rewritten to the

PixGlory URL only once the upload is confirmed. wp pixglory migrate runs the same migration

from the command line, with a --dry-run mode.

External services

PixGlory is a paid image CDN service, not a bundled tool: it stores and serves your media on its

own infrastructure, the same way a plugin like Disqus offloads comments to a third-party service.

This plugin is a client for that service and requires a PixGlory account (creating one is free)

and a connection key from that account before it talks to PixGlory at all. It contacts exactly two

kinds of remote host, described in full below, and nothing else. It loads no remote code, script,

style, or font of any kind; every file it runs ships inside the plugin’s own files.

1. com/api/v1

No request reaches this host until you paste a connection key on the PixGlory admin menu and

press Connect, and that action is this plugin’s only source of consent. After you connect:

• Every request this plugin makes (a new upload being offloaded, the daily or per-upload

heartbeat, and the Connection tab’s “Test connection” button) carries your site’s address and

its WordPress and plugin version numbers, so your PixGlory dashboard can show the connection as

active and confirm which versions it is running. This is sent any time the plugin talks to

PixGlory, whether or not offloading itself is turned on.

• When “Offload new uploads” is on, or while a migration you started is running, this plugin also

sends the bytes, filename, size, and MIME type of each image being offloaded, and stores the CDN

URL PixGlory returns as WordPress attachment metadata.

• No other site data (post content beyond the image bytes being sent, user accounts, or other

plugins’ settings) is ever sent to PixGlory.

com. Terms of Use:

com/terms. Privacy Policy:

com/privacy.

2. g. com/{organization}/{project} or a custom domain

you attached to it

If you turn on “Serve from PixGlory,” this plugin rewrites your site’s rendered image URLs to

point at your own PixGlory CDN project instead of your own server, but only for images you already

offloaded and only once PixGlory has confirmed a working URL for that specific image. This is your

own account’s storage serving your own media back to your own visitors, not a third-party asset

load: no visitor’s browser fetches anything from a PixGlory host until you have both connected an

account and turned this setting on.

If PixGlory cannot be reached, or your account is over its quota, none of the above blocks or

delays anything: uploads keep working normally and images keep rendering from your own server (see

the FAQ).