> 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/borders.md).

# Borders

Add a decorative border to your images

Install a [border pack](/squash/quick-guide/nodes/effects.md#effect-packs), then choose a border in the **Borders** section to add a decorative frame to your images.

1. Check that a border pack is enabled in **Settings → Effects**.
2. In the Borders section, use the search field or browse the border thumbnails.
3. Click a border and check the result in the [preview pane](/squash/quick-guide/editor.md).

Picking a border turns Borders on. Choose **None**, the first thumbnail, to stop adding a border.

The Borders section appears when at least one border pack is enabled. Border packs are managed alongside filter packs, but their styles appear in Borders rather than Effects.

You can combine a border with an effect or watermark, and save the combination in a [Preset](/squash/quick-guide/presets.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 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/borders.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 `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.