QUIC.cloud is the CDN and online services platform built by LiteSpeed Technologies to work hand in hand with the LiteSpeed Cache plugin. What sets it apart is that it caches WordPress’s dynamic HTML pages, not just images and stylesheets, and purges them automatically when you edit content. It also provides image optimisation, critical CSS and DNS. This guide explains how it works, its new plans and how to set it up.
Article current as of 3 November 2026. Plans are those published in QUIC.cloud’s official documentation, taking effect on 10 November 2026.
Key takeaways
- QUIC.cloud is run by QUIC Cloud Inc. and developed by LiteSpeed Technologies. Its CDN only works with the LiteSpeed Cache plugin.
- Unlike a typical CDN, it caches the WordPress pages themselves and purges them in sync with your server cache.
- The online services (image optimisation, critical CSS, UCSS, viewport images, LQIP) work with or without the CDN.
- New plans from 10 November 2026: Free ($0), Basic ($5/month), Pro ($20/month), Business ($100/month), Enterprise (from $250/month), per domain.
- Before switching on the CDN, check your email records, your SSL certificate and any CAA records, and turn off DNSSEC if you move to QUIC.cloud DNS.
What is QUIC.cloud?
QUIC.cloud is a content delivery network combined with optimisation services, operated by the US company QUIC Cloud Inc. and developed by LiteSpeed Technologies, the company behind the LiteSpeed web server. It plugs into WordPress through the free LiteSpeed Cache plugin, which drives both the local cache and the CDN.
It comes in two parts:
- The CDN: servers around the world (QUIC.cloud’s home page listed 78 points of presence when we checked) that keep copies of your pages and files close to visitors, with HTTP/3 and anycast DNS.
- Online services: processing done on QUIC.cloud’s servers at LiteSpeed Cache’s request, such as image compression and conversion or critical CSS generation.
New to LiteSpeed Cache? Start with our LiteSpeed Cache setup guide: QUIC.cloud builds on those settings.
How is QUIC.cloud different from a regular CDN?
A regular CDN mostly caches static files (images, CSS, JavaScript) and passes HTML requests back to your server. QUIC.cloud also caches the HTML pages WordPress generates, because it shares LiteSpeed Cache’s logic: when the plugin purges a page on your server, the CDN copy is purged at the same time.
That synchronised purge solves the main headache of caching HTML at the edge: serving a stale page after an update. LiteSpeed Cache knows which pages depend on a piece of content (the post, the home page, category archives…) and purges exactly those, using tags.
| Criterion | General-purpose CDN | QUIC.cloud with LiteSpeed Cache |
|---|---|---|
| — | — | — |
| Static files (images, CSS, JS) | Yes | Yes |
| WordPress HTML pages | Depends on configuration and custom rules | Yes, natively |
| Purge after editing content | Manual, via API or a dedicated plugin | Automatic, page by page |
| Personalised content (cart, account) | Usually bypassed | Excluded by default; private cache and ESI available |
| HTTP/3 all the way to the origin | Rarely | Yes, when the origin runs LiteSpeed |
| Requirement on the site | None in particular | LiteSpeed Cache plugin required |
According to the documentation, a page stays in the CDN cache for 24 hours after it was last requested, and for up to 7 days if it is requested at least once a day. WooCommerce cart, checkout and account pages are excluded from cache by default.
What services does QUIC.cloud offer?
QUIC.cloud offers a CDN, free DNS for CDN users, security protections and optimisation services: image compression and WebP or AVIF conversion, critical CSS (CCSS), unique CSS per page (UCSS), viewport images (VPI) and low-quality image placeholders (LQIP).
| Service | What it does | Helps with |
|---|---|---|
| — | — | — |
| CDN | Serves pages and files from the nearest point of presence | Distant or international audiences, traffic spikes |
| Image optimisation | Compresses JPEG and PNG, generates WebP or AVIF versions | Page weight, LCP |
| Critical CSS (CCSS) | Works out the CSS needed for the above-the-fold area | Render delay, LCP |
| UCSS | Works out the CSS each page type actually uses | CSS weight |
| Viewport images (VPI) | Detects images visible on load so they aren’t lazy-loaded | LCP |
| LQIP | Generates a blurred preview shown while the image loads | Perceived speed |
| QUIC.cloud DNS | Anycast DNS, free for CDN users | Enabling the CDN on a root domain |
| Security | Protection against common attacks, bot challenge, advanced rules depending on plan | Login forms, brute-force attacks |
Key point: the optimisation services don’t require the CDN. You can have QUIC.cloud optimise images or generate critical CSS while serving your site straight from your host. Since November 2025, the CDN’s bot challenge uses ALTCHA instead of Google reCAPTCHA.
How much does QUIC.cloud cost?
From 10 November 2026, QUIC.cloud bills per domain on five plans: Free ($0), Basic ($5 a month), Pro ($20), Business ($100) and Enterprise (from $250). They replace the previous credits and tiers system, and every domain moves to the Free plan by default.
| Plan | Monthly price per domain | CDN bandwidth included | Security |
|---|---|---|---|
| — | — | — | — |
| Free | $0 | Unlimited, on a smaller network of US and EU nodes | Anti-hack protection, fixed settings |
| Basic | $5 | 100 GB | Custom settings, Under Attack mode, maintenance mode |
| Pro | $20 | 500 GB | Adds bot management, Content-Security-Policy, blocking and redirect rules |
| Business | $100 | 4 TB | As Pro |
| Enterprise | From $250 | 12 TB and up | As Pro |
Rules worth knowing:
- Free plan optimisation allowance: 100 images, 20 page optimisation requests (CCSS, UCSS and VPI combined) and 20 LQIP requests per month. Paid plan allowances had not been finalised when we checked.
- Included on every plan: home page optimisation once a week.
- Packs: $20 adds 250 GB of CDN or extra optimisation to one domain, with no expiry.
- Bandwidth overage: the domain moves to the smaller network until the end of the period, keeping its plan features.
- Optimisation overage: optimisation pauses until the next month unless you buy a pack.
These terms have just been overhauled and QUIC.cloud says more details are coming, so re-read the official page before you subscribe.
Do you actually need QUIC.cloud?
Not necessarily. If your site already runs on a LiteSpeed server and most visitors are near it, the server cache does the heavy lifting and the optimisation services are often enough. The CDN pays off for international audiences, traffic spikes, or hosting that doesn’t run LiteSpeed.
| Your situation | Recommendation |
|---|---|
| — | — |
| LiteSpeed server, audience mostly in one region | Server-side LSCache + optimisation services; CDN optional |
| Audience spread across continents | CDN worth it: it brings pages and files closer to visitors |
| Nginx or Apache hosting | The QUIC.cloud CDN brings LiteSpeed Cache page caching, otherwise unavailable on those servers |
| Site already behind another CDN (Cloudflare…) | Put only one CDN in front of the site; QUIC.cloud can use Cloudflare as DNS only |
| High-traffic WooCommerce store | CDN useful to absorb spikes; carts and accounts are still served by your server |
Before deciding, measure your server response time (TTFB) from several regions: our guide to reducing WordPress TTFB explains how, and our article on WordPress Core Web Vitals shows how much of LCP depends on the server.
How do you enable QUIC.cloud from LiteSpeed Cache?
Since LiteSpeed Cache 7.0, the old domain key has been replaced by a guided activation under General > Online Services. You link the site to QUIC.cloud, anonymously or with an account, then enable the CDN if you want it, following the official activation guide.
Prepare first:
- Export or note your current DNS zone, especially your MX, SPF, DKIM and DMARC email records.
- Make sure the site already has a valid SSL certificate, to avoid an HTTPS gap while the CDN certificate is issued.
- If your domain has CAA records, allow
letsencrypt.org. - If you’ll use QUIC.cloud DNS, turn off DNSSEC at your registrar: QUIC.cloud doesn’t support it.
- Back up the site.
Then:
- In WordPress, open LiteSpeed Cache > General > Online Services and click Enable QUIC.cloud services. The plugin detects your server and its IP address.
- Choose Stay Anonymous to use only the optimisation services, or Register to create an account (needed for the CDN, usage tracking and purchases), then confirm your email.
- Without the CDN, click Finish Link Setup and you’re done. With the CDN, click Enable CDN and continue with setup.
- Pick the activation mode: QUIC.cloud DNS (I want to use QUIC.cloud DNS, then Add DNS Zone) or a CNAME record.
- In DNS mode, replace the name servers at your registrar with the ones QUIC.cloud gives you, and remove any extra ones.
- Click Finish Link Setup and go back to WordPress. The plugin’s CDN tab should end up showing the CDN in use, DNS verified and a valid SSL certificate.
- If your host filters incoming connections, have QUIC.cloud’s IP addresses allowed: the list changes regularly.
CNAME or QUIC.cloud DNS: which mode should you choose?
CNAME mode keeps your current DNS but only suits a subdomain such as www. DNS mode hands the whole zone to QUIC.cloud and also works for the root domain. If your site runs without www and your DNS isn’t on Cloudflare, DNS mode is the simplest route.
| Criterion | CNAME mode | QUIC.cloud DNS mode |
|---|---|---|
| — | — | — |
| Where your DNS records live | With your current provider | With QUIC.cloud (zone recreated) |
| www site | Yes | Yes |
| Root domain site (no www) | Only with Cloudflare DNS | Yes |
| Name server change | No | Yes, at the registrar |
| DNSSEC | Kept | Must be turned off |
How do you check the CDN is working?
Request a page and look at the response headers: x-qc-pop shows which point of presence served it and x-qc-cache shows the CDN cache status. A second request should return a cache hit.
# Run twice: the second response should report a hit
curl -sI https://www.example.com/ | grep -i -E "x-qc-pop|x-qc-cache|x-litespeed-cache"Also test a WooCommerce checkout or account page: it must not come from cache. Finally, check that visitor IP addresses still show correctly in your analytics and security plugins: behind a CDN, the real IP arrives in the X-Forwarded-For header, which should only be trusted from QUIC.cloud’s IPs (“Use Client IP in Header” setting on LiteSpeed).
What should you watch out for?
Most post-activation issues involve email, the SSL certificate and visitors’ real IP addresses. You avoid them by preparing the DNS zone, installing a valid certificate before switching and allowing QUIC.cloud’s IPs wherever needed.
- Email: if your MX record points to the root domain, mail may head to QUIC.cloud. The email troubleshooting page recommends an A record (such as
mail) pointing to your origin IP, referenced by the MX. - SSL: the CDN certificate comes from Let’s Encrypt. Restrictive CAA records or Let’s Encrypt rate limits can block it.
- Repeated purges: above 10 identical purge commands in a minute, QUIC.cloud runs only one every 10 seconds.
- Free plan: the CDN runs on a smaller US and EU network, fine for a European or North American audience, less useful for Asia or Latin America.
- Personal data: according to its privacy policy, QUIC.cloud is a US company, acts as a processor for visitor data and may store data worldwide. Mention it in your privacy policy and, in the EU, in your record of processing activities.
QUIC.cloud at Hosterwise
At Hosterwise, QUIC.cloud is included in every plan: it is not active by default, you switch it on yourself for your sites, and its reverse proxy then sits in front of our LiteSpeed Enterprise servers. Once the CDN is enabled, public pages are cached on the worldwide network and purged together with LSCache by the LiteSpeed Cache plugin, with HTTP/3 end to end; the cart, customer account and admin are still served by the server, where ESI and the Redis object cache remain available. There is no QUIC.cloud subscription to take out on your side. Explore our LiteSpeed WordPress hosting or compare plans on our pricing page. Our support team, available 24/7, answers your questions about caching and the CDN.
QUIC.cloud FAQ
Is QUIC.cloud free?
There’s a Free plan at $0: unlimited CDN bandwidth on a smaller US and EU network, plus a small monthly optimisation allowance (100 images, 20 page optimisations, 20 LQIP). Paid plans start at $5 per month per domain from 10 November 2026.
Do I need a LiteSpeed server to use QUIC.cloud?
No. The CDN works in front of Apache or Nginx and then brings LiteSpeed Cache page caching, otherwise limited to LiteSpeed servers. The LiteSpeed Cache plugin is still required. With a LiteSpeed origin, you also get end-to-end HTTP/3.
Can I use QUIC.cloud with Cloudflare?
QUIC.cloud offers an official integration in which Cloudflare acts as DNS only, with the CNAME record set to “DNS only”. Stacking two CDNs that both cache the site makes purging and troubleshooting harder: pick the one that actually serves your pages.
Does QUIC.cloud work with WooCommerce?
Yes. Cart, checkout and account pages are excluded from cache by default, just as in LiteSpeed Cache. For personalised fragments such as the mini cart, LiteSpeed Cache can use ESI, which the QUIC.cloud CDN supports. On a LiteSpeed Enterprise server, as at Hosterwise, ESI also works without the CDN.
How do I turn QUIC.cloud off?
In LiteSpeed Cache, disable the CDN, then use the disconnect link under Online Services. If you moved to QUIC.cloud DNS, recreate your zone with your DNS provider and switch the name servers back at your registrar first, or your site and email will go offline.
Is QUIC.cloud GDPR compliant?
QUIC.cloud publishes a privacy policy, a data processing agreement and its list of sub-processors. It is a US company that may transfer data outside the EU, so list it as a processor in your records and privacy policy, and get advice if you handle sensitive data.

