> 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/keepouts.md). # Keepouts Summary of using Keepouts in Quilter to restrict placement and routing areas, including common uses and how to specify them in your CAD tool. ### Overview Quilter integrates directly with keepouts defined in your CAD tool, so you can control where traces, vias, components, and pours are allowed. That's pretty much it – just add a keepout to your board, and we'll steer clear of it! ### Why should I use keepouts? Keepouts can help Quilter define the desired boundaries for design activity. Some common reasons to use keepouts include: 1. **Reserving space for mechanical features**, such as mounting holes, connectors, and heat sinks, where traces or components shouldn't go. 2. **Protecting sensitive areas**, like RF zones, from routing that could affect signal integrity. 3. **Enforcing design intent**, such as keeping parts out of high-heat zones or away from noisy power areas. ### How to specify Uploading a keepout to Quilter for layout candidate generation is easy. Just define it in your CAD tool as you normally would and save it along with your other design files when setting up a new layout job. --- # 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/keepouts.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.