100% local processing — your files never leave your computer

G-code Visualizer

Render a G-code file's toolpaths, colored by feature, movement type, tool or feed rate — directly in your browser.

Your G-code file stays on this device. MeshWrench reads and renders it locally in your browser.

Up to 400 MB. Targets common FDM slicer output from Cura, PrusaSlicer, OrcaSlicer and Bambu Studio.

Waiting for a file

Interactive, categorized toolpath preview. Drag to rotate, scroll to zoom.

Show
File size
Decoded lines
Detected slicer
Layers
Layer detection
Tools
Linear moves
Arc moves
Rendered segments
Unknown commands
Malformed lines
Checksums
Model width
Model depth
Model height

Current command
Position (X/Y/Z)
Extrusion (E)
Feed rate
Elapsed (feed-rate-only estimate)

Movement

Extrusion moves
Travel moves
Retracts
Extrusion distance
Travel distance
Total Z travel
Feed rate range

Time estimates

Slicer-provided estimate
Feed-rate-only estimate

The feed-rate-only estimate divides path distance by commanded feed rate — it never models acceleration, jerk, pressure advance or firmware queues, and is never the same as actual print time.

Tools and temperatures

Tools used
Bed temperature setpoints
Fan state changes

Things to know about this file

    Five ways to color a toolpath

    What this isn't

    This is a visual renderer for a G-code file that already exists — never a slicer, never a firmware emulator, never a printer connection. It never uses WebSerial and never executes a single command.

    Supported G-code scope

    A documented semantic subset aimed at common FDM output for Marlin- and Klipper-style printers, covering typical patterns from Cura, PrusaSlicer, OrcaSlicer and Bambu Studio — not universal G-code support. Unknown commands are counted and disclosed, never silently faked.

    Frequently asked questions

    What do the color modes show?

    Feature type (walls, infill, support, bridges, etc. — from the slicer's own comments), movement type (extrusion vs. travel vs. retract), tool, layer (a gradient from first to last layer), and feed rate (a gradient from slowest to fastest commanded speed).

    Is my G-code file uploaded?

    No. It's parsed and rendered entirely in your browser, inside a background Web Worker.

    Does this execute the G-code or connect to a printer?

    No, never. This is a visual renderer only — it never uses WebSerial and never sends a command anywhere.