Project
Skip to content

Original research · open data (CC0)

3D File Size Benchmark

Thirteen meshes, from a 12-triangle cube to a 65,024-triangle sphere, written to seven formats, measured to the byte and read back to verify. Download the data and reproduce it.

By the 3DA.XYZ editorsUpdated 2026-11-05Original renders & data

Key findings

  • Binary STL size is exactly 84 + 50 × triangles bytes — confirmed for all 13 meshes. At 65,024 triangles that is 3,251,284 bytes.
  • ASCII STL was 4.1× larger than binary STL for identical geometry (204 vs 50 bytes per triangle).
  • GLB was 4.2× smaller than binary STL (12.0 bytes per triangle), because it stores each shared vertex once.
  • 3MF with standard ZIP compression was the smallest: 548,981 bytes, 5.9× smaller than binary STL. Uncompressed, the same 3MF was the second-largest file.
  • Every file read back identically: same triangle count, closed surface and volume, in all 91 format/mesh combinations.
Try itSee the same effect on your own model: open it in the Studio and export it as STL, GLB and 3MF. Open the Studio →

How size scales

102050100200121001,00010,00065,024STL bin 50.0STL ASCII 204.1OBJ 34.0PLY 19.0GLB 12.03MF stored 69.03MF deflate 8.4Bytes per triangle (log scale)Triangles (log scale)
Bytes per triangle for each format as the mesh grows from 12 to 65,024 triangles. Labels show the value at 65,024 triangles. Binary STL is a flat 50 bytes per triangle; indexed formats fall toward their per-vertex cost.

Full results (bytes)

MeshTrianglesVerticesSTL binSTL ASCIIOBJPLYGLB3MF stored3MF deflateVerified
20 mm cube1286841,5552834781,0282,0081,106✓
20 mm UV sphere, 6 segments24141,2843,7055517121,1842,6911,220✓
20 mm UV sphere, 8 segments48262,4848,0811,0531,1681,4724,0331,411✓
20 mm UV sphere, 12 segments120626,08420,2152,5232,5382,3408,0231,949✓
20 mm UV sphere, 16 segments22411411,28442,6835,5624,5153,59214,6972,769✓
20 mm UV sphere, 24 segments52826626,48499,33113,46510,2917,24033,2395,306✓
20 mm UV sphere, 32 segments96048248,084190,67526,56918,49912,42861,4638,687✓
20 mm UV sphere, 48 segments2,2081,106110,484437,88362,15542,21327,408140,72318,835✓
20 mm UV sphere, 64 segments3,9681,986198,484801,287119,21175,65348,528259,37934,186✓
20 mm UV sphere, 96 segments9,0244,514451,2841,821,927279,291171,717109,200596,41974,063✓
20 mm UV sphere, 128 segments16,1288,066806,4843,281,101508,222306,695194,4521,073,991132,457✓
20 mm UV sphere, 192 segments36,48018,2421,824,0847,418,3971,205,840693,384438,6802,483,923290,824✓
20 mm UV sphere, 256 segments65,02432,5143,251,28413,272,8052,209,7281,235,720781,2084,486,851548,981✓

Method

Each mesh is generated in code (watertight, millimetres), exact-welded, then written by the 3DA.XYZ mesh engine to each format. Sizes are exact byte counts of the written files. gzipBytes = gzip level 6 of that file (a proxy for HTTP compression). 3mf = stored (uncompressed) ZIP as written by the engine; 3mf-deflate = the same three parts re-packed with raw DEFLATE level 6, as typical 3MF exporters do. Every file is parsed back and checked for identical triangle count, closure and volume.

  • Sizes depend on the writer: number formatting (6 decimals here), headers, indexing and metadata. Other applications will produce different byte counts for the same geometry.
  • OBJ and PLY here store indexed vertices; STL stores three corners per triangle.
  • GLB here stores positions + 16/32-bit indices and one material; no normals, UVs or textures.
  • The 3DA.XYZ Studio and converter download the deflate variant of 3MF when the browser supports CompressionStream.

Environment: Node.js v22.23.4, engine SHA-256 5097bda723dbb76c…, script SHA-256 3b52af7ce75d763a…. Re-run with node benchmark.js alongside ax-mesh.js. Data licence: CC0.

Cite this data

3DA.XYZ (2026). 3D file format size benchmark, v1. https://3da.xyz/lab/format-benchmark/