cadexchanger.com

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.

CAD Exchanger offers both perpetual and subscription licensing, and the company states that this dual model is designed to be convenient for both startups and enterprise customers. That is the full extent of what the official site discloses: it confirms the two licensing types and the two audience groups, but does not publish prices, seat counts, or tier names. If you need actual numbers or terms, you have to contact the vendor or go through the product pages.

What the official site says about licensing

The relevant statement appears in the "Why CAD Exchanger?" section of cadexchanger.com, under the heading "Cost-Effectiveness":

• Perpetual and subscription licensing are both offered.
• The licensing applies to both software developers and end-users.
• The company describes the model as convenient for both startups and enterprise customers.

That is a positioning claim rather than a price list. Nothing on the page specifies cost, minimum commitment, or what separates a startup deal from an enterprise deal.

Why the two-axis model matters

The licensing structure has two independent dimensions, and understanding them explains why the same vendor can serve a solo developer and a large manufacturer.

Axis 1: Perpetual vs. subscription

• Perpetual means you pay once and keep the right to use that version, which suits teams that need a fixed, predictable capital expense and long-lived deployments.
• Subscription spreads cost over time and typically tracks ongoing updates, which suits teams whose needs or headcount change.

The site does not say which products are available under which model, so treat this as a general distinction rather than a confirmed mapping.

Axis 2: Developers vs. end-users

This is the more important split for budgeting, because it maps onto different products:

A startup building a quoting platform is a developer customer even if it is small. A large engineering department that just needs to open and convert files is an end-user customer even if it is big. Size and licensing category are not the same thing.

How to decide which path fits you

Because pricing is not published, the practical question is which product and which licensing type to ask about. Use these conditions:

