1.  [Documentation](/en/docs)
2.  [Getting started](/en/docs/getting-started/quickstart)
3.  Core concepts

# Core concepts

Three ideas explain DocTransform: your rows stay in your browser, a Template saves your steps and mapping lines them up with the destination.

## Your rows stay in your browser

DocTransform keeps the rows of your file in your browser, in IndexedDB, not on our servers. Exporting runs in your tab too, so the file you download is built on your device. The uploaded file stays on the server only while you edit and is removed after 30 minutes without activity.

## A template is an ordered list of steps

A template saves the steps you applied to a file, in order, together with your mapping. Run it on a new file with the same columns to repeat the result in seconds, from the app or from [your first API run](/en/docs/api/quickstart). If a step is wrong, [Undo and redo](/en/docs/guides/undo-redo) walks back through your changes.

## Mapping aligns your columns with the destination

Mapping points each of your columns at the name your destination expects, for example Unit Price at Unit\_Price. It is saved in the template with the other steps, and a column must exist before a step uses it.

## A reference table is a file you keep to look values up in

A reference table is a file you save once, such as a product catalog or a list of customer codes. A template can look values up in it, for example to add each product’s category by its SKU, and it does so every time the template runs. Reference tables you save stay in your account until you delete them.

A join step in a template reads the table as it is on the day of the run. See [Joining files](/en/docs/guides/joining-files) for how to save one.
