> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/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/elements-docs/elements-language/component/properties-json/ui-controls/theme-border-width.md).

# Theme Border Width

Displays the Theme Studio Border Width control.

{% tabs %}
{% tab title="Control Example" %}

```json
{
  "title": "Card Border",
  "id": "cardBorderWidth",
  "themeBorderWidth": {
    "default": {
      "base": {
        "top": "1",
        "right": "1",
        "bottom": "1",
        "left": "1"
      }
    }
  }
}
```

{% endtab %}

{% tab title="Group Example" %}

```json
{
  "groups": [{
    "title": "Card Styles",
    "properties": [{
      "title": "Card Border",
      "id": "cardBorderWidth",
      "themeBorderWidth": {
        "default": {
          "base": {
            "top": "1",
            "right": "1",
            "bottom": "1",
            "left": "1"
          }
        }
      }
    }]
  }]
}
```

{% endtab %}
{% endtabs %}

The following example links all four sides together and starts with a 2 unit border:

```json
{
  "title": "Border",
  "id": "buttonBorderWidth",
  "themeBorderWidth": {
    "default": {
      "base": {
        "top": "2",
        "right": "2",
        "bottom": "2",
        "left": "2",
        "linkAll": true
      }
    }
  }
}
```

A named width from the theme can also be used as the default:

```json
{
  "title": "Border",
  "id": "cellBorderWidth",
  "themeBorderWidth": {
    "default": {
      "base": {
        "name": "none"
      }
    }
  }
}
```

### Supported Options

The themeBorderWidth control supports the following options.

| Key       | Type   | Notes                                                                           |
| --------- | ------ | ------------------------------------------------------------------------------- |
| `default` | object | Per-breakpoint defaults (`base`, `sm`, `md`, …). See the breakpoint keys below. |

Each breakpoint object inside `default` supports these keys:

| Key                           | Type    | Notes                                                                 |
| ----------------------------- | ------- | --------------------------------------------------------------------- |
| `top` `right` `bottom` `left` | string  | Border width per side, as a theme border-width token.                 |
| `name`                        | string  | A named theme border width applied to all sides, for example `none`.  |
| `custom`                      | boolean | When `true`, values are arbitrary CSS values instead of theme tokens. |
| `linkHorizontal`              | boolean | Links the left and right sides together.                              |
| `linkVertical`                | boolean | Links the top and bottom sides together.                              |
| `linkAll`                     | boolean | Links all four sides together.                                        |

### Value

In templates, `{{id}}` outputs the Tailwind border-width utility classes for the selected sides, prefixed for each breakpoint the user has configured.


---

# 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://docs.realmacsoftware.com/elements-docs/elements-language/component/properties-json/ui-controls/theme-border-width.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.