Convert DAE to GLB

Why convert DAE to GLB?

DAE (Collada) is an XML-based format that was widely supported a decade ago, but modern web and AR pipelines use glTF. Converting DAE to GLB brings an older asset into a format that Three.js, Babylon, model-viewer and current game engines load quickly. The conversion keeps the meshes, hierarchy, materials and textures, and writes them into one binary file so there are no loose texture images to lose. The Collada header's unit and up axis are read, so a model in inches or centimetres is scaled to glTF's metres, and the orientation is adjusted for glTF's Y-up convention. Animation and rigging in the DAE are not carried through by this converter.

How to convert DAE to GLB

1. Drop your DAE file (with its textures, if separate) onto the converter — it opens in your browser, nothing is uploaded.
2. Check the preview and the dimensions in mm; fix units or the up axis in “Units & orientation” if the size or orientation looks wrong.
3. Choose GLB as the output and click Convert. Several files download as one ZIP.

What carries over from DAE to GLB

What changes

• Textures referenced by the DAE are embedded in the GLB.
• Units from the DAE header are converted to metres.
• Skeletal animation and controllers are not exported.
• Older Collada shader effects are mapped to glTF's standard material.

Tips

• Put the DAE and its texture images in the same upload so textures can be found.
• Open the GLB in the viewer to check for missing textures or flipped faces.
• Large embedded textures can make the GLB heavy; resize them first for web use.

About DAE files

COLLADA, short for COLLAborative Design Activity, was started by Sony Computer Entertainment and handed to the Khronos Group, which published it as an open XML standard; it became ISO/PAS 17506. Files use the .dae extension. The goal was a neutral format that let different content-creation tools exchange assets without losing information, so it is broader than a mesh format: it describes geometry, materials and effects, images, cameras, lights, skeletons, skin controllers, animations and even physics. It declares its own unit with a meter attribute and an up_axis setting, which is more than OBJ or STL offer. Because it is verbose XML, files are large, and glTF has since taken over the role of Khronos's recommended runtime format. DAE still turns up in SketchUp downloads, Google Earth content, robotics (ROS) and older game and simulation assets.

About GLB files

GLB is the binary container for glTF 2.0, the format the Khronos Group describes as the JPEG of 3D. One .glb file bundles a JSON scene description, binary mesh buffers and embedded images, so nothing can go missing in transit. The format was designed for efficient delivery and loading on the web, and it is now used by Three.js, Babylon.js, model-viewer, Google Search 3D results, Meta platforms, Unity and Unreal importers, and many marketplaces such as Sketchfab. glTF defines a physically based metallic-roughness material model, a node hierarchy, cameras, skins and animations. Coordinates are in metres with +Y up and a right-handed system. It is excellent for display and game assets, but it is a presentation format rather than a manufacturing one, so print workflows usually convert it first.

3D printing notes

Slicers do not open DAE, so models are converted to STL or 3MF. SketchUp users run into this often, because SketchUp exports DAE and its models are drawn in inches. Since the file records its unit scale, a correct importer gets the size right, though SketchUp-style models are also built from many separate faces and groups, with duplicated or internal geometry that can confuse slicers. Check the reported dimensions and the watertight status after conversion. MeshShift reads DAE in the browser, applies the unit and up axis from the file, and can save the result as STL, 3MF, OBJ or GLB. It does not write DAE.

More conversions