> For the complete documentation index, see [llms.txt](https://docs.quilter.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quilter.ai/downloading-candidates.md).

# Downloading candidates

Overview of downloading Quilter-generated layout candidates, including native file formats for offline review, and tracking downloaded jobs.

### Overview

Once you've reviewed a layout candidate, you can download it for offline inspection. To download a candidate for offline review, click the "download" button at the bottom right of the candidate preview pane.&#x20;

Layout candidates are always returned in their original native file format, making it easy to inspect and review them offline. This way, you can:

* Run your own design rule checks (DRCs)
* Validate the design with simulation
* Send the design to colleagues for feedback and approval

<figure><img src="https://1761213452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL9R6Vsa5jGn27oTws0tG%2Fuploads%2FSVB6zt2Mm3LcW6KPwC5C%2Fimage.png?alt=media&amp;token=5b76aee2-244b-43a7-93a3-e4906ee2e564" alt=""><figcaption><p>Click the button to download your layout candidate</p></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.quilter.ai/downloading-candidates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
