The short answer
Browsers can draw one 3D format on their own: glTF/GLB, via WebGL. Everything else — FBX, OBJ, STL, and CAD like STEP — has to be converted first, then displayed. So “in-browser 3D preview” splits into two very different claims: renders glTF (easy, table stakes) versus generates a preview from your source formats (the actual feature). When a catalog shows a grey icon instead of your model, it's doing the first and skipping the second.
The buyer's test, in one line: upload your real .fbx, .obj, .glb and .stp/.step files — not the vendor's demo assets — and check that each shows a rendered, rotatable preview rather than a generic icon. If it can't, the rest of the feature list doesn't matter for a 3D library.
What “native” preview actually means
There are three levels of “preview,” and vendors use the word for all of them:
- Icon only. The file is stored; you see a grey 3D placeholder. Useless for finding the right mesh.
- Generated snapshot / turntable. The tool renders the model server-side on ingest and stores an image or short spin. Fast to browse, works for any format the tool can read.
- Live interactive viewer. The model loads in a WebGL canvas you can orbit, zoom and inspect — usually glTF/GLB, sometimes after an on-the-fly conversion.
For a shared library, the generated snapshot is what makes search usable, and the interactive viewer is the bonus that saves opening the file at all. Which 3D formats a tool can turn into either one is the question that separates a real 3D catalog from a general DAM.
Format by format: what previews, and how
| Format | Browser can draw it? | What the tool must do |
|---|---|---|
| glTF / GLB | Yes, via WebGL | Nothing — load and orbit |
| FBX | No | Convert to GLB, then render |
| OBJ | No | Convert (with .mtl/textures), then render |
| USDZ | On Apple devices (AR Quick Look) | Serve directly to iOS; convert elsewhere |
| STL | No | Tessellate is already done; render mesh |
| STEP / IGES / SolidWorks | No | Tessellate solids to a mesh, then render |
The pattern: the closer a format is to a ready-to-draw mesh, the less work a preview takes. CAD is the hardest because the tool must first turn exact solids into triangles — a capability engineering teams should test explicitly.
Which tools generate real previews
In our 3D asset management roundup, the tools that generate previews from source formats — not just render glTF — are the ones worth shortlisting. Daminion renders meshes and tessellates CAD server-side, so STEP and SolidWorks parts show up as real thumbnails beside your photos and PDFs; Perforce Helix DAM adds an interactive viewer over a Perforce depot for FBX, USD, GLB, OBJ and DAE; echo3D converts and streams optimized glTF for web and AR delivery. Generic cloud DAMs, by contrast, usually stop at “renders what a browser already can,” which is why 3D files disappear into grey icons there.
If your format won't preview: the derivative trick
Some source format will always slip through — a niche CAD kernel, an exotic exporter. The universal fallback is to batch-export a glTF/GLB or PDF snapshot alongside the original and let the catalog index that as a linked preview, so the master stays editable while the lightweight copy is what everyone browses. Done right, this is part of your versioning workflow: when the master changes, the derivative regenerates. Keeping a glTF derivative next to every master is the single highest-leverage habit for reliable previews.
FAQ
Can a browser preview FBX, glTF or OBJ files?
A browser renders glTF/GLB natively through WebGL, so those show a real, rotatable model with no plugin. FBX and OBJ are not drawn directly — the tool has to convert them (usually to GLB) first, then display the result. So the honest answer is: glTF previews everywhere; FBX and OBJ preview only if your software generates a derivative. Confirm your exact formats render before you commit.
Why does my DAM show a grey icon instead of the 3D model?
Because it is storing the file, not rendering it. Most general-purpose DAMs preview only what a browser can display on its own; hand them an FBX, OBJ or STEP file and they fall back to a generic icon. A 3D-capable catalog generates an actual preview — a snapshot or turntable — server-side. If finding the right mesh matters, that generation step is the feature to test for.
How do you preview a STEP or SolidWorks CAD file in a browser?
CAD files store precise solids, not display meshes, so they must be tessellated into a triangle mesh before a browser can show them. Engineering-oriented tools such as Daminion and Perforce Helix DAM do this conversion for you and present a rotatable preview; generic cloud DAMs typically cannot. Always test your real .stp/.step and .sldprt files, not just the vendor's demo assets.
What is the easiest way to get in-browser 3D previews across a team?
Use a catalog that generates previews on ingest, so every file gets a rendered thumbnail automatically and the whole team sees models without opening Blender or a CAD app. Standardize on a glTF/GLB derivative alongside each master file for the widest compatibility, and pick a tool that covers your specific source formats out of the box.