FIELD GUIDES / 05
Inspect the file, not just the model.
Five focused workflows for the questions that come up after slicing. Each guide tells you what to inspect, which view to use, and where the file stops being evidence.
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.
How to open a G-code file
G-code is plain-text machine instruction, but opening it in a text editor does not show the shape of the toolpath. A viewer turns supported motion commands into a spatial preview while keeping the source available.
Read print time, filament, and dimensions from G-code
A G-code file can contain slicer estimates and enough motion to calculate useful measurements. The important part is knowing which values were declared, measured, estimated, or assumed.
Find travel moves that may contribute to stringing
Stringing happens on the physical print, but the file can reveal where the nozzle travels without extrusion and whether retraction commands or extrusion-only retract moves appear around those journeys.
How to locate a likely Z seam in G-code
A perimeter loop has to start and end somewhere. When those points align across layers, the printed surface may show a vertical seam—but the viewer displays paths, not the final surface artifact.
LOCAL FILE / NO UPLOAD
Inspect your file now
The viewer reads G-code locally in this browser. No file upload or account is required.