Do I need an image optimization plugin or extra CDN on SwiftPress?
Whether you need WordPress image plugins or a third-party image CDN on SwiftPress—and how our edge network fits in.
Short answer: You are not required to install an image optimization plugin or point images at a separate image CDN to get fast delivery on SwiftPress. Our platform already includes a global CDN tuned for WordPress, including edge-side image handling. If you previously used an external CDN only for images, it’s usually best to turn that off so traffic flows through SwiftPress end-to-end—you’ll get consistent caching, security, and optimizations without fighting duplicate layers.
That said, good habits still matter: don’t upload massive originals when a web-sized image is enough (see below).
How SwiftPress handles images
SwiftPress serves your site through our own edge and CDN. Image optimisation is part of that stack: requests for images can be processed at the edge so visitors often receive smaller, modern formats (for example WebP or AVIF when the browser supports them and the savings are worthwhile), while files in your WordPress Media Library stay as you uploaded them.
In practice:
- Originals in WordPress are not rewritten for the sake of “CDN optimisation” plugins that duplicate every size on disk.
- HTML from WordPress may still reference your normal URLs; negotiation and transformation can happen when the asset is served through our network.
- Benefits stack with our WordPress-focused tuning (caching, compression, TLS)—without you wiring up a second CDN just for images.
Exact behaviour can vary by file type, size, and browser—edge optimisation is there to reduce bytes on the wire, not to replace sensible uploads.
Will I see .webp in WordPress or in the page source?
Often, no—or not in the way a “local WebP converter” plugin would show. Because optimisation happens on our infrastructure, you may still see your original filenames and URLs in the editor and in HTML, while the browser receives an optimised representation for that request. That’s expected: the source of truth remains in WordPress; delivery is optimised at the edge.
To confirm optimisation is active for a given image:
- Open your site in Chrome (or another browser with devtools).
- Open Developer Tools → Network.
- Reload the page, filter by Img (or search for an image URL).
- Select a request and inspect Response headers: look for Content-Type (e.g.
image/webp) and any cache / CDN headers your request returns.
External tools such as GTmetrix waterfall views can also show response types and timings for image requests.
Does that mean image dimensions don’t matter?
No. Edge optimisation does not excuse uploading huge originals. A 15–20 MP photo will still be heavy to pull and process even when optimised. Best practice:
- Resize to the largest size you actually need for the layout (or use WordPress’s built-in sizes).
- Consider a helper such as “Resize Image After Upload” (or similar) if editors often drop in massive files—it reduces storage and editor load, complementing what the CDN does on delivery.
What about image optimisation plugins?
- Not mandatory for “SwiftPress to work.” Many sites run no dedicated image plugin.
- Optional plugins can still help with workflow (bulk resize, lazy-load tweaks, art direction). Avoid stacking multiple heavy optimisation plugins that rewrite files on disk and duplicate what the edge already does—that can cause confusion and bloat.
If you use a third-party image CDN or proxy, disable it for SwiftPress unless we’ve agreed a specific setup—otherwise you may bypass our edge and lose part of the benefit you’re paying for.
Need help?
Use — same as the Support link in the site footer (opens the chat widget). You can also sign in at my.swiftpress.io. We don’t offer email support — see How to contact customer support. If something in this article doesn’t match your dashboard, and we’ll point you to the right screen.