How to Reduce STL File Size Without Wrecking the Model

A 400 MB STL is slow to open, slow to slice, and a pain to share. Almost always it is that big for one reason: it has far more triangles than the shape actually needs. A high-resolution 3D scan, a detailed sculpt, or a CAD export set to a very fine tolerance can all produce meshes with millions of facets where a few hundred thousand would print identically. This guide covers the three real ways to make an STL smaller — decimate the mesh, re-export it coarser from CAD, or move to a compressed format — and, just as importantly, when each one is the right call and how far you can push it before the model suffers.

Why STL Files Get So Big

An STL stores every triangle explicitly: three vertices and a normal per facet, with no compression and no reuse of shared points. File size is therefore almost linear in triangle count. Double the triangles, double the size. So the question "how do I make this smaller" is really "how do I use fewer triangles for the same shape".

Meshes end up with too many triangles for predictable reasons. Scanners output one triangle per handful of captured points, producing millions regardless of how simple the object is. Sculpting tools work at a subdivision level chosen for editing, not for export. And CAD exporters tessellate curves at whatever deflection you set — leave it very fine and a smooth fillet becomes thousands of tiny facets. Recognising which of these produced your file also tells you which fix to use.

The Three Ways to Shrink an STL

The order matters. If you have the source CAD, re-exporting is the cleanest option and costs the geometry nothing. If you only have the mesh, decimation is the tool. Switching format helps at the margin but is rarely the main lever. The rest of this guide takes them in that order.

Mesh Decimation: When the Mesh Is All You Have

Decimation reduces triangle count by collapsing edges. The standard method, quadric edge collapse, repeatedly removes the triangle pair whose disappearance changes the surface least. The effect is that flat regions — where many triangles describe what one could — lose facets first, while tightly curved areas keep theirs. This is the same algorithm behind Blender's Decimate modifier and MeshLab's quadric simplification, and it is what our simplify tool runs.

Because it is approximating, decimation moves surfaces slightly — that is exactly how it saves space. On an over-tessellated scan the movement is invisible at print scale even at an 80 or 90 percent reduction. On a model that is already lean, or whose detail is fine relative to its size, artifacts show up much sooner. There is no universal safe number; the honest method is to reduce, look, and back off if curves start to facet.

One rule keeps you safe: decimation is one-way. It cannot add back detail that a previous reduction removed, so keep your original high-resolution file if there is any chance you will need it again. Reduce a copy, never your only master.

Step by Step: Decimating an STL in the Browser

1. Upload the STL or OBJ to the simplify tool. If the file came from a scan or an unknown source, check it in the repair tool first — decimating a mesh that already has holes or non-manifold edges can make those defects worse.

2. Choose a target. "Reduce by percentage" is the natural choice when you just want it lighter; 70% off is a sensible first try for a dense mesh. Use a target triangle count instead when a slicer, engine, or marketplace imposes a hard limit you have to land under.

3. Run it and read the report. The console prints the triangle count and file size before and after, and flags any change in enclosed volume over 1%. For a functional part, that volume line is the one to watch: if a critical dimension moved, ease off the reduction.

4. Inspect the result. Look at the curved surfaces at the scale you will actually print or view. If they have gone visibly polygonal, reduce less; if they still look smooth, you may be able to reduce more. It is quick to try a couple of settings.

Re-Export From CAD: the Cleanest Fix

If you still have the source CAD or a STEP file, do not decimate at all. Re-tessellate the exact surfaces at a coarser resolution instead. Decimation approximates an approximation — it works from triangles that were themselves a rough version of the true surface — whereas re-exporting goes back to the mathematical geometry and builds a fresh, cleaner mesh at the density you ask for. The control is the deflection setting: raise it and you get fewer triangles that still follow the true curve, rather than facets chipped off an existing mesh.

Switching Format: 3MF and Compression

3MF stores the same mesh in a zipped XML container, so for identical geometry it is usually smaller than the equivalent ASCII STL, and it carries color and print settings that STL cannot. If your slicer accepts 3MF — PrusaSlicer, Bambu Studio, and Cura all do — exporting to it is a small, free saving on top of any decimation. It is not a substitute for reducing triangle count, though: a 3MF of a ten-million-triangle mesh is still a heavy file. Reduce first, then pick the lighter container.

A note on binary versus ASCII STL: binary STL is already much smaller than the text variant for the same mesh, roughly a fifth of the size, and most tools export binary by default. If your file is unusually large for its triangle count, confirm it was not saved as ASCII.

What Not to Do

Do not decimate a file you then need to edit precisely in CAD — a reduced mesh is a worse starting point for CAD conversion, not a better one. Do not reduce a mesh that is already broken; repair it first. And do not throw away your high-resolution original in the name of saving disk space, because the reduction cannot be undone. Used on the right file, decimation is nearly free; used on the wrong one, it quietly costs you detail or a clean source you cannot get back.