A Fusion 360 program looks intimidating the first time because the post processor writes everything out explicitly, including blocks you would never type by hand. The good news is that Fusion is consistent and well-commented, so once you know the order it writes things in, you can read any posted file the same way every time. The comments in parentheses are the key: Fusion names each operation and each tool, so you are never guessing what a section is for.
Reading the output is not an optional nicety. The post processor turns your toolpath into machine code, but it cannot know whether the work offset matches your real setup or whether a rapid clears your fixture. Those are your checks, and you can only make them if you can read the file. So learning to read Fusion output is the difference between trusting a black box and actually controlling what your machine does.
Read it in blocks, not line by line
Every posted program follows the same skeleton. Fusion writes a safety header, then repeats a tool-change block for each tool, then ends the program. If you read it as blocks instead of as hundreds of separate lines, a 2,000 line file becomes six or seven repeating sections. G-code itself is modal, meaning a command like G01 stays active until something cancels it, which is why most lines look like bare coordinates: the mode was set once at the top of the block.
The single most useful habit is to read the parenthetical comments first. Fusion’s post inserts lines such as a tool description and an operation name in parentheses, and the control ignores them. They tell you “this next chunk is the 6 mm flat endmill doing the 2D contour,” which is exactly the orientation you need before reading the moves. If you skim only the comments, you get a table of contents for the whole program before you read a single coordinate.
The anatomy of a Fusion block
Here is what each part of a typical milling block means, in the order Fusion writes it.
| Block | Typical codes | What it does |
|---|---|---|
| Safety start | G90 G94 G17, G20 or G21 | Absolute mode, feed per minute, XY plane, inch or mm |
| Work offset | G54 | Selects the setup origin you touched off |
| Tool change | T2 M06 | Puts tool 2 in the spindle |
| Operation comment | (2D Contour1) | Names the operation, control ignores it |
| Spindle and coolant | S8000 M03, M08 | Spindle clockwise at speed, flood coolant on |
| Length offset and approach | G43 H2, G00 | Applies tool length offset, rapids to position |
| Cutting moves | G01 X Y Z F | Linear feed moves at the programmed feedrate |
| Retract | G28 or G53 Z | Returns Z to a safe height |
| Program end | M30 | Ends and rewinds the program |
Read top to bottom and you will see that pattern repeat for each tool. The Autodesk Fusion documentation explains how the manufacturing workspace builds these operations, and the Autodesk post processor library shows how a chosen post controls the exact formatting you see.
A line-by-line read of a real header
To make this concrete, here is how you would read the opening of a typical Fusion program in plain English. The point is not to memorize this exact file but to see how each line maps to a thought.
| Line | How you read it |
|---|---|
| (T2 D=6 CR=0 - flat endmill) | The next section uses a 6 mm flat endmill, tool 2 |
| G90 G94 | Absolute coordinates, feed per minute |
| G17 | Working in the XY plane |
| G21 | Millimeters, so every number is in mm |
| G54 | Use work offset 1 |
| M06 T2 | Change to tool 2 now |
| S8000 M03 | Spindle on clockwise at 8000 rpm |
| G43 H2 | Apply tool 2 length offset, vital for correct Z |
| G00 X0. Y0. | Rapid above the start point |
| Z15. | Rapid to a safe height first |
| M08 | Coolant on |
| G01 Z-2. F300. | Feed to 2 mm depth at 300 mm per minute |
Notice that the safe Z move happens before the plunge, and the length offset G43 is applied before any Z motion that matters. Reading in this order is how you catch a missing G43 or a plunge that skips the safe approach.
Where beginners misread the output
Two things catch people. The first is the safe retract line: G28 and G53 both move to a machine reference, and if you misread which axis is retracting, you can misjudge clearance. G28 goes to the reference position through an intermediate point you can set, while G53 moves directly in machine coordinates for one block. The second is units. A file posted in G20 (inch) sent to a machine set up for millimeters is a fast way to a wreck, so confirming G20 versus G21 in the header is non-negotiable.
A third, subtler issue is the tool length offset. The G43 H number must match the tool whose length you measured. If the post outputs G43 H2 but your length offset for that tool lives in a different register, Z will be wrong by the difference, which is how tools dive into parts. Reading the H number and confirming it against your offset table prevents it.
Why Fusion output differs between machines
The post processor you select decides the exact text Fusion writes, which is why the same toolpath posts differently for a Haas, a Fanuc, or a generic control. One post may output G28 for retracts while another uses G53. One may write tool changes as T2 M06 and another as M06 alone with the tool preselected. None of this changes what your toolpath does; it changes how the file reads. So when you move a job to a different machine, expect the posted file to look different and read it fresh rather than assuming it matches the last one.
A short pre-cut checklist
Before you run a Fusion program, a quick read pass catches most problems. Confirm the units block. Confirm the work offset matches your setup. For each tool, confirm the T number, the M06, the spindle speed, and the G43 H. Read the first Z move to be sure there is a safe approach before any plunge. Read the retract between operations to be sure the head clears clamps. It also helps to understand how the control actually reads the file, because that demystifies why order and modal state matter so much. A general code reference such as the LinuxCNC G-code list is a good companion for looking up any word Fusion outputs that you do not recognize.
Reading arc moves and canned cycles
Two parts of a Fusion program look more cryptic than the straight moves, so they are worth a closer look. The first is arcs. A curved cut uses G02 for a clockwise arc or G03 for counterclockwise, and Fusion usually describes the arc with I and J values, which are the offsets from the start point to the arc center, rather than a radius. So a line like G02 X40. Y10. I10. J0. means cut a clockwise arc to that endpoint around a center 10 mm away in X. Some posts output an R radius instead. You rarely need to compute these by hand, but recognizing G02 and G03 tells you the tool is following a curve, and the direction tells you which way around.
The second is hole-making. When Fusion drills, it often posts a canned cycle such as G81 for simple drilling, G83 for peck drilling, or G84 for tapping. A canned cycle packs a whole up-down-retract motion into one line with a Z depth, an R retract plane, and an F feed, then repeats it at each hole position until G80 cancels it. Reading G83 with a Q value, for example, tells you the post chose peck drilling with a peck depth, which is exactly what you want to confirm for a deep hole. If you see a string of XY positions after a G81 line, those are the hole locations the cycle repeats at.
| Code | What it does | What to confirm |
|---|---|---|
| G02 / G03 | Clockwise / counterclockwise arc | Direction and the I, J, or R values |
| G81 | Simple drill cycle | Z depth and R retract plane |
| G83 | Peck drill cycle | The Q peck depth for deep holes |
| G84 | Tapping cycle | Feed matches the thread pitch |
| G80 | Cancel canned cycle | It appears after the holes are done |
These are still just patterns. Once you can spot them, the densest-looking parts of a Fusion program become readable.
Make the reading automatic
The difference between staring at a posted file and reading it is recognition speed. When G43, G54, M08, and G28 register instantly, you stop decoding and start verifying, which is the whole point. If you are still translating each code, the checklist above takes ten minutes and you are tempted to skip it; when the codes are automatic, the same read takes thirty seconds.
That recognition is recall, and recall responds to short repeated practice. The free G-Code Sprint app at GCodePractice.com runs 60-second rounds on the common G and M codes and repeats the ones you miss, so the words Fusion writes into every program become words you read without thinking. It is an educational practice tool for building that fluency, not a machine controller or a verifier, so always prove the program on your machine with the usual safe checks. A few drills a day plus reading every posted file in blocks will make Fusion output feel routine quickly. If you want to go a step further, the same skill lets you hand-edit a posted file safely when you need a one-off change.
Frequently asked questions
How do you read Fusion 360 post processor G-code?
Read it in blocks instead of line by line. Start with the parenthetical comments, which name each operation and tool, then follow the standard order: safety header, work offset, tool change, spindle and coolant, tool length offset, approach, cutting moves, retract, and M30. Confirm the units and work offset before cutting. To read those codes at a glance, the free G-Code Sprint app at GCodePractice.com drills the common G and M codes in 60-second recall rounds.
What do the parentheses mean in Fusion 360 G-code?
They are comments. The control ignores anything in parentheses, and Fusion uses them to label each operation and describe each tool, which makes them the easiest way to navigate a long program. Reading only the comments gives you a table of contents for the file.
Why does Fusion 360 output G28 or G53?
Both send an axis to a machine reference position for a safe retract between operations or at program end. G28 goes through an intermediate point to the reference, while G53 moves directly in machine coordinates for that block. Read which axis is moving so you understand the clearance.
Do I need to check units in Fusion output?
Yes, always. The header shows G20 for inch or G21 for millimeters. Running an inch program on a metric setup, or the reverse, scales every move wrong, so confirm units before the first run.
What is G43 in a Fusion 360 program?
G43 applies a tool length offset, with the H number pointing to the offset register for that tool. It is what makes Z correct for each tool’s length. Confirm the H number matches the tool whose length you measured, because a wrong offset sends the tool to the wrong depth.
Why does my Fusion program look different on another machine?
Because the post processor you choose controls the formatting. A different post for a different control can change retract codes, tool-change style, and more, even for the same toolpath. Read each posted file on its own terms rather than assuming it matches the last machine.