Overview

Cache helps the website respond faster by storing already processed versions of pages and assets. In an editing context, this means a change may not appear immediately on the frontend if an older cached version is still being served.

Cache HTML
Image cache
Visual update

1

What “clear cache” means

Core concept and practical impact

Cache HTML

Stores processed page versions to speed up website response time and reduce repeated work on the server.

Image cache

Stores processed image versions, such as resized outputs and variations used on the frontend.

Expected result

Once the cache is cleared, the system regenerates the latest version of the content or asset on the next visit.

Key idea: clearing cache does not delete website content. It simply forces the system to stop using an old in-memory version and regenerate the current one.
2

When to use each cache type

The difference between HTML and images

Cache HTML
When it makes sense When the website still shows old text, blocks, structure or pages even though the changes were already published in the backoffice. What it usually resolves Differences between what has already been saved/published in Studio and what still appears on the website frontend. What to expect afterwards On the next page load, the system will typically regenerate the updated HTML.
Image cache
When it makes sense When an image was replaced, optimized or updated, but the website still shows the old version. What it usually resolves Cases where the file has already changed in the backoffice, but cached image variations have not yet been regenerated on the frontend. What to expect afterwards Images will be served again from the latest version, with updated dimensions or processing whenever applicable.
Attention: if the change still does not appear after clearing Studio cache, the issue may be in the browser cache, an intermediate CDN, or the fact that the change was not actually saved/published yet.
3

How to clear the website HTML cache

Recommended backoffice flow

1. Open the Cache section

In the Studio side menu, open the Cache area, where the actions to clear this layer are grouped.

2. Select “Clear HTML cache”

Choose the Clear HTML cache action to force the regeneration of the website HTML pages.

3. Confirm the success message

After the action, check whether Studio shows a confirmation that the HTML cache was cleared successfully.

4. Test on the frontend

Go back to the website and confirm whether the updated content is now visible. If needed, do a hard refresh in the browser.

Practical tip: this action is especially useful after changes to pages, blocks, menus, text or structure that are already correct in the backoffice but still do not appear on the website.
4

How to clear the website image cache

When images do not update

1. Go to the Cache area

From the side menu, open the same Cache section where the clear actions are available.

2. Choose “Clear cache images”

Use the Clear cache images option when the problem is related to an image that did not update on the frontend.

3. Validate on the website

After clearing, test again the page or block where the image appears to confirm that the new version is now being served.

4. Confirm the context

If the image is still wrong, also confirm that the correct file was actually replaced in the backoffice and that there is no other similar version being used in the content.

Important: clearing image cache solves the technical regeneration side, but it does not fix wrong files, swapped names or incorrect choices inside the content.
5

Quick checklist before clearing cache

Avoid unnecessary steps

  • Confirm that the change has already been saved or published in the backoffice.
  • Understand whether the problem is related to content/HTML or specifically to an image.
  • Test again after clearing and, if needed, do a hard refresh in the browser.
  • Make sure you are not validating an old page, a copy or a different environment than the expected one.
6

Explore also

Topics related to maintenance and assets