If you uploaded changes but still see the old version of your website, the most likely cause is caching: your browser, your host or a content delivery network (CDN) is showing a saved copy. Try a hard refresh (Ctrl+F5 or Ctrl+Shift+R in most Windows browsers) or open the page in a private window. If the old version is still there, check that you uploaded the right file to the right folder on the server.
This guide explains how to tell which problem you have, and how to fix each one.
Step 1: Rule out your browser's cache
Browsers save copies of pages, stylesheets, scripts and images so sites load faster next time. After an update, your browser may keep using its saved copy for a while. To check:
- Hard refresh: press Ctrl+F5 or Ctrl+Shift+R on the page. This asks the browser to fetch fresh copies instead of using its cache.
- Private window: press Ctrl+Shift+N in Chrome or Edge, or Ctrl+Shift+P in Firefox, and open your site there.
- Another device: look at the page on your phone using mobile data, not your Wi-Fi.
If the new version appears in a private window or on another device, the files on the server are fine and your browser was showing an old copy. Visitors who have been to your site before may see the same thing briefly, which is why the CSS tip below is worth using.
Why CSS changes are the worst for this
Stylesheets are often cached longer than pages. You can upload a new page and a new style.css, refresh, and see new text with old styling. A reliable fix is to add a version number to the stylesheet link in your pages and change it whenever you update the file:
<link rel="stylesheet" href="css/style.css?v=2">
The browser treats style.css?v=2 as a new address and downloads it. Next time, change it to v=3. The same works for scripts.
Step 2: Check for host or CDN caching
If a private window and another device both still show the old version, the copy may be cached before it reaches any browser. Some hosts cache pages on the server, and services that sit in front of a site (CDNs) keep copies around the world.
- Look in your hosting control panel for a cache setting, often with a Purge or Clear cache button.
- If you use a CDN, clear its cache for the files you changed, or for the whole site.
- If you are not sure whether either applies, ask your host's support.
Caches usually expire on their own after a while, but clearing them gets your changes out straight away.
Step 3: Check you uploaded to the right place
If no cache explains it, the new file may not have replaced the old one. This is very common. Check each of these on the server:
- Right folder. Your site's public folder is often
public_html,wwworhtdocs. Files uploaded elsewhere, such as the folder above it, are not served to visitors. - Not a nested copy. If you uploaded your whole site folder into the public folder, your new files may sit in
public_html/my-site/while the old ones are still inpublic_html. - Exactly the same name.
About.htmlandabout.htmlare different files on many servers. So areindex.htmandindex.html. - The file's date. Most FTP programs show when each file was changed. If the server copy has an old date, the upload did not happen or failed.
- Another home page file. If the folder contains both
index.phpandindex.html, the server may show the PHP one, even though you updated the HTML one.
Step 4: Check you edited the right file
Sometimes the upload is fine, but the change was made somewhere else:
- You have two copies of your site on your PC and edited the older one.
- You changed a style in one stylesheet, but the page loads a different one.
- You edited the text in a shared header file but did not upload the pages that use it, or the change was overridden by a style in the page itself.
- You saved the file in your editor but uploaded before the save finished.
Open the file on the server (many FTP programs let you view or download it) and check that it contains your change. If it does, the problem is caching. If it does not, it is the upload or the local file.
Quick reference
| What you see | Most likely cause | What to do |
|---|---|---|
| New version in a private window only | Browser cache | Hard refresh; add ?v=2 to CSS links |
| Old version everywhere, file on server is new | Host or CDN cache | Clear the cache in your control panel or CDN |
| Old version everywhere, file on server is old | Upload failed or went to wrong folder | Upload again to the public folder |
| New text but old styling | Cached stylesheet | Version the stylesheet link |
| Some pages updated, others not | Not every changed file was uploaded | Upload all changed files |
The easier way: see exactly what Apollo Editor published
Apollo Editor is a Windows desktop HTML editor with optional built-in publishing that keeps track of what you upload, which takes much of the guesswork out of this problem.
- Changed file detection, so files you edited are not left behind.
- A publishing log that records what was uploaded.
- Transfer verification, to confirm files arrived.
- Saved server profiles, so uploads always go to the folder you set up.
Your site stays as plain HTML, so you can still check the server with any FTP program. For more help, read how to upload your website to a web host, images not showing on your website and FTP vs SFTP vs FTPS.
Frequently asked questions
How do I force my browser to show the new version?
Press Ctrl+F5 or Ctrl+Shift+R for a hard refresh, or open the page in a private window.
Why do CSS changes take a while to appear?
Browsers and some hosts cache stylesheets. Adding a version number to the link, such as style.css?v=2, makes browsers fetch the new file.
Could I have uploaded to the wrong place?
Yes. Check that the file went into the site's public folder and replaced the file with exactly the same name and path.
