Beyond the Slicer: The Complete Guide to Verifying Additive Manufacturing G-Code

You’ve dialed in your CAD model, optimized your orientation, and let your slicing software do its magic. A fresh .gcode file sits on your desktop, ready to command your 3D printer. But before you hit print—and potentially risk a multi-hour print failure, a clogged hotend, or a glorious plastic “spaghetti monster”—there is one critical step remaining: G-code verification.

While modern slicers are remarkably sophisticated, they aren’t infallible. Bugs happen, settings get crossed, and strange geometry can trick algorithms. Verifying your G-code acts as your final safety net, ensuring your printer executes your design with absolute precision.

Here is how to properly inspect, simulate, and verify your additive manufacturing G-code before material ever hits the build plate.

Why Slicer Previews Aren’t Always Enough

Most makers rely entirely on the built-in preview window of their slicer (like Cura, PrusaSlicer, or Bambu Studio). While these previews are fantastic for catching obvious layer gaps or overhang issues, they only show what the slicer thinks it told the printer to do.

Verifying the actual text-based G-code file or using an independent third-party simulator catches anomalies that the slicer might gloss over, such as:

• Orphaned extrusion moves or sudden jumps in coordinates.
• Corrupted macro scripts injected at the start or end of the print.
• Incorrect thermal commands that could overheat material or cause a cold extrusion fault.

Step 1: Perform a Visual Layer-by-Layer Inspection

The first line of defense is a thorough visual check. Load your G-code into a dedicated offline or web-based G-code viewer (such as NC Viewer, GCode.Viewer, or your slicer’s layer slider).

• Check the First Layer: This is where 90% of prints fail. Zoom in closely on Layer 1. Look for consistent line spacing, proper skirt/brim loops, and ensure the nozzle path doesn’t start floating mid-air.
• Scan for Anomalies (The “Elevator” Bug): Scroll rapidly up and down through all layers. Look for sudden, inexplicable flashes where the model shifts sideways or spikes upward. This usually indicates a mesh error or a slicing glitch.
• Inspect Retractions and Travel Moves: Ensure the printer isn’t making excessive, erratic travel moves across visible outer walls, which can leave stringing or scarring on your finished part.

Step 2: Use Third-Party Simulators

For high-stakes prints—such as functional engineering components, expensive engineering filaments (like PEEK or carbon-fiber composites), or long multi-day jobs—running a hardware-agnostic simulation is invaluable.

• Toolpath Analysis: Simulators parse the G-code instruction by instruction, calculating the exact kinematic movement of the print head.
• Time and Filament Estimation Cross-Check: Compare the simulator’s estimated print time and filament usage against your slicer’s prediction. Massive discrepancies often point to corrupted feed rates (F parameters) or bad acceleration limits.

Pro Tip: If your firmware utilizes advanced features like Linear Advance or Pressure Advance, ensure your simulation accounts for how sharp corners will be handled to prevent under- or over-extrusion at vertices.

Step 3: Spot-Check Critical G-Code Commands

You don’t need to read G-code like Matrix code, but knowing a few foundational commands allows you to quickly audit the text file using any standard text editor (like Notepad++ or VS Code). Open the file and check these key milestones:

1. Initialization and Homing (G28 / G29)

Look at the very beginning of the file. Ensure the printer homes its axes (G28) and, if applicable, runs bed leveling mesh probing (G29 or M420) before the hotend heats up to printing temperatures. Heating too early can ooze plastic onto the bed and ruin your probe points.

2. Temperature Management (M104, M109, M140, M190)

Verify that the target temperatures match your filament specifications:

• M104 / M109: Sets and waits for extruder temperature.
• M140 / M190: Sets and waits for bed temperature.
• Check: Ensure there are no typos resulting in a freezing bed (