FBX was created in 1996 by Kaydara, a Canadian software company, as the native project format for FiLMBOX, a tool built around motion-capture data for driving animated characters. That motion-capture heritage is still visible in FBX’s strength at carrying complex skeletal animation and mocap data alongside geometry \u2014 a combination few other interchange formats handled well at the time.<\/p>
Kaydara was acquired by Alias in 2004, and Alias was in turn acquired by Autodesk in 2006, putting FBX under Autodesk’s stewardship as the interchange format connecting its own product line \u2014 Maya, 3ds Max, MotionBuilder \u2014 as well as most third-party DCC tools and game engines. Autodesk has continued to extend the format over decades, but the specification and SDK have remained largely Autodesk-controlled rather than an open standard, which is a recurring source of import\/export inconsistencies between different software versions.<\/p>
In DAM terms, FBX is the workhorse of game-development and animation asset pipelines: it’s typically the format a rigged, animated character or prop is exported to once modeling and rigging are finished in the source tool. A DAM serving a studio or agency needs to manage FBX both as a deliverable (for engine ingestion) and as an intermediate exchange artifact, tracking which source file, exporter version, and target engine each FBX was produced for \u2014 since a file that imports cleanly into Unity may behave differently in Unreal or Blender.<\/p>","protected":false},"excerpt":{"rendered":"
A binary\/ASCII 3D interchange format from Kaydara, now owned by Autodesk, carrying geometry, materials, rigging, animation, and camera\/light data between DCC applications.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"What can FBX carry that a simpler format like OBJ cannot?","answer":"OBJ stores only static geometry, UV coordinates, and basic material references, a single frozen mesh with no motion or scene context. FBX captures a full animated 3D scene: skeletal rigs with bones and skinning weights, keyframe and motion-capture animation, cameras, lights, and a hierarchical scene graph linking parent-child node transforms. This makes FBX the format of choice for production pipelines that carry rigged characters, camera moves, and lighting setups, not just isolated shapes."},{"question":"Why do FBX files sometimes look different when opened in different software?","answer":"Autodesk's FBX specification and SDK have historically not been fully open, so different applications' importers\/exporters can interpret materials, pivots, and axis orientation inconsistently \u2014 a known source of round-trip errors between tools."},{"question":"Should a DAM store the FBX export or the original authoring file (Maya\/3ds Max\/Blender)?","answer":"Both, ideally \u2014 the source file preserves full editability, while the FBX is the interchange deliverable actually consumed by game engines and other pipelines; a DAM should link them as related versions of the same asset."},{"question":"Can a DAM preview FBX animation, not just a static mesh?","answer":"Only with a dedicated 3D viewer capable of playing back FBX animation tracks \u2014 most DAM platforms show, at best, a static thumbnail of the bind pose unless a specialized 3D\/animation preview plugin is integrated."},{"question":"Is FBX an open, standardized format like glTF?","answer":"No. FBX is a proprietary Autodesk format; its specification has historically been closed and revised without full public documentation, unlike glTF, which is an open standard maintained by the Khronos Group with a public spec and conformance process. Autodesk does provide the FBX SDK so other applications can read and write the format, but the format itself, its evolution, and its documentation remain under Autodesk's control rather than an open standards body."},{"question":"What metadata should a DAM capture for an FBX asset?","answer":"The exporting application and version, target engine\/use case, whether embedded or external textures are used, and whether animation\/rigging data is included \u2014 these determine compatibility far more than the file extension alone."},{"question":"Why is FBX so common in game-asset DAM pipelines specifically?","answer":"Both Unity and Unreal Engine treat FBX as a first-class native import format for characters, props, and animation, making it the standard handoff point between art\/animation tools and the game engine."},{"question":"Does FBX embed textures, or reference them externally?","answer":"It can do either \u2014 FBX supports embedding texture image data directly inside the file for a fully self-contained asset, or referencing external texture files by path, and a DAM should record which mode was used since it affects whether the FBX is portable on its own."}],"checked_date":"2026-08-11","sources":[{"statement":"FBX was originally developed in 1996 by Kaydara for its motion-capture software Filmbox","source_name":"Wikipedia \u2014 FBX","url":"https:\/\/en.wikipedia.org\/wiki\/FBX","checked":"2026-08-07"},{"statement":"Kaydara was acquired by Alias in 2004, and Alias was acquired by Autodesk in 2006, bringing FBX under Autodesk","source_name":"CAD Exchanger \u2014 What is FBX file format","url":"https:\/\/cadexchanger.com\/fbx\/","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"FBX file: 3D geometry, rigging and animation exchange explained","seo_description":"","noindex":false,"ext":"fbx","full_name":"Filmbox","vendor_name":"Kaydara (acquired by Alias in 2004, then Autodesk in 2006)","introduced":"1996, originally for Kaydara's FiLMBOX motion-capture software","container_notes":"FBX bundles far more than geometry: meshes, UV and material assignments, embedded or linked textures, skeletons and skinning weights, keyframe and motion-capture animation, cameras, and lights can all travel in a single .fbx file. It supports both a binary and a human-readable ASCII encoding of the same schema. Because Autodesk's specification has historically been closed and revised without full public documentation, different applications' FBX exporters\/importers can interpret features (especially materials and pivots) inconsistently, which is the format's most common practical headache.","open_with":[{"platform":"Windows\/macOS\/Linux","how":"Autodesk FBX Review \u2014 free standalone viewer from Autodesk for inspecting FBX geometry and animation"},{"platform":"Windows\/macOS\/Linux","how":"Blender (free) imports and exports FBX via its built-in importer, widely used as a format bridge"},{"platform":"Game engines","how":"Unity and Unreal Engine both import FBX as a first-class asset format for characters, props, and animation"},{"platform":"Autodesk Maya \/ 3ds Max","how":"Native FBX import\/export as Autodesk's own interchange path between its own DCC tools"}],"archive_advice":"FBX is the de facto interchange format between game engines and 3D content-creation tools, so a DAM supporting game or real-time production pipelines should expect FBX as a primary managed asset type, typically alongside its source authoring file (Maya, 3ds Max, Blender). Because Autodesk's FBX SDK and format revisions aren't fully open, exporter\/importer mismatches between application versions are common \u2014 a DAM should record the exporting application and FBX SDK\/format version in metadata so downstream teams can diagnose compatibility issues. As with other 3D formats, most DAM platforms cannot preview FBX natively; pair ingest with an automated thumbnail\/turntable render step or a dedicated 3D viewer integration.","related":[],"tool_link":""},"silo":[23],"class_list":["post-3128","format","type-format","status-publish","hentry","silo-formats"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/3128","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\/3128\/revisions"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=3128"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=3128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}