Reference Formats
FBX
A binary/ASCII 3D interchange format from Kaydara, now owned by Autodesk, carrying geometry, materials, rigging, animation, and camera/light data between DCC applications.
Extension
.fbx
Full name
Filmbox
Introduced
1996, originally for Kaydara's FiLMBOX motion-capture software
Vendor
Kaydara (acquired by Alias in 2004, then Autodesk in 2006)
What is inside the container
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.
How to open it
For archives
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 — 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.
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 — a combination few other interchange formats handled well at the time.
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 — Maya, 3ds Max, MotionBuilder — 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.
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 — since a file that imports cleanly into Unity may behave differently in Unreal or Blender.
Frequently asked
What can FBX carry that a simpler format like OBJ cannot?
FBX supports skeletal rigging, skinning weights, keyframe and motion-capture animation, cameras, lights, and embedded materials — a full animated scene — while OBJ is limited to static geometry only.
Why do FBX files sometimes look different when opened in different software?
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 — a known source of round-trip errors between tools.
Should a DAM store the FBX export or the original authoring file (Maya/3ds Max/Blender)?
Both, ideally — 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.
Can a DAM preview FBX animation, not just a static mesh?
Only with a dedicated 3D viewer capable of playing back FBX animation tracks — most DAM platforms show, at best, a static thumbnail of the bind pose unless a specialized 3D/animation preview plugin is integrated.
Is FBX an open, standardized format like glTF?
No — FBX is proprietary to Autodesk, unlike glTF or COLLADA which are Khronos Group open standards; this matters for long-term archival risk since Autodesk controls format changes.
What metadata should a DAM capture for an FBX asset?
The exporting application and version, target engine/use case, whether embedded or external textures are used, and whether animation/rigging data is included — these determine compatibility far more than the file extension alone.
Why is FBX so common in game-asset DAM pipelines specifically?
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.
Does FBX embed textures, or reference them externally?
It can do either — 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.
Sources
- FBX was originally developed in 1996 by Kaydara for its motion-capture software Filmbox checked 2026-08-07 — Wikipedia — FBX
- Kaydara was acquired by Alias in 2004, and Alias was acquired by Autodesk in 2006, bringing FBX under Autodesk checked 2026-08-07 — CAD Exchanger — What is FBX file format