If you came looking for 3mf to stl, this article covers a different 3D-file task: checking glTF materials, geometry, and animations in a viewer before publishing. It explains what visual inspection can reveal, rather than how to convert a file.
An asset can look convincing in a still image and fail as soon as someone rotates it or plays an animation. I use a quick viewer pass to separate material problems from mesh problems, check each clip, and decide whether the file is ready for its destination.

The short version
- Open the asset under studio lighting and rotate it before judging its PBR materials.
- Switch between textured, clay, and wireframe views to work out whether a defect comes from maps or geometry.
- Play each animation clip, scrub through it, and check the rest pose.
- Read the texture, material, mesh, triangle, and file-size stats before deciding what to compress.
Start with an inspection baseline
I open the exported file in SupaVoxel’s glTF viewer before handing it to a developer or putting it on a product page. It opens .glb and .gltf assets in the browser, shows their materials under studio lighting, and provides animation controls and mesh statistics. The file is parsed locally rather than uploaded.
- Load the export you intend to publish. A .glb contains its geometry and images in one file. If your .gltf references separate files, include its .bin buffer and images when opening it. The useful test is of the actual deliverable, not an earlier working copy.
- Orbit around the whole model. Zoom in on surfaces that carry important detail, then look from behind and underneath. A flattering front view can hide an unfinished back, misplaced surface, or unexpected gap.
- Record what you see before changing anything. Note the file size, triangle and vertex counts, mesh and material counts, texture count, and bounding-box dimensions. Those readings give you a baseline for comparing a revised export.
A viewer is a visual check, not a specification validator. It also cannot guarantee that another engine will render the asset identically. Treat a clean viewer pass as permission to test in the destination, not as a substitute for that test.
Separate material defects from mesh defects
PBR materials describe how a surface responds to light. A base-color map supplies color; metallic-roughness describes surface behavior; normal, occlusion, and emissive maps add other visible effects. Studio lighting makes it easier to notice when those parts disagree. Rotate the object rather than judging it from one camera angle: a metallic surface or rough patch may only look wrong as the lighting moves across it.

The viewer provides the lighting, display modes, and statistics used for this inspection pass.
- Inspect the textured view. Look for missing areas of color, odd reflections, inconsistent roughness, and details that appear to slide or stretch across a surface. If an image is missing from a separately packaged .gltf, the viewer can still open the model and list the image that was not included.
- Turn on clay mode. Clay hides the textures. If the apparent defect disappears, investigate the maps or material setup. If the silhouette or surface still looks wrong, the geometry deserves attention instead.
- Turn on wireframe. Check whether edges and triangles follow the shape you expected. Wireframe is particularly useful where a smooth-looking render conceals a sparse mesh or a complicated patch of topology.
The distinction saves time. Re-exporting textures will not fix a misshapen silhouette; remodeling a sound mesh will not fix an absent image. The viewer supports base-color, metallic-roughness, normal, occlusion, and emissive maps, but not KTX2/Basis textures. If the target asset depends on an unsupported texture format, test that format in the target application rather than assuming the viewer has shown the finished result.
Play the clips and inspect the rest pose
A good still frame says little about an animated asset. Motion can reveal stretching, intersections, or a pose that reads poorly from another angle. When a glTF contains skinned, keyframed, or morph-target clips, the viewer starts playback after opening the file.
- Use the clip picker to check each intended animation. Do not stop after the clip that starts automatically.
- Pause and scrub the timeline. Examine the points where the silhouette changes most. Orbit the camera while paused so you can see whether a problem is genuinely in the motion rather than hidden by the viewing angle.
- Compare with Rest pose. If the model looks sound at rest but breaks during a clip, concentrate your next inspection on that animation. If it already looks wrong at rest, fix the base asset first.
- Change playback speed when needed. The controls run from 0.25× to 2×, which helps with both close inspection and judging the overall motion.
This is a visual playback check. Once it passes, play the same file in its intended engine or web scene. The target remains the final judge of appearance and behavior.
Let the stats guide compression
File size is worth checking alongside the image and motion, especially for a model people will load on a phone. But a triangle count by itself is not a verdict on performance. Meshes and materials also matter: their counts roughly correspond to draw-call work in a real-time engine. Read the numbers together, then decide what to simplify.
- Check textures against total file size. Textures can make up most of a GLB. If the asset looks good but is too heavy for its destination, inspect texture resolution before removing geometric detail that defines the silhouette.
- Check meshes and materials. Ask whether separate pieces and distinct surfaces serve a visible purpose. A model with many materials deserves a closer look even when its triangle count seems reasonable.
- Check triangles and vertices against the intended use. Look at wireframe before reducing geometry; the goal is to preserve the shape that matters to the viewer.
- Reopen the changed export. Compare its stats with your baseline, then repeat the material and animation checks. A smaller file is not an improvement if an important map or clip no longer looks right.
For a web asset, the viewer’s guidance is to aim under a few MB and compress textures first. That is a practical starting point, not a universal pass mark. The destination’s requirements should settle the budget.
If the destination is AR
AR makes scale part of the review. glTF uses meters, so the viewer’s bounding-box dimensions can reveal an object that will be implausibly large or small when placed in a room. An AI-generated model, for example, does not inherently know the physical dimensions of the object in its source photo.
The AR 3D models guide covers setting real-world size and preparing the platform-specific files: GLB for Android Scene Viewer and USDZ for Apple’s AR Quick Look. Its Android guidance recommends staying under 100,000 triangles and 10 MB, with textures no larger than 2048 × 2048. Use those as destination checks after the visual inspection, then test on the phones people will use.

The AR workflow adds physical size and phone-specific delivery checks to the viewer pass.
If the destination is a print
A model that renders correctly is not necessarily printable. glTF can carry textures, animation, and surfaces intended only for a camera; a slicer needs geometry that forms a usable solid. Watch for floating details and single-face parts that have no wall thickness.
The glTF to STL converter turns the geometry into an STL, converts meter-based dimensions to millimeters, and orients the model Z-up on the bed. It drops materials, textures, and animation; a skinned character is written in the pose in which its file opens. Conversion does not close holes, so inspect the result and repair it if the slicer reports open geometry.

The conversion controls address print size and orientation, not the visual materials checked in the glTF viewer.
FAQ
Does a good clay-mode result mean my textures are correct?
No. Clay mode hides textures, making it useful for isolating geometry. Return to the textured view to inspect color, surface response, and missing images.
Can I use the viewer as a glTF validation report?
No. It is useful for visual inspection, playback, dimensions, and counts, but it does not provide a glTF specification validation report.
Should I reduce triangles or textures first?
Use the stats and the visible result to decide. Textures are often the bulk of a GLB, so check them first when file size is the concern. Reduce geometry only after inspecting what that geometry contributes to the shape.