• You only need to view, explore, and convert files yourself → ask about CAD Exchanger Lab as an end-user license.
• You are embedding CAD import/export into your own application → ask about the SDK, and specify your language (C#, C++, Java, JavaScript, or Python).
• You are building a quoting, DFM, or manufacturing-as-a-service platform → ask about Manufacturing Toolkit.
• You need something the off-the-shelf products do not do → ask about Custom Development.
• You need a fixed long-term cost and can live without continuous updates → ask whether perpetual licensing applies to your product.
• You expect your usage or team to change → ask about subscription terms.

What is not disclosed

Be aware of these gaps before you plan a budget:

• No prices, tiers, or seat minimums appear on the site.
• No payment platforms or checkout links are listed.
• No statement says anything is free, and no login requirement is described either way.
• The split of which products support perpetual vs. subscription licensing is not specified.

The site does note that the products are trusted by "industry leaders and startups from 110+ countries," which supports the claim of broad applicability but tells you nothing about terms.

Practical next step

Go to cadexchanger.com, identify which of the four offerings matches your use case, and request licensing details directly. Bring two questions: (1) is this available under both perpetual and subscription, and (2) what does the developer vs. end-user distinction mean for my specific scenario. Those two answers will determine whether the model actually fits a startup budget or an enterprise procurement process.

CAD Exchanger's main technical advantages are data healing for poor-quality CAD files, patented parallel computation for performance, and a split design that gives end users an intuitive UI while giving developers a structured API with full documentation. These advantages matter most if you work with messy imported geometry, large assemblies, or need to embed CAD import/export into your own software.

Data quality: automatic healing of poor CAD data

CAD files often arrive with gaps, mismatched surfaces, or other defects that break downstream modeling or visualization. CAD Exchanger applies automatic algorithms to heal this poor data, so you spend less time manually repairing geometry before you can use it.

This is relevant when:

• You receive STEP, JT, or other neutral-format files from suppliers with inconsistent quality.
• You need clean B-Reps or polygonal meshes for visualization, simulation, or quoting.
• You want to avoid rebuilding models that were exported incorrectly.

The healing runs as part of the import/conversion process rather than as a separate manual step, which is the practical difference from tools that only flag errors.

Performance: patented parallel computation

CAD Exchanger uses patented parallel computation technology to ensure high performance. In practice, this means the heavy work of reading, converting, and processing CAD data is spread across multiple cores instead of running as a single-threaded task.

For you, that translates to:

• Faster handling of large assemblies and complex B-Rep models.
• Better throughput when converting many files in a batch.
• More predictable performance on modern multi-core hardware.

The site presents this as a core reason to choose the product, alongside quality and ease of use.

Two audiences, two interfaces

CAD Exchanger is deliberately split so that the same underlying technology serves different users through different surfaces.

The SDK supports C#, C++, Java, JavaScript, and Python, so you can integrate CAD import/export into applications written in common languages rather than being locked to one stack.

What you can actually do with the data

The technical strengths feed into concrete capabilities:

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

If your task is "open this supplier file, check the assembly structure, and export a clean STL," the combination of healing plus multi-format support is what makes that a single workflow instead of several tools.

Licensing and fit

CAD Exchanger offers perpetual and subscription licensing for both software developers and end users, and the site states it is used by organizations from 110+ countries, from startups to enterprise customers. That flexibility matters if you need to match licensing to how long you'll use the tool or how you distribute it in your own product.

How to decide

• Choose CAD Exchanger Lab if you mainly need to view, explore, and convert files yourself on desktop, web, or mobile.
• Choose the SDK if you're building CAD import/export into your own application and want a documented API across C#, C++, Java, JavaScript, or Python.
• Consider Manufacturing Toolkit if you're building quoting, DFM, or MaaS platforms and need feature recognition and DFM checks.

The deciding factors are usually data quality (do your files arrive broken?) and performance (are your assemblies large?). If both are yes, the healing algorithms and parallel computation are the advantages that justify the choice.

CAD Exchanger is a platform for viewing, exploring, and converting 3D CAD data across desktop, web, and mobile. It reads and writes SolidWorks, STEP, JT, STL, and 30+ other 3D formats. The product line splits into three tracks: CAD Exchanger Lab for end users who need to open and convert files, CAD Exchanger SDK for developers embedding CAD import/export into their own software, and Manufacturing Toolkit for teams building quoting, DFM (design-for-manufacturing), and MaaS (manufacturing-as-a-service) platforms. It suits engineers working with mixed-format CAD files, software developers who need CAD libraries in C#, C++, Java, JavaScript, or Python, and businesses that want custom engineering software built around CAD data.

What CAD Exchanger actually does

The core job is format interoperability. CAD files come in dozens of incompatible formats, and moving geometry between them usually loses structure, metadata, or precision. CAD Exchanger addresses that by reading and writing 30+ formats while preserving:

• Assemblies and parts — the component hierarchy, not just a flattened mesh
• Precise B-Reps and polygonal meshes — both exact boundary representations and tessellated geometry
• Metadata and PMI — product manufacturing information such as dimensions and tolerances attached to the model

For visualization, it supports sectioning, explode views, and multiple display modes, so you can inspect internal structure and assembly relationships rather than just looking at a static render.

The three product lines

If you just need to open a STEP file someone sent you and export it as STL, Lab is the relevant product. If you're building an application that must ingest customer CAD files, the SDK is the entry point. If you're building a quoting or manufacturing platform, Manufacturing Toolkit adds DFM checks and feature recognition on top.

Why teams choose it

Three stated differentiators:

• Quality — automatic algorithms to heal poor or broken CAD data, plus patented parallel computation for performance on large models
• Ease of use — a clear UI for end users and a logically structured API with documentation for developers
• Cost-effectiveness — perpetual and subscription licensing for both developers and end users, positioned as workable for startups and enterprise customers alike

The data-healing point matters in practice: real-world CAD files are often exported badly, with gaps, flipped normals, or missing topology. Automatic repair reduces manual cleanup before conversion.

Who uses it

CAD Exchanger states it is trusted by industry leaders and startups from 110+ countries. That spans two very different use cases: a single engineer converting a file on a desktop, and a software company licensing an SDK to handle CAD import inside a commercial product. The licensing model (perpetual or subscription, for both developers and end users) is designed to fit both ends of that range.

Getting started

The site's own framing is "It's easy to get started" — the practical path depends on which track you're on:

• End user → download CAD Exchanger Lab, open a file, and convert or inspect it
• Developer → evaluate the SDK in your language of choice (C#, C++, Java, JavaScript, Python) and check the API documentation
• Platform builder → look at Manufacturing Toolkit for quoting, DFM, and MaaS scenarios

Pricing, trial terms, and platform availability are not specified in the source material, so check the product pages directly for current licensing options and supported operating systems before committing.

CAD Exchanger reads and writes SolidWorks, STEP, JT, STL, and more than 30 other 3D formats, and it can view, explore, and convert that data across desktop, web, and mobile. It fits the common case where a part or assembly arrives in a format your tool doesn't open, or where you need to move geometry between CAD systems without losing structure. It is not a full CAD authoring tool — the emphasis is on import/export, inspection, and visualization rather than creating or editing designs.

What CAD Exchanger can do with a file

The workflow is built around three operations:

• Import/export — read and write SolidWorks, STEP, JT, STL, and 30+ other 3D formats.
• Access — reach assemblies and parts, precise B-Rep geometry and polygonal meshes, plus metadata and PMI (product manufacturing information).
• Visualize — use sectioning, explode views, and multiple display modes to inspect the model.

So a typical task is: open a file in a format you can't otherwise read, check its structure and dimensions, then export it to a format your downstream tool accepts.

Formats and what each is good for

The distinction that matters most: B-Rep formats (SolidWorks, STEP, JT) carry precise surfaces and edges, while mesh formats like STL carry triangles only. If you convert a B-Rep model to STL, you keep the shape but lose the precise geometry and much of the structure — so choose the target format based on what the next tool actually needs.

Which product to use

CAD Exchanger is offered in several forms, and the right one depends on who you are:

• CAD Exchanger Lab — a desktop app for viewing, exploring, and converting 3D CAD data across 30+ formats. Best for an individual who just needs to open and convert files.
• CAD Exchanger SDK — 3D CAD libraries for C#, C++, Java, JavaScript, and Python. Best for developers embedding import/export into their own software.
• Manufacturing Toolkit — an SDK for building quoting, DFM, and MaaS platforms.
• Custom Development — bespoke engineering software and customization of existing applications.

The site notes that licensing is available as both perpetual and subscription, for developers and end-users, and positions this as suitable for startups and enterprise customers alike. It does not publish specific prices on the page, so check current terms directly before committing.

Practical notes before you convert

• Check the target format's limits first. If the receiving tool only accepts meshes, exporting to STL is fine; if it needs editable geometry, stay with STEP or another B-Rep format.
• Expect cleanup on poor data. The platform advertises automatic algorithms to heal poor data, which matters when source files are messy or come from mixed sources.
• Verify structure survives. Assemblies, metadata, and PMI are only useful if the target format supports them — confirm after export rather than assuming.
• Match the tool to the job. For one-off viewing and conversion, the desktop Lab app is the direct route; for repeated or embedded conversion, the SDK is the relevant choice.

If your goal is simply "open this file and give me a format my other software can read," CAD Exchanger covers that across 30+ formats. If your goal is to design or edit models, you'll want a CAD authoring tool instead.