> 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/templates-jobs-and-output.md). # Templates, Jobs and Output ## Templates A template is an InDesign document that has been initialized and uploaded through PrintUI. Templates contain the page design, editable frames, fixed artwork, styles, colors, fonts, and template options used by the editor and server. Upload a revised template with the same name only when existing jobs should continue using that template identity. Existing jobs rely on compatible page sizes and frame structure. If the new design changes frame structure or page sizes substantially, upload it as a new template instead. ## Jobs A job is a user-customized version of a template. Jobs store the user edits, such as text changes, image replacements, page edits, and style choices. The editor opens a job or creates one from a template through the host system. When the user clicks Finished, the surrounding website or platform decides whether to generate output, start approval, store the job, or continue another workflow. ## Output types PrintUI can generate multiple kinds of output, depending on the account features and APIs used: * High-resolution PDF for print production. * JPEG or PNG previews and production images. * IDML for editable InDesign exchange workflows. * Resized PDF or image output. * Imposed output using an imposition template. PDF behavior can be controlled with built-in or uploaded [PDF presets](/printui/guides/pdf-presets.md). Presets can define bleeds, crop marks, image resolution, color space, and other production settings. --- # 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/templates-jobs-and-output.md?ask=&goal= ``` `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.