> 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/output-preview-and-finish.md).

# Output, Preview and Finish

## Preview in the editor

The Preview button can show output choices configured by run-time options, including PDF, JPEG, and PNG when enabled by the host workflow.

Use preview to review text, image placement, links, page order, non-printing layer behavior, background and foreground rendering, and final appearance.

## Finish handling

When the user clicks Finished, the editor sends `printui_finished` to the embedding page. The host page should save or route the job, then request any required output.

The Finished button label and confirmation message can be customized with run-time options. A separate warning can appear if the user has not visited every page.

## Cancel handling

Cancel is optional. To show a Cancel button, configure cancel text and alert behavior, and implement `printui_cancel` handling in the embedding page.

## Output review

Before releasing a template, generate representative output and check:

* Font embedding and font substitution.
* Bleeds and crop marks from the selected [PDF preset](/printui/guides/pdf-presets.md).
* Image resolution and compression.
* Spot colors and color conversion.
* Links and page navigation.
* Overset text and table behavior.
* Non-printing layer inclusion or omission.
* Performance for [complex documents](/printui/guides/job-complexity.md).

The editor preview does not replace final PDF testing. Always generate a production PDF with the preset used by the host workflow before releasing a template.


---

# 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/output-preview-and-finish.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.