> 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/standard-pla-is-actually-strong.md). # Standard PLA is Actually Strong Many people in the 3D printing community often consider standard PLA to be a weak or fragile material. However, this perception doesn’t tell the full story. In reality, standard PLA exhibits impressive strength in several important mechanical aspects. It is known for being very rigid and having good tensile strength, allowing it to withstand substantial loads and maintain its shape under pressure. This makes PLA well-suited for many applications where stiffness and dimensional stability are critical. The misconception about PLA’s weakness largely stems from its relatively low impact resistance. While PLA can handle steady forces and tension well, it is more prone to cracking or breaking when subjected to sudden impacts or drops. This means that although a PLA print might not bend or deform easily under normal use, it can be brittle when faced with sharp shocks or accidental falls. Therefore, impact resistance is just one way to measure material strength, and PLA’s excellent rigidity and tensile capabilities mean it can be quite strong when used in the right contexts and for parts designed to avoid impact stresses. {% 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/the-basics/fun-3d-printing-facts/standard-pla-is-actually-strong.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.