---
title: CDN links and updates
description: Use current assets, keep your links up to date, and troubleshoot files that are not loading.
sidebar:
  label: Links and updates
  icon: globe
  order: 8
---

Use **[https://cdn.shaughv.com/](https://cdn.shaughv.com/)** for current assets. Copy a file URL or snippet from its guide, and your site can load the asset directly.

## Find the right file

Start with the [asset showcase](/showcase) to see the artwork and try the fonts. Each guide provides the file links and code needed to use them:

- [Fonts](/fonts): family names, supported weights, and stylesheet imports.
- [Brand assets](/brand): logos, favicons, crests, and figurines.
- [Motion](/motion): animated marks and loaders.
- [Quickstart](/quickstart): a working first example for your site.

For a complete list of available files, open the [asset catalog](https://cdn.shaughv.com/tree.json). Copy the exact URL, including capitalization and file extension.

## How updates reach your site

The guides and catalog are updated alongside the assets. Check the relevant guide when adding a new family, changing an embed, or replacing an asset.

If you link directly to a stylesheet or script, your site receives updates to that URL as its cached copy refreshes. Downloads copied into your own project stay as they are until you replace them.

Fonts and images are cached for longer. A changed binary asset is published at a new filename, so adopting that version means updating your link to the new URL from the catalog. Refreshing the page alone will not change which filename your site uses.

## If something does not load

1. **Open the file URL directly.** If it is missing, find its current URL in the catalog. Check capitalization and the extension.
2. **For fonts, load the stylesheet first.** Then use the exact CSS family name and an available weight from the [font guide](/fonts). Downloading a font file alone does not apply it to the page.
3. **For an older-looking result, check the URL and cache.** Confirm that your code points to the intended file. During development, a hard refresh can help with a browser's cached stylesheet or script; a newly named asset still needs its new URL.
4. **Compare with the showcase.** If the [live preview](/showcase) works, compare your embed with the guide's example, including dimensions, color, and font settings.

The [technical reference](/reference) has the cache durations, file namespaces, and cross-origin details if your integration needs them.