# Versioning

## Overview&#x20;

Thunkable’s versioning functionality allows you to preserve a version of your drag and drop project at a point in time. Project versioning provides a better way to organize and manage multiple versions of your projects, allowing you to easily find past iterations and revert back to previous versions if you make changes to the original version that you end up disliking.

There are two forms of versioning available, auto-versioning and manual versioning, both of which are available to our Builder and Advanced Creators.&#x20;

Accelerate and Builder plans allow for 10 manual versions per project, and Advanced plans allow for 50 versions per project. Overall storage limits remain the same and each saved version counts towards the account’s limit, meaning if a creator makes one version of a 50MB project they will be using 100MB of account storage. For more on plan limits please see here: [Thunkable pricing](https://thunkable.com/pricing).

## Video Tutorial

### How to Save Versions of Your Thunkable Project

In this tutorial, we’ll show you how to use Thunkable’s versioning functionality to preserve a version of your project at a point in time.

{% embed url="<https://youtu.be/CXtBrjJ8Fw8>" %}

## Auto-versioning

Never worry about losing your app progress with auto versioning. Thunkable automatically backs up your projects every few hours.

To access the two most recent auto versions of your project:&#x20;

1. Access the **Design** tab of your project.&#x20;
2. Click the **Version History** clock icon in the upper right.\
   ![](https://1223006790-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LAn5scXl2uqUJUOqkJo-84897653%2Fuploads%2FhF1d6rLal19IWnZ6oSj2%2Fversion_history.png?alt=media\&token=fa736d9f-4610-4a1d-9b19-18284d976af8)

Each auto version’s name reflects the date and time the version was created.

### Version actions&#x20;

Click the version’s vertical ellipsis to access its version actions.

#### Restore&#x20;

The Restore option reverts your current project to this version.&#x20;

## Manual versioning

### Create an app version&#x20;

To save a version of your project:&#x20;

1. Access the **Design** tab of your project.&#x20;
2. Click the **Version History** clock icon in the upper right.\
   ![](https://1223006790-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LAn5scXl2uqUJUOqkJo-84897653%2Fuploads%2FMlRBkSymotbnqTwa1cHG%2Fverioning-new%20Version%20History%20icon.png?alt=media\&token=8bbb7863-d047-4b93-a544-0c8cfd7f7c33)
3. Click **Create Version**. A new version of the project is created with the default version name reflecting the date and time the version was created.&#x20;
4. To change the name of a version, click in the version name field and type your preferred version name.

### Version actions&#x20;

Click the version’s vertical ellipsis to access its version actions.

#### Restore&#x20;

The Restore option reverts your current project to this version.&#x20;

#### Save As&#x20;

The Save As option saves that version as a new project. Select a name for your new project and then click Create. The newly created project is now available on your Projects Page, and the version will remain within the existing project.

#### Delete

The Delete option will permanently delete the selected version. This action can’t be undone.

## Additional considerations&#x20;

* If you downgrade your subscription plan, you will lose your oldest versions up to your new limit.&#x20;
* Creating a new version of a project makes a full copy of the project, including project settings such as name, project privacy, data, etc. Restoring a version will also restore those settings.


---

# Agent Instructions: 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:

```
GET https://docs.thunkable.com/getting-started/versioning.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
