> For the complete documentation index, see [llms.txt](https://docs.cartographer3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cartographer3d.com/cartographer-probe/installation-and-setup/software-configuration/z-offset.md).

# Z Offset

{% hint style="info" %}
If you are using `CARTOGRAPHER_TOUCH_HOME`, you shouldn't have to care about your scan offset. Everything that scan is used for, is relative to itself and the Z-offset is a constant that is applied to every measurement. Thus it *only* has an impact, if you start printing without using `CARTOGRAPHER_TOUCH_HOME`.
{% endhint %}

We implement Klipper's `Z_OFFSET_APPLY_PROBE` , this will apply the offset to the *last* homed mode used. This means if the last mode you used was `G28`, it will apply the offset to your scan model. If the last mode you used was `CARTOGRAPHER_TOUCH_HOME` it will apply to your touch model.

### Babystep adjusting Z offset

We recommend you follow [Ellis' Print Tuning Guide](https://ellis3dp.com/Print-Tuning-Guide/articles/first_layer_squish.html).

This is easiest to do through Mainsail or Fluidd. These will show a button to adjust your z offset "live", during a print. You must use the save icon that appears next to the adjustment controls AS WELL as a SAVE\_CONFIG.

Short version is to run the following macros to adjust gcode while printing a bunch of first layer squares, until you achieve the perfect first layer.

To move **up**, use `SET_GCODE_OFFSET Z_ADJUST=+0.01 MOVE=1`

To move **down**, use `SET_GCODE_OFFSET Z_ADJUST=-0.01 MOVE=1`

To finalize, use `Z_OFFSET_APPLY_PROBE`, you can then see what changed

> cartographer: touch default z\_offset: -0.1

Remember to run `SAVE_CONFIG` to persist the change to your configuration.

{% hint style="info" %}
A smaller number means a larger distance between the bed and the nozzle. This can seem counterintuitive, but this is to keep it in line with Klipper's virtual probe, and makes sense from a technical point of view.

The user should never change the number manually in the config, as that can risk causing issues.
{% endhint %}


---

# 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://docs.cartographer3d.com/cartographer-probe/installation-and-setup/software-configuration/z-offset.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.