> For the complete documentation index, see [llms.txt](https://wiki.polymaker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.polymaker.com/the-basics/fun-3d-printing-facts/larger-nozzles-better-layer-adhesion.md).

# Larger Nozzles = Better Layer Adhesion

Using a larger nozzle in 3D printing can result in better layer adhesion primarily due to the increased extrusion width and thicker layers. When the nozzle diameter is larger, it deposits a wider bead of molten filament, which creates a greater surface contact area between successive layers. This increased area facilitates better bonding as more molten material from one layer fuses into the previous layer, enhancing the overall mechanical strength of the print. Thicker layers associated with larger nozzles also mean fewer total layers in the print, which reduces the cumulative number of potential weak interfaces that could cause delamination or layer separation. Therefore, parts printed with larger nozzles often demonstrate improved inter-layer strength because there are simply fewer opportunities for adhesion failures across layers.

{% embed url="<https://www.youtube.com/shorts/l15j5UTmj_g>" %}


---

# 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://wiki.polymaker.com/the-basics/fun-3d-printing-facts/larger-nozzles-better-layer-adhesion.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.