> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-work-with-rich-text-fields.md).

# How To: Work with Rich Text Fields

Preserve or strip formatting when working with rich text fields.

Use the right output mode when rich text fields contain formatting you either need to keep or remove.

### Problem

You have rich text fields with HTML formatting that need to be displayed or stripped in your documents.

### Solution 1: Preserve Formatting

**Use triple braces:**

```
{{{!Opportunity.Description__c}}}
```

This preserves:

* Bold, italic, and underline
* Font colors and sizes
* Bullet and numbered lists
* Hyperlinks
* Tables
* Images in PDF and DOCX

### Solution 2: Strip Formatting

**For merge fields:**

```
{{!Opportunity.Description__c strip-html="true"}}
```

**For related lists:**

```
<column type="text">Description__c</column>
```

**Input:** `<p>This is <b>bold</b> text with <a href="#">links</a></p>`\
**Output:** `This is bold text with links`

### Solution 3: Preserve Formatting in Related Lists

```
<column type="rtf">Rich_Notes__c</column>
```

### Comparison

| Method              | HTML Tags | Formatting | Images       | Best for                    |
| ------------------- | --------- | ---------- | ------------ | --------------------------- |
| `{{{!Field}}}`      | Rendered  | Preserved  | PDF and DOCX | Standalone rich text output |
| `strip-html="true"` | Removed   | Lost       | No           | Plain text output           |
| `type="rtf"`        | Rendered  | Preserved  | PDF and DOCX | Rich text inside tables     |
| `type="text"`       | Removed   | Lost       | No           | Plain text inside tables    |

### Tips

* Use triple braces for standalone rich text fields.
* Use `type="rtf"` inside table columns.
* Strip HTML when you need plain text only.
* Test images and formatting in the output format you support.


---

# 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://help.sdocs.com/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-work-with-rich-text-fields.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.