How to Read G-Code on a 3d Printer

Every 3D printer runs on a set of instructions called G-code. If you've ever watched a print fail halfway through or wondered why your printer moved a certain way, the answer is almost always sitting in that G-code file. Learning how to read G-code on a 3D printer gives you real control over your prints. It helps you troubleshoot problems faster, fine-tune settings without re-slicing, and understand exactly what your machine is doing at every layer. You don't need to be a programmer you just need to know what to look for.

What exactly is G-code?

G-code is a plain-text language that tells your 3D printer what to do, step by step. Each line of code is one instruction move here, heat up this, extrude this much filament. Your slicing software (like Cura or PrusaSlicer) generates these files automatically from a 3D model. The printer reads them line by line from top to bottom.

A G-code file usually ends in .gcode, and you can open it in any basic text editor. Inside, it looks like a list of short commands with numbers after them. That's it. No fancy formatting, no hidden layers just text.

If you want a breakdown of what the individual commands do, we cover the most common G-code commands for 3D printers in detail on another page.

How is a G-code file structured?

A typical G-code file follows a predictable pattern. It starts with setup commands, moves into the actual printing instructions, and ends with shutdown steps. Here's a rough outline:

Start sequence homing axes, heating the bed and nozzle, priming the nozzle
Layer-by-layer print moves travel moves, extrusion moves, fan and speed changes
End sequence turning off heaters, disabling motors, moving the head away from the print

Comments in the file start with a semicolon (;). They don't affect the printer at all they're just notes for you. Slicers add comments to label layers, settings, and sections so you can find your way around the file more easily.

What do the most common G-code commands mean?

You don't need to memorize hundreds of commands. A handful of them make up most of what you'll see in any G-code file:

G28 Home all axes. The printer moves to its starting position.
G90 Absolute positioning. All coordinates are measured from the origin point.
G91 Relative positioning. All coordinates are measured from the current position.
G1 Controlled linear move. This is the workhorse command it tells the print head to move to a specific point while extruding filament.
G0 Rapid move. Same as G1 but without extruding. Used for travel moves.
M104 / M109 Set or wait for nozzle temperature.
M140 / M190 Set or wait for bed temperature.
M106 Turn on the part cooling fan at a given speed.
M107 Turn off the fan.
M84 Disable stepper motors at the end of a print.

For a complete list tailored to a popular printer, check our Marlin G-code list for the Ender 3. It covers the commands that specific firmware supports.

How do you open and read a G-code file?

You don't need special software. Save your .gcode file and open it with any plain text editor Notepad on Windows, TextEdit on Mac (switch to plain text mode), or any code editor you prefer.

A monospace font makes reading much easier because all the letters and numbers line up evenly. Something like Fira Code works well for this.

If you want something more visual, there are free online G-code viewers that render your file as a 3D preview. These tools trace the toolpath so you can see each movement on screen. Popular options include:

GCode.ws (browser-based)
Repetier-Host (desktop application with a built-in viewer)
gcodeanalyser.com

A visualizer is especially helpful when you want to spot a weird travel move or see which layer a problem starts on. But reading the raw text is what gives you the real understanding.

Can you walk through a real G-code example?

Let's look at a short, typical start sequence and break it down:

