3D Print Cost CalcQuote workspace

Time · G-code

3D Printing Time Calculator

Read the honest print-time estimate — your slicer’s own — straight from a G-code file, along with the filament usage it reports. Drop a file below; it is parsed entirely in your browser and never uploaded. If you already know the time, use the manual converter to cost it.

Read a slicer’s estimate from G-code

Parsed entirely in your browser — the file never leaves this device.

Drop a .gcode file here, or

Convert & cost a time manually

Already know the time? Convert hours and minutes, and see labour cost at your rate.

h
m
$ / h

Total time

2h 30m

2.50 h

Time cost

$50.00

at $20.00/h

Print time cannot be derived from an STL — it depends on slicer settings the mesh does not contain. The G-code reader above reports your slicer’s own estimate, which is the honest source.

This tool will not guess time from an STL

Print time is set by slicer choices — layer height, speeds, infill, supports — none of which live in a mesh file. We read the estimate your slicer already computed and tell you which slicer produced it, instead of fabricating a number from geometry.

Where the time actually comes from

When a slicer exports G-code it writes a summary into comment headers. Cura uses ;TIME: in seconds and ;Filament used: in metres; PrusaSlicer, OrcaSlicer and Bambu Studio use ; estimated printing time and ; filament used [mm|g|cm3]. The reader scans for these, attributes the slicer, and keeps the raw lines as evidence so you can see exactly what it relied on.

What to do with the time

Time drives two cost layers: energy (watts × hours × rate) and machine depreciation (cost per hour × hours). Feed the hours into the electricity calculator and the full cost calculator to turn an estimate into a price.

Frequently asked questions

Can I calculate print time from an STL file?
Not honestly. An STL describes geometry only — it has no layer height, speed, infill or support settings, which is what determines time. Any “STL time estimate” is a guess. The truthful source is your slicer’s own estimate, written into the G-code, which is what this tool reads.
Which slicers does the G-code reader support?
Cura, PrusaSlicer, OrcaSlicer, Bambu Studio and SuperSlicer. Each writes its estimated time and filament usage into comment headers in a slightly different format; the reader detects the slicer, tells you which one it found, and shows the exact lines it used.
Is my G-code file uploaded?
No. The file is parsed entirely in your browser and never sent anywhere. It works offline, and local file paths are stripped from anything displayed. See the privacy page.
Why might the time be missing from my G-code?
Some post-processing scripts strip the header comments, and a few slicers omit the estimate. When the reader cannot find a time it says so plainly rather than returning zero — use the manual converter, or re-slice with header comments intact.