G-code Analyzer

What the analyzer reads out of the file

• Layers and layer height. Layer-change comments (;LAYER_CHANGE, ;LAYER:,; layer num/total_layer_count) are counted first, with the Z height that follows each one. If a file has no layer comments, layers fall back to the distinct Z heights of extruding moves.
• Filament length from the toolpath. Every positive extrusion value in the file is summed, honouring M82(absolute) and M83 (relative) extrusion modes, so the total includes skirts, brims, supports and purge towers exactly as sliced.
• Estimated weight. Filament length is turned into volume with the filament cross-section you enter, then into grams with the density you choose. It is arithmetic on the sliced toolpath, not a scale reading.
• Tool changes and manual swaps. T0,T1 and friends are counted per tool with their share of the extrusion, and every M600 manual filament change is listed with the layer it happens on.
• Temperature setpoints. M104/M109 and M140/M190 give the minimum and maximum nozzle and bed setpoints plus how often they change — the usual signature of a first-layer temperature bump.
• Speed and flow peaks. The highest feedrate in the file and the highest per-move volumetric flow (extrusion × cross-section ÷ move time) are reported. The flow figure is a per-move average, which is the useful number for comparing against a max volumetric speed limit.
• The slicer's own estimates. Time and filament values written as comments (; estimated printing time,; filament used [mm], ;TIME:,;Filament used: and others) are shown next to the toolpath totals so you can see whether the file and the comments agree.

How to use it

1. Slice your model, then use Export G-code (not the.3mf project) so the file contains the full toolpath and the slicer's comments.
2. Drag the file onto the drop zone, or pick it with the file button.
3. Set the filament diameter and density only if they differ from the defaults; the weight and flow figures update immediately.
4. Read the report, then copy it as plain text if you want to keep it with your print notes.

A typical OrcaSlicer export carries verbose comments, so the panel of profile values and estimates is usually well filled. Files from printers that strip comments (some vendor slicers and most "gcode-only" exports from a phone app) still parse, but only the toolpath-derived numbers will be available.

Where the weight estimate and the slicer's estimate differ

Slicers write their own filament and weight figures into header comments. Those numbers come from the same toolpath, so they normally land within a few percent of the analyzer's total. A larger gap usually has one of three causes:

• The density or diameter is wrong. The slicer's comment uses the filament profile's diameter and density; the analyzer uses what you enter. A 1.75 mm profile with a 2.85 mm setting in the form changes the weight by more than 2.6 times.
• The comments were edited or trimmed. Post-processing scripts, "remove all comments" export options and hand-trimmed files leave comments that no longer describe the toolpath.
• Filament was added after slicing. A purge line or manual change macro inserted by the printer's own start G-code is not in the slicer's comment totals but is in the toolpath total.

When the two disagree by more than 15%, the report says so instead of hiding it.

What this tool cannot tell you

• It does not simulate the print. It counts what the file contains; it cannot predict whether the part will warp, string or fail.
• It cannot see the model. There is no geometry in G-code, so the report has no dimensions, volume or cost estimate for the part itself.
• Layer figures depend on the file's comments. A comment-stripped file gets layers counted from Z moves, and spiral vase files under-count layers that way. The report always states which method was used.
• Flow peaks are per-move averages. Firmware look-ahead can smooth short segments, so treat the number as an upper bound for a segment rather than an instantaneous reading.
• Large files take a moment. Files above 64MB are not parsed at all, because a browser tab would run out of memory.

Frequently asked questions