Universal workbench

G-code Toolpath Safety Inspector

Normalize bounded G0–G3 motions without executing, simulating, or controlling a machine.

Device-onlyNo uploads. Ever.

Pipelines, branches, presets, naming, and detailed controls

Display

Text sizeDensity High contrast Monospace editor

Quick start

JSON → YAML WebP → PNG SVG → React JSX Plain text → Base64

From

Help me choose the best output Suggested: Toolpath JSON

What matters most?

Recommendations use the registered target format and tested fidelity classification. They never inspect or upload your content.

01Input

Drop files or a folder hereChoose G-code files or a folder — batch input is welcome

Choose files Choose folder

or paste content

02Configure & run

G-codeToolpath JSON

structural conversion · single or batch

Conversion preflightSize, memory, engine, execution, and fidelity before you start

Input: 104 B
Estimated peak memory: 16 MiB
On-demand download: No large engine download
Execution: Responsive local worker
Fidelity: No lossy step declared

What to providePaste G-code content or drop a matching file.What you’ll getProduces previewable Toolpath JSON text and a correctly named download.

Output naming & batch behavior

Filename templateAvailable variables: {output} (converter’s meaningful name), {name}, {target}, {ext}, {index}. Duplicate names receive a safe numeric suffix.

Exampleoutput.toolpath.json

Pipeline 1 linear · 0 branches

Why use A → B → C?

A pipeline feeds each result directly into the next compatible converter. Use one when the destination needs an intermediate representation or when you want to inspect and normalize that middle format.

JSON → CSV → XLSX turns records into rows before building a workbook.
Markdown → HTML → DOCX resolves markup before creating a document.
SVG → PNG → PDF intentionally flattens vector artwork before placing it on a page.

Only type-compatible next steps are offered. Lossy steps are marked before you run them.

1G-code to Toolpath JSONstructural

Add compatible step

Parallel output branchesEach branch receives the final linear result. Branches do not feed or depend on one another.

Add a parallel destination

Processing happens locally. Your file bytes are never sent anywhere.

About this utility

How to use G-code Toolpath Safety Inspector

Normalize bounded G0–G3 motions without executing, simulating, or controlling a machine.

What to provide

Drop the files described by this task. The selected converter validates signatures and processes them locally.

Choose files or drag them into the local converter workbench. The source signature is checked before processing.
Review the task-specific options, fidelity warning, memory estimate, and destination representation.
Select “Convert on this device,” then preview, compare, download, or continue through a compatible in-memory handoff.

What the result means

The converter workbench provides previews, progress, cancellation, warnings, and individual or ZIP downloads.

Privacy and safety

This utility is loaded as browser code and processes your input only in this tab. OmniCastConverter has no upload endpoint and never stores your content, filenames, tokens, or secrets. Generated markup and code are shown as inert text and are never executed.

Limitations

The focused task reuses its tested converter contract; source-format fidelity and browser memory limits remain visible before execution.

Try the included example

Select “Load example” at any time to restore this tested sample.

; local toolpath example
G21
G90
G0 X0 Y0 Z5
G1 Z0 F300
G1 X40 Y0 F900
G1 X40 Y20
G1 X0 Y20
G1 X0 Y0
M30