Local model inspection
Online 3D File Viewer
Open a GLB, glTF, STL, OBJ, FBX or PLY model in your browser. Select its local resource files when needed, then rotate, zoom and compare material views. Selected model bytes are processed on your device. The total file selection limit is 50 MB.
Last updated
- Model bytes stay local
- GLB · glTF · STL · OBJ · FBX · PLY
- Maximum 50 MB total
Works locally · GLB, GLTF, STL, OBJ, FBX, PLY · Maximum 50 MB combined
Select one model and its local BIN, MTL or texture files together.
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.
Choose the viewer for your 3D file
Use the file extension to identify the starting format. A viewer can only show information that the file contains and the importer supports. A gray STL and a textured GLB can represent the same shape while carrying very different scene data.
| Format | What to select | What to check |
|---|---|---|
| GLB | One self-contained .glb | Geometry, supported materials and playback of the first supported animation clip. |
| glTF | One .gltf plus its referenced local .bin and image files | Missing dependencies, material appearance and scene orientation. |
| STL | One ASCII or binary .stl | Surface shape; STL does not provide the material and texture workflow of GLB. |
| OBJ | One .obj, plus local .mtl and referenced images when used | Geometry, material assignments and missing texture files. |
| FBX | One supported .fbx, plus local images when referenced | Importer compatibility, material differences and the visible scene. |
| PLY | One .ply that contains mesh faces | Surface geometry and vertex colors when present. |
How to open a 3D file online
Select one primary model file. If it refers to separate resources, select those files in the same selection. Keep the original filenames. For a downloaded archive, extract it on your device first; the tool does not open ZIP or RAR files.
Once the model appears, use orbit and zoom to examine the silhouette, the underside and areas hidden in a single preview image. Reset the camera if you lose the model. Compare the shaded view with wireframe to inspect the distribution of triangles. A useful review takes more than one viewing angle.
- Start with the format-specific instructions if the asset has several files.
- Select the model and its required local resources; keep the total at or below 50 MB.
- Read any load error before retrying. A missing image requires a resource fix, not a different camera angle.
- Inspect the model at the distance and orientation relevant to your project.
Understand what the preview can show
Textures, vertex colors and material properties come from the asset. Changing the material view is an inspection aid; it does not add detail to the source. A normal view helps you compare surface direction. Wireframe helps expose dense regions and long thin triangles. Neither view is a repair report.
Some formats can carry cameras, lights, animation or application-specific settings. The viewer reports supported animation availability and plays the first imported clip; it does not provide a clip selector. It does not reproduce every feature from Blender, a CAD application or a game engine. Check the original file in the destination application before approving a production asset.
Local file handling and the 50 MB limit
The tool reads your selected file bytes in browser memory. It does not send those bytes to a model-processing server. The site can still load public reference models, scripts and other website resources, and can send usage events. The local-processing claim applies to the files you select.
The 50 MB limit applies to the whole selected set, including textures and binary buffers. Compressed file size is not a memory budget. Large images, many mesh parts and dense geometry can use much more memory while the browser creates the scene. For a slow model, export a smaller inspection copy and keep the full source separately.
When a 3D model will not open
First check the actual format. Renaming a file from .blend to .glb does not convert it. Re-export from the source application in a supported format. If the asset depends on local images or a binary buffer, include those files and retain the referenced names.
Remote dependencies are blocked. Use local resources that you have permission to inspect. Decoder-dependent or unsupported compressed assets need an uncompressed export. A WebGL error points to browser or graphics availability; it does not establish that the model itself is corrupt.
Prepare a complete file set before opening it
For a one-file format, preparation can be as simple as finding the GLB or STL on your device. For a resource-based format, first identify the primary model and the files it names. For example, a glTF export might contain scene.gltf, scene.bin and a color image. An OBJ export might contain chair.obj, chair.mtl and a wood image. Select the relevant set together.
Keep resource names as the exporter wrote them. A missing image cannot be fixed by choosing any image with a matching extension. If several resources share an ambiguous filename, make a clean portable export from the source application. The browser does not have general access to the folder on your device; it can use the files you explicitly select.
The selected set can contain one primary model with its supported resource files. Do not select several main models and expect a scene merge. Use separate inspections when you need to compare two assets. Preserve each source package so the review can be repeated with the same input.
Review a model for the job it must do
For a game prop, start with the silhouette at its intended viewing distance. Look at thin details, dense geometry and the appearance of repeating surfaces. Then check texture memory, draw calls and collision in the game engine. The browser preview can expose a visible issue early, but it does not reproduce an entire running scene.
For a product or scan reference, inspect the captured surface and note areas that need another source view. A good preview does not establish measurement accuracy, physical construction or permission to reuse the asset. Keep those requirements separate from the task of opening the file.
For a printable part, inspect the visible surface here and use a slicer and modeling tool for units, watertightness, wall thickness and supports. A viewer does not establish that a model will print successfully. Using the right next tool makes the inspection useful without treating a display as a manufacturing check.
Continue from inspection to a usable handoff
Use the viewer to decide what needs attention before you change the asset. For static GLB or STL geometry that exceeds a triangle budget, the separate mesh simplifier can create a reduced copy. Keep texture size and triangle count as separate checks.
Use a converter only when the receiving workflow needs another format. A conversion can discard data that the output format cannot express. MeshCrate generation remains in development; these tools inspect and convert existing files.
Viewer questions
Is this a free 3D model viewer?
Yes. You can open a supported local model and inspect it without paying for generation or joining the generation notification list.
Can I use it on a phone?
A browser with WebGL can display supported models. Available memory and graphics performance vary. A smaller file is a better starting point on a phone; large texture sets and dense geometry can exceed its practical limits.
Does opening a model change my original file?
No. Inspection reads the selected files. It does not overwrite them. Conversion and simplification are separate tools that create a downloadable result.
Can it open Blender, STEP, USD or a ZIP archive?
Those inputs are not accepted here. Export a supported GLB, glTF, STL, OBJ, FBX or PLY from a suitable source application first. Extract an archive before selecting its files.
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.