What is the difference between CAD Exchanger Lab, CAD Exchanger SDK, and Manufacturing Toolkit?

CAD Exchanger is one product family split by who you are and what you need to build. CAD Exchanger Lab is a desktop application for end users who need to view, explore, and convert CAD files. CAD Exchanger SDK is a set of 3D CAD software libraries for developers who need to embed import/export and visualization into their own applications. Manufacturing Toolkit is a CAD SDK aimed specifically at developers building quoting, DFM (design-for-manufacturing), and MaaS (manufacturing-as-a-service) platforms. If you just need to open and convert files yourself, choose Lab. If you are writing software that handles CAD data, choose the SDK — and if that software is a manufacturing or quoting platform, look at Manufacturing Toolkit.

The three products side by side

CAD Exchanger Lab: for people who work with files directly

Lab is the desktop application. Its purpose is to let you view, explore, and convert 3D CAD data across 30+ file formats without writing any code.

What you can do with it, based on the product description:

• Import/export — read and write Solidworks, STEP, JT, STL, and 30+ other 3D formats.
• Access model structure — assemblies and parts, precise B-Reps and polygonal meshes, metadata and PMI.
• Visualize — sectioning, explode views, and multiple display modes.

Choose Lab if your task is to open a file someone sent you, inspect an assembly, or convert between formats for downstream use. You do not need programming knowledge, and you are not building a product on top of it.

CAD Exchanger SDK: for developers embedding CAD capability

The SDK provides 3D CAD software libraries for C#, C++, Java, JavaScript, and Python. It is the right choice when CAD handling is a feature inside software you are building, not a task you perform yourself.

The source material highlights two things the SDK is designed around:

• Quality — automatic algorithms to heal poor data, plus patented parallel computation technology for performance.
• Ease of use for developers — a logically structured API with comprehensive documentation.

Choose the SDK if you need to import, export, or visualize CAD data inside your own application and want to control that behavior programmatically. The multi-language support matters here: you can work in the language your existing codebase already uses.

Manufacturing Toolkit: for quoting and MaaS platforms

Manufacturing Toolkit is described as a CAD SDK for developers building quoting, DFM, and MaaS platforms, with DFM checks and feature recognition. It sits in the same developer-facing category as the SDK but is scoped to a specific problem domain: turning CAD models into manufacturing-relevant information.

Choose it if your product needs to analyze parts for manufacturability or generate quotes automatically. If you are building a general-purpose CAD viewer or converter, this is likely more specialized than you need — the SDK is the broader fit.

How to decide

Work through these questions in order:

1. Will you use the software yourself, or will you ship it to others? Yourself → Lab. Ship it → SDK or Manufacturing Toolkit.
2. If you are shipping it, is the product about manufacturing, quoting, or DFM? Yes → Manufacturing Toolkit. No → SDK.
3. Does your codebase use C#, C++, Java, JavaScript, or Python? The SDK supports all five, so language is unlikely to rule it out.

One note on licensing: the source material states that perpetual and subscription licensing are available for both software developers and end users, and that the products are positioned as convenient for both startups and enterprise customers. It does not publish specific prices, so confirm current terms directly with CAD Exchanger before committing.

A practical example

Suppose a machine shop wants to let customers upload a STEP file and get an instant quote. The shop's developers would build the upload and quoting logic, and use Manufacturing Toolkit to read the geometry, run DFM checks, and extract the features the quote depends on.

Now suppose the same shop's engineers just want to open that STEP file, check the assembly, and export an STL for a colleague. They would use CAD Exchanger Lab — no development involved.

And suppose a separate software company wants to add a "view 3D model" button to its own design-review tool. That company would use CAD Exchanger SDK to embed import and visualization in its application.

Same underlying technology family, three different entry points depending on whether you are the user, the developer, or the developer with a manufacturing-specific problem.