> 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/design-parameters/single-sided-placement.md). # Single-sided placement Instructions for managing single-sided placement in Quilter, including automatic exploration, forcing double-sided layouts, and specifying single-sided constraints. ### Overview When exploring placement solutions, Quilter will automatically flip components between the top and bottom layers unless they are specifically associated with a placement region on that layer. For every layout job, **Quilter automatically tries to create some single-sided layout candidates** if it finds a valid placement solution that uses only one side. ### How to specify #### As a preference Quilter allows for preferential filtering by single-sided placement. To do this, go to the design parameters page and check the "Show single-sided layouts only" option. This will apply a filter during candidate review that you can remove if we don't generate any single-sided candidates. #### As a requirement Quilter will automatically try single-sided candidates first and only switch to double-sided placements if it can't find a valid solution. \ To make Quilter only explore single-sided placements, create [Placement regions](/design-parameters/placement-regions.md) that include all components and link them to the top layer of your PCB. --- # 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/design-parameters/single-sided-placement.md?ask=&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.