OmniCastCONVERTER
Buy me a coffee ↗
Universal workbench

Toolpath JSON to G-code

Create G-code from Toolpath JSON locally, with no upload or account.

Device-onlyNo uploads. Ever.
Pipelines, branches, presets, naming, and detailed controls
Display
Quick start
Help me choose the best output Suggested: G-code

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

01Input
Drop files or a folder hereChoose Toolpath JSON files or a folder — batch input is welcome
or paste content
265 chars · 1 lines · 265 B
02Configure & run
Toolpath JSONG-code
structural conversion · single or batch
Conversion preflightSize, memory, engine, execution, and fidelity before you start
Input
265 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 valid Toolpath JSON syntax or drop one or more .toolpath.json files.What you’ll getProduces previewable G-code text and a correctly named download.
Output naming & batch behavior
Exampleoutput.gcode
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.
1Toolpath JSON to G-codestructural
Parallel output branchesEach branch receives the final linear result. Branches do not feed or depend on one another.
Processing happens locally. Your file bytes are never sent anywhere.
About this conversion

How to convert Toolpath JSON to G-code

Before you start

Paste valid Toolpath JSON syntax or drop one or more .toolpath.json files.

Accepted: .toolpath.json · application/json
  1. Paste valid Toolpath JSON content, choose files, or drag them onto the drop zone.
  2. Confirm the detected format. Mixed-format batches are flagged before conversion.
  3. Select “Convert on this device.” Produces previewable G-code text and a correctly named download.

How this converter behaves

Biological, molecular, genomic, matrix, and binary scientific metadata are parsed into bounded typed records and serialized locally without executing content.

What happens to your data?

The conversion engine runs in this browser tab. OmniCastConverter has no upload API and never sends your content, file name, or converted result to a server.

Fidelity and limitations

This route is classified as structural. The converter preserves meaning and structure supported by both formats.

  • Scientific records are validated and normalized, but domain-specific annotations and application conventions may require expert review.
  • Toolpaths are inspected and normalized only. Machine state, offsets, canned cycles, macros, extrusion semantics, controller dialects, and physical safety are not simulated; always verify output in the target machine software.

Try a valid example

The “Use example” action in the workbench loads this exact input. Produces previewable G-code text and a correctly named download.

{"units":"millimeters","positioning":"absolute","motions":[{"kind":"rapid","x":0,"y":0,"z":5},{"kind":"linear","z":0,"feed":300},{"kind":"linear","x":40,"y":0,"feed":900},{"kind":"linear","x":40,"y":20},{"kind":"linear","x":0,"y":20},{"kind":"linear","x":0,"y":0}]}