How to Reduce STL File Size Without Losing Visible Detail
A 120 MB STL is slow to download, slow to open and can freeze a browser tab or a slicer on a modest computer. Buyers on mobile data notice big downloads, and many marketplaces limit upload sizes. The good news is that most oversized STL files are far bigger than a printer can use. This guide explains where the bytes go, shows measured sizes for the same mesh in seven formats, and walks through the order of fixes that gives the largest saving for the least loss of detail.
The short answer
- Export binary STL, never ASCII. In our test the ASCII version of the same mesh was 4.6 times larger.
- Remove geometry nobody needs (hidden inner faces, duplicates, stray islands).
- Decimate in steps and compare against the original. Hand-sized figures usually look the same at 100,000 to 400,000 triangles.
- Offer 3MF next to the STL. In our test it was 23% of the binary STL size for a noisy, scan-like mesh and 16% for a smooth one.
- Zip the download. A zipped binary STL was 28% (smooth surface) to 42% (noisy surface) of the original size.
Why the size follows the triangle count
A binary STL stores each triangle as a normal vector (12 bytes), three corner points (36 bytes) and a 2-byte attribute field: exactly 50 bytes per triangle, plus an 84-byte header. Nothing else is stored, so a model with 1,000,000 triangles is always 50,000,084 bytes, whatever it looks like. STL also repeats every corner point for every triangle that touches it. On a closed surface each corner is shared by about six triangles, so formats that store points once (OBJ, PLY, 3MF) need far less space.
What we measured
We generated two test shapes (a smooth sphere and a noisy, scan-like sphere), each at about 50,000 and 200,000 triangles, and wrote every mesh in each format. Sizes are real file sizes in megabytes (1 MB = 1,000,000 bytes).
Smooth surface (typical CAD or clean sculpt)
| Triangles | Binary STL | ASCII STL | OBJ | PLY (binary) | 3MF | Binary STL zipped |
|---|---|---|---|---|---|---|
| 50,244 | 2.51 MB | 11.66 MB | 1.75 MB | 0.96 MB | 0.42 MB | 0.73 MB |
| 201,608 | 10.08 MB | 46.77 MB | 7.20 MB | 3.83 MB | 1.61 MB | 2.85 MB |
Noisy surface (typical 3D scan or heavy sculpt)
| Triangles | Binary STL | ASCII STL | OBJ | PLY (binary) | 3MF | Binary STL zipped |
|---|---|---|---|---|---|---|
| 50,244 | 2.51 MB | 11.66 MB | 1.75 MB | 0.96 MB | 0.59 MB | 1.06 MB |
| 201,608 | 10.08 MB | 46.77 MB | 7.20 MB | 3.83 MB | 2.31 MB | 4.28 MB |
Chart: the same 201,608-triangle noisy mesh in six formats.
What the numbers tell us
- ASCII STL is the worst choice. It needs about 232 bytes per triangle against 50 for binary. A scan that is 10 MB in binary becomes about 47 MB in ASCII.
- Smooth surfaces compress much better than noisy ones. The zipped smooth sphere shrank to 28% of its binary size, the noisy one only to 42%. Noise is incompressible, which is also a hint that a scan carries detail a printer cannot reproduce.
- 3MF was the smallest option in every test because it shares corner points and compresses the XML.
- PLY and OBJ both share corner points, so they sit in between. Binary PLY was 38% of binary STL; text OBJ was 71%.
Estimate your own file size
Enter a triangle count to estimate the size of the same mesh in each format. The estimate uses the bytes-per-triangle ratios measured above and is accurate to roughly ±15% for closed, single-surface meshes. Real models with colours, textures or many separate parts will differ.
How much detail does a printer actually use?
A typical FDM printer with a 0.4 mm nozzle and 0.2 mm layers cannot make features much smaller than 0.2 to 0.4 mm. Resin printers reach finer detail, but even they have limits of a few hundredths of a millimetre. If your triangles are smaller than that, they add file size without adding anything the printer can use. As an example, covering the surface of a 60 mm wide sphere-like figure with 0.1 mm triangles takes about 2.6 million triangles, yet the printer cannot reproduce structure at that scale.
Fix order: biggest saving first
1. Export in binary
If your tool offers a choice, pick binary STL. This costs nothing and is the first thing to check. If you received an ASCII file, open it once in any mesh tool and save it as binary.
2. Remove what is not needed
- Hidden internal geometry: faces inside the model that no one will see or print.
- Duplicate objects: a mesh accidentally exported twice. Check the triangle count against what you expect.
- Construction helpers and stray fragments left from booleans or sculpting.
- Tiny disconnected islands from scanning. Many tools can remove components below a size threshold.
3. Decimate in steps
Decimation lowers the triangle count while keeping the overall shape. Blender has the Decimate modifier, MeshLab has quadric edge collapse simplification, and most slicers and sculpting programs offer a similar function. Work gradually:
- Duplicate your model so you keep the original.
- Reduce the triangle count to about half and compare in a viewer.
- Inspect sharp edges, text, eyes and thin parts first; they show damage earliest.
- Continue until detail starts to degrade, then go back one step.
Flat areas can lose many triangles without any visible change; curved and detailed areas need more. If your tool has options to preserve boundaries or planar regions, switch them on.
4. Offer 3MF as well
3MF shares corner points and zips its XML, so it was the smallest format in every test above. It also stores units and colours, which STL cannot. Modern slicers read it. Keep an STL in the download for compatibility. See STL vs 3MF vs OBJ vs PLY for when each format makes sense.
5. Zip the files
Zipping lets you bundle several parts and a readme and avoids browsers opening a raw STL instead of downloading it. As the tables show, the saving depends on the surface: smooth meshes shrink a lot, noisy ones barely.
Triangle budgets to start from
| Object | Good starting range | Binary STL size |
|---|---|---|
| Simple mechanical part | 5,000 to 50,000 triangles | 0.25 to 2.5 MB |
| Detailed figure, hand-sized | 100,000 to 400,000 | 5 to 20 MB |
| Large sculpt or scan | 400,000 to 1,000,000 | 20 to 50 MB |
These are starting points, not rules. Judge by looking at the result and, when the print matters, by printing a small test of the most detailed region.
How to check the result
- Compare the original and reduced meshes side by side from several angles.
- Compare their volumes. A change of more than one or two percent means you removed too much or damaged thin walls.
- Zoom into faces, text and thin connections.
- Run the reduced file through a pre-print check: decimating a file that still has holes can make the holes worse.
Common mistakes
- Decimating the only copy of the model.
- Reducing a model that is already low-poly, which creates visible facets.
- Decimating before fixing holes and flipped faces.
- Sending buyers an ASCII STL saved from a sculpting tool.
- Judging quality on screen only: shading hides faceting that appears on the print.
Frequently asked questions
Why is my STL so much bigger than the same model in OBJ?
Because STL repeats every corner point for each triangle. On a closed surface each point is shared by about six triangles, so OBJ, PLY and 3MF store roughly one sixth of the point data.
Will zipping damage my STL?
No. Zip compression is lossless; the file is identical after unzipping.
Is there a size limit for marketplaces?
Limits differ between platforms and change over time, so check the current upload rules of the platform you use. Keeping each file well under 100 MB is a sensible habit in any case.
How many triangles does my model have?
For a binary STL: (file size in bytes minus 84) divided by 50. The STLtoMP4 viewer also shows the triangle count when you open a model.
How we measured
The two test meshes are UV spheres of 20 mm radius with 158 x 160 segments (50,244 triangles) and 316 x 320 segments (201,608 triangles). The "noisy" variants add Gaussian noise with a standard deviation of 0.05 mm to every vertex radius. Each mesh was written as binary STL, ASCII STL (%e number formatting, as most exporters use), OBJ (six decimals), binary PLY (float32 positions, int32 indices) and 3MF (XML, DEFLATE). Zipped sizes use DEFLATE level 6. A sphere is not a realistic shape, but every closed triangle mesh has about two triangles per vertex, so the structure of these formats' sizes carries over; compression ratios will vary with real data. The raw numbers are available as a CSV file.