> For the complete documentation index, see [llms.txt](https://docs.devin.fm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devin.fm/guides/versions/save-a-version.md).

# Save a Version

## Guide

To save a [version](/features/version-control.md#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](/guides/projects/project-settings.md). 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`.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devin.fm/guides/versions/save-a-version.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.