> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/gum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/gum/gum-tool/gum-elements/nineslice/is-tiling-middle-sections.md).
# Is Tiling Middle Sections
## Introduction
The `Is Tiling Middle Sections` property controls whether the non-corner sections of a NineSlice are tiled (repeated) instead of stretched. By default this value is `false`, meaning the middle sections stretch to fill the available space. When set to `true`, the middle sections repeat their texture at its natural size instead of stretching.
This property appears in the **Source** category in the **Variables** tab.
This is useful for textures with repeating patterns like brick walls, chains, or borders where stretching would distort the pattern.
Two NineSlices, one streching and one tiling middle section
## Default Behavior (Stretching)
By default, when a NineSlice is resized, the five non-corner sections (Top, Bottom, Left, Right, and Center) are stretched to fill the space between the corners. This works well for smooth or gradient textures, but can create visible distortion with patterned textures.
## Tiling Behavior
When `Is Tiling Middle Sections` is set to `true`, the five non-corner sections repeat their texture instead of stretching:
* **Top** and **Bottom** edges tile horizontally
* **Left** and **Right** edges tile vertically
* **Center** section tiles in both directions
The four corner sections (Top Left, Top Right, Bottom Left, Bottom Right) are never tiled — they always render at their natural size regardless of this setting.
---
# 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.flatredball.com/gum/gum-tool/gum-elements/nineslice/is-tiling-middle-sections.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.
