> For the complete documentation index, see [llms.txt](https://motivlabs.gitbook.io/impulse-user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://motivlabs.gitbook.io/impulse-user-manual/content-storage-options.md).

# Content Storage Options

Impulse has three options for content storage each with various pricing options. 

## Temporary Storage

Temporary storage is storage that only last for the length of a sync/pipeline transaction. This means that every transaction all content will need to be picked up again adding additional time to the length of the transaction. 

Temporary storage is the default of all transactions unless otherwise specific. 

{% hint style="info" %}
Storage also effects where the [get-set-field](/impulse-user-manual/content-manipulators-motators/get-set-field.md) or [store-field](/impulse-user-manual/content-manipulators-motators/store-field.md) manipulator retrieve and store their values. If using temporary storage, ensure that all jobs are in a pipeline sharing the same temporary storage. 
{% endhint %}

## Content Storage

Content storage is storage that lasts across transactions. This data is not deleted after a transaction is finished. This allows for transactions to run faster since they only need to pick up content that has been changed since the last time it was picked up. 

Content storage must be specified at the job option level or the REST endpoint level. 

## Snapshot Storage 

Snapshot storage is storage that captures all the content picked up for a transaction into a specific snapshot that acts as a point in time capture for the content. 

Snapshot storage must be specified by the REST endpoint used to start a transaction.