FBX Viewer

How to view an FBX file

1. Select a binary FBX file using the picker above.
2. MeshWrench resolves it locally, in a background worker — nothing leaves your device.
3. Once resolution finishes, drag to rotate, scroll to zoom, and use the panel below the viewport to fit the view, toggle wireframe, switch material display or shading, or show and hide individual mesh instances.

What the FBX Viewer displays

After a file loads, the panel below the viewport shows file size, FBX version, encoding, model/geometry/ mesh-instance/material counts, embedded and external texture counts, control-point and polygon counts, rendered triangle count, skipped-polygon count, source-normal/UV/vertex-color availability, the file's own declared unit scale and axis system, and normalized dimensions. A scene tree lists every model and mesh instance in the file's real hierarchy, so you can inspect — and individually show or hide — the pieces of a multi-part model.

Supported binary FBX versions

This viewer reads binary FBX versions 7000 through 7700 — both node-record layouts binary FBX has used across that range: 32-bit offset and length fields below version 7500, and 64-bit fields from 7500 onward. A version outside this range, or an ASCII FBX file, is rejected clearly and safely, rather than misread as something it isn't. This is a deliberately scoped first implementation, not a claim of universal FBX compatibility.

Materials and embedded textures

A practical first-viewer subset renders: Lambert and Phong diffuse color and factor, opacity where it's deterministically available from the file's own declared properties, and each mesh instance's connected material. A texture embedded directly in the file — connected through a Video object's own embedded bytes — is decoded and shown, the same way MeshWrench's GLB Viewer decodes its own embedded base-color textures. A texture that only references an external file is detected and disclosed, but MeshWrench never fetches it — doing so would mean making a network request outside your browser's local processing, which this project never does.

Units and axis handling

FBX files declare their own coordinate unit scale and axis system in GlobalSettings. When a file declares both completely and consistently, this viewer converts its coordinates exactly once into a right-handed, Y-up system, normalized to meters. When either is missing or contradictory, MeshWrench doesn't guess: coordinates are shown exactly as declared, in plain model units, with a clear note explaining why.

What this viewer doesn't do: animation and rigging

This is a static mesh viewer. Animation stacks and curves, skin deformers, skeletons, blend shapes, cameras, lights, NURBS/patch geometry, subdivision surfaces and constraints are all detected and listed in the model info panel when present, but never applied — what renders is always the file's default, undeformed base geometry. MeshWrench doesn't claim animated, rigged or skinned FBX support.

Why an FBX may not open

• The file is an ASCII FBX file rather than binary — only binary FBX is supported in this phase.
• The file's declared FBX version is outside the 7000–7700 range this viewer supports.
• The file's internal node-record data is truncated, corrupted, or references an offset outside the file.
• A mesh references a control point or polygon that doesn't exist, or a polygon has fewer than three vertices.
• The file's model hierarchy contains a circular reference.
• The file is more complex (models, geometries, polygons or triangles) than this tool's safety limits currently allow.

Is the FBX uploaded?

No. There is no server-side file-processing route in MeshWrench at all. Your browser reads the file with the standard File API, hands its bytes to a Web Worker running on your device, and renders the result with WebGL — also on your device. You can verify this yourself: open your browser's developer tools, watch the network tab, and load a file. No request containing your file, or any value found inside it, will appear.