LiveChat 
Support 
How to Clear Cache on Squarespace (And Why Your Browser Is Usually the Real Problem)
You edited a page on Squarespace, hit save, and reloaded the site — but the old version is still showing. Your first instinct is to find a “clear cache” button somewhere in the dashboard. Here is the uncomfortable truth: on Squarespace, there is no server-side cache button to press. Squarespace is a fully managed platform, and it controls its own server and CDN caching layers. You cannot flush them directly.
The good news is that you almost never need to. In the overwhelming majority of cases, the stale content you are looking at lives in your own browser, not on Squarespace’s servers. This guide explains exactly what “clearing cache on Squarespace” really means, how to force your changes to appear, and why a managed builder behaves so differently from self-hosted hosting where you control every cache layer yourself.
Key Takeaways
• Squarespace does not give you a server-cache flush button — it manages server and CDN caching for you.
• Roughly 90% of “my changes aren’t showing” problems are browser cache, not Squarespace.
• The fastest fix is a hard refresh (Ctrl+Shift+R / Cmd+Shift+R) or checking the page in an incognito window.
• Squarespace’s CDN typically updates automatically within minutes — usually you just need to wait briefly.
• On a self-hosted site, you control server caching directly; on a managed builder, you do not.
Why don’t my Squarespace changes appear immediately?
When a page looks outdated after you publish, the cause is almost always one of two caching layers working as designed. Understanding which one is responsible tells you exactly what to do next.
Browser cache is the big one. To make pages load faster, your browser saves copies of images, CSS, fonts, and sometimes HTML on your device. When you revisit the page, the browser may serve its saved copy instead of fetching the new version from Squarespace. The site genuinely updated — you are just looking at a local snapshot.
CDN propagation is the smaller, temporary one. Squarespace serves your site through a content delivery network (CDN): a global fleet of edge servers that cache your content close to visitors. After you publish a change, those edge nodes need a short moment to pick up the new version. This usually resolves on its own within minutes.
Notice what is missing from that list: a server cache *you* can clear. That option simply does not exist on a managed builder, and you do not need it.
What are the cache layers between you and your live site?
It helps to see the full path your request travels. Each layer can hold a copy of your content, and each one is controlled by a different party.
| Cache layer | Where it lives | Who controls it | Can you clear it on Squarespace? |
|---|---|---|---|
| Browser cache | Your own device | You | Yes — this is the one you can and should clear |
| CDN / edge cache | Squarespace’s global edge servers | Squarespace | No — updates automatically within minutes |
| Platform / server cache | Squarespace’s origin servers | Squarespace | No — fully managed, no user access |
The pattern is clear: the only layer you have direct control over is the browser cache. That is also, conveniently, where the problem almost always is. So when someone asks “how do I clear my Squarespace cache,” the practical answer is “clear your browser cache and give the CDN a minute.”
How do I clear my browser cache to see Squarespace changes?
Because your browser is the usual culprit, start here. These methods go from fastest to most thorough.
Do a hard refresh first
A hard refresh forces your browser to ignore its saved copy and pull a fresh version directly from the server. It is the single fastest fix and solves the majority of stale-content complaints.
- Windows / Linux: `Ctrl + Shift + R` (or `Ctrl + F5`)
- Mac: `Cmd + Shift + R`
Do this while viewing the page that looks outdated. In most cases, your changes appear instantly.
Check the page in an incognito or private window
An incognito window (Chrome/Edge) or private window (Safari/Firefox) starts with no cached files and no saved cookies. Opening your page there bypasses your normal browser cache entirely.
This is also the best diagnostic test. If the page looks correct in incognito but wrong in your normal window, you have confirmed the problem is your browser cache — not Squarespace. The fix is then simply to clear your regular browser’s cache.
- Chrome / Edge: `Ctrl + Shift + N` (Windows) or `Cmd + Shift + N` (Mac)
- Firefox: `Ctrl + Shift + P` or `Cmd + Shift + P`
- Safari: File → New Private Window
Here is the mental model most people miss: on a managed builder like Squarespace, you cannot flush the server cache yourself — and that is by design. Squarespace deliberately abstracts that layer away so you never have to think about it. The flip side is that when something looks stale, the cause is almost never the server. In practice, about 90% of “cache” problems on Squarespace are sitting in your own browser, which you control completely. On self-hosted hosting, the equation flips: you own the server cache too, which means more responsibility but also far more control. Knowing *which* cache you are actually fighting is half the battle.
Clear your full browser cache when needed
If a hard refresh and incognito both fail to help on your normal browser, clear the browser cache outright. The path differs slightly per browser:
- Chrome / Edge: Settings → Privacy and security → Clear browsing data → select *Cached images and files* → Clear.
- Firefox: Settings → Privacy & Security → Cookies and Site Data → Clear Data → check *Cached Web Content*.
- Safari: Safari → Settings → Advanced → enable *Show Develop menu*, then Develop → Empty Caches.
After clearing, reload the page once and your latest Squarespace content should load fresh.
What about clearing cache on different browsers and devices?
A common point of confusion: you fixed the page on your laptop, but a colleague on their phone still sees the old version. This is expected. Each browser and each device keeps its own independent cache. Clearing the cache on one machine does nothing for another.
If you are verifying changes for a client or team, ask them to do their own hard refresh, or send them an incognito link to confirm the live version. Mobile browsers cache aggressively, so on phones the incognito-window check is often the quickest way to confirm what is genuinely live versus what is locally cached.
Do I ever need to wait for Squarespace’s CDN to update?
Occasionally, yes — but not for long. If you have hard-refreshed, checked incognito, and the change *still* is not visible everywhere, you may simply be in the brief window where Squarespace’s CDN is propagating your update across its edge servers.
The correct response here is patience, not troubleshooting. CDN propagation on Squarespace typically completes within a few minutes. Wait a short while, then re-check in a fresh incognito window. There is no button to speed this up, because the layer belongs to Squarespace — and that is the fundamental trade-off of any managed platform.
This is exactly where the difference between a locked-down builder and self-hosted hosting becomes concrete. On Squarespace, caching is a black box: convenient, but entirely out of your hands. If you ever need to *guarantee* an instant purge, run advanced caching rules, or fine-tune how your CDN behaves, a managed builder simply will not let you.
With DarazHost self-hosted hosting (for WordPress and other platforms), you get full control over every cache layer. Server-side caching with LiteSpeed Cache can be purged on demand the moment you publish — no waiting, no guessing. You decide your CDN configuration, your cache rules, and your expiry policies. Pair that with fast SSD storage for quick origin responses and 24/7 expert support when you want a second set of eyes, and you move from “hoping the platform updates” to “knowing your changes are live.” For anyone who has outgrown the constraints of a builder, that control and flexibility is the whole point.
How do I confirm my changes are actually live?
When you need certainty, run this quick sequence:
- Hard refresh the page (`Ctrl/Cmd + Shift + R`).
- Open the page in incognito to bypass your browser cache.
- If incognito shows the change but your normal window does not, clear your browser cache.
- If incognito *also* shows the old version, wait a few minutes for CDN propagation, then re-check.
- Test on a second device or browser to confirm what real visitors see.
If the change is correct in a fresh incognito window on more than one device, it is live for your audience — regardless of what your everyday browser is still showing you.
Frequently asked questions
Is there a “clear cache” button in the Squarespace dashboard? No. Squarespace is a managed platform and does not expose a server-cache flush control. Caching at the server and CDN level is handled automatically. The cache you can clear is your browser cache.
Why do I still see old content after publishing on Squarespace? Almost always because your browser is serving a saved copy. Do a hard refresh or open the page in incognito. If it still looks old everywhere, give Squarespace’s CDN a few minutes to propagate the update.
How long does Squarespace’s CDN take to update? Typically just a few minutes. Propagation across edge servers is automatic, and there is no way to manually trigger or accelerate it on a managed platform.
Does clearing my cache on one device fix it for everyone? No. Each device and browser has its own cache. Other visitors must clear their own, or you can verify the true live version using an incognito window on each device.
Can I control server caching like on a self-hosted site? Not on Squarespace. On self-hosted hosting, you control server and CDN caching directly — including on-demand purges with tools like LiteSpeed Cache — which a managed builder does not allow.