; Start G-code this is just a comment labeling the section
G28 home all axes
M140 S60 start heating the bed to 60°C (doesn't wait)
M104 S200 start heating the nozzle to 200°C (doesn't wait)
M190 S60 wait until the bed reaches 60°C
M109 S200 wait until the nozzle reaches 200°C
G92 E0 reset the extruder position to zero
G1 Z5 F3000 move the Z axis up 5mm at 3000mm/min
G1 X10 Y10 F5000 move the head to X10, Y10 (a corner of the bed)
G1 Z0.3 F1000 lower the nozzle to 0.3mm above the bed
G1 E5 F300 push 5mm of filament out to prime the nozzle

That's a complete startup. Every line does exactly one thing. The F values are feed rates (speed). The S values are settings like temperature. The E values control how much filament the extruder pushes out.

Why would you want to edit G-code by hand?

Most of the time, your slicer handles everything. But there are real situations where reading and editing the file saves you time:

Print failed at layer 80 You can open the file, find the comment marking that layer, and delete everything before it. Then add a start sequence that heats up and homes the printer. Resume the print from that point instead of starting over.
Temperature tuning mid-print You notice the layers look rough at one temperature. You can insert an M104 command at a specific layer to change the nozzle temp partway through.
Custom start or end scripts Want the nozzle to wipe itself before printing? Want the bed to cool down gradually? You can edit the start and end sequences directly.
Debugging strange movements If the print head does something unexpected, reading the G-code at that point usually reveals the cause.

What mistakes do beginners make when reading G-code?

A few common trip-ups to watch for:

Confusing G0 and G1 Both move the head. G0 is travel (no extrusion), G1 is a print move (with extrusion). Mixing them up in your head leads to wrong conclusions about what the printer is doing.
Forgetting about the E value The extruder position is cumulative by default. If you see G1 E120.5, that doesn't mean it's pushing out 120.5mm right now it means the total extruder position should be 120.5mm since the counter was last reset.
Ignoring feed rates The F value sets the speed for all following moves until a new F value appears. Beginners sometimes think each line has its own speed, but the last F command carries forward.
Not reading comments Slicers add comments like ;LAYER:25 or ;TYPE:WALL-OUTER. Skipping these makes the file much harder to navigate.
Editing the wrong file Always keep a backup of your original G-code before making changes.

How do you find a specific layer in a G-code file?

Most slicers insert a comment before each layer change. In Cura, it looks like ;LAYER:0, ;LAYER:1, and so on. Use your text editor's search function (Ctrl+F or Cmd+F) and type the layer number you're looking for.

Some slicers also comment the total number of layers near the top of the file. PrusaSlicer, for example, adds ; total layers count = 150 early on so you know the scope of the print.

What are the key G-code parameters you'll see over and over?

When you look at a G1 move line, here's what each part means:

X, Y, Z Coordinates. Where the print head should go.
E Extruder position. How much filament has been fed.
F Feed rate. How fast the head moves, in mm/min.

So a line like G1 X50.2 Y30.8 Z0.3 E5.12 F1200 means: move in a straight line to X50.2, Y30.8, at height Z0.3, while extruding filament up to position E5.12, at a speed of 1200mm/min.

Once you see this pattern a few times, the rest of the file starts making sense.

How does the firmware affect which G-code commands work?

Not every printer supports every G-code command. The firmware installed on your printer's board determines what commands are available. Most consumer printers run Marlin firmware, which supports a large set of standard G and M codes. Some printers run Klipper, RepRapFirmware, or proprietary firmware with their own extensions.

If you send a command the firmware doesn't recognize, it usually just ignores it but sometimes it causes unexpected behavior. Always check what your specific firmware supports before adding commands by hand. You can find authoritative details on the RepRap G-code wiki.

What's a practical way to start learning?

You don't have to study the whole file at once. Try this approach:

Slice a simple model (a calibration cube works well)
Open the .gcode file in a text editor
Read the first 20–30 lines and identify every command
Search for the first LAYER comment
Pick one line in the middle of the print and figure out what it does
Read the last 10–15 lines (the end sequence)

After doing this a few times with different models and settings, you'll start recognizing patterns without effort.

Quick checklist: reading G-code files with confidence

Open the .gcode file in a plain text editor with a monospace font
Look for comments (;) to orient yourself they label layers, types, and sections
Remember the basic format: command + parameters (G1 X Y Z E F)
Use search (Ctrl+F) to jump to a specific layer or command
Check the start and end sequences first they're the easiest to understand
Match commands against your firmware's supported list before editing anything
Always save a backup before making manual changes to a G-code file
Use a G-code visualizer to cross-reference what you read with a 3D preview

Start with one file, read through it section by section, and look up any command you don't recognize. Within a few sessions, you'll be able to scan a G-code file and know exactly what your printer is about to do.