> 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-wiki/polymaker-wiki-ko/undefined/fun-3d-printing-facts/extrusion-temp-printing-temp.md).

# 압출 온도 ≠ 인쇄 온도

3D 프린팅에서는 슬라이서에 설정한 출력 온도와, 실제로 필라멘트가 노즐에서 나올 때의 온도가 같지 않을 수 있습니다.

이 내용은 재료 과학의 [Warping](https://app.gitbook.com/s/KnR2KiZmkGXTiYikBIdN/undefined-1/undefined-3/undefined-2)에서도 다루지만, 핵심은 소재가 가열되는 데 시간이 필요하다는 점입니다.

즉, 핫엔드가 필라멘트를 충분히 녹일 수 있는 속도보다 더 빠르게 출력하면, 실제 압출 온도는 슬라이서 설정값보다 더 낮아집니다.

**압출 온도**: 플라스틱이 노즐에서 나올 때의 실제 온도

**압출 속도**: 플라스틱이 노즐에서 나오는 체적 속도(mm³/s)

<figure><img src="https://1079524973-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0XKp816hibEsjBQtrHfc%2Fuploads%2Fgit-blob-0d6d8e0debde9fb67a2284c05e235fe5a84cee10%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

그래서 고유량 핫엔드가 아닌 장비에서 아주 빠르게 출력할 때는, 제조사 권장 온도보다 조금 더 높게 잡아야 할 수 있습니다.

출력 속도 때문에 실제 압출 온도가 너무 낮아지면 아래 문제가 생길 수 있습니다.

* 표면이 매트해짐
* 압출 부족
* 노즐 막힘

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


---

# 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-wiki/polymaker-wiki-ko/undefined/fun-3d-printing-facts/extrusion-temp-printing-temp.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.
