Local model inspection

FBX Viewer Online

Open a supported FBX file in your browser and inspect its geometry and compatible materials. Include local images when the file references them. FBX features vary by exporter; check the visible result and any available animation before using the asset in your destination application.

Last updated

Works locally · FBX · Maximum 50 MB combined

Select one model and its local BIN, MTL or texture files together.

Choose a FBX model or drop it here.

Your file is parsed in memory. It is never uploaded.

Drag to rotate. Right-drag or two-finger drag to pan; scroll or pinch to zoom. Keyboard: arrows rotate, Shift + arrows pan, + / − zoom, R resets. Animation starts only when you press Play.

Choose an existing model from your device. This tool does not generate a new 3D asset.

How to inspect an FBX model online

Select an FBX from your device, plus the local images that its materials reference. The full selection must stay within 50 MB. If the asset arrived as an archive, extract it before you choose the files. Remote texture locations are not fetched.

When the scene loads, first check the shape and orientation. Rotate around the model and compare the back and underside with your expectations. If animation is available, the playback control plays the first imported clip. Use the source or destination application to review other clips. A successful import does not mean every exporter-specific feature has been reproduced.

  • Export a compatible FBX from the source application.
  • Include the relevant local images with the FBX selection.
  • Inspect the whole scene before judging a small material detail.
  • Approve scale, rig behavior and materials in the receiving application.

FBX compatibility depends on the export

FBX can carry much more than a triangle surface. Its data can include hierarchies, deformers, animation and material connections. Different applications write and interpret these features differently. This browser viewer provides an inspection path for supported files, not a replacement for the original authoring application.

Use a modern FBX 7.x export. Older files and unsupported variants can fail to parse. If a model does not open, re-export a simple compatible version from the source application. Keep the original file so you can return to the full scene and its export settings.

Check textures and material differences

The browser can only display materials and texture encodings supported by its importer and renderer. Use local PNG, JPEG or WebP resources when separate images are required. Native shader graphs, procedural textures and renderer-specific nodes need a suitable baked or simplified export.

If a textured model appears flat, confirm that the correct local images were selected and that their names match the file references. If the resources are present, compare the source material with the supported export. Different lighting and material interpretation can change the result even when the geometry is correct.

Review animation as a separate part of the asset

An FBX can contain animation, but the presence of animation data does not establish that every clip will import or play as intended. The browser control plays the first imported clip without a clip selector. Inspect its motion at the parts that matter: hands, joints, attachment points and any moving props. Review the default pose too.

A browser preview does not replace testing a rig in the destination engine. Constraints, custom controllers, retargeting rules and application-specific behavior may need an export bake or a dedicated import workflow. Use the original rig for editing and review other animation clips in an appropriate application.

Inspect scale, orientation and visible structure

Automatic framing helps you find the imported scene. It does not prove that the unit scale and orientation suit your project. Check a known feature against a reference in the receiving application. Review the pivot before using the model as a placed prop or animated object.

Use wireframe for dense regions, thin triangles and unexpected surfaces. Use a normal view when shading looks inconsistent. These views help you identify areas to investigate; they do not repair a mesh or validate collision, skin weights or production topology.

If the FBX will not load

Check the error and export version first. An old or incomplete file needs a new export. A missing resource needs the referenced local file. Renaming another asset format to .fbx does not convert it, and a remote dependency remains blocked even when the FBX itself is local.

A scene can also exceed practical browser memory while fitting the 50 MB selection limit. Dense geometry and large images expand in memory during import. For review, export one relevant object or a smaller scene copy. Keep the complete source in the authoring tool.

Prepare a review export without losing the source

Keep the native project and create a separate FBX for inspection. Choose the objects you intend to review and make the material dependencies explicit. If a large production scene contains unrelated content, exporting only the relevant asset can make the review easier and reduce browser memory use.

If the source uses procedural or renderer-specific materials, bake or simplify them through a workflow appropriate to that application. A texture image can replace some appearance data, but it does not automatically capture every property of a complex shader. Check the prepared export in the source tool before sending it onward.

When several versions exist, use distinct filenames and keep the export settings with the asset. That makes it possible to compare the same object after a rig, material or unit change. The browser preview does not store a native scene history or identify which export option produced a difference.

Use a consistent review order for an FBX handoff

First confirm that the intended objects are present. Next inspect the default pose, scale and orientation. Then review the supported material appearance. Finally inspect available motion. This order helps you distinguish a missing object from a camera issue, or an animation issue from a problem already visible in the base pose.

Check important areas at more than one angle. A joint can look correct in one pose while showing an unexpected deformation during motion. A textured surface can appear plausible from the front while a missing resource becomes obvious on the back. Keep a short note of the input file and the visible issue when you return to the source application.

Approval still belongs in the application that will use the asset. A game engine may add its own import rules, animation handling, collision setup and lighting. Use the browser view to reduce avoidable handoff mistakes, then confirm the behavior in that final environment.

Convert a supported FBX when you need GLB

GLB can be a useful delivery format for supported geometry, compatible materials and the animation or deformation features that survive import and export. The separate FBX to GLB converter creates a downloadable copy. Do not assume every FBX feature can pass through that conversion.

When animation or rig behavior matters, inspect the relevant clips and poses in the downloaded GLB and in the destination application. Conversion cannot recreate a feature that was dropped in the source export. It also cannot reproduce every native material or controller from the original project.

Viewer questions

Which FBX versions should I use?

Use a modern FBX 7.x export. Compatibility still depends on the file and features used. Re-export an older or unsupported file from the authoring application.

Does the FBX viewer support animation?

It can play the first supported imported animation clip. There is no clip selector. This does not guarantee every rig, constraint or exporter-specific animation feature will match the source application.

Why are my FBX materials different?

A browser importer does not reproduce every native shader graph. Check local image selection, filenames and the source export. Bake or simplify unsupported materials before export.

Can I view a private FBX without uploading it?

Selected file bytes are read locally by the browser tool. Include the local texture files needed by the model. The website itself can still make normal asset and usage-event requests.

Is FBX to GLB available for animated characters?

The converter can export supported imported animation, skins and morph data when the export path supports them. It does not guarantee every FBX rig or clip will match the source. Inspect the downloaded GLB in the destination application.

Does MeshCrate upload my selected files?

The tool reads selected model files and their selected dependencies in your browser. It does not upload those file bytes. The website still loads application code, fonts and public assets, and it can send usage events. Local file processing does not mean the whole website is offline. Remove the file or close the tab when you finish.

What is the file size limit?

The total selected model and dependency files must be 50 MB or less. A small file can still require substantial browser memory after parsing. If loading fails, close other demanding tabs or export a smaller model. Archives and remote model URLs are not accepted.

Continue with the format you need

You’re on the early-access list.

We’ll email when MeshCrate launches.

Trial incentives for early participants

You’ll receive trial incentives when we launch. We’ll share the offer and how to claim it in your launch email.

You’re signed in for product updates and trial incentives. Joining does not charge you.

Privacy notice · No payment or image upload.