Formats

Previewing STEP and OBJ files before you slice

By Petros, who builds Meshory · Updated Sep 18, 2026 · 7 min read

STL is not the only thing in a print library any more. Functional parts arrive as STEP, scanned and sculpted models as OBJ, and neither gets a preview from Windows Explorer or macOS Finder. The usual workaround is to open the slicer, which works but is a slow way to answer a question as small as which way up is this. This guide covers why those formats are invisible, what is actually worth checking before you slice, and how to see it without launching anything.

There is a specific frustration in downloading a folder of mechanical parts, seeing a wall of identical gray icons, and having no way to tell a bracket from a bearing housing without opening each one. It is the same problem as STL thumbnails not showing, except worse, because for STEP there is no shell extension that fixes it.

Why STEP has no preview anywhere

STL and OBJ store a mesh: an explicit list of triangles with coordinates. Anything that can read the file can draw it. STEP does not. A STEP file stores boundary representation, which describes shapes as exact mathematical surfaces rather than triangles: a cylinder is stored as a cylinder, not as an approximation of one.

That is what makes STEP the better format for functional parts, because it keeps the design's real precision instead of freezing it at whatever resolution the export used. It is also exactly why nothing shows you a picture. To draw a STEP file, a program must first tessellate it, turning those exact surfaces into triangles it can render. That needs a CAD kernel, which is a serious piece of software, and it is why no lightweight thumbnail plugin has ever solved STEP the way several have solved STL.

What you are actually checking before a slice

It helps to be precise about the question, because it is smaller than it looks. Opening a slicer answers it, but slicers are built to prepare one print rather than to browse fifty candidates. Four things decide whether a file is worth loading at all.

• Orientation. Which way up did the designer save it? A part exported lying on its side needs rotating before anything else, and you can see that in a second from a rendered preview.
• Scale and units. STEP carries units, STL famously does not. A model that arrives ten times too large or too small is usually a unit mismatch, and it is visible the moment you see the part next to a build volume.
• Part count. A STEP file can hold a whole assembly. Knowing it contains eleven components rather than one changes whether this is a five-minute print or an afternoon.
• Is this even the right file. Most of the time this is the real question, and a thumbnail answers it without opening anything.

Only the first three need a viewer. The fourth, which is the one you ask most often, needs nothing more than a picture in a grid.

Rendering the formats that have no previews

Meshory renders a thumbnail for every STL, 3MF, OBJ, FBX and STEP it indexes, including the ones inside ZIP, RAR, 7Z and TAR/TGZ archives, and opens the same five in a built-in viewer with orbit, pan and zoom. STEP and STP parts and assemblies open directly, with no conversion step first, which matters because converting a STEP file to STL to look at it is both slow and lossy: you would be discarding the precision that made it a STEP file.

For OBJ, material files are read as well, so a model that ships with an accompanying .mtl renders with its colours rather than as flat gray. Multi-plate Bambu 3MF projects open plate by plate rather than as one merged blob. The full list of what gets indexed and what renders is in the docs, and the formats section has the per-format detail.

One honest limit on STEP

Duplicate matching treats STEP differently from meshes, and it is worth knowing before you rely on it. A STEP file matches other STEP files, but it will not match an STL that was exported from the same CAD model. That is not an oversight: the STL is a tessellation, and the triangles it contains depend entirely on the export resolution someone chose. Two exports of one part at different resolutions are genuinely different meshes, so matching them to the STEP original would mean guessing.

In practice, if you keep both the STEP and an exported STL of the same part, expect them to be listed as two models. That is the accurate answer, even though it is the less impressive one. How hash and geometry detection work covers where each tier applies.

Where this fits in a mixed library

Most libraries are not one format. A functional printer ends up with STEP from GrabCAD and vendor sites, STL from Printables, 3MF from their own slicer projects, and OBJ from anything sculpted or scanned. The organizing problem is the same regardless of format, and the main library guide covers it; what changes with STEP and OBJ in the mix is that the free thumbnail fixes stop helping, because they were written for STL. The format thumbnail guide goes through which free tools cover which extensions and where each stops.