> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/assets/version-control-and-stacking.md).

# Version Control and Stacking

## Versioning and Comparison

As you’re going through review and approval cycles for your creative work, Shade enables you to nest your versions in an organized way and visually compare what changes have transpired version over version. Comparing assets isn’t limited to nested versions; you can select files from within you folder hierarchy, views, collections, or search results, and compare those as well.

Key features:

* No limits to how many versions can exist within a stack
* Compare up to 6 assets side by side at once
* Compare mixed media types to ensure a cohesive look across videos, photos, and designs

### Comparing media that hasn’t been versioned

From within your folder hierarchy, a view, collections, or search results:

1. Select up to 6 files
2. Right-click on any of the selected items
3. Choose **Compare X Assets**

A viewer window will open showing all selected assets.

* Press the play button to simultaneously playback any video files
* Select a file to view existing or leave comments
* Close the comment panel if you want to dedicate the full page to viewing whats being compared

### Versioning, managing versions, and comparing versions

#### Creating versions

There are 3 flows for versioning:

1. Upload a new file is in Shade in the same folder as the previous version or version stack
2. Drag and drop it directly onto the older version, or existing version stack

OR

1. Right-click on the file where you’re looking to add your new version
2. Choose **Upload New Version**

OR

1. Double-click a file to open it
2. Click the 3-dot menu in the top right corner
3. Choose **Upload New Version**

#### Managing versions

When viewing files and folder:

1. Right-click on a file that has versions
2. Choose **Manage Versions**
3. Click and drag handles next to version numbers to modify the order of versions
4. Click the 3-dot menu for a given version to remove from the version stack

From within the asset viewer/player page:

1. Click the 3-dot menu in the top right corner
2. Choose **Manage Versions**
3. Click and drag handles next to version numbers to modify the order of versions
4. Click the 3-dot menu for a given version to remove from the version stack

#### Comparing Version

There are 3 flows for comparing versions:

1. Right-click on a file with versions
2. Choose **Compare Versions**
3. Select the versions you want to compare

OR

1. Double-click a file to open it
2. Click the 3-dot menu in the top right corner
3. Choose **Compare Versions**
4. Select the versions you want to compare

A viewer window will open showing all selected versions.

* Press the play button to simultaneously playback any video files
* Select a file to view existing or leave comments
* Close the comment panel if you want to dedicate the full page to viewing whats being compared

### Comparison views

When comparing assets or versions, you can switch between three views:

* **Side by side** shows the assets next to each other. This view is always available.
* **Stacked** layers the assets on top of each other. It is available when all assets are images or videos, with up to 4 videos.
* **Swipe** lets you swipe between two assets. It needs at least two images, videos, or documents.

You can also switch views with the keyboard: **`b`** for side by side, **`t`** for stacked, and **`w`** for swipe.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.shade.inc/assets/version-control-and-stacking.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
