# Asset Versioning ### About this export | Field | Value | | --- | --- | | **content_type** | lesson | | **platform** | contentstack-academy | | **source_url** | https://www.contentstack.com/academy/courses/contentstack-assets-foundations/asset-versioning | | **course_slug** | contentstack-assets-foundations | | **lesson_slug** | asset-versioning | | **markdown_file_url** | /academy/md/courses/contentstack-assets-foundations/asset-versioning.md | | **generated_at** | 2026-05-28T12:30:00.528Z | > Part of **[Contentstack Assets Foundations](https://www.contentstack.com/academy/courses/contentstack-assets-foundations)** on Contentstack Academy. **Academy MD v3** — structured for retrieval; no quiz or assessment keys. #### Video details #### At a glance - **Title:** Asset Versioning - **Duration:** 3m 40s - **Media link:** https://cdn.jwplayer.com/previews/1OG3niVD - **Publish date (unix):** 1778505351 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113701 kbps - video/mp4 · 180p · 180p · 148559 kbps - video/mp4 · 270p · 270p · 170858 kbps - video/mp4 · 360p · 360p · 192569 kbps - video/mp4 · 406p · 406p · 206338 kbps - video/mp4 · 540p · 540p · 250771 kbps - video/mp4 · 720p · 720p · 322395 kbps - video/mp4 · 1080p · 1080p · 529107 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/1OG3niVD-120.vtt` #### Video transcript In a fast-moving content team, mistakes happen. A designer uploads the wrong crop. A writer accidentally deletes a critical disclaimer from the metadata. In most systems, that's a crisis. In Assets, it's just a version. Asset versioning is your built-in safety net, providing a complete history of every change you made to your library. And the great thing is, you don't have to turn on Assets. It's always watching. Every time you update a file, you change a metadata field, or even just hit save, Content Stack automatically creates a new version. And it's not just for the image itself. It's for the entire asset record. If you change any type of meta information, that change is captured as a distinct moment in time. So to illustrate this, I'm going to open up this image here, which I have a bunch of different versions for. And this one's a little bit more visual in the sense that I made some visual updates to this image. So first and foremost, how do you see the versions? Well, there's two ways. Over here on the right-hand side, you can click Versions to expand this panel. This same icon is available up here towards the top. It acts as a toggle, so if you click it again, it will just collapse. But I do want to expand it. I know version 3 looks different, because right now this is a black and white version. So if I click version 3, it will load, and you can see it's not the black and white version. And you can navigate all the different versions the same way. Now, if I come in here and make another change, like I add a campaign name, I'll type in Summer 2026, if I save this asset, a new version will be created. It's now version 9. Now, one of the things that doesn't make a lot of sense are the version names sometimes, and you may want to update them. And you can do that by clicking this little icon here, and we can call this Metadata Change. Or we could be really specific and type in Campaign Name. And when you press Return or Enter, it's applied. I could come down here and change this to Color Image. So by doing this, you're giving each version state a unique name, making it a lot easier to identify what that version actually represents. And the great thing is, the most powerful feature here is the rollback recovery mechanism. Let's say I no longer wanted that metadata associated with it. I could come back here and click on version 8, and then I can click Save Asset, and you'll notice it'll be renamed a new version number, which in this case will be version 10. And if we look at the editable metadata, you can see it no longer has that campaign name. Safety also means control. While anyone with view access can see the version history, only users with edit permissions can rename or restore versions. So versioning turns your asset library into a time machine. It reduces risk, supports audit requirements, and gives your team the freedom to iterate faster because they know they can always go back. #### Key takeaways - Connect **Asset Versioning** 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 Asset Versioning. Asset Versioning in Contentstack Assets Foundations (contentstack-assets-foundations). ### Retrieval tags - Asset - Versioning - contentstack-assets-foundations - lesson 05 - Asset Versioning - contentstack-assets-foundations lesson ### Indexing notes Index this lesson as a primary chunk tagged with lesson_id "05" and topics: [Asset, Versioning]. Parent course slug: contentstack-assets-foundations. 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: Asset Versioning | `https://cdn.jwplayer.com/v2/media/1OG3niVD/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/` |