Convert SLDPRT to CATIA V4 in your application
3D InterOp is a CAD interoperability SDK that lets your software read SLDPRT files and write CATIA V4, with exact B-Rep geometry carried across and nothing tessellated.
Spatial does not offer an online converter or a desktop conversion app. 3D InterOp is a component that software vendors embed in their own products.
- Reads SOLIDWORKS part · Writes CATIA V4
- Exact geometry → exact geometry
- C++ / C# APIs
SLDPRT to CATIA V4 at a glance
Both formats store exact geometry, so the model stays exact. The differences are in the product data each one can carry.
| SOLIDWORKS part (source) | CATIA V4 (target) | |
|---|---|---|
| Full name | SOLIDWORKS Part | CATIA Version 4 |
| Standard / owner | Dassault Systèmes SOLIDWORKS | Dassault Systèmes |
| File extensions | .sldprt | .model, .exp, .session |
| Geometry | Exact B-Rep | Exact B-Rep |
| Assemblies / structure | Part file (assemblies are SLDASM files) | Yes (written as parts only) |
| PMI | Semantic (DimXpert) and graphical, SOLIDWORKS 2014 and later | None in the format |
| 3D InterOp support | Read only | Read and write |
What's preserved, what changes
Here is what your application can expect to carry across from SOLIDWORKS part to CATIA V4.
-
Preserved
Exact geometrySolids and surfaces stay exact B-Rep. The model is never reduced to a triangle mesh.
-
Not carried
PMICATIA V4 has no PMI, so the PMI read from SLDPRT isn’t written. Keep STEP AP242 as an output when PMI matters.
Why software vendors add SLDPRT to CATIA V4 conversion
Deliver in your customer’s CAD format
Aerospace and automotive OEMs often require supplier data in CATIA V4. Writing it lets your users meet that requirement directly from your application.
Exact geometry, ready to edit
CATIA V4 keeps exact B-Rep geometry, so the receiving engineer can measure, modify or machine the model in CATIA.
No neutral-format round trip
Writing CATIA V4 directly avoids an extra STEP or IGES step, and the loss each extra translation can add.
Things to check before you ship
- Written CATIA V4 versions: CATIA 4.1.9 to 4.2.4 (.model).
- The CATIA V4 writer isn’t available in 3D InterOp CGM.
- Supported SLDPRT input: SOLIDWORKS 98 to 2026.
- Validate a sample of translated files in the target system your users actually work with.
Working with Spatial was a real milestone for us: Thanks to the powerful 3DInterOp library, we were able to successfully bring our complex CAD-based solutions to the cloud while remaining flexible to meet individual customer requirements. For us, Spatial is not just a technology partner, but a true enabler of our product strategy.
Dr. Arno Michelis, Founder, Simus Systems
Read the Case StudyAbout the formats
-
Source format
What is an SLDPRT (.sldprt) file?
An SLDPRT file is a SOLIDWORKS part: a single component with its exact 3D geometry, feature tree and properties. SOLIDWORKS is built on the Parasolid kernel.
-
Target format
What is a CATIA V4 (.model) file?
CATIA V4 is the legacy generation of Dassault Systèmes’ CATIA, whose models are mostly stored in .model files. Many aerospace and automotive archives still hold CATIA V4 data.
Frequently asked questions
Yes. Both formats store exact B-Rep geometry, so the model is translated without being tessellated into triangles.
CATIA V4 has no PMI, so the PMI read from SLDPRT isn’t written. When PMI matters, offer STEP AP242 as an output.
No. The CATIA V4 writer isn’t available in 3D InterOp CGM.
Yes. If your application uses Parasolid, a Parasolid-based SOLIDWORKS reader is available.
Semantic PMI from SOLIDWORKS 2014 to 2026, and graphical PMI from SOLIDWORKS 2014 onwards.
3D InterOp reads SOLIDWORKS 98 to 2026.
3D InterOp writes CATIA 4.1.9 to 4.2.4 (.model).
-
Building software that needs to convert SLDPRT to CATIA V4?
3D InterOp is an SDK that lets your application read SOLIDWORKS part and write CATIA V4 alongside 30+ CAD and BIM formats.