How to inspect G-code before printing
A final G-code check can catch the wrong export, an unexpected footprint, missing layers, odd feature paths, or long travel moves before they consume machine time and filament.
Open the sliced file, confirm the file summary, scan the complete 3D path, then inspect critical layers in 2D. Treat anything unusual as a reason to return to the slicer—not as proof that the printer will fail.
0101 / Inspection steps
Inspection steps
Use the views in this order so the broad shape, the layer detail, and the source line tell one consistent story.
- 01
Confirm you opened the intended export
Start with the filename and file summary. A plausible-looking model can still be an older slice or a profile made for another job.
- Check slicer metadata and layer height when the file provides them.
- Compare X, Y, and Z path dimensions with the part you intended to print.
- 02
Scan the complete path in 3D
Rotate the toolpath and color it by print feature. Look for the expected walls, infill, supports, skirt or brim, and the overall height of the job.
- Make sure nothing sits unexpectedly outside the main footprint.
- Move the layer slider through major shape changes instead of checking only the top view.
- 03
Inspect critical layers in 2D
Check the first printable layer, layers where a new island begins, bridges or supports appear, and the final solid layers. Turn on non-printing travel when path order matters.
- Look for gaps, isolated fragments, or paths that cross open space unexpectedly.
- Select a suspicious path and jump to its original G-code line for context.
02 / What to look for
What to look for
These are observable clues in the file, not guarantees about the physical print.
Footprint
The measured X/Y path range should make sense for the intended model and build plate.
Layer continuity
New regions should appear where the model geometry expects them, with support or a previous layer beneath when required.
Motion pattern
Long travel moves, frequent island changes, or an unexpected feature color deserve a closer layer-by-layer look.
03 / What this cannot prove
What this cannot prove
A G-code viewer reads planned commands. It does not see nozzle condition, wet filament, calibration, or how firmware and hardware execute the job.
- The preview cannot confirm bed adhesion, extrusion quality, belt tension, nozzle clearance, or the printer's real coordinate calibration.
- Feature labels and slicer estimates depend on comments and metadata actually stored in the file; missing metadata may remain unknown or be estimated.
04 / Common questions
Common questions
Does a clean preview guarantee a successful print?+
No. It confirms that the planned path looks coherent. Hardware, material, calibration, temperature, and firmware behavior can still change the physical result.
Which layers should I inspect first?+
Start with the first printable layer, the first layer of each new island, major overhang or support transitions, and top solid layers.
06 / Technical sources
Technical sources
The workflow is grounded in current viewer behavior and these official technical references.