> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/guides/automations/batch-enhance-photos-with-topaz.md).

# Batch-enhance photos with Topaz

Upscale, denoise, sharpen, or deblur every photo dropped into a folder with Topaz Labs, and save the results next to the originals.

**Outcome:** photos dropped into a `To enhance` folder are processed by Topaz Labs, and the enhanced copies are saved to an `Enhanced` folder. The originals stay untouched.

**Who it's for:** photo teams and archives cleaning up low-resolution, noisy, or soft images in bulk.

**Time:** about 10 minutes.

## Before you start

* Build [Your first automation](/guides/automations/your-first-automation.md) first if you haven't used the automation editor.
* In **Settings > Integrate > Integrations**, open **Topaz** and connect it with your Topaz API key.
* Create a `To enhance` folder and an `Enhanced` folder.

## Steps

{% stepper %}
{% step %}

### Trigger on uploads to To enhance

Create an automation named `Enhance photos`. Choose **Asset Uploaded** and set **Upload location** to `To enhance`.
{% endstep %}

{% step %}

### Skip anything that isn't an image

Add a **Filter** step that continues only when the asset's **type** is image.
{% endstep %}

{% step %}

### Pick the enhancement

Add one of the Topaz actions, with **Asset** set to the uploaded asset:

| Action            | Use it for                              |
| ----------------- | --------------------------------------- |
| **Upscale Image** | Low-resolution images you need bigger   |
| **Denoise Image** | High-ISO or grainy shots                |
| **Sharpen Image** | Images that are slightly soft           |
| **Deblur Image**  | Motion blur, lens blur, or missed focus |

You can chain several, for example **Denoise Image**, then **Upscale Image**.
{% endstep %}

{% step %}

### Save the results

Add **Save Files to Drive**. Set **Source URLs** to the Topaz step's output URLs (Shade suggests this step and fills them in), and set **Destination folder** to `Enhanced`.
{% endstep %}

{% step %}

### Save, activate, and test

Click **Save**, then **Activate**, and drop one image into `To enhance`. Check the **Runs** tab if nothing shows up in `Enhanced` after a minute or two.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Never save results into the folder you're watching. Each saved file counts as a new upload and starts the automation again.
{% endhint %}

## Variations

* **Choose per photo instead of per folder:** use a **Manual Trigger** that runs on **Files**, so anyone can right-click an image, choose **Run automation**, and pick the enhancement.

## Related guides

* [Auto-organize new uploads](/guides/automations/auto-organize-new-uploads.md)
* [Your first automation](/guides/automations/your-first-automation.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.shade.inc/guides/automations/batch-enhance-photos-with-topaz.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.