> 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/guides/preflight-package-and-upload.md).

# Preflight, Package, and Upload

The PrintUI Management panel checks templates before upload so problems are found before users edit jobs.

## Preflight

Run **Preflight** after initializing and preparing a template. Preflight checks for unsupported features, missing or invalid fonts, link problems, packaging issues, and document structures that may not work in the editor.

Fix every preflight error before uploading. Upload also runs preflight and packaging automatically, but separate preflight is easier for template cleanup.

## Package

Packaging creates the files PrintUI needs for server processing and browser editing. It also generates medium-size JPEG thumbnails suitable for storefront or template selection workflows.

If packaging fails with a vague InDesign error, try packaging the document through InDesign itself, exporting to IDML and reopening, or copying the pages into a clean document.

## Upload templates

1. Log in through the PrintUI panel.
2. Open the template in InDesign.
3. Click **Upload**.
4. Respond to prompts for missing fonts.
5. Wait for upload and server processing to finish.
6. Test the template in a browser.
7. Generate final output to verify fonts, links, colors, and rendering.

## Manage fonts

The PrintUI panel can upload, remove, and download account fonts. Upload additional styles in a family, such as bold or italic, when users should be able to choose them in the editor.

Remove fonts carefully. Templates that use a removed font may stop rendering correctly.

## Update templates safely

Do not remove an existing template before uploading a new version unless you intend to delete associated customized jobs.

To update an existing template while preserving jobs, upload the revised template with the same name and keep page sizes, units, text frames, and image frames compatible with the previous version.

For major design changes, upload a new template name and leave the old template available for existing jobs.


---

# 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/guides/preflight-package-and-upload.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.