Compatibility scope
CutOps exports visual, structured, and machine-neutral geometry files for downstream work. Compatibility depends on the target system's schema, import rules, units, geometry expectations, and machine workflow. A file that opens successfully is not by itself proof that it is production-ready.
Status legend
- Verified
- Tested and documented against a defined third-party software or machine configuration.
- Generic export
- Standards-based or visual output without a vendor-specific guarantee.
- Requires mapping
- The data is usable after fields, units, or conventions are aligned.
- Unsupported
- CutOps does not generate or claim this output.
No third-party software or machine configuration is currently published as Verified. CutOps-native behavior is described in the CutOps scope column; downstream compatibility remains a separate claim.
Export compatibility matrix
| Format | Status | CutOps scope | Intended use | Compatibility boundary |
|---|---|---|---|---|
| JSON | Requires mapping | Import: project; Export: project | CutOps project backup, transfer, and re-import | CutOps uses its native project schema; other systems require explicit schema mapping |
| CSV | Requires mapping | Import: parts; Import: stock; Export: parts; Export: stock; Export: cut-list | Parts, stock, and ordered cut-list data | CutOps templates are native; external column names and schemas require explicit mapping |
| PNG | Generic export | Export: pattern-layouts | Visual pattern review and operator reference | Image output contains no machine instructions or structured geometry import |
| Generic export | Export: operational-report | Operational report, print, and production handoff | Document output must be checked against the selected current result | |
| DXF | Generic export | Export: manufacturing-package | Rectangular pattern geometry for downstream CAD/CAM preparation | Machine-neutral ASCII DXF R12; target-system validation is required |
| External ERP, MES, and estimating schemas | Requires mapping | CSV or JSON data exchange | Transfer parts, stock, or cut-list data | No universal external schema or direct connector is claimed |
| G-code, toolpaths, controller files, and postprocessors | Unsupported | Not generated | Machine execution | Must be created and verified in the appropriate downstream system |
DXF manufacturing package
The DXF export is a ZIP package with one machine-neutral ASCII DXF R12 file per unique pattern, plus manifests, placement data, and operator guidance. Geometry represents rectangular layout planning; it is not a router toolpath or a controller program.
Import the package into the intended CAD/CAM workflow, confirm units and scale, map layers or fields as required, generate machine-specific operations there, and validate the result on the target process. CutOps does not claim compatibility with a manufacturer or controller unless that exact workflow has been documented and tested.
Downstream handoff checklist
- Export the selected, current result rather than a stale comparison.
- Confirm file units, dimensions, kerf assumptions, and repeated-pattern counts.
- Review every unplaced part before releasing the job.
- Map external fields, layers, origins, and conventions explicitly.
- Generate and simulate machine-specific operations in the target CAD/CAM system.
- Verify the first pattern against real stock, tooling, and machine constraints.
For a full inventory of available controls and formats, see product capabilities and limitations.