G-code Analyser
Read a sliced file: time, filament, size and layers.
File
Result
Your converted file will appear here.
About the G-code Analyser converter
A G-code file already knows everything about the print. The trouble is that it knows it across several hundred thousand lines of coordinates.
Drop one in and get the summary: how long it takes, how much filament it uses, how big the model is and how many layers it has.
Two sources, and it says which one it used
Slicers write summary comments into the file, and those are authoritative — they come from a full simulation of acceleration and jerk. Where they exist, they are used.
Where they do not, the moves are added up instead. The filament line says which of the two produced the figure, because the difference matters: a slicer estimate accounts for the whole toolpath, while a sum of moves is exact about plastic but knows nothing about time.
Absolute and relative extrusion
In absolute mode the E value on each move is a running total, and the filament used is the difference between one move and the next. In relative mode each E value is the amount for that move alone.
Reading one as though it were the other is the difference between forty metres of filament and forty kilometres, so the mode is tracked properly, including the G92 resets that reset the counter mid-print.
Retractions are not consumption
A retraction pulls filament back so it does not ooze during a travel move, and pushes it out again afterwards. Counting only the positive moves would charge for that plastic twice.
The total is the net, so it matches what actually leaves the spool. The number of retractions is reported separately, since an unusually high count is often worth investigating.
It feeds the cost calculator
The last section of the report is a small block of JSON with the grams and hours already filled in, in the shape the 3D print cost calculator reads.
Copy it, paste it into that page, and you have a full cost with electricity, machine wear and failures without retyping anything off your slicer.
Frequently asked questions
Why does it not estimate the print time itself?
Because doing it properly means simulating your firmware’s acceleration and jerk settings move by move. A naive calculation from distance and feedrate comes out a third or more too fast, which is worse than saying nothing. If your file has no estimate in it, re-slice with that option enabled.
The model size looks smaller than I expected.
The bounding box is measured from extruding moves only. Travel moves and the priming line at the edge of the bed are excluded, because including them would report the size of the bed rather than the size of the part.
Can it show me a preview of the toolpath?
Not yet. Rendering a toolpath means drawing millions of segments, which is a different kind of tool from a summary — your slicer already does it well.
Will it handle a 500 MB file?
It reads the file line by line rather than holding a parsed copy, so large files are limited by your device rather than by an upload. Nothing is sent anywhere, which is also why a file that size is practical at all.