> 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/code/files-and-fonts.md).

# Files and Fonts

This section covers file loading and font setup for Gum projects. The font pages form a small hub: start at **Fonts** to pick a strategy, then follow the links from there for detail.

## Fonts

* [Fonts](/gum/code/files-and-fonts/fonts.md) — start here. Decision tree: which font strategy fits your game.
* [Font Strategies](/gum/code/files-and-fonts/fonts/font-strategies.md) — detailed walkthroughs of each strategy with code samples.
* [Font Performance](/gum/code/files-and-fonts/fonts/font-performance.md) — where the costs live (generation, memory, draw calls).
* [Font Preloading](/gum/code/files-and-fonts/fonts/font-preloading.md) — making sure every font/size/style your game uses is ready before gameplay starts.
* [Fonts on Web](/gum/code/files-and-fonts/fonts/fonts-web.md) — bandwidth vs CPU tradeoffs for web targets.
* [Font Localization](/gum/code/files-and-fonts/fonts/font-localization.md) — current behavior and the planned per-locale system.
* [Font Cache](/gum/code/files-and-fonts/fonts/font-cache.md) — the build-time `.fnt` atlas system.
* [BitmapFont](/gum/code/files-and-fonts/bitmapfont.md) — text measurement API and character info.

## Files

* [File Loading](/gum/code/files-and-fonts/file-loading.md) — `RelativeDirectory`, file caching, and general file loading.
* [Animation Chains](/gum/code/files-and-fonts/animation-chains.md) — loading and playing back `.achx` frame animations on Sprite and NineSlice.
* [Content Using Embedded Resources](/gum/code/files-and-fonts/content-using-embedded-resources.md) — mobile and cross-platform file loading.
* [Troubleshooting](/gum/code/files-and-fonts/troubleshooting.md) — file loading issues.


---

# 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://docs.flatredball.com/gum/code/files-and-fonts.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.