3D Printing · G-code
G-code Simulator
Drag in a sliced .gcode file. See the toolpath in 3D, scrub the print timeline, and check what the slicer's actually about to do before you start a 12-hour print.
Bambu Studio / PrusaSlicer / OrcaSlicer / Cura outputs all supported.
No .gcode handy?
Why preview G-code before printing?
- Catch supports going to weird places— slicer support algorithms occasionally route under overhangs that won't actually need them, wasting filament and time.
- Verify travel routing — long travel moves across previously printed areas mean ringing / scarring; enable Show travel moves and watch the gray lines cross the model.
- Spot weird layer transitions — scrub layer-by-layer to find the layer where the print suddenly looks different (often where slicer changed strategy or hit an interface).
- Sanity-check before a 12-hour print — much cheaper than discovering at layer 200 that the model lifted off the bed at layer 3.
Print time and filament estimates are computed from the G-code itself (feedrate × distance, filament cylinder volume × density). Real-world times are typically 5–15% longer due to acceleration limits the previewer doesn't simulate.