Skip to content

ASCII vs Binary STL: Why Is My STL File So Big?

Enes Vural
Watch it in 30 seconds25 MB... for a DONUT?!Watch on YouTube

An STL file comes in two encodings with the same triangles inside: ASCII (readable text) and binary (raw numbers). ASCII is about 5× larger: a 100,000-triangle model is 5.0 MB as binary and 25.2 MB as ASCII, too big for a 25 MB email attachment. Open the file in a text editor to tell which one you have, and re-export it as binary from Blender or MeshLab to shrink it without changing the model.

You try to email a print-ready model and Gmail refuses: the file is over 25 MB. It is a donut. A plain, smooth torus with nothing special about it. The model is not the problem. The way the file was written is.

I build Extrude, a 3D file viewer for phones, and our numbers show how common this is. Of the models people opened in it in September and October 2026, 27.2% on Android and 18.4% on iPhone were ASCII STL. That is more than one in four files on Android carrying about five times the data the same model needs as binary.

What is the difference between ASCII and binary STL?

Both describe a surface as a list of triangles, each with a normal and three corners. The difference is how the numbers are written.

  • ASCII STL spells every number out as text, with keywords around it: facet normal, outer loop, vertex, endloop, endfacet. One triangle takes seven lines.
  • Binary STL stores each triangle as exactly 50 bytes: twelve 4-byte numbers and a 2-byte spare field, after an 80-byte header and a 4-byte triangle count. The Library of Congress format description covers both layouts.

So a binary STL’s size is fixed by its triangle count: 84 bytes + 50 bytes per triangle. An ASCII file has no fixed size; it depends on how many digits the exporter writes.

How much bigger is an ASCII STL?

To get a real number, I generated a 100,000-triangle torus and saved it both ways, with the ASCII version in the common scientific-notation style.

One 100,000-triangle model, four filesBinary STL5.0 MBASCII STL25.2 MB25 MB email limitBinary, zipped1.1 MBASCII, zipped2.1 MBSame triangles in every file. Binary size = 84 bytes + 50 bytes per triangle.
ASCII came out 5.05 times larger. Zipping narrows the gap but does not close it.
File Size
Binary STL 5.0 MB
ASCII STL 25.2 MB
Binary STL, zipped 1.1 MB
ASCII STL, zipped 2.1 MB

The ASCII file crosses Gmail’s 25 MB attachment limit, so Gmail would send it as a Drive link instead. The binary file fits five times over.

How do you tell which one you have?

  1. Open it in a text editor. If you see readable lines such as facet normal 0.0 0.0 1.0 and vertex 12.5 3.0 0.0, it is ASCII. If you see unreadable characters, it is binary.
  2. Check the size against the triangle count. If your slicer or viewer shows the triangle count, multiply it by 50 and add 84. If the file is that size to the byte, it is binary.
  3. Do not trust the first word. ASCII files must start with solid, but some exporters also write solid at the start of a binary file’s free-text header, so a file that begins with solid can still be binary.

Myth: “ASCII STL is more precise”

It usually is not. Binary STL stores each coordinate as a 32-bit floating-point number, which is roughly seven significant digits: finer than a micrometre on a 100 mm part, and far finer than any FDM or resin printer can reproduce. Most exporters write ASCII with a similar number of digits, so you get the same geometry in a much bigger file. The only real advantage of ASCII is that a person can read it, which is handy for debugging an exporter and little else.

How do you convert ASCII STL to binary?

  • Blender: File, Import, STL. Then File, Export, STL, and leave ASCII unticked.
  • MeshLab: File, Import Mesh. Then File, Export Mesh As, choose STL, and keep Binary encoding ticked.
  • From your CAD tool: most exporters have an ASCII or binary option; pick binary once and every future file will be small.

The triangles do not change, so the model prints exactly the same. If you share the file by chat or email, zip it as well, or send a 3MF, which is compressed by design.

Can you open ASCII STL on a phone?

Yes. Extrude (listed as STL Viewer on the App Store and Google Play) opens both kinds offline and never uploads the file. A big ASCII file takes a few seconds longer to load, especially on an older phone, but it shows the same model. Here is how to open STL files on Android and on iPhone, or drop the file into the browser STL viewer on a computer.

Questions

What is the difference between ASCII and binary STL?

They hold the same triangles. ASCII STL writes every number as readable text, binary STL stores it as raw 4-byte values. The shape is identical, but the ASCII file is several times larger.

How much bigger is an ASCII STL?

About five times. A 100,000-triangle model we generated was 5.0 MB as binary STL and 25.2 MB as ASCII STL. Binary size is always 84 bytes plus 50 bytes per triangle.

How do I know if my STL is ASCII or binary?

Open it in a text editor. An ASCII STL is readable and full of lines that start with facet normal and vertex. A binary STL looks like garbage characters. Do not rely on the first word alone: some binary files also begin with solid.

How do I convert ASCII STL to binary?

Open it in Blender or MeshLab and export it again as STL with ASCII turned off (Blender) or binary encoding turned on (MeshLab). The model does not change, only the file gets smaller.

Do slicers and phone viewers open ASCII STL?

Yes. Every common slicer reads both kinds, and so does Extrude (listed as STL Viewer on the App Store and Google Play). ASCII files just take longer to download and load.

Open 3D files on your phone

Extrude is free and keeps files on your device. Listed as “STL Viewer”.

Download on the App StoreGet it on Google Play
Enes Vural

Written by

Enes Vural

Founder and developer

Enes builds Extrude, the phone app listed as STL Viewer on the App Store and Google Play. He writes the file parsers and the native 3D viewers (Filament on Android, SceneKit on iOS), and ships features people ask for by email. He writes about 3D file formats, viewing and checking models on a phone, and preparing parts for printing.