Website projects always load the live site
A website project has no stored copy of your site. Every time someone opens it, Huddlekit fetches the site as it is right now, so changes you publish show up without you doing anything to the project.
What can lag behind is the cache. Huddlekit caches pages and assets briefly so projects load quickly, which means a change you published moments ago may not be visible yet — most often as an old image, a stale stylesheet, or a page that has not picked up your latest edit.
Purge the cache
There are two ways to force fresh content:
- Purge cache — open the Huddlekit menu in the top-left of the project toolbar and choose Purge cache. This clears the whole project's cache and reloads the preview.
- The reload button in the URL bar — reloads the page and fetches fresh content at the same time.
Purging affects the project for everyone, not just you. If a client reports stale content, purging once from your side clears Huddlekit's copy for them too. Their own browser may still hold an old image or stylesheet, so they may need to press the reload button once. They do not need to clear their browser cache.
Guests on a share link can purge as well, so a reviewer who suspects they are looking at an old page can refresh it themselves.
When purging will not help
Broken layout, wrong fonts, or box-outline icons
If the page renders but the styling is clearly wrong — icons showing as empty boxes, fonts falling back, elements stacked oddly — that is usually a stylesheet or font file the site serves in a way Huddlekit could not fully rewrite. Purge once in case it is a stale asset; if it looks the same afterwards, email support@huddlekit.com with the project URL and we'll look into it.
A password or coming soon page instead of the site
That is a gate rather than a cache problem. See Reviewing password-protected and pre-launch sites.
An error message where the site should be
Use the Retry button on the message first. If it keeps failing, see Website project limitations.
What happens to existing comments
Refreshing does not touch feedback. Comments, replies, statuses, and their screenshots are kept as they were.
The screenshot saved with a comment is a record of what the page looked like when the comment was left, so it will not update when the site changes. That is deliberate — it is how you can still see what a reviewer was pointing at after the page has been rebuilt.
Comment pins are anchored to the element that was clicked. If that element is edited or removed in a later release, its pin can move or stop appearing on the page. The comment itself is never lost — it stays in the comments sidebar and on the Tasks board, with its screenshot and page URL intact.
Project thumbnails
The preview image on a project card is generated separately and is not refreshed by a cache purge. It is taken when the project is created, and again if you change the project's URL, but it does not update on its own after that. If a thumbnail stays blank or badly out of date, email support@huddlekit.com and we can regenerate it.