Built this because every G-code viewer was slow, server-dependent, or hadn't been updated since 2015

Most G-code viewers haven't changed in a decade. Here's what the data actually shows:

The problem is real:

• NCViewer gets ~94K monthly visits — yet users still complain about animation speed control being completely broken, and gcode.ws openly admits it's "slow, memory hungry" on their own homepage SimilarwebOnline GCode Viewer

• The vast majority of NC viewers don't handle machine-specific G-code dialects — they assume a generic dialect and silently ignore anything they don't understand, which means bugs slip through undetected CNC Cookbook

• Every major alternative still requires either a file upload (privacy risk), a desktop install, or locks layer inspection behind a paid plan

The market is growing fast — tooling isn't keeping up:

• The global 3D printing market hit $15.35B in 2024, projected to reach $35.79B by 2030 at 17.2% CAGR MarketsandMarkets

• The CNC simulator software market alone is valued at $187.5M in 2024, growing at 8.3% CAGR toward $416.8M by 2033 datahorizzonresearch

• Millions of FDM, CNC, and bioprinting engineers are verifying G-code daily — with tools built in 2015

What GCodex does differently:

✓ Runs 100% client-side — your file never leaves your machine ✓ Layer-by-layer inspection with toolpath animation ✓ Export to STL, OBJ, SVG, CSV, JSON — all in browser ✓ Supports CNC, FDM, and bioprinters (including Marlin & Klipper) ✓ No upload. No signup. No tracking. Free forever.

I built this because I was running a bioprinter lab and needed a fast, private viewer that actually worked on non-standard G-code. Nothing out there fit.

Curious: What's the biggest pain point you've hit with existing G-code tools? Roadmap is being shaped by real user feedback — drop it below.