Online 3D viewer.

Maintained by Bake3D · Updated 8 October 2026

What you can check with this viewer

Most free viewers show a model and stop there. This one also shows what is inside the file, so you can judge it before you use it.

• The skeleton. Each bone is drawn as a white pointer, with an orange dot at each joint. The body turns see-through so you can follow the bones. The panel counts the bones, shows the longest chain and lists every bone name.
• Every animation. Pick a clip, then play it, pause it, step one frame at a time or drag the time bar. Slow it down to a quarter of its speed, and loop it or play it once.
• The real numbers. Triangles, vertices, meshes, materials, each texture with its size in pixels, and the size of the model in metres when the file says what its unit is.
• The look. Turn on the wireframe to see the triangles. Turn textures off to see the bare shape. Pick a dark, grey, light or clear background, then save a PNG snapshot.

How to open a 3D file

1. Drop your file on the box above, or press Choose files. Each file can be up to 64 MiB.
2. If the model comes in several files, drop them together. A .gltf file usually has a .bin file and some images. An .obj file often has an .mtl file and images. You can also drop the whole folder, or the .zip you downloaded.
3. Drag to turn the model. Scroll or pinch to zoom. Drag with the right mouse button, or with two fingers, to move it.
4. Read the panel beside the view, and use the toolbar above it to change the view.

Your file never leaves your computer. The viewer reads it inside this browser tab. There is no upload and no account.

No model at hand? Our free rigged and animated 3D models are a fox, a robot, an old man and a T. rex. Each one opens in this viewer with one click from that page, with its bones and every clip.

Which formats it opens

• GLB and glTF. The open standard from the Khronos Group. They can hold the mesh, materials, textures, bones, skin and animations. They are always in metres, with Y up. Use the glTF viewer page for files that come in several parts, and the GLB viewer page for single files.
• FBX. Autodesk’s format, common in Unity, Unreal Engine and Maya. It can hold meshes, bones and animation takes, and it says what its unit is. See the FBX viewer page.
• OBJ. A simple, older format for shapes, with materials in a separate .mtl file. It has no bones, no animation and no unit. See the OBJ viewer page.
• STL. Triangles for 3D printing, with no color and no unit. Most STL files are in millimetres with Z up. To look for holes before you print, use the STL checker.
• PLY. Meshes or point clouds, often from 3D scanners, sometimes with a color on each point.
• 3MF. The newer 3D printing format. The viewer reads its shapes, places them where the file says and converts its unit to metres. It does not show 3MF colors.

Read the numbers

Triangles are the flat faces the model is made of. More triangles mean finer detail and more work for the graphics card. Our guide on reducing the polygon count shows how to bring the number down.

Vertices are the corners of those triangles. The count depends on how the file is stored. A glTF shares corners between triangles. The three.js loaders for FBX and OBJ give every triangle its own three corners. So our sample fox shows 41,822 vertices as a GLB and 180,000 as an FBX, with the same 60,000 triangles.

Size is the box around the model at rest: width, height and depth. glTF is always in metres. FBX stores its unit, and the viewer reads it. STL, OBJ and PLY do not store a unit, so compare the size with what you expect.

Textures lists each image with its size in pixels. The memory figure is an estimate of what the graphics card needs for the images without compression: 4 bytes per pixel, plus one third for the smaller copies it keeps (mipmaps). One 2048 × 2048 image needs about 21 MB.

Bones are the joints a model bends at. The deepest chain counts the bones from the root to the farthest tip. Long chains are normal for tails, necks and tentacles.

When a file does not open

• “This glTF needs scene.bin.” The .bin file is missing. Drop it together with the .gltf, or drop the whole folder.
• Missing textures. The notes in the panel name each missing image. Drop the images with the model.
• A Blender file. The viewer cannot read .blend files. In Blender, choose File, Export, glTF 2.0, and open the .glb here.
• A Collada (.dae) file. The viewer does not read Collada. Our free DAE to FBX converter turns it into an FBX, with its bones and animation, that opens here.
• The model lies on its side. STL, OBJ, PLY and FBX files do not always say which way is up. Switch the Up axis in the panel.
• “The file looks cut short or damaged.” The download probably stopped early. Download the file again.

Need a model that moves?

This viewer shows models you already have. If you need a character that moves and you do not have one, Bake3D can turn one picture into a rigged, animated 3D model. You can describe a motion in plain words and download GLB or FBX. Start with the free demo to see the rig and the motion first.

Common questions

Is my file uploaded?

No. The viewer reads your file inside this browser tab and never sends it anywhere. The page only downloads the viewer itself and, for Draco compressed glTF files, a small decoder from bake3d.ai.

Can it show the skeleton of any model?

It shows every bone stored in the file. That means the joints of each skinned mesh, and also bones with no mesh at all, like an FBX that only holds a skeleton and its motion. Control rigs and constraints from Blender or Maya are usually not saved in GLB or FBX, so only the bones show.

Why does the model look different in Blender or Unity?

Every app lights and shades models in its own way. This viewer uses three.js with soft studio light. Material features that three.js does not support fall back to the base material. Always check the final look in the app you will use.

Does it open compressed glTF files?

Yes, for Draco compression. We opened a Draco compressed knot of 7,680 triangles that takes 23 KB. Files with meshopt compression or KTX2 textures go through the three.js decoders too, but we have not tested them with real files yet.

What did we test?

We opened these files in Chrome, at desktop and phone sizes. Our sample fox as a GLB: 60,000 triangles, 29 bones, three animations and one 2048 × 2048 texture. The same fox as a .gltf with a .bin and a JPEG, and as a .zip of those files. The fox as an FBX made by our GLB to FBX converter, and as an OBJ with an MTL and its texture. A Draco knot. A 40 × 30 × 20 mm wedge as binary STL, text STL, 3MF and text FBX. A colored PLY cube and a PLY point cloud of 20,000 points. A text FBX with five bones and one take but no mesh. We also opened a glTF without its .bin, a GLB cut to a third of its length and a .blend file, and each one showed a clear message. Automated tests cover the format detection, the file matching, the counts and the sample files. We have not tested Safari or Firefox yet.