> 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/pdf-presets.md). # PDF Presets PDF presets control how PrintUI generates production PDF files from a job. Use them when output needs specific bleeds, crop marks, image handling, color conversion, compression, or PDF standards. ## What a PDF preset controls A PDF preset can define production settings such as: * Bleed and crop mark behavior. * Image resolution and compression. * Color conversion and output intent. * PDF compatibility and standards. * Printer marks and page information. * Transparency and flattening behavior, depending on the preset. The exact settings come from the preset file or built-in preset chosen for output. ## Built-in presets PrintUI servers include common InDesign PDF presets. Typical presets include: * PrintUI Default * High Quality Print * Interactive * PDFX1a 2001 * PDFX3 2002 * PDFX4 2008 * Press Quality * Smallest File Size The available list can vary by account or server configuration. Check the current account settings or API documentation for the exact names available to your workflow. ## Custom presets Use a custom PDF preset when your print shop or production workflow requires specific output settings. InDesign PDF preset files use the `.joboptions` extension. Administrators can upload custom presets through account settings where available, or developers can manage them through PrintUI APIs when supported by the integration. ## Bleeds and crop marks Bleed guides defined in InDesign Document Setup are not preserved as editable template behavior after upload. For most production workflows, define bleeds and crop marks in the PDF preset instead of showing them to users in the editor. If users need to see bleed, trim, safe area, or crop marks while editing, draw those guides manually in the template. Use non-printing layers for guides that should appear in the editor but not in final output, or use fixed layers for visible marks that should be part of the design. ## Color profiles PDF presets can depend on ICC color profiles. If a custom preset requires a profile that is not installed on the PrintUI server, contact PrintUI support before using that preset in production. Always generate a test PDF and confirm color behavior before releasing a template that depends on a new preset. ## Test a preset Before using a preset with live jobs: 1. Upload or choose the preset. 2. Generate a PDF from a representative job. 3. Check bleeds, trim, crop marks, page size, fonts, image quality, color conversion, and file size. 4. Send the PDF to the printer or production team for approval when required. 5. Record the preset name expected by the host system or API call. ## Common mistakes Do not assume the editor preview shows every production PDF setting. Preview is for review; the final PDF preset controls production output. Do not remove or rename a preset used by an integration without updating the host system or API configuration. Do not rely on InDesign bleed setup alone when the production PDF must include bleeds or crop marks. Confirm the final PDF generated by PrintUI. --- # 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/pdf-presets.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.