Free Online FBX Viewer
FBX is the format studios still trade game assets in, and it is the one format that carries rigs, animation, cameras, lights and units together. This viewer opens .fbx files with the three.js FBXLoader, locally in the browser, and shows you the geometry, its materials and its real proportions.
It is an inspection tool, not an animation player. A rigged character appears in its bind pose, skeletons are parsed so the mesh stands correctly, and embedded texture files are decoded straight from the FBX.
Select the model together with its material, texture and binary files. Files stay in this browser.
AO mode displays authored occlusion maps; white means none is supplied. This is not real-time ambient occlusion.
- Vertices
- —
- Triangles
- —
- Materials
- —
- Dimensions
- —
How it works
Add your FBX file
Drop a .fbx file onto the drop zone or click to browse. Binary FBX from Maya, 3ds Max, Blender and Mixamo opens directly; ASCII FBX works too but is much larger, so it parses more slowly.
Inspect geometry and materials
Left-drag to orbit, scroll to zoom, right-drag to pan. Use wireframe or normal shading to check triangulation and flipped faces, and read vertex, face and material counts plus bounding-box dimensions from the info panel.
Convert in the browser if you need another format
There is no open-source Python reader for FBX, so FBX conversion runs browser-first: three.js extracts the mesh locally, the mesh is uploaded, and the server writes OBJ, GLB, glTF, STL, PLY, USDZ or 3MF from it.
Local parsing, 500MB ceiling
FBXLoader runs in the tab, so the file is never uploaded and the viewer can accept up to 500MB. Nothing is stored and no account is needed.
Binary and ASCII FBX
Both flavours load: compact binary FBX 7.x as written by current DCC tools, and the older ASCII form. Files from pre-6.1 versions or with unusual property encodings are the ones most likely to fail.
Textures embedded in the file
FBX can pack its texture images into the file itself, and the loader decodes that embedded media. That is why an FBX usually looks right without hunting for a texture folder next to it.
Rigs parsed, animation not played
Skeletons are read so skinned meshes stand in their bind pose, but this viewer does not run animation clips. Review motion in the engine you are targeting, where playback actually matters.
Ten shading modes and viewport tools
Textured, wireframe, unlit, normal, matcap, AO, depth, UV checker, diffuse and X-ray, plus grid, auto-rotate, camera reset, fullscreen and a PNG snapshot for bug reports.
Honest numbers
Vertex count, triangle count, material count and bounding-box dimensions come from the parsed geometry, not from the file header, so they reflect what the loader actually read.
What Is a FBX File?
FBX began life at Kaydara as a film and game interchange format and was acquired by Autodesk in 2006. It exists in two encodings: a compact binary form that almost every exporter writes by default, and an ASCII form that is readable but several times larger.
What makes FBX persistent is breadth. A single file can hold polygon meshes, subdivision surfaces, NURBS, skeletons with skin weights, animation curves, blend shapes, cameras, lights and materials, and it records the unit system so a model authored in centimetres survives a round trip between tools.
The price is complexity. FBX is proprietary, its SDK is a large C++ library, and there is no maintained pure-Python reader, which is why this project previews FBX in the browser and converts it browser-first rather than pretending a server-side parse exists. Files exported by very old versions, or ones that reference textures by absolute Windows paths, are the usual causes of a failed load.
Advantages
- Carries rigs, animation, cameras and lights, not just geometry
- First-class import in Unity, Unreal and most DCC tools
- Records units, so scale survives a round trip
- Embedded media keeps textures inside one file
Disadvantages
- Proprietary and heavy to parse; no open-source Python reader here
- ASCII FBX is huge, so exports are slow and memory-hungry
- Texture references can break when they point at absolute paths
- Only the newest file version from a newer DCC release may fail to open in older tools
Who Uses This FBX Viewer?
Game developers
Check a character or prop FBX from an asset store before importing it: confirm the scale is metric, the rig stands in a sane pose and the materials came along.
Roblox and mobile creators
Inspect the mesh and triangle budget of a MeshPart or mobile asset before uploading it into a platform with strict limits.
3D artists receiving outsourced work
Review a delivered FBX from a freelancer in the browser, without installing the exact DCC version the file was authored in.
Technical artists and pipeline developers
Diagnose a reported bad export quickly: look at the triangulation, spot flipped normals and confirm the file is what the bug report says it is.
AR and VR developers
Verify orientation and scale before a model becomes a tracked object or a placed prop, where being 100x off is expensive to discover late.
Students and teachers
Open a course asset on any machine, including ones where installing Autodesk software is not an option.
Frequently Asked Questions
What is an FBX viewer?
It is a tool that parses an Autodesk FBX file and draws its geometry in an interactive viewport, so you can inspect shape, scale, materials and triangulation without opening Maya, 3ds Max or Blender. This one runs entirely in your browser with a three.js FBXLoader and never uploads the file.
How do I view an FBX file online?
Drag the .fbx onto the drop zone or click to browse. Binary FBX 7.x from current exporters loads fastest; ASCII FBX also loads but the text form can be several times larger. The model is framed automatically once parsing finishes and nothing is uploaded.
Does the viewer support both binary and ASCII FBX?
Yes, both are handled. The loader covers the FBX 6.1 to 7.5 range that modern tools write; very old versions, or files that use unusual property encodings, may fail. If a file will not load, re-export it as binary FBX 7.4 or as GLB from the application that authored it.
Does the viewer play FBX animations?
No. Animation curves are parsed but not played, so a rigged character is displayed in its bind pose and blend shapes appear at their default weights. This page is for static inspection of geometry, materials and scale; review motion in the engine or DCC tool you are actually delivering to.
Will I see the textures that are inside my FBX?
Yes. FBX can embed its texture images, and the loader decodes that embedded media, so an exported character usually arrives fully textured. Files that reference images by absolute path, such as a C:\Users\... location on the machine that exported them, cannot resolve those references in a browser; re-export with embedded media.
Is my FBX file uploaded to a server?
No. Parsing and rendering are local, and the viewer accepts files up to 500MB without a bandwidth cost. The only upload happens if you then choose a conversion, where the extracted mesh goes to the server-side pipeline with a 50MB limit.
Can I convert an FBX to OBJ, GLB or STL?
Yes, but via the browser-first path, because no open-source Python FBX reader exists. Three.js parses the file in your tab, the extracted mesh is uploaded (up to 50MB), and the server writes OBJ, GLB, glTF, STL, PLY, USDZ or 3MF from it. Geometry and base materials survive; skeletons and animation do not, because the target mesh formats cannot carry them.
Why does my FBX look far too large or too small?
FBX records a unit scale, and exporters do not all write the same one: a file authored in centimetres or inches can arrive 100x or 25.4x away from what you expected. Check the export unit in the DCC tool, or convert to STL and use the STL editor's scale-to-width operation to set the longest axis to an exact millimetre value.
What is the maximum FBX file size this viewer accepts?
500MB, parsed locally, with no upload. In practice the limit is your device's memory plus the encoding: a 200MB ASCII FBX costs far more to parse than a 200MB binary one, because the text form stores every number as characters. Re-exporting as binary usually shrinks the file several times over.