> 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-display-long-urls-or-text-without-breaking-layout.md).

# How To: Display Long URLs or Text Without Breaking Layout

Wrap long URLs or serial numbers without breaking the layout.

Use `breakeverynchars` when long unbroken strings overflow a cell or page.

### Problem

Long unbroken strings like URLs, serial numbers, and hashes overflow table cells or fail to wrap.

### Solution

**Insert line-break opportunities:**

```
{{!Opportunity.Long_URL__c breakeverynchars="50"}}
```

**For related lists:**

```
<column breakeverynchars="40">Long_Serial_Number__c</column>
```

### Practical Examples

**Product serial numbers:**

```
<table>
<!--{{!
<lineitems>
<listname>opportunitylineitems</listname>
<column>PricebookEntry.Product2.name</column>
<column breakeverynchars="20">SerialNumber</column>
</lineitems>
}}-->
</table>
```

**Long URLs:**

```
<p>Reference: {{!Case.Reference_URL__c breakeverynchars="60"}}</p>
```

**Input:** `https://www.example.com/very/long/path/to/resource/that/needs/to/wrap`\
**Output:** `https://www.example.com/very/long/path/to/resource/that/n eeds/to/wrap`

### For PDF-Upload Templates

If you use PDF-Upload templates, add this to the **Additional Style** field:

```
white-space: normal!important;
```

This forces text to wrap at the inserted break points.

### Tips

* Choose the break interval based on column width.
* Smaller values create more wrap points.
* Too small can make text hard to read.
* Test with real data before release.
* This works with any text field.


---

# 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-display-long-urls-or-text-without-breaking-layout.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.