Format coverage

3MF, OBJ and FBX thumbnails: why most free tools stop at STL

By Petros, who builds Meshory · Updated Aug 27, 2026 · 7 min read

Most thumbnail fixes are built for STL, because STL is the simplest 3D format ever to succeed: a bare list of triangles that a weekend project can render. The other formats in a mixed library are harder, and the tooling shows it. 3MF previews on Windows come from a fragile built-in handler that breaks after updates. OBJ is covered by the better shell extensions but not by Windows itself. FBX and STEP get nothing at all. This guide goes format by format through why the gaps exist, which free fixes cover what, and how a library app closes all of them at once.

The symptom is a checkerboard. You install a thumbnail fix, your STL files finally show previews, and the folder still looks broken: the 3MF projects your slicer saved are gray, the OBJ scans are hit-and-miss, and every FBX from a miniature bundle is an anonymous icon. Each gray stripe has its own cause, so take them one at a time.

Why every free tool starts (and usually ends) with STL

STL is an unordered pile of triangles: no materials, no scene, no units, no compression. That makes it a poor archival format and a wonderful target for tool authors, because a renderer for it is a small, finishable project. Combine that with STL being the oldest and most numerous format in 3D printing and the result is predictable: the free tools cluster around it. The best shell extensions reach a little further (stl-thumb, the best known, renders STL, OBJ and 3MF on 64-bit Windows), but the further a format gets from a simple triangle list, the thinner the coverage, and the fixes covered in the STL thumbnails guide taper off exactly along that line.

3MF: the one format Windows half-supports

3MF is the odd case where Windows itself once did the job. Windows 10's 3D era shipped a thumbnail handler for the format (ms3dthumbnailprovider.dll, part of the same push that preinstalled 3D Viewer and Paint 3D), which is why people remember 3MF previews working out of the box. It's also why the forums fill with "my 3MF thumbnails quit showing" threads: the handler's file associations are fragile, installing or uninstalling other 3D software can strip them, and Windows 11 has deprecated the apps that era shipped. 3MF previews that arrived by default tend to leave without warning.

There's a second wrinkle: a 3MF is a ZIP-based package, and slicers like Bambu Studio, PrusaSlicer and OrcaSlicer usually embed a rendered preview image inside it when saving a project. A tool that reads the package can show that embedded image without rendering any geometry at all. Meshory does exactly this, using the slicer's own preview directly when one exists and rendering the model itself when one doesn't; the rare project file with neither is why a 3MF can show blank.

OBJ and FBX: one covered, one abandoned

OBJ sits on the lucky side of the line. It's a plain-text format from the 1990s, simple enough that the good shell extensions include it, so if you've installed stl-thumb your OBJ files probably preview fine. The caveat is that OBJ splits a model across files (geometry in the .obj, materials in a .mtl, textures in image files beside it), so a thumbnail renders the shape but a moved or half-copied model can lose its materials silently.

FBX is the abandoned one. It's Autodesk's proprietary scene format, built for animation rigs and game assets rather than printing, and parsing it properly is a serious engineering job rather than a weekend one. No mainstream free shell extension renders FBX previews, and plenty of paid tools skip it too. That matters to 3D printing people more than it used to, because miniature and terrain creators increasingly ship FBX alongside STL in their bundles, and those files stay invisible in every file manager.

STEP: the hardest format of all

STEP files aren't meshes at all. They describe exact curves and surfaces, the way CAD systems think, and turning that into triangles a renderer can draw requires a CAD kernel. That's why STEP previews essentially don't exist in the free thumbnail world: the problem is orders of magnitude harder than reading triangles. Meshory ships STEP and STP support anyway, with a rendered thumbnail and a real 3D view for each file, assemblies keeping their colors and part names. One caveat: for duplicate detection, STEP files are matched against other STEP files, not against an STL export of the same part.

One renderer for every format, everywhere you browse

The pattern across all four formats is the same: shell extensions patch one format list into one file manager on one machine, and every format past STL falls off somebody's list. A library app closes the gaps by rendering previews itself, in its own window, with its own renderer. Meshory renders STL, 3MF, OBJ, FBX and STEP on macOS, Windows and Linux alike, including models still inside ZIP, RAR and 7Z archives, which no file manager previews at all. Rendering is demand-driven through a pool of background workers that follows what's onscreen and keeps itself within strict memory bounds, so a folder of heavy scans can't overwhelm the machine. The format-by-format detail is in the support matrix.

Once every format renders, the downstream problems get easier too: a visual grid is how you spot the same model saved as both STL and 3MF, which is work for the duplicate finder's geometry matching rather than your memory. Thumbnails are step 5 of the complete guide to organizing an STL library; this page and the STL-specific fixes are the two halves of that step.