
Convert STL files between ASCII and binary in your browser, see triangle counts, and know what the conversion drops.
An STL that opens fine in one program can be painfully slow, oversized or flatly refused in another, and the cause is often just which of the two STL encodings it uses. STL ASCII / Binary Converter detects the encoding of the file you drop in and writes the other one, in the browser, with a small summary of what it found.
The clip below walks through a conversion.
An STL file is a list of triangles. In the ASCII form each triangle is spelled out as text: a line with the facet normal, three lines of vertex coordinates, and closing keywords. In the binary form there is an 80-byte header, a four-byte triangle count, and then exactly 50 bytes per triangle. Same geometry, very different weight.
To make that concrete, we generated a smooth ball of radius 20 with 50,880 triangles and wrote it both ways using the same routines the converter uses. The ASCII file came to 11,072,273 bytes, about 10.6 MB. The binary file was 2,544,084 bytes, about 2.4 MB, which is the 84 bytes of header plus 50,880 times 50. The binary file is a little over four times smaller, and a slicer has far less text to parse. Your own model will land on a different ratio depending on how many digits the exporter wrote per coordinate, but the direction is always the same.
Go to binary when a file is too big to email, when an upload form has a size cap, or when a slicer is sluggish with a big text file. Go to ASCII when a person or script has to read the file: diffing two versions in a text comparison, checking a coordinate by eye, or feeding a pipeline that only understands the text form. Some very old tools only accept ASCII, and some newer ones prefer binary, so the requirement comes from the destination, not from the file.
The usage is counted when you download the result, not when you drop the file, so previewing the detection and the numbers does not spend a trial use.
For the generated ball the card reports 50,880 triangles and 25,442 vertices. The vertex number is far lower than three times the triangle count (which would be 152,640) because the tool merges corners that sit at the same position before counting. A closed, well-formed surface ends up with roughly half as many unique corners as triangles, so 25,442 against 50,880 is what a watertight ball looks like. A much higher ratio means many corners are not shared, which points to open edges or loose pieces, and is a reason to look at the model in the 3D Mesh Viewer before printing.
The Triangles figure is the one to compare with your slicer. If the slicer reports a different count after import, something other than this conversion changed the model.
The converter carries the geometry only. The 80-byte header text of a binary file is not copied, and any colour bytes some programs store in the two spare bytes of each triangle are discarded. Face normals are recalculated from the triangle corners rather than copied. For printing this is normally harmless, because slicers recompute normals anyway. If you rely on vertex or face colours, convert with a method that preserves them, or keep the original file next to the converted one.
The new binary file gets its own header text, and the ASCII output starts with a solid line named after your file. Coordinates are written at single-precision float accuracy, the same as the binary format.
A binary STL whose header happens to begin with the word "solid" is a classic trap, because that is also how ASCII files begin. The converter checks the file size against the triangle count in the header as well as the opening text, so a mislabelled binary file is still recognised as binary. If the detection line surprises you, trust the size arithmetic: 84 plus 50 times the triangle count should equal the byte size of a binary file.
An empty or damaged file produces a message saying no geometry was found, or that the file could not be parsed. Multi-part models are fine because STL has no notion of parts, only triangles. And if the file is not an STL at all, say an OBJ or a 3MF, this tool will not help; that is the job of the 3D Mesh Converter, or the Universal File Converter for general formats.
Convert, then reopen the converted file in the viewer and compare the shape with the original. Check the triangle count on the card against the original run. Rename the output to include the date or revision. Keep the original file untouched until the print has finished or the client has accepted the delivery. More background on visual checks is in the article on checking a mesh before printing, and the rest of the group is in 3D tools.
The file is read and rewritten inside your browser tab, so the model itself is not uploaded. Large meshes need memory, though: a few million triangles can take noticeable time to parse and may strain a small laptop, so close other heavy tabs first.
Which 3D handoff causes you the most trouble: slicer imports, client deliveries or file size caps? Say so on the contact page, and we will cover it next.