Skip to content

Free Online GLB Viewer

GLB is the single-file binary flavour of glTF: geometry, PBR materials, textures and animation packed into one buffer, which is why it is the default delivery format for the web and increasingly for engines. This viewer loads .glb files locally with a three.js GLTFLoader, so a 500MB asset is inspected without a byte leaving your machine.

It is also the most reliable viewer on the site, because a GLB has no side-car files to lose: materials and textures cannot go missing the way they do with OBJ or COLLADA. What it will not do is play animation clips, so treat this page as a static inspection of shape, scale and surface quality.

Select the model together with its material, texture and binary files. Files stay in this browser.

Shading

AO mode displays authored occlusion maps; white means none is supplied. This is not real-time ambient occlusion.

Model info
Vertices
—
Triangles
—
Materials
—
Dimensions
—
Free Online GLB Viewer 100% private — your file never leaves this browser tab.

How it works

Add your GLB file

Drop a .glb file onto the drop zone or click to browse. Everything the model needs is inside that one file, so materials and textures appear without selecting anything else; files up to 500MB are accepted.

Inspect materials, UVs and scale

Orbit with the left mouse button, zoom with the wheel, pan with the right button. Use the textured mode to judge PBR response, UV checker to spot stretched texture coordinates and wireframe to check the triangle budget for your target platform.

Convert for legacy or print pipelines

GLB to STL, GLB to OBJ, GLB to FBX, GLB to glTF, GLB to PLY and GLB to USDZ all run server-side with a 50MB limit. Remember that glTF is defined in metres while STL is unitless and slicers assume millimetres, so a print export usually needs a scale step.

◈

Local load, 500MB ceiling

GLTFLoader parses the binary buffer in the tab, so an unreleased game asset or a client deliverable is never uploaded. There is no account, no queue and no retention.

◈

One file, nothing to lose

GLB packs geometry, PBR materials and textures into a single buffer, so the missing-texture problem that plagues OBJ and COLLADA simply does not occur. What you inspect is what the receiver will see.

◈

Real PBR shading

Base colour, metallic-roughness, normal, occlusion and emissive maps are all applied, which makes this the right place to judge whether an asset reads correctly under lighting rather than only in the authoring viewport.

◈

Ten shading modes

UV checker for texture layout, wireframe for triangle density, normal for surface orientation, X-ray for internal structure, plus unlit, matcap, AO, depth and diffuse-only for separating material problems from lighting problems.

◈

Upfront about extensions and animation

Compression extensions such as Draco or KTX2 need extra decoder libraries, so a compressed file may fail to load until you re-export it uncompressed. Animation clips are parsed but not played here.

What Is a GLB File?

glTF was introduced by the Khronos Group in 2017 and became ISO/IEC 12113 in 2022. It is a JSON scene description with binary buffers, which is why it is compact and fast to load: the JSON gives structure, the buffers hold vertices, indices and image data with no parsing overhead.

The GLB flavour merges all of that into a single file: a 12-byte header, a JSON chunk, and one or more binary chunks holding geometry and textures. Nothing is external, so a GLB cannot arrive with missing images, and a viewer needs exactly one network request.

The specification defines metres as its unit and Y as up, supports PBR metallic-roughness materials, skeletal and morph-target animation, skinning, cameras and a node hierarchy, and grows through ratified extensions: KHR_draco_mesh_compression and KHR_texture_basisu for size, KHR_materials_* for advanced shading, KHR_lights_punctual for lights. Engines and browsers that do not recognise an extension are required to ignore it and render the fallback, which is what keeps glTF files portable.

Advantages

  • One file carries geometry, PBR materials and textures
  • Loads directly in browsers, Android and game engines
  • Compact binary buffers keep file size predictable
  • Defined in metres with a Y-up convention, so scale is unambiguous

Disadvantages

  • Not human-readable, so debugging means tooling
  • Editing usually goes through a DCC tool
  • Compression extensions need matching decoders
  • Some legacy pipelines still expect OBJ or FBX

Who Uses This GLB Viewer?

Web and 3D developers

Check an asset before wiring it into three.js, Babylon.js or model-viewer, and confirm the triangle count and texture sizes fit a mobile frame budget.

Game developers

Review a GLB from an asset store or an outsourced artist, and confirm that materials are embedded rather than referencing files that will not ship.

E-commerce and AR teams

Verify a product model reads correctly under PBR lighting before it goes live in a configurator or a Scene Viewer AR experience.

3D artists and generalists

Open a delivery quickly without launching a full DCC application, and screenshot the viewport for a review thread.

XR developers

Inspect models destined for headsets, where polycount and material complexity directly determine whether the frame rate holds.

Makers converting to print

See what a downloaded GLB actually contains, then convert it to STL and scale it to real millimetres in the STL editor.

Frequently Asked Questions

What is a GLB viewer?

It parses a GLB, the binary single-file form of glTF, and renders its scene: geometry, PBR materials, textures and node transforms. This viewer runs locally with a three.js GLTFLoader, accepts files up to 500MB, and reports vertex, face and material counts plus bounding-box dimensions.

How do I open a .glb file online?

Drag the .glb onto the drop zone or click to browse. Because everything is inside the one file there is nothing else to select, and the model is framed automatically once parsed. Nothing is uploaded and no plug-in is required.

Is my GLB uploaded to a server?

No. The binary buffer is parsed and rendered inside the browser, and files up to 500MB are supported without any upload. The only transfer happens if you explicitly choose a conversion, where the server-side pipeline takes up to 50MB.

Why does my Draco-compressed GLB fail to load?

Because Draco and meshopt are compression extensions, not core glTF: reading them requires an extra decoder library on top of the loader, and KTX2 or Basis textures need a transcoder in the same way. If a compressed file will not open, re-export it uncompressed from Blender (Export glTF 2.0 with compression off); the geometry is identical, only the file is larger.

My model is black or magenta. What does that mean?

A black or magenta surface usually means a texture could not be decoded or found, rather than a broken mesh; magenta is the classic missing-texture placeholder. Check whether the file uses KTX2 or Basis images, and verify the material by switching to diffuse-only and unlit shading, which remove lighting from the equation.

Does the viewer play glTF animations?

No. Animation clips, skinning and morph targets are parsed, but this page renders a static scene for inspection of shape, materials and scale. The bind pose is what you see, so review motion in the engine, viewer or DCC application you are actually delivering to.

What is the difference between GLB and glTF?

They describe the same scene with the same feature set; the difference is packaging. GLB is one binary file with the JSON and buffers inside, while a .gltf is JSON that points at external .bin and image files, so it behaves like a folder. Use GLB to hand a model to somebody, and glTF when you want to diff or patch the structure; glTF to GLB bundles it back into one file.

Why does my GLB print tiny when I convert it to STL?

Because glTF is defined in metres and STL is unitless while slicers assume millimetres: a character 1.8 units tall becomes 1.8mm of plastic. Convert to STL, then use the STL editor's scale operation to set the longest axis to a real millimetre value such as 100mm before printing.

Can I convert a GLB to STL, OBJ or FBX?

Yes. GLB to STL, GLB to OBJ, GLB to FBX, GLB to glTF, GLB to PLY and GLB to USDZ are all available; the geometry is preserved, materials survive in formats that support them, and animation does not survive a mesh-based export. Conversions run server-side with a 50MB limit per file.

What is the maximum GLB file size?

500MB, parsed locally. Practical performance depends on the texture payload as much as the triangle count: a 200MB GLB that is mostly 4K textures decodes more slowly than one of the same size with modest images. Downscaling textures to what the display actually needs is the single most effective optimisation.