---
title: "My browser does not reload the updated sprite sheet"
description: "How to use the \"Enable cache busting\" setting so your app fetches the latest sprite sheet after redeploying, instead of serving a stale browser or CDN copy."
canonical: "https://www.codeandweb.com/texturepacker/knowledgebase/cache-busting"
product: "texturepacker"
source: "html"
---

# My browser does not reload the updated sprite sheet

If you redeploy your game with an updated sprite sheet, browsers and CDNs may keep serving the old cached version — even though the new file is already on your server. As a result, your players see outdated sprites until they manually clear their cache.

Enable cache busting to fix this:

*   In the GUI: open the advanced **Data file** settings and check **Enable cache busting**.
*   On the command line: pass `--enable-cache-busting`.

When enabled, TexturePacker appends a hash-based query string to the texture file name inside the data file, e.g.:

```json
"image": "sheet.png?v=ab12cd34"
```

The hash changes whenever the sprite sheet content changes. Browsers and CDNs treat each unique URL as a separate resource, so they fetch the new file instead of serving the cached one.

This setting is **disabled by default** and is only available for the **PixiJS** and **Phaser** data formats. Both load the texture URL from the data file, so no changes are needed in your application code — once you re-publish with cache busting enabled, the next deploy invalidates the cache automatically.

See also: [Enable cache busting](https://www.codeandweb.com/texturepacker/documentation/texture-settings.md#enable-cache-busting) in the Texture Settings reference.

## Structured data

```json
{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "headline": "My browser does not reload the updated sprite sheet"
}
```