> For the complete documentation index, see [llms.txt](https://docs.gta.clothing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gta.clothing/basics/useful-to-know/project-history.md).

# Project History

Restore points that let you roll back a project, drawable or texture

## Introduction

**Project History** keeps restore points for the edits that are worth being able to take back. It is not the same thing as the automatic backup save described in [Durty Cloth Projects](/basics/useful-to-know/durty-cloth-projects.md): that one protects you from losing unsaved work, this one lets you undo a change you made on purpose and then regretted.

## What gets recorded

Recorded as grouped changes, as they happen:

* File replacements
* Optimizer runs, including model, texture and map generation
* Dummy replacements
* File repairs
* Editor saves, such as material or embedded texture edits

Collected when you save the project:

* Settings changes
* Structural edits

## Rolling back

Each row says what caused the change, such as model optimization, texture optimization, generated maps or a live texture edit. Select it to see the affected files and available before/after details, including triangle counts, texture dimensions, compression formats and sizes. Live edits identify the diffuse, normal or specular channel. History opened from one drawable or texture variation shows the details for that selection. Older restore points may have fewer details.

Select an entry and roll back:

* the **whole project**, or
* a single **cloth drawable**, or
* a single **texture variation**.

Rolling back one drawable is usually what you want. It means a bad optimizer result on one item does not cost you every other change you made in the same session.

{% hint style="info" %}
Each project keeps up to **100 restore points**. They are lightweight, so this costs far less space than 100 copies of the project.
{% endhint %}

## Things worth knowing

* History writes are transactional, so a restore point stays consistent even when an antivirus scanner or search indexer observes the write.
* If a cleanup removed the data an older rollback needed, the entry says so rather than failing halfway through.
* A very large operation is recorded as a bounded project level restore point instead of thousands of individual ones.
* Running **Optimize & cleanup project data** from the Project Actions deletes unused files, which can remove what older restore points need.

{% hint style="warning" %}
Automatic recovery backups are a separate system and are not part of Project History. See [Durty Cloth Projects](/basics/useful-to-know/durty-cloth-projects.md).
{% endhint %}