# Save a Version

## Guide

To save a [version](https://docs.devin.fm/features/version-control#versions) of a branched development file:

1. Go to Branches -> Versions
2. Select the desired file from the list
3. Select the top Active File line in the version list.
4. In the right sidebar, enter a version description and select Full Backup or Clone
5. When prompted, enter a [version number](#version-numbers).

{% hint style="warning" %}
Versions are backups of the development file. They can be either clones or full backups and the default choice can be specified in [project-settings](https://docs.devin.fm/guides/projects/project-settings "mention"). For large file sizes (> 100MB), we recommend using Clone as default. Choosing Full Backup might result in bad performance on your development server. 
{% endhint %}

## Video Tutorials

### Connect to a branched development file

{% embed url="<https://vimeo.com/1038622621>" %}
Make changes to a development file
{% endembed %}

### Make changes to a file (and see the changes)

{% embed url="<https://vimeo.com/1038622257?share=copy#t=0>" %}
Make changes to a development file
{% endembed %}

### Save a new version with the changes

{% embed url="<https://vimeo.com/1038622732?share=copy#t=0>" %}
Saving a Version
{% endembed %}

## Version Numbers

Devin supports a wide variety of versioning conventions, but we recommend using a standard convention like [Semantic Versioning](https://semver.org) or similar that uses a format that looks like `MAJOR.MINOR` or  `MAJOR.MINOR.PATCH`.&#x20;

For more advanced use cases, like when you're dealing with pre-release versions, Devin also supports version numbers that include letters, such as `2.10.3-alpha` and `2.10.3-beta8`.