> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/frequently-asked-questions/how-do-i-control-text-wrapping.md).

# How do I control text wrapping?

{% hint style="info" %}
It's not possible to control text-wrapping when you're using the [SNA template](/guides/templates.md#sna-social-network-analysis-template), or any view that has "fast" quality or uses the WebGL renderer.
{% endhint %}

When you want to fit text inside of an element, or just make sure that labels underneath elements aren't too wide, you can customize your **text-wrapping**.

As long as you aren't using the [SNA template](/guides/templates.md#sna-social-network-analysis-template), "fast" quality, or the WebGL renderer, you can force a line break in the label of an element, connection, or loop by adding a **double-space** inside the label.

Here's a screenshot of an element before adding any double-spaces:

![element with unusually long label](https://1181816445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkXSW1nEf49ISqGxYuRfS%2Fuploads%2Fgit-blob-4f06d9f0240efb1a8022452d95e22837949a2716%2Funusually-long-label.png?alt=media)

And here's a screenshot of that same element, with a double-space between the words "with" and "an", and with a double-space between the words "unusually" and "long".

![element with unusually long label broken up using double-spaces](https://1181816445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkXSW1nEf49ISqGxYuRfS%2Fuploads%2Fgit-blob-26279eb23c0966877cc59fb34a492d4774d6fe00%2Funusually-long-label-double-space.png?alt=media)

For a solution that's a bit more automated, and doesn't require you to open each profile and tinker with double-spaces in every label, you can use the `text-overflow` property in the Advanced Editor. You can use `text-overflow` inside of [`@settings`](/guides/default-view-settings.md#change-default-view-settings-in-the-advanced-editor), or inside of a block that starts with any [selector](/guides/selectors.md).

```scss
@settings {
  text-overflow: auto 20;
}

element {
  text-overflow: wrap 10;
}
```

The table below has a description of all the possible values you can use for the `text-overflow` property, and what the effect of each one is.

| Value           | Effect on text overflow                                                                                                                                                                                                    |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `off`           | Text wrapping will be turned off completely.                                                                                                                                                                               |
| `auto`          | Shorthand for `auto 20` (see `auto [number]` explanation).                                                                                                                                                                 |
| `auto [number]` | Text will wrap at the first space it finds after `[number]` characters (e.g. `10` characters if you specify `auto 10`). If you add a double-space anywhere in the label, the entire label will only wrap at double-spaces. |
| `manual`        | Text will only wrap at double-spaces.                                                                                                                                                                                      |
| `wrap`          | Shorthand for `wrap 20` (see `wrap [number]` explanation).                                                                                                                                                                 |
| `wrap [number]` | Text will wrap at the first space it finds after `[number]` characters (e.g. `10` characters if you specify `wrap 10`). Double-spaces will be ignored and will nor force text to wrap.                                     |
| `clip`          | Shorthand for `clip 20` (see `clip [number]` explanation).                                                                                                                                                                 |
| `clip [number]` | Text will clip and be replaced with an ellipsis after `[number]` characters (e.g. `10` characters if you specify `clip 10`). Text will never wrap.                                                                         |


---

# 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.kumu.io/frequently-asked-questions/how-do-i-control-text-wrapping.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.