> For the complete documentation index, see [llms.txt](https://blackridge.gitbook.io/sonicforge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blackridge.gitbook.io/sonicforge/generation-history.md).

# Generation History

SonicForge keeps a local history of generated sounds so you can return to previous results across editor sessions.

## What you can do

From the history, you can:

* Access previously generated sounds.
* Replay a result.
* Import a previous result into the project.
* Save a previous result again.
* Clear the history when you no longer need the entries.

New history entries appear at the bottom of the list.

## Working with history

Use the history to compare prompt variations and revisit useful results without generating them again. Preview a result before importing or exporting it.

## Clearing history

Use the history clearing control in SonicForge when you want to remove stored entries. Make sure you no longer need the listed results before clearing them.

History is stored locally by the plugin. It is not a cloud library or a replacement for keeping important exported WAV files or project assets. Export or import sounds you want to preserve as part of your project workflow.