Privacy · Security

Is GCode Viewer Safe? Are My Files Uploaded to Your Servers?

When you open a slicer GCode file with Thingraph GCode Viewer, where does the data go? This page explains the client-side preview model.

Short answer

Your GCode content is not uploaded to Thingraph servers for viewing. Parsing and rendering happen in your browser using WebGL (@gcode-viewer/core / Three.js). We do not run a cloud conversion service that stores your toolpaths.

How local preview works

1. You choose a file on your device (or paste a URL).
2. The file bytes are loaded into your browser.
3. The viewer parses GCode and draws the toolpath with WebGL on your GPU.
4. No step sends the full file to a Thingraph backend for processing or storage.

Loading from a URL

If you use from url, the browser requests the file from that host directly. Thingraph does not download it on your behalf or keep a copy. The remote server must allow cross-origin access (CORS) for the load to succeed.

Viewer only

GCode Viewer does not edit, overwrite, or upload your slicer output. For changes, use your slicer or a dedicated GCode editor, then re-open the file here to preview.

Analytics

Like many websites, we may use privacy-conscious analytics (for example page views) that do not include your GCode file contents. See our Privacy Policy for product-specific details.