> For the complete documentation index, see [llms.txt](https://docs.santacruzsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.santacruzsoftware.com/printui/core-concepts/fonts-images-and-galleries.md).

# Fonts, Images and Galleries

## Fonts

PrintUI can use built-in fonts and client-uploaded fonts. Uploaded fonts must be licensed for server use and embeddable in PDF output when PDF generation is required.

Supported upload formats are Windows TrueType and OpenType fonts, usually `.ttf` and `.otf`. PostScript fonts, older Mac TrueType formats, `dfont` files, Multiple Master fonts, and many converted legacy fonts are not supported.

Avoid Adobe Fonts unless you have downloaded and installed separately licensed font files that can be uploaded. Adobe's font service license does not allow uploading synced fonts to PrintUI servers.

## Images

Use images sized for the final output. For print templates, 200 to 300 dpi at placed size is usually appropriate. Very large images increase upload time, editor load time, and output processing time without improving quality.

JPEG is preferred for photographic artwork because it compresses well. PNG is appropriate when transparency is required. Complex vector artwork can slow processing and may need to be converted to JPEG or PNG.

## Galleries

The Image Gallery Browser can show local uploads, social galleries, storage galleries, approved gallery connector content, or a separate template-background gallery.

Gallery qualifiers and frame keywords can filter the available images so users see the right assets for a template, campaign, user, or selected frame.

Image-related run-time options control whether uploads are allowed, which galleries appear, whether image filtering is enabled, the minimum image resolution, and how replacement images are placed.


---

# 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.santacruzsoftware.com/printui/core-concepts/fonts-images-and-galleries.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.