> 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/polymaker-products/more-about-our-products/other-polymaker-information/we-dry-our-filament-before-shipping.md). # We Dry our Filament Before Shipping Polymaker takes the quality of their filament seriously by ensuring that every spool is **pre-dried before shipping**. Moisture is a common enemy of 3D printer filaments—it can lead to issues like stringing, clogging, poor surface quality, or even compromised mechanical properties during printing. To counter this, Polymaker subjects their filament to a controlled drying process before it is packaged. Polymaker's approach aligns with best practices in filament production: exposing the spools to precise heat and airflow to remove absorbed water, making sure the material is in an optimum, low-humidity state when it leaves the factory. Once the drying is complete, each filament spool is **vacuum sealed in a bag along with a desiccant pack**. This airtight packaging locks out external moisture and ensures the filament remains dry during storage and shipping. The packaging process is designed to guarantee that, upon arrival, the filament is **ready to print straight out of the bag**, requiring no additional drying steps for most users. This practice is especially important for humidity-sensitive materials like nylon, but Polymaker applies this process across their PLA and other product lines to ensure consistent printing performance and reliable results. If the vacuum seal remains intact until opening, users can confidently load the filament into their printer and begin printing immediately, knowing that Polymaker's pre-shipping preparation safeguards both print quality and ease of use. {% embed url="" %} --- # 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/polymaker-products/more-about-our-products/other-polymaker-information/we-dry-our-filament-before-shipping.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.