> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/flatredball/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/flatredball/glue-reference/files/file-types/font-.fnt.md).

# Font (.fnt)

### Introduction

Font files (.fnt) are produced by AngleCode's Bitmap Font Generator ( <https://www.angelcode.com/products/bmfont/> ). These files can be loaded through the FlatRedBall Editor and used on FlatRedBall Text objects. Note that the recommended approach for working with files is through Gum. If using Gum, you do not need to explicitly load font files in the FlatRedBall Editor.

### Working with .fnt Fiels in the FRB Editor

To load a font file:

1. Verify that you have the .fnt file and any referenced files already placed in the correct folder. This is important because both files must be part of the project.
2. Drag+drop the .fnt file into your Files folder - either in Global Content Files or the Files folder of a Screen or Entity

Your font file should appear in the Files folder.

<figure><img src="https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2FLsfoCxIn97aulJAvuq64%2Fimage.png?alt=media&amp;token=11225b9c-302d-4207-800e-e4d8d84acbc2" alt=""><figcaption><p>Font file in an Entity's Files folder</p></figcaption></figure>

This file can now be referenced on a Text's Font property.

<figure><img src="https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2F6PXUmVeeBKJNzlTmfGXI%2Fimage.png?alt=media&amp;token=b273e1e1-d8be-4676-88b5-a1068b01b754" alt=""><figcaption><p>TextInstance with a Font assigned</p></figcaption></figure>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flatredball.com/flatredball/glue-reference/files/file-types/font-.fnt.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 `build a script that syncs our docs to a CMS` 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.