> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/squash/quick-guide/nodes/export.md).
# Export
Choose export destinations and save processed images
Use **Location → Save To** in the sidebar to choose where your processed images go. Click **Export Images** at the bottom of the settings sidebar to export the whole batch. In the Free version, a pill beside the button shows how many free exports are left today, and the button may read **Export 3 of 12** or **Unlock to Export**; see [Is Squash free?](/squash/licensing-faq.md#is-squash-free).
### Choosing a destination
| Destination | Where files go |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Choose Folder… | A folder you select in the macOS panel. Squash remembers it for later exports. |
| Same Folder as Original | Beside each source image, even when the batch comes from several folders. |
| Subfolder of Original | Into a named subfolder inside each source image's folder. Choose `squashed`, `minified`, `compressed` or **Custom…**. |
| Recent folder | A previously selected destination. Squash keeps up to five recent folders. |
If no destination is set, exporting prompts you to choose one. A single image with no destination uses the macOS Save panel.
Use **Show in Finder** to open a chosen destination folder. **Clear Recents** clears the recent-folder menu. Export destinations can also be saved in [Presets](/squash/quick-guide/presets.md).
When saving beside originals, macOS may ask you to grant access to their folders. Images without an original file location, such as pasted images, prompt for a destination instead.
### Subfolders
The **Subfolder** field under **Save To** adds folders inside whichever destination you chose. Leave it empty to save straight into the destination.
| Save To | Where files go |
| ----------------------- | --------------------------------------- |
| A chosen folder | `your folder/subfolder/` |
| Same Folder as Original | `original's folder/subfolder/` |
| Subfolder of Original | `original's folder/squashed/subfolder/` |
Type a name, or click **+** to add tokens and [variables](/squash/quick-guide/variables.md). All the [Rename](/squash/quick-guide/nodes/rename.md#filename-tokens) tokens work here except **Describe**, so each image can go to its own folder. Type `/` to nest folders.
| Subfolder | Example folder |
| ------------------------- | --------------------------------------------------- |
| `web` | `web` |
| `{{year}}/{{var:Client}}` | `2026/Acme` |
| `{{aspect}}` | `3x2` for landscape images, `2x3` for portrait ones |
| `{{folder}}/{{format}}` | `Holiday/jpg` |
The caption below the field shows where the first image in the list will go, and each row in the image list shows its own path. Squash creates the folders when you export. If a folder can't be created, only the images going there fail.
A few rules keep files inside your destination:
* A path can be up to five folders deep. When saving to **Subfolder of Original**, the named subfolder counts towards the five.
* `:` and `\` are removed from folder names, and a folder that would be named `.` or `..` is skipped.
* A folder whose name comes out empty, such as one that's just a [variable](/squash/quick-guide/variables.md#empty-values) with no value, is skipped. If every folder is skipped, images save straight into the destination.
**Custom…** under **Subfolder of Original** takes tokens and variables in the same way.
The **Subfolder** field applies when you export to a destination from Save To. Dragging an image out of Squash, **Export Selected Image As…** and **Export Image To…** save exactly where you choose, and images with no original file location go straight into the destination you pick for them.
### Overwrite
With **Overwrite** off, an existing file is preserved and Squash adds a numbered suffix to the new filename, such as `photo-1.jpg`.
With Overwrite on, files with matching names can be replaced. When a same-folder export would replace originals, Squash shows a warning unless you have previously chosen to suppress it.
{% hint style="warning" %}
Saving to **Same Folder as Original** with Overwrite enabled can replace your source files. Check the planned output names and destination before exporting. Use a separate folder or leave Overwrite off to keep original files.
{% endhint %}
### Showing exported images in Finder
In **Settings → General**, select **Show exported images in Finder** to reveal the exported files or destination after a successful save. If an export spreads images across several subfolders, Squash opens the top of the destination instead of selecting each file.
### Exporting one image
Choose **File → Export Selected Image As…** (**Command-Shift-E**) to save the current image to a location you choose. A row's **Export Image To…** action also opens a destination panel.
**File → Export All Images** (**Command-E**) exports the whole batch. **File → Squash** calculates the compressed results without writing them to your destination.
You can also drag an image out of Squash to export a processed copy, or use **Copy Squashed** to put it on the clipboard.
### Progress
The **Activity** button (the progress ring at the bottom left of the settings sidebar, beside **Export Images**) shows export progress. Click it to follow or cancel an export, or to choose **Show in Finder** for a recent one. Export files are created during the export operation; wait for it to finish and check the destination before removing the batch.
Squash 3 reference screenshots
These screenshots show the earlier Squash 3 interface.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.realmacsoftware.com/squash/quick-guide/nodes/export.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.