---
title: "Fusion 360 G28 vs G53 Safe Retract: Which to Choose and Why"
description: "Fusion 360's post asks how to retract: G28 moves through a waypoint you command, G53 goes straight to machine coordinates. The decision and the reasons."
url: https://gcodepractice.com/journal/fusion-360-g28-vs-g53-safe-retract/
canonical: https://gcodepractice.com/journal/fusion-360-g28-vs-g53-safe-retract/
author: "Lawrence Arya"
authorUrl: https://www.linkedin.com/in/vibecoding/
published: 2026-06-07
updated: 2026-06-07
category: "Code reference"
tags: ["fusion 360", "g28", "g53", "safe retract"]
lang: en
---

# Fusion 360 G28 vs G53 Safe Retract: Which to Choose and Why

> **TL;DR** Fusion 360's safe-retract option chooses how posted programs send the machine home, and the mechanics decide the answer: G28 retracts move through an intermediate waypoint computed under the program's modal state, the safe idiom exists precisely to neutralize that waypoint, while G53 moves command machine coordinates directly, no waypoint, no offset arithmetic, no modal traps. On controls that support G53, it is the cleaner choice and the common recommendation; G28 remains the compatibility answer for controls and shops where it is convention. Whichever the post emits, read the retract block once and understand it, because it runs at the end of every program, forever.

Buried in Fusion 360's post properties is an option that decides how every program you ever post will end: the safe-retract style, typically offering G28, G53, and sometimes clearance-height variants. It is a one-click choice with mechanics underneath, and the mechanics, not preference, should make the decision, because the retract block is the most-executed safety code a shop runs: end of every program, every cycle, forever.

## What both options are protecting against

A retract's job is humble and absolute: get the tool clear of the work, the fixture, and the operator's plans, from wherever the program happened to finish, before tool changes and program end. The danger it must survive is inherited state, whatever distance mode, work offset, and tool length the program leaves active, because the retract runs last and inherits everything. Both options answer that danger; they answer it with different amounts of machinery, and the comparison below is really about how much inherited state each one must survive.

## The mechanics, side by side

| Property | G28 retract | G53 retract |
| --- | --- | --- |
| The route | Through an intermediate waypoint, then to reference | Straight to commanded machine coordinates |
| What computes the move | The waypoint, under active distance mode and offsets | Nothing: machine coordinates, one block |
| The famous trap | The waypoint, when not neutralized | None equivalent |
| The safe form | G91 G28 Z0 G90: zero-distance waypoint | G53 G00 Z0: says what it does |
| Availability | Ancient and universal | Common, with per-control variations |

The [reference documentation](https://linuxcnc.org/docs/html/gcode/g-code.html) states both plainly, and the asymmetry is the story: G28 is a two-leg move whose first leg, the waypoint, is computed under the program's modal state, which is exactly how it produces the [overtravel alarms](/journal/z-axis-overtravel-on-g28/) and [chuck dives](/journal/why-did-my-z-axis-dive-into-the-chuck-on-g28/) this site has dissected, while G53 is a one-leg move in machine coordinates with nothing to compute and therefore nothing to trap. The safe G28 idiom neutralizes the waypoint completely, and posts emit it correctly; the difference is that G53 has nothing needing neutralization.

## The decision, made practical

On controls that support G53 cleanly, choose it: the retract block then says exactly what it does, G53 G00 Z0, top of travel, machine coordinates, readable by anyone at a glance, and immune to every offset and mode the program might leave active. This is the common recommendation across the [post-configuration world](/journal/fusion-360-post-processor-g-code-output-wrong/): one leg, no waypoint, nothing inherited to survive.

Choose G28 where compatibility or convention says to: controls with restricted G53 handling, shops whose proving rituals and templates expect the G28 form, programs that must run across mixed fleets. The G28 choice is not wrong, it is the [safe idiom](/journal/safe-z-retract-code-for-fanuc-before-opening-door/) doing its job, it simply carries one more concept the reader must know to read it, the neutralized waypoint, where G53 carries none.

Set the choice once in the post's per-machine configuration, matched against your control's documentation, and let every future program inherit it. The [post library's](https://cam.autodesk.com/hsmposts/) machine-specific posts often default sensibly for their targets, which is one more argument for machine-specific posts over generic ones.

## The verification either choice deserves

Whatever the dialog emits, the retract block gets read once with full understanding: the G53 form checked for sensible machine coordinates, the G28 form checked for its G91 Z0 G90 idiom rather than a naked waypoint, either form dry-run watched to its end. That single read converts the option from a dialog mystery into owned code, and it is a five-minute version of the general rule this entire [G-code](https://en.wikipedia.org/wiki/G-code) curriculum keeps landing on: code that runs unattended forever earns one attended read first. The vocabulary that makes the read instant, G28's two legs, G53's one, the modal words around them, is core material, drilled free in the 60-second rounds on the [G-code practice page](/g-code-practice/), and the retract block is among its best returns on investment: one small block, read once, trusted for years.

## Sources

- [Autodesk: Fusion 360 post processor library](https://cam.autodesk.com/hsmposts/)
- [LinuxCNC: G-code reference](https://linuxcnc.org/docs/html/gcode/g-code.html)
- [Wikipedia: G-code](https://en.wikipedia.org/wiki/G-code)

## Frequently asked questions

### Should I use G28 or G53 for safe retract in Fusion 360?

On controls that support G53, it is the cleaner mechanism and common recommendation: machine coordinates directly, no waypoint, no modal dependence. G28 stays right where the control or shop convention expects it, with the safe idiom neutralizing its waypoint.

### What is the actual difference between G28 and G53 retracts?

The route: G28 goes through an intermediate waypoint computed under active modes and offsets, then to reference; G53 goes straight to commanded machine coordinates, one move, nothing to compute, nothing to trap.

### Why does Fusion 360 even offer the choice?

Compatibility: G53 handling varies across controls while G28 is ancient and universal, so posts expose the option. Set it once per machine in the post configuration.

### What should I check in the posted output either way?

Read the retract block once: sensible machine coordinates in the G53 form, the G91 Z0 G90 idiom in the G28 form, then dry-run the ending. The most-executed safety code earns one attended read.

---

Source: https://gcodepractice.com/journal/fusion-360-g28-vs-g53-safe-retract/
Author: Lawrence Arya — https://www.linkedin.com/in/vibecoding/