Reduce STL file size without losing detail
Drop the STL into the free Meshcast STL Optimizer. Welding duplicate vertices alone cuts file size by roughly 50 % with zero visual change; the simplify slider then decimates triangles, for scans and sculpts you can usually remove 60–75 % before anything is visible. A split viewer shows original vs optimized side by side. Everything runs in your browser.
What the generator does, and what it doesn't
Handled for you
- Collapses triangles where the surface is flat and keeps them where it curves, rather than decimating evenly
- Preserves the mesh boundary, so the silhouette survives the reduction
- Shows the before and after triangle count and file size, so you can stop at the right point
Still your call
- Simplifying throws detail away. It is a trade, not a free win
- It cannot repair a broken mesh on its own, and decimating a repaired mesh can break it again
If the generator refused your file, the message is explained here: why was my model rejected. Almost every rejection is the same thing, a mesh with holes, and the “Fix it for me” button in the popup resolves most of them in one click.
Why STL files get huge
An STL is just triangles, and three things inflate the count:
- 3D scans sample the surface at sensor resolution, millions of triangles, most describing flat areas that need only a handful.
- Sculpts (ZBrush, Blender, Nomad) export at sculpting resolution, which is far finer than any nozzle can print.
- Wasteful export. The STL format stores every triangle with three complete vertex copies, so each vertex is written 5–6 times. That's pure redundancy.
The pain is real: slicers crawl or crash on 100 MB meshes, most upload forms cap at 50–100 MB, and emailing a scan becomes impossible. The fix is two-part, weld the redundant vertices, then decimate triangles the print can't show anyway.
Shrink it in 5 steps
Drop the STL
Upload to the optimizer, binary or ASCII, up to ~100 MB. Nothing is sent to a server: diagnosis, repair and simplification all run locally in your browser via WebAssembly.
Read the diagnosis
In seconds you get a checklist: triangle count, duplicate vertices, non-manifold edges, holes, flipped normals, degenerate faces. The auto-repair fixes what it finds, more on that below.
Set the reduction
The Auto setting trims about 30 % of triangles, a safe default. For a dense scan, drag the simplify slider further; the decimator removes triangles where the surface is flattest first, so detail survives far longer than you'd expect.
Compare before and after
The viewer shows Original and Optimized side by side with a shared orbit, drag either one and both rotate in lockstep. Check the silhouette and the finest feature you care about. If something softened, ease the slider back.
Download, or hand off
Export the fixed STL, then upload it to whichever generator you need. Every Meshcast tool accepts a repaired STL directly.
How far can you cut?
Rule of thumb: an FDM printer with a 0.4 mm nozzle can't reproduce surface detail finer than ~0.4 mm, so triangles smaller than that are dead weight.
| Source | Typical count | Safe reduction |
|---|---|---|
| 3D scan (photogrammetry) | 1–10 M triangles | Remove 70–90 % |
| Digital sculpt | 0.5–5 M | Remove 60–75 % |
| Downloaded miniature | 0.2–1 M | Remove 30–50 % |
| CAD export (hard edges) | 10–200 k | Remove 0–20 %, already efficient |
Repair while you shrink
Big files are often broken files, and the optimizer fixes both in the same pass: it re-stitches non-manifold edges (edges shared by three or more triangles, which make slicers refuse the file or slice garbage), closes holes, flips inverted normals and deletes degenerate triangles. The result is a watertight mesh, which matters double if the STL is headed for a mold, since boolean operations require watertight input. If your print is failing in weird ways, see troubleshooting too.
Simplifying troubleshooting
The simplified model looks wrong
Cause Reduced too far, or reduced a model that was already at its limit. Hard-edged mechanical parts lose their edges long before organic shapes do.
Fix Step back up and compare Original against Fixed in the split viewer before downloading. Aim to stop at the point where the silhouette is unchanged; that is what actually matters on a print.
Rule of thumb For scans and sculpts, cutting 60–75 % of triangles is usually invisible, because an FDM nozzle cannot reproduce detail finer than about 0.4 mm anyway.
The file shrank even though I simplified nothing
Cause Not a bug. Most STL exporters write every triangle with three full vertex copies, so the same point is stored over and over.
Fix Nothing to fix. Welding those duplicates typically halves the file with zero change to a single triangle of visible geometry. It is the cheapest saving available and it happens automatically.
The model broke after simplifying
Cause Decimating a repaired mesh can re-open it. Simplification collapses edges, and an edge collapse near a patched hole can leave a non-manifold vertex behind.
Fix Simplify first, then repair, rather than the other way round. If a model must survive boolean operations afterwards, reduce less aggressively.
Does my file get uploaded anywhere?
No. It is loaded into your browser's memory, repaired and simplified via WebAssembly, and the download is generated on your device.
The model never leaves your computer, which is also why very large files are limited by your own RAM rather than by an upload cap.
Made by meshcast.app. Got stuck? Email a photo and I'll help you debug.