G-code preview and analysis

A 3D G-code preview shows where the nozzle will go before you waste filament. Analysis means searching lines, highlighting travel vs extrusion, and catching motion that a text file hides.

The problem this answers

You have G-code from 3dSynth or another generator and need to see seams, hops, and wild travels. Reading thousands of G1 lines is not a review.

How people do it without 3dSynth

PrusaSlicer, OrcaSlicer, and vendor tools preview their slice. Standalone viewers (ncviewer, gcode.ws) plot files but rarely edit with a synced 3D view. That is enough when you only need a sanity check.

How 3dSynth does it

Custom G-code is an editor plus 3D preview and playback. Generated modules preview in the same viewer. The G-code Inspector (Premium, web and desktop) searches lines and lists export warnings. Preview may skip the collision buffer; export does not. Docs: Custom G-code overview · Inspector.

Example

Paste or open a file, orbit the path, jump to a layer, search for G0. Tutorial: What is G-code.

When it works

Debugging generated vases, combining or trimming paths, teaching G-code, checking dialect after a printer-profile change.

When another tool is better

If you need the slicer’s estimate of time, filament, and support structures from an STL, use that slicer’s preview. 3dSynth does not replace a slicer’s costing UI or tree-support planner.

Related: direct G-code · Custom G-code · all guides · Launch app