WordPress integration

Why it is not first

A WordPress plugin rewrites URLs inside content that a customer has already published. Getting that wrong breaks a live site in a way that is tedious to undo, so it needs the URL contract, the preset model, and the fallback behaviour to be settled first — which is what the current release is for.

Shipping a plugin against a contract we were still changing would mean asking early adopters to upgrade through breaking changes on their production sites.

What it will do

• Rewrite media library URLs at render time, leaving the database untouched.
• Map WordPress image sizes onto PicSoar presets.
• Emit srcset from preset width families rather than from registered sizes.
• Fall back to the original URL whenever the plugin is disabled, misconfigured, or unreachable.
• Never modify or delete anything in wp-content/uploads.

That last point is the design constraint the whole plugin is built around: deactivating it must restore the previous behaviour completely, with no cleanup step.

Using the CDN with WordPress today

You do not need the plugin. Register your WordPress host as an origin with the base path/wp-content/uploads, then rewrite URLs in your theme or with any existing URL-rewriting plugin:

https://your-site.com/wp-content/uploads/2026/08/photo.jpg

becomes

https://cdn.picsoar.com/v1/prj_your_project_key/content/2026/08/photo.jpg

The path after the preset is relative to your configured base path. Nothing about your WordPress installation changes.

Tell us you want it

We prioritize by demand. Get in touch and say which WordPress setup you run — multisite, a page builder, an existing offload plugin — and it goes into the planning.

There is no waitlist form on this page because we have not built the mailing infrastructure to honour one. An input that silently discards your address is worse than no input.