# Tool changes And Z Height

**URL:** <https://forum.onefinitycnc.com/t/tool-changes-and-z-height/7715>\
**Category:** Original/PRO Series (Buildbotics) (Gen 1)\
**Created:** [September 14, 2021, 4:10pm UTC](https://forum.onefinitycnc.com/t/tool-changes-and-z-height/7715 "2021-09-14T16:10:13Z")\
**Posts on this page:** 1\
**Showing post:** 43

<div class="post-metadata">

**Author:** ![349iq2345](https://avatars.discourse-cdn.com/v4/letter/3/bb73d2/32.png) [@349iq2345](https://forum.onefinitycnc.com/u/349iq2345)\
**Post date:** [March 23, 2023, 8:08pm UTC](https://forum.onefinitycnc.com/t/tool-changes-and-z-height/7715/43 "2023-03-23T20:08:12Z")

</div>

Hey Mike,

> [@Mike01](#):
>
> can you think of any pros/cons of running a single gcode file with multiple manual tool changes vs running them as separate files, one for each tool change?

usually you would say, if your program is well-tested and mature for production, _one g-code program with all the tools_ saves time.

Many forum members here say the advantages of _one g-code program per tool_ is that you can change the program for a certain tool easier or re-run a pass easier. They put the name of the tool into the file name, and the pass that it is for.

---

_[View the full topic](https://forum.onefinitycnc.com/t/tool-changes-and-z-height/7715)._