01 / METHOD
How to use this g-code analyzer tool
- Choose a plain-text .gcode, .gco, or .gc file from your device.
- Wait for local parsing; the file is not sent to this site.
- Use the summary as an inspection aid and confirm critical details in your slicer or machine workflow.
02 / APPLICATIONS
When it is useful
- Sanity-check temperatures before printing
- Inspect movement bounds and layer markers
- Compare slicer metadata and estimated time
03 / MODEL
Assumptions and limitations
Assumptions
- Movement uses common G0/G1 commands and standard X/Y/Z/E parameters.
- Layer comments and metadata are slicer-dependent.
- Bounds reflect commanded coordinates, not necessarily extruded model bounds.
Limitations
- The analyzer does not simulate firmware state, arcs, macros, kinematics, coordinate transforms, or machine safety.
- Do not treat the summary as validation that a file is safe, complete, compatible, or free of malicious/custom commands.
04 / FAQ
Common questions
Is my G-code uploaded?
No. The selected file is read by JavaScript in your browser; this site has no upload endpoint.
Why can bounds differ from model size?
Commanded motion can include purge lines, skirts, homing-related moves, or travel beyond the printed part.
Can this detect unsafe G-code?
No. It is a summary tool, not a firmware simulator, security scanner, or machine-specific safety check.