You update a picture, open the page and see yesterday’s version. On another device, the new picture appears immediately. Before repeating the edit, it helps to ask a different question: where did each browser get its copy?
Caching is one reason two visits can show different results, though it is not the only possible cause.
A saved response can save a trip
MDN’s HTTP caching guide distinguishes private caches, such as a browser’s cache, from shared caches that can serve multiple users. It also explains freshness and revalidation: a stored response may be reused while fresh, or checked with the server before further use according to the applicable rules.
The useful everyday idea is that a request does not always require the same content to be downloaded again from its original source. That can make pages faster, but it gives troubleshooting more than one place to look.
Separate the symptom from the explanation
Write down the exact page URL, what looks old, and where you see it. Is it the article text, a stylesheet or one image? Does the issue occur in one browser or several? Did you change the file itself, its URL, or the page that refers to it?
A page can load while one of its resources remains unchanged. “The website is cached” is therefore less useful than “this image URL still returns the previous picture in this browser”.
Use a controlled comparison
Try an ordinary reload, then compare the exact same URL in another browser or a private window. Those checks can help distinguish local state, but they do not prove that every upstream cache has been bypassed. A private window may still receive a response from a shared cache.
If you manage the site, inspect the response headers and the cache controls provided by your hosting or publishing system. Purge the relevant site cache through its documented controls when appropriate, then check the affected page and resource again. Avoid changing several unrelated settings at once.
Remember what clearing a browser can and cannot do
Removing local cached files affects that browser’s stored copies. It does not necessarily remove a response held by a server or CDN. Clearing cookies is a different action that may sign you out; it should not be treated as interchangeable with clearing cached images and files.
For repeatedly updated assets, site maintainers often use versioned resource URLs so a changed file has a distinct address. The exact approach depends on the publishing system.
When the resource is a picture, first confirm that the new export itself looks right. See our image-format comparison guide for a useful check before upload.
Reference: MDN, HTTP caching. The scenarios are illustrative, not a diagnosis of a particular website.