> 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/template-architecture/document-formats/pdf-templates/supported-fonts-in-pdf-format.md).

# Supported Fonts in PDF Format

Salesforce PDF rendering supports a limited set of `font-family` values.

These rules apply to server-side PDF rendering. Browser output can differ.

### Supported `font-family` values

| Typeface         | Supported `font-family` values                      |
| ---------------- | --------------------------------------------------- |
| Arial Unicode MS | `Arial Unicode MS`                                  |
| Helvetica family | `sans-serif`, `SansSerif`, `Dialog`                 |
| Times family     | `serif`, `Times`                                    |
| Courier family   | `monospace`, `Courier`, `Monospaced`, `DialogInput` |

### Fallback behavior

If you use a value that is not listed here, PDF output falls back to `Times`.

For example, `Helvetica` is not a supported `font-family` value in Salesforce PDF rendering.

Use `sans-serif` instead.

{% hint style="warning" %}
If PDF output does not use the font you expect, check the exact `font-family` value first.
{% endhint %}

### Multibyte character support

`Arial Unicode MS` is the only multibyte font available in Salesforce PDF rendering.

Use it when your document includes characters from languages that do not use the Latin character set.

`Arial Unicode MS` does not support bold or italic styling in this PDF rendering context.

For guidance on that limitation, read [Bold and Italics with Unicode Fonts In PDF](/sdocs/template-architecture/document-formats/pdf-templates/bold-and-italics-with-unicode-fonts-in-pdf.md).

### Web font support

Web fonts are not supported when a page is rendered as a PDF file.

### Related resources

* Review [PDF Rendering Considerations](/sdocs/template-architecture/document-formats/pdf-templates/pdf-rendering-considerations.md) for broader PDF rendering limits.
* Review [How to Handle International Characters](/sdocs/template-architecture/template-settings/document-options-tab/how-to-handle-international-characters.md) for Unicode setup guidance.
* Review Salesforce's [supported PDF fonts reference](https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_output_pdf_supported_fonts.htm).
* Review Salesforce's [PDF rendering considerations](https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_output_pdf_considerations.htm).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sdocs.com/sdocs/template-architecture/document-formats/pdf-templates/supported-fonts-in-pdf-format.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.