Convert 3DXML to SLDASM

A 3DXML assembly needs this conversion when it must be opened and edited in SOLIDWORKS, whose native assembly format is .sldasm. The result is also useful for delivering an assembly to a SOLIDWORKS team, but the conversion may require separate part files and rebuilt assembly relationships.

What the 3DXML format is

3DXML is Dassault Systèmes’ XML-based 3D exchange format, used by CATIA, 3DEXPERIENCE, ENOVIA, DELMIA, and related product-lifecycle applications. It carries product structures, geometry, visualization data, properties, and sometimes PLM or annotation data.

A 3DXML file may contain precise B-rep solids and surfaces, tessellated display meshes, assembly hierarchies, or references to external resources. The extension does not prove that the file contains editable CAD solids; some packages are intended mainly for viewing in 3D XML Player or a Dassault application. Collect the accompanying resource files before conversion because linked geometry, textures, or component data may be stored separately.

What the SLDASM format is

SLDASM is the native SOLIDWORKS assembly format. It stores component instances, assembly hierarchy, mates, configurations, suppression states, and references to separate SOLIDWORKS part files such as .sldprt.

An SLDASM is therefore usually not a self-contained replacement for 3DXML. A translator normally creates one assembly file plus one part file for each converted component, although SOLIDWORKS can also contain virtual components. The format lets recipients inspect the assembly in SOLIDWORKS, add mates, measure components, create drawings, and continue mechanical design work.

How to convert 3DXML to SLDASM

Use a CAD translator whose current support matrix explicitly lists 3DXML input and SOLIDWORKS assembly output. Datakit conversion products and CAD Exchanger Desktop or Cloud are possible candidates, but supported 3DXML variants, assembly export, and required licenses differ by edition and release. Confirm the exact matrix before purchasing or uploading a file.

1. Make a working copy of the 3DXML package and place all related resource files in an accessible location.
2. Open the file in the translator with File → Open. Check whether the import contains exact solids, surfaces, or only tessellated meshes.
3. Inspect the product tree. Remove duplicate representations and unwanted reference geometry, and retain the original hierarchy if the software provides an assembly-structure option.
4. Use File → Export or File → Save as and select SolidWorks Assembly (*.sldasm). Enable component-file creation, assembly-structure preservation, component-name preservation, and geometry healing or sewing when available.
5. Export to a dedicated folder and keep the generated .sldasm and .sldprt files together. The assembly normally stores links to those component files.
6. Open the assembly in SOLIDWORKS. If references are missing, use File → Find References or the available reference-repair command to locate the generated part folder.
7. Run Tools → Evaluate → Import Diagnostics on imported parts when the command is available. Check units, component positions, critical dimensions, mass properties, appearances, and the product tree, then save in the required SOLIDWORKS version.

If direct SLDASM export is unavailable, use a translator that can write an assembly-capable STEP file. Export as STEP AP214 or AP242, open the STEP assembly in SOLIDWORKS, select the appropriate import options, and save it as .sldasm. This route generally preserves separate components and spatial structure but not native SOLIDWORKS features, original mates, or design history.

Online conversion is suitable only for nonconfidential files and only when the provider explicitly lists both 3DXML input and SLDASM output. CAD Exchanger Cloud is an option to check; browser services often support 3DXML-to-STEP but not native SLDASM export. Verify how the service handles linked resources, component files, file-size limits, retention, and deletion before uploading proprietary data.

Quality and compatibility limitations

Conversion cannot recreate CATIA or 3DEXPERIENCE feature histories, sketches, formulas, knowledge rules, or proprietary constraints as native SOLIDWORKS features. Converted parts commonly become imported or fixed bodies, so mates, parametric features, and design intent may need to be rebuilt.

Mesh-only 3DXML data cannot produce accurate editable SOLIDWORKS solids without reverse engineering. Increasing tessellation improves appearance but does not restore analytic faces, holes, threads, tolerances, or exact dimensions. External references, unpublished components, configurations, appearances, product metadata, and PMI annotations may also be omitted.

Confirm units and coordinate orientation before export, and compare critical dimensions with the source model. Treat the converted assembly as validated only after checking component count, hierarchy, positioning, references, and geometry inside SOLIDWORKS.