COLLADA began at Sony Computer Entertainment, created by R\u00e9mi Arnaud and Mark Barnes starting around SIGGRAPH 2003, with COLLADA 1.0 announced a year later at SIGGRAPH 2004. Its goal was explicitly collaborative \u2014 the name stands for COLLAborative Design Activity \u2014 and it was notable for bringing major, normally competing DCC vendors including Alias, Discreet, and Softimage together to support a common XML-based interchange schema for the first time.<\/p>
In July 2005, Sony announced that COLLADA had been approved by the Khronos Group as an open industry standard, and stewardship formally transferred to Khronos in January 2006, the same consortium that later developed glTF. COLLADA went on to become the required interchange format for Google Earth and the SketchUp 3D Warehouse in the mid-to-late 2000s, and was used in PlayStation 3 development pipelines, cementing it as a significant cross-industry format for a period.<\/p>
For a DAM today, COLLADA mostly surfaces in legacy asset libraries \u2014 older architectural visualization archives, historical SketchUp Warehouse downloads, or game assets from the mid-2000s. It’s rarely a current production target since FBX and glTF have taken over its roles for DCC interchange and runtime delivery respectively, so a DAM’s job with .dae assets is usually migration: converting them forward to a currently-supported format while preserving the original as historical record.<\/p>","protected":false},"excerpt":{"rendered":"
An open XML-based 3D interchange schema originated at Sony, later governed by the Khronos Group, designed to exchange geometry, materials, and animation between otherwise incompatible DCC tools.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"Is COLLADA still an actively used format for new 3D production?","answer":"Rarely \u2014 COLLADA has largely been superseded by FBX for DCC-to-DCC interchange and by glTF for runtime\/web delivery, so new DAM ingestion of .dae files is mostly historical archives rather than current production output."},{"question":"What does the acronym COLLADA actually stand for?","answer":"COLLAborative Design Activity, reflecting its origin as a cross-vendor effort at Sony that brought competing DCC tool makers together to agree on one interchange schema."},{"question":"Why might a DAM still have a large volume of COLLADA files?","answer":"COLLADA was the required export format for Google Earth and the SketchUp 3D Warehouse for years, so architecture, urban-planning, and visualization DAM archives from that era often hold substantial .dae libraries."},{"question":"Should a DAM convert legacy COLLADA assets to glTF or FBX?","answer":"For active reuse, yes, but conversions should be visually spot-checked since COLLADA's XML schema has historically been implemented inconsistently across tools, so materials and animation don't always translate perfectly on the first pass."},{"question":"Does COLLADA support animation and rigging, or just static geometry?","answer":"It supports both \u2014 skinning, skeletal animation, cameras, and lights are all part of the schema, giving it a scope closer to FBX than to simpler geometry-only formats like OBJ or STL."},{"question":"Is a .dae file readable as plain text?","answer":"Yes, COLLADA is XML, so a DAM can extract scene structure and node metadata by parsing the file directly, without needing a 3D rendering engine, unlike binary formats such as FBX or STL."},{"question":"Who currently governs the COLLADA standard?","answer":"The Khronos Group, the same industry consortium behind OpenGL, Vulkan, and glTF, which took over stewardship from Sony in January 2006."},{"question":"What's the practical downside of COLLADA's XML-based design for DAM storage?","answer":"XML verbosity means .dae files run considerably larger than binary equivalents (FBX, GLB) for the same scene complexity, which matters for storage and transfer costs on large legacy archives."}],"checked_date":"2026-08-07","sources":[{"statement":"COLLADA was initially released in October 2004, created at Sony Computer Entertainment by R\u00e9mi Arnaud and Mark Barnes","source_name":"Wikipedia \u2014 COLLADA","url":"https:\/\/en.wikipedia.org\/wiki\/COLLADA","checked":"2026-08-07"},{"statement":"In July 2005 Sony Computer Entertainment announced COLLADA had been approved by the Khronos Group as an open standard","source_name":"Sony Interactive Entertainment \u2014 Collada Approved by Khronos Group as Open Standard","url":"https:\/\/sonyinteractive.com\/en\/press-releases\/2005\/collada-approved-by-khronos-group-as-open-standard\/","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"","seo_description":"","noindex":false,"ext":"dae","full_name":"COLLAborative Design Activity (Digital Asset Exchange)","vendor_name":"Sony Computer Entertainment, later stewarded by the Khronos Group","introduced":"October 2004 (COLLADA 1.0); transferred to Khronos Group stewardship in 2006","container_notes":"A COLLADA (.dae) file is XML describing geometry (meshes, curves), materials and shaders, scene hierarchy, cameras, lights, skinning, and animation \u2014 a broader scope than OBJ or STL, closer to FBX in ambition. Because it's plain XML it's verbose and human-inspectable but produces large files for complex scenes. COLLADA notably became the first cross-vendor interchange effort with participation from Alias, Discreet, and Softimage, and it was adopted as the required interchange format for Google Earth\/SketchUp 3D Warehouse models and PlayStation 3 development, though its practical relevance has since been largely superseded by FBX and glTF.","open_with":[{"platform":"Windows\/macOS\/Linux","how":"Blender (free) imports and exports COLLADA .dae files"},{"platform":"Windows\/macOS","how":"Autodesk Maya and 3ds Max both support COLLADA import\/export via plugin or built-in translator"},{"platform":"Web browser","how":"Online viewers such as the Autodesk Viewer or various open-source Three.js-based viewers render .dae directly"},{"platform":"Google SketchUp legacy exports","how":"Older SketchUp versions export directly to COLLADA for use in Google Earth and other 3D pipelines"}],"archive_advice":"COLLADA is now largely a legacy interchange format \u2014 most active 3D pipelines have moved to FBX for DCC-to-DCC exchange or glTF for delivery \u2014 so a DAM encountering .dae assets should treat them as historical or migration-source material rather than a target format for new production. Because COLLADA is verbose XML with a somewhat loosely enforced spec, materials and animation don't always round-trip cleanly between applications, so any DAM-driven format conversion (e.g., .dae to glTF) should be spot-checked visually rather than assumed lossless. As with other 3D formats, expect no native preview in most DAM platforms; COLLADA's XML structure at least makes metadata extraction (scene contents, node names) straightforward without a full 3D renderer.","related":[],"tool_link":""},"silo":[23],"class_list":["post-3132","format","type-format","status-publish","hentry","silo-formats"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/3132","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/format"}],"version-history":[{"count":0,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/3132\/revisions"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=3132"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=3132"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}