> 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/readme.md).

# Welcome

Welcome to PrintUI, the InDesign-powered web-to-print platform for creating templates, customizing jobs in a browser, and generating production output.

PrintUI helps teams turn Adobe InDesign documents into browser-editable templates and production-ready output. Designers prepare templates in InDesign, upload them through the PrintUI panel, and decide which text, images, pages, colors, styles, and frames users may change. End users open the PrintUI web editor from a storefront, portal, DAM, BrandingUI, Sagittarius, or another host system to customize jobs without needing InDesign.

These docs are written for template designers, production users, developers, and administrators who work with PrintUI templates, jobs, editor options, image galleries, fonts, PDF, JPEG, PNG, and IDML output, and InDesign Server workflows.

***

## Where to start

* [**Getting started**](/printui/getting-started/getting-started.md): Learn the PrintUI workflow, main roles, and first setup decisions.
* [**Quickstart for users**](/printui/getting-started/quickstart.md): Open a job, edit allowed content, preview, finish, or cancel.
* [**Designer onboarding**](/printui/getting-started/designer-onboarding.md): Prepare an InDesign document, initialize it, preflight, upload, and test.
* [**Core concepts**](/printui/core-concepts/core-concepts.md): Understand templates, jobs, layers, frames, fonts, galleries, output, and run-time options.
* [**Guides**](/printui/guides/guides.md): Follow step-by-step workflows for template preparation, editor customization, images, text, pages, imposition, output, and troubleshooting.
* [**Reference**](/printui/reference/reference.md): Look up run-time options, supported InDesign features, template rules, glossary terms, and troubleshooting notes.

## Core features

* **InDesign template preparation**: Initialize existing InDesign documents, create required PrintUI layers, mark editable and non-editable content, set frame options, and package templates for the cloud.
* **Browser-based job editing**: Let users edit approved text, images, colors, tables, page order, page layouts, and optional new content in a controlled HTML5 editor.
* **Designer-controlled restrictions**: Hide editor controls, lock frames, limit colors, enforce document styles, require image resolution, warn about overset text, and control page editing through template setup and run-time options.
* **Image galleries and uploads**: Replace images from local uploads, approved gallery connectors, social or storage galleries, and template-background galleries with optional qualifiers and frame keyword filtering.
* **Font management**: Use built-in fonts or upload licensed TrueType and OpenType fonts for template rendering, PDF embedding, and editor font menus.
* **Production output**: Generate high-resolution PDF, JPEG, PNG, IDML, resized output and imposed output through PrintUI APIs and InDesign Server processing.
* **Localization and editor options**: Launch the editor in supported locales and customize button labels, confirmation text, palettes, guides, previews, non-printing layers, zoom, and pasteboard behavior.
* **Advanced template workflows**: Build multi-page, multi-size, resizable, Fast Edit, and imposition templates for print, digital, storefront, campaign, and automation workflows.

***


---

# 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/readme.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.