# [Usage](../../../usage.md) > Framework refresh assets

Use `kfw:refresh-assets` when the browser bundle is stale or custom CSS/JS was added. Unlike `cache:clear` (server cache), it bumps the asset version and recompiles the public bundles so clients download the new files.

---

## Method

### `php artisan kfw:refresh-assets`

#### Arguments

None.

#### What it does

- Advances `kfwAssetsVersion` beyond both the cache value and `storage/app/kfw-assets-version.txt`.
- Stores the new version in cache (`forever`) and in the version file.
- Concatenates CDN, framework, and custom JS into `public/vendor/k-framework/kfw_assets.js`.
- Concatenates CDN, framework, and custom CSS into `public/vendor/k-framework/kfw_assets.css`.
- Copies `kfw_boot.css`, `kfw_boot.js`, and `kfw_boot_helpers.js` verbatim.
- Writes `public/vendor/k-framework/kfw_assets_version.txt` with the new version.

---

## Output

Console lines confirming compilation and the output paths with the new version.

---

## Example

```bash
php artisan kfw:refresh-assets
```

Custom assets in `public/vendor/k-framework/custom-js` and `custom-css` are picked up automatically. For publishing plus refresh, use `kfw:publish`.

## See also

- [Usage](../../../usage.md)
- [Framework publish](kfw_publish.md) — publishing plus refresh
- [Framework update](kfw_update.md) — full update workflow
- [Registering custom CSS and JS](../../frontend/registering_assets.md) — custom asset sources