> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/gum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/gum/gum-tool/gum-elements/text/use-font-smoothing.md).

# Use Font Smoothing

### Introduction

The Use Font Smoothing value controls whether the Text instance uses an auto-generated font which applies font smooth (anti-aliasing). This effect of this value can be easily observed if zoomed in.

<figure><img src="https://2695663588-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fzQmxQ1VeUFHcoo2c%2Fuploads%2Fgit-blob-12a994cfd809b8b99e3dd5a5b65d900de9dfca62%2F10_06%2036%2030.gif?alt=media" alt=""><figcaption><p>Text toggling Use Font Smoothing</p></figcaption></figure>

This value is true by default because it usually produces more visually appealing fonts. If your project is using an intentionally pixelated font then you may want to disable this property to preserve the pixelated aesthetic.

<figure><img src="https://2695663588-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fzQmxQ1VeUFHcoo2c%2Fuploads%2Fgit-blob-7442c0c93daa74dae7091ff6170dd9e2e14425ba%2Fimage.png?alt=media" alt=""><figcaption><p>Title Screen in BattleCrypt Bombers intentionally using a pixelated font for buttons</p></figcaption></figure>

Use Font Smoothing also affects the outline. When it is disabled, an `Outline Thickness` of `N` draws exactly `N` pixels of fully opaque outline around each glyph, with no partially transparent edge. When it is enabled, the outer edge of the outline is soft.

Pixelated fonts are usually designed to be used at a paritcular Font Size. For more information about Font Size mulitples and pixelated fonts, see the [Font Size](/gum/gum-tool/gum-elements/text/font-size.md#font-size-and-pixel-fonts) page.


---

# 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://docs.flatredball.com/gum/gum-tool/gum-elements/text/use-font-smoothing.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.