Convert 3DXML to OBJ

OBJ is needed when a mesh editor, renderer, game engine, slicer, or visualization tool cannot open a Dassault Systèmes 3DXML file. The conversion produces broadly supported polygon geometry, but it discards most CAD and PLM data.

What 3DXML contains

3DXML is a Dassault Systèmes exchange format used by CATIA, DELMIA, ENOVIA, 3DEXPERIENCE applications, and older 3DVia products. It is commonly used to share CATIA-derived product data without distributing native CATPart or CATProduct files.

A 3DXML file is generally a compressed package containing XML product-structure information and geometric representations. Depending on the source and export settings, it can contain assembly instances, tessellated display meshes, exact geometry data, colors, annotations, metadata, and references to other files. Converter support varies by 3DXML version and by the representations included in the package.

What OBJ provides

OBJ is a text-based polygon-mesh format introduced by Wavefront. It stores vertices, faces, normals, texture coordinates, object names, and groups; material definitions are usually written to a separate .mtl file, while texture images remain separate files.

OBJ imports into Blender, Autodesk Maya, 3ds Max, MeshLab, Unity, many slicers, and numerous rendering applications. It is suitable for mesh editing, rendering, and sharing polygon geometry, but it cannot retain parametric features, B-rep solids, constraints, PMI, BOM data, kinematics, or complete CAD assembly relationships.

Convert with desktop software

CAD Exchanger Lab and Datakit CrossManager are desktop converters that support 3DXML import and OBJ export in supported editions. Check the vendor's current format matrix before purchase or conversion, because supported 3DXML variants and licensing differ.

1. Open the .3dxml file and verify that required parts appear in the assembly tree or viewport.
2. Set output units if the converter offers unit controls. OBJ has no standardized unit declaration.
3. Export as Wavefront OBJ; in CAD Exchanger Lab, use File → Save As and select OBJ.
4. Enable normals and material export when available. Select tessellation quality appropriate to the destination: finer meshes improve curved surfaces but increase file size and polygon count.
5. Keep the exported .obj, .mtl, and texture files in the same folder.
6. Open the result in the receiving application and check dimensions, orientation, visible parts, normals, and materials.

CATIA can open many 3DXML files, but OBJ export is not included in every CATIA configuration or license. If OBJ is absent from File → Save As or the available export translators, use a dedicated converter; changing the filename extension does not convert the model.

Online conversion option

CAD Exchanger Cloud can convert files in a browser when its current format list accepts the specific 3DXML variant. Upload the model, choose OBJ, download the result, and extract the downloaded archive before opening the OBJ so that its .mtl and textures remain available. Do not upload controlled technical data, customer models, export-restricted files, or designs covered by confidentiality obligations to any third-party conversion service.

Quality and compatibility limits

OBJ receives polygon geometry, not editable CATIA features or guaranteed exact solids. A 3DXML package containing only a low-detail visualization mesh cannot be converted into engineering-accurate geometry; request a higher-quality source export or a neutral CAD file such as STEP when dimensional fidelity matters.

Assemblies may become separate OBJ objects or groups, or may be flattened by the converter. Part names can survive, but assembly constraints, configurations, metadata, annotations, and 3DEXPERIENCE links normally do not.

Check scale after import. A model authored in millimeters can be interpreted as meters or inches by software that assumes different OBJ units. Measure a known feature before editing, rendering, or manufacturing, then apply a uniform scale correction if necessary.

Materials may change because 3DXML appearance data and OBJ/MTL use different shading models. Texture paths can also break after files are moved; keep all exported files together and use relative texture paths where supported.

Large assemblies can create very large OBJ files because OBJ stores mesh data as text. Reduce tessellation density or export only required components; use GLB, FBX, or another compact mesh format if the target application accepts it and requires preserved scene data or smaller delivery files.