About This Reference
CAD Interoperability Reference is an independent technical publication about moving CAD and 3D design data between software ecosystems without losing sight of the work that follows the transfer.
The question behind the reference
“Can this application open that file?” is only the beginning of an exchange decision. The useful question is whether the received result contains the information the next task needs.
The reference frames an exchange as:
source environment → transfer mechanism or representation → destination environment → required information → downstream objective → validation evidence
That model keeps shape, product structure, design intent, engineering meaning, spatial context, visual data, dependencies, and manufacturing information from being treated as interchangeable.
How the coverage is organized
The portal is organized around information layers and decision stages rather than a generated list of file extensions or every possible software pair. Use the preservation strategy material to define what must survive, then explore the relevant layer:
- geometry, topology, and mesh fidelity;
- product structure, identity, and references;
- editability and design intent;
- engineering semantics and documentation;
- spatial context and BIM exchange;
- visual scenes and assets; or
- manufacturing, fabrication, and quality handoffs.
The formats, profiles, and translators and ecosystem routes sections address how data crosses a boundary. Transfer failures and recovery addresses incomplete or degraded results. Validation and long-term reuse closes the loop with acceptance, reproducibility, archival, and retrieval.
How claims are treated
The reference separates several claims that are often collapsed into “compatible”:
- a product documents support for an operation or representation;
- a format or profile defines a capability or conformance scope;
- a particular route has observed preservation results;
- the destination retains the editability or update behavior a task needs; and
- the result is practically useful for a stated purpose.
Product release, transfer direction, settings, profile, dependency package, and test scope matter. When the available information is limited or model-specific, the writing keeps that boundary visible instead of turning a narrow result into a universal promise. Readers should still test important exchanges with the actual source, destination, release, and downstream task.
Independence and limits
The reference is not affiliated with the vendors, standards bodies, service providers, or software products it discusses unless a page expressly states otherwise. It does not operate as a converter, file-transfer service, certification body, or substitute for a project’s engineering, manufacturing, BIM, inspection, or acceptance process.
The goal is decision support: help a technically capable reader define the exchange, identify what matters, choose a route worth testing, and retain evidence that the received result is fit for purpose. It is not a claim that every route has been tested or that a successful import proves preservation.
Corrections and updates
Formats, products, standards, and documentation evolve. Pages may therefore be updated when evidence, scope, or reader needs change. If you find a statement that is unclear or appears to exceed its stated evidence, compare it with the linked source and the exact route before relying on it.