# Text

The **Text** component is used to display text in your apps. It supports both binding to *Data Values*, and constant text-defined design time in the UI Designer.

### White Space and Line Break

Sequences of white space in the text value are by default collapsed, and newline characters are handled the same as the other white space. Its lines wrap as necessary to fill the container.

This default behaviour can be overridden. In the **Text** component's Property Pane, open the format\_paint **Style** section and change the **Line Break** value to, for instance, `Pre Wrap` to respect sequences of white space and newline characters. Have a look in the corresponding *Blue Dot* for details about all **Line Break** options.

### Wrapping and ellipsis (...)

You may force the text to be truncated into 1 line with an ellipsis (...) at the end, using the **No Wrap** setting.

If you do *not* tick No Wrap, the text will / may break over multiple lines.

You may limit the number of lines using the **Max Lines** setting. E.g. having the Max Lines set to 4, the text will be truncated with an ellipsis (...) at the end of the 4th line.

### Markdown

The **Text** component has built-in support for parsing Markdown content. You may activate this by ticking **Enable Markdown** in the component properties. Styling defined in the current *Theme* is applied to relevant HTML elements.

Markdown is a lightweight markup language for creating formatted text using a plain-text editor, allowing text to be converted to HTML.

See the [Markdown](/reference/platform-concepts/markdown.md) section for details about supported Markdown syntax.

### Rich Text

The **Text** component can be used to render a Rich Text property, either as Plain Text, Markdown or HTML. When databinding to a data value, [Value processor](/reference/platform-concepts/value-processor.md) must be enabled to make Rich Text properties available for selection. The image below shows how to perform this action in the databinding dialog. Note: Rich Text properties will be disabled before enabling the Value Processor.

<figure><img src="/files/AfAYAZWmW9ygYAuvUKI4" alt="" width="354"><figcaption><p>How to format a Rich Text property to Plain Text in a Text component</p></figcaption></figure>


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://docs.appfarm.io/library/ui-components/text.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.