Tiny Online Tools
Everything the file will admit to
A sliced G-code file already contains the answer to most of the questions people ask before starting a print: how much filament it needs, what it will cost, how tall each layer really is, how much of the time is spent travelling rather than printing, what temperatures it commands, and which of the slicer's several hundred settings produced it. This tool reads all of it in your browser and lays it out in one report.
Measured, modelled, inferred
The report keeps three kinds of number apart, because they do not deserve the same confidence.
Measured. Filament length is the sum of the extrusion values on extruding moves. It is arithmetic on the file, and it lands within a fraction of a percent of the figure the slicer itself writes into the header — you can see both, side by side, with the difference. Mass, volume and cost follow from it once you pick a diameter, a density and a price; eleven common materials are preset and the file's own declared values can be adopted in one click.
Modelled. Printing time comes from a motion-planner model — junction speeds from jerk or junction deviation, a reverse and a forward acceleration pass, then trapezoidal integration of every move — not from dividing distance by feedrate, which overstates a detailed print badly. It is still an estimate, and it depends on the machine limits you enter. Change the acceleration and watch it move. Where the slicer wrote its own estimate, that is shown next to ours with the difference. Note that when the program itself sets M204 or M205, those win over the form from that line onward, which is what a printer would do.
Inferred. Extrusion width is back-calculated from the extrusion values and the measured layer height using a rounded-rectangle bead model. The file never states it.
Layers as they are, not as the header claims
Every layer height is measured from the Z values in the program. A first layer that differs is flagged, and so is any layer that departs from the rest — which is how a variable-layer-height print, or a priming line laid down above the first layer, shows itself. The declared layer count and the measured one are both reported when they disagree.
The rest of the report
A per-feature breakdown with distance, filament and time. A distance-weighted speed histogram. The temperature, fan and tool-change timeline. A command histogram. The non-G/M commands — which is how you discover your file contains Klipper macros. And a searchable table of every header setting. Download the whole thing as JSON, or the per-layer table as CSV.