> 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-convert-text-to-uppercase-or-lowercase.md).

# How To: Convert Text to Uppercase or Lowercase

Force text into uppercase or lowercase for addresses, emails, and document styling.

Use text case attributes when stored Salesforce values do not match your output style.

### Problem

You need to standardize text appearance regardless of how it is stored in Salesforce.

### Solution

**All Uppercase:**

```
{{!Account.BillingStreet ToUpperCase="true"}}
{{!Account.BillingCity ToUpperCase="true"}}, {{!Account.BillingState ToUpperCase="true"}} {{!Account.BillingPostalCode}}
```

**Result:** `123 MAIN STREET, APT 3`

**All Lowercase:**

```
{{!Contact.Email ToLowerCase="true"}}
```

**Result:** `john.smith@example.com`

### Common Use Cases

**Mailing Labels (Uppercase):**

```
<p>
{{!Account.Name ToUpperCase="true"}}<br>
{{!Account.BillingStreet ToUpperCase="true"}}<br>
{{!Account.BillingCity ToUpperCase="true"}}, {{!Account.BillingState ToUpperCase="true"}} {{!Account.BillingPostalCode}}
</p>
```

**Email Addresses (Lowercase):**

```
<p>Email: {{!Contact.Email ToLowerCase="true"}}</p>
```

**Legal Documents (Uppercase for Emphasis):**

```
<p><strong>{{!Account.Name ToUpperCase="true"}}</strong> hereby agrees...</p>
```

### Tips

* Postal codes usually stay as-is.
* Use uppercase for mailing addresses when automated sorting matters.
* Use lowercase for email addresses for consistency.


---

# 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-convert-text-to-uppercase-or-lowercase.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.