> 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/printing-fast-matte-surface-finish.md).

# Printing Fast = Matte Surface Finish

If you notice that one section of your print appears more matte compared to other areas, it’s often a sign that you are printing too quickly for the particular hotend and material combination you’re using. Certain materials are not designed for high flow rates and can develop a dull, matte finish when pushed beyond their optimal extrusion speed. This happens because the filament doesn’t have enough time to fully heat up to the designated temperature, resulting in incomplete melting and less glossy surface quality.

To maintain a consistent shiny finish while printing at higher speeds, it’s important to use materials specifically formulated for high flow applications along with a hotend capable of handling those flow rates. High flow hotends allow the filament to heat more efficiently and extrude smoothly even at faster speeds, helping preserve the intended surface appearance. Balancing the right material, hotend, and print speed is key to achieving fast prints without sacrificing aesthetic quality.

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


---

# 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/printing-fast-matte-surface-finish.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.