> For the complete documentation index, see [llms.txt](https://www.locksmith.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.locksmith.guide/tutorials/more/how-to-clear-cache-for-a-single-website.md).

# How to clear cache for a single website

{% hint style="info" %}
This guide is geared towards merchants on Shopify using the Locksmith app. If you are arriving from elsewhere, you may still find it useful - simply down scroll to the section for the browser you are using.
{% endhint %}

## Why this is useful

If you are using Locksmith's passcode, secret link, newsletter, or location key-condition types on your Shopify store, Locksmith remembers access of specific visitors via browser cache. Once the lock is open, the locked content will be accessible and will begin to appear in searches and collection view (if applicable) for the rest of the visitor's browser session.

If you want to re-test what a new user would, you will need to use a browser with clean cache. Keep in mind that you may find it easier to simply open up an **incognito window,** or use a **different browser or device**. However, those steps can be tedious if you would like to test multiple times in quick succession.

{% hint style="warning" %}
**Important:** If you're using a URL with the `shopifypreview.com` domain to test, Locksmith changes won't appear there.

The Shopify theme editor's built-in preview bypasses Locksmith entirely. Locks, keys, and any manual locking code can look like they are not in place.

If you're testing your published theme, open the live storefront URL in a new private browsing window.

If you're testing an unpublished theme, use the preview URL that includes `?fts=0&preview_theme_id=` followed by your theme ID, as described in [Testing Locksmith on unpublished themes](https://www.locksmith.guide/tutorials/more/testing-locksmith-on-unpublished-themes).
{% endhint %}

Following the steps in this guide will help you clear the cache for a single website, **without needing to clear the cache for all websites**. GIFs included!

## Browser-specific steps

### Chrome

![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/5ddd799f2c7d3a7e9ae472fc/images/5e641c9204286364bc966164/file-2HsomwevFh.gif)

1\. Right click, choose "Inspect"

2\. In the Dev Tools menu that shows up, find the "Application" tab

3\. In the Application tab, make sure that "Storage" is selected in the left menu.

4\. Click, "Clear site data", and you're done!

### Firefox

![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/5ddd799f2c7d3a7e9ae472fc/images/5e641da22c7d3a7e9ae8d827/file-Sr47LG4xWE.gif)

1\. Directly to the left of the URL bar, click on the lock icon.

2\. Choose "Clear Cookies and Site Data" and the very bottom of the drop down

3\. Make sure you choose your site only, and click Remove.

4\. You're done!

### Safari

![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/5ddd799f2c7d3a7e9ae472fc/images/5e641fc82c7d3a7e9ae8d82c/file-pe35Od54lZ.gif)

1\. Go to Safari > Settings > Privacy

2\. Search for your website.

3\. Click on your website, and click "Remove"

4\. You're done.

### Internet Explorer

1. Go to your website (that you want to delete cookies and cache for)
2. Launch Developer Tools ( or press F12)
3. Go to the Network tab
4. Click the Clear browser cache button, or press Ctrl + R.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.locksmith.guide/tutorials/more/how-to-clear-cache-for-a-single-website.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.