# Understanding Asset URLs and Metadata

### About this export

| Field | Value |
| --- | --- |
| **content_type** | lesson |
| **platform** | contentstack-academy |
| **source_url** | https://www.contentstack.com/academy/courses/creating-and-managing-content/understanding-asset-urls-and-metadata |
| **course_slug** | creating-and-managing-content |
| **lesson_slug** | understanding-asset-urls-and-metadata |
| **markdown_file_url** | /academy/md/courses/creating-and-managing-content/understanding-asset-urls-and-metadata.md |
| **generated_at** | 2026-05-08T12:23:52.525Z |

> Part of **[Creating and Managing Content](https://www.contentstack.com/academy/courses/creating-and-managing-content)** on Contentstack Academy. **Academy MD v3** — structured for retrieval; no quiz or assessment keys.

<!-- ai_metadata: {"lesson_id":"06","type":"video","duration_seconds":174,"video_url":"https://cdn.jwplayer.com/previews/Pa89JRVq","thumbnail_url":"https://cdn.jwplayer.com/v2/media/Pa89JRVq/poster.jpg?width=720","topics":["Understanding","Asset","URLs","and","Metadata"]} -->

#### Video details

#### At a glance

- **Title:** Understanding Asset URLs and Metadata.mp4
- **Duration:** 2m 54s
- **Media link:** https://cdn.jwplayer.com/previews/Pa89JRVq
- **Publish date (unix):** 1757693687

#### Streaming renditions

- application/vnd.apple.mpegurl
- audio/mp4 · AAC Audio · 113772 kbps
- video/mp4 · 180p · 180p · 185894 kbps
- video/mp4 · 270p · 270p · 243630 kbps
- video/mp4 · 360p · 360p · 294945 kbps
- video/mp4 · 406p · 406p · 335306 kbps
- video/mp4 · 540p · 540p · 479154 kbps
- video/mp4 · 720p · 720p · 715848 kbps
- video/mp4 · 1080p · 1080p · 1564741 kbps

#### Timed text tracks (delivery)

- **thumbnails:** `https://cdn.jwplayer.com/strips/Pa89JRVq-120.vtt`

#### Video transcript

Every asset isn't just a file. It comes with a story, who uploaded it, when it was modified, where it's being used, and the web addresses that allow developers and front ends to pull it into your site. This is where metadata and asset URLs come into play. When you click into an asset, ContentStack shows you more than just a preview. You'll see details like file type, size, dimensions, and even a list of entries that reference the asset. That's critical for knowing whether it's safe to delete or replace something. You'll also see the asset's UID, a unique identifier that never changes, and two different URLs, the file URL and the permanent URL. Here's the distinction. The file URL points to the specific file you uploaded. If you replace that file with a new one, the file URL changes. Think of it as a snapshot in time. The permanent URL is a stable link that always points to the latest version of the asset. Even if you update or replace the file, the permanent URL stays the same and automatically delivers the new version. Think of it as the permanent address that always leads to the current file. So why does this matter? If you're linking an asset into templates, websites, or emails, you'll want to use the permanent URL. It ensures that when the file is updated, your front end doesn't break. Your content automatically reflects the latest version. You may have to create a permanent URL link if one doesn't exist. Just click the Generate Permanent URL link. You'll see it's generated. Then just save the asset. Let's see how this works in practice. With this asset, find the Permanent URL field. Click Copy URL, then paste it into a new browser tab. Notice the image renders immediately. Now imagine replacing this file with a new version. If you were to refresh the browser or call the image from a different app, you'd see the updated file even though you're calling the exact same URL. That's the reliability permanent URLs provide. They make asset delivery predictable and keep your experiences consistent without you having to hunt down broken links. Understanding the metadata and URLs behind your assets helps you make smarter decisions. Whether that's cleaning up unused files, checking dependencies before deleting, or knowing how the front end is pulling in your content. With this knowledge, you're managing assets with confidence, not guesswork.

#### Key takeaways

- Connect **Understanding Asset URLs and Metadata** back to your stack configuration before moving to the next module.
- Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment.
- Re-read the delivery versus management boundary for anything you changed in the entry model.

## Supplement for indexing

### Content summary

Understanding Asset URLs and Metadata. Understanding Asset URLs and Metadata in Creating and Managing Content (creating-and-managing-content).

### Retrieval tags

- Understanding
- Asset
- URLs
- and
- Metadata
- creating-and-managing-content
- lesson 06
- Understanding Asset URLs and Metadata
- creating-and-managing-content lesson

### Indexing notes

Index this lesson as a primary chunk tagged with lesson_id "06" and topics: [Understanding, Asset, URLs, and, Metadata].
Parent course slug: creating-and-managing-content. Use asset_references URLs as thumbnail hints in search results when present.
Never surface LMS quiz content or assessment answers from this file.

### Asset references

| Label | URL |
| --- | --- |
| Video thumbnail: Understanding Asset URLs and Metadata | `https://cdn.jwplayer.com/v2/media/Pa89JRVq/poster.jpg?width=720` |

### External links

| Label | URL |
| --- | --- |
| Contentstack Academy home | `https://www.contentstack.com/academy/` |
| Training instance setup | `https://www.contentstack.com/academy/training-instance` |
| Academy playground (GitHub) | `https://github.com/contentstack/contentstack-academy-playground` |
| Contentstack documentation | `https://www.contentstack.com/docs/` |
