STL Viewer: Meshy 3D Agent for Resin Minis: A 388 MB STL for One 32 mm Dwarf

STL Viewer: Meshy 3D Agent for Resin Minis: A 388 MB STL for One 32 mm Dwarf

STL Viewer, Meshy 3D Agent, Snapshapy

The print file Meshy 3D Agent gave me for a 32 mm resin dwarf is a 387.7 MB STL with 7,754,470 faces, delivered as a 194.2 MB zip. Snapshapy's 3D Agent answered the same job with a 3.0 MB STL of 59,928 faces, 129 times smaller. On a 12 Mbps line that is ≈129.5 s of waiting against ≈2.0 s. Both files are valid prints: watertight, one body, 0 non-manifold edges, 32.00 mm tall. Only one of them came out at 32 mm without me typing the height myself.

I ran Meshy 3D Agent at meshy.ai on Meshy Pro ($20 a month for 1,000 credits) and Snapshapy's 3D Agent at snapshapy.com on Snapshapy Pro, both on my own paid accounts. This review is about the thing a resin printer actually receives: the downloaded file, opened in my own mesh tool and measured.

My verdict in 60 seconds — Meshy 3D Agent 61/100, Snapshapy 88/100

Meshy 3D Agent produces a correct 32 mm dwarf, but it hands it over as a 387.7 MB file sized at 12.0 cm until you change it, while Snapshapy's file is 3.0 MB and already 32 mm.

  • STL file size — Meshy 2/10 · Snapshapy 9/10 — 387.7 MB vs 3.0 MB, 129× heavier
  • Download on 12 Mbps — Meshy 3/10 · Snapshapy 9/10 — ≈129.5 s for the 194.2 MB zip vs ≈2.0 s
  • Size out of the box — Meshy 4/10 · Snapshapy 10/10 — dialog at 12.0 cm with Resize off vs a file already 32.00 mm tall
  • Print-ready file — Meshy 9/10 · Snapshapy 9/10 — both watertight, 1 body, 0 non-manifold edges, 32.00 mm tall
  • Print detail / mesh density — Meshy 9/10 · Snapshapy 6/10 — 7,754,470 vs 59,928 faces, 0.035 vs 0.309 mm mean edge
  • Print-prep cost — Meshy 4/10 · Snapshapy 10/10 — 10 credits and ≈363 s vs free in 6.6 s
  • Extra clicks for the run — Meshy 4/10 · Snapshapy 9/10 — 11 beyond the 3 messages vs 2 (Export → STL)
  • Credits for one dwarf — Meshy 3/10 · Snapshapy 9/10 — 76 vs 11, $1.52 vs $0.52, 6.9×

The concrete problems:

  • Meshy's print file kept the 3D model's full density: 7,754,488 triangles in the GLB, 7,754,470 faces in the STL.
  • The resulting STL is 1.5× heavier than the 262.4 MB textured GLB it came from.
  • Meshy's download dialog opened with Resize OFF and Height 12.0 cm, 3.75× the size I asked for in message 3.
  • Getting the file took 4 dialog clicks, a ≈129.5 s zip download, and an unzip.

For a 32 mm resin miniature, I would use Snapshapy.

Three messages, one dwarf, two test days

I typed the same three messages into both agents, word for word:

  1. "Design 4 concepts for a 32 mm tabletop miniature: a dwarf warrior with an axe and a round shield."
  2. "Use option 1 and make it a 3D model."
  3. "Prepare it for resin printing at 32 mm tall."

Whenever an agent showed a choice card, I picked the first option. I ran the Snapshapy side the next day, after an update; the Meshy numbers are from the first day. Meshy ran on 2026-11-03, Snapshapy on 2026-11-04 in a new conversation.

Meshy 3D Agent home with the Top Up button.

  • Messages typed — Meshy 3 · Snapshapy 3
  • Credits spent — Meshy 76 · Snapshapy 11 · 6.9×
  • Job time, whole run — Meshy ≈1,189 s · Snapshapy ≈430 s

Message 3 is the one this article follows, because it decides what lands on the printer.

Inside the 194.2 MB zip: one dwarf and 7,754,470 faces

Meshy's STL arrived zipped at 194.2 MB. Unzipped it is 387.7 MB for one figure, a single body that stands 32.00 mm tall. The zip roughly halves the transfer, but the slicer still has to load all 387.7 MB.

My render of Meshy's repaired print mesh (textures removed).

  • STL on disk — Meshy 387.7 MB · Snapshapy 3.0 MB · 129×
  • Faces — Meshy 7,754,470 · Snapshapy 59,928 · 129×
  • Transfer size — Meshy 194.2 MB zip · Snapshapy 3.0 MB STL · 64.7×

Both STLs spend the same 50 bytes per triangle, so the size gap is the face count and nothing else. Meshy kept nearly every face its 3D step made. My wireframe render of a close-up shows what that means at 32 mm: the lines sit so close together that the mesh prints to the screen as a solid black shape.

Meshy STL wireframe: 7,754,470 faces, so dense it renders solid black.

At 32.00 mm tall, that is about 242,000 faces for every millimeter of height, all of which the slicer has to read before it can show me the Meshy dwarf.

Snapshapy's 3.0 MB STL: triangles you can count

Snapshapy's file is a plain STL, not zipped, at 3.0 MB. It also measures 32.00 mm tall and is one watertight body.

My render of Snapshapy's 32 mm STL: watertight, one body, 3.0 MB.

  • Faces — Meshy 7,754,470 · Snapshapy 59,928
  • Mean triangle edge at 32 mm — Meshy 0.035 mm · Snapshapy 0.309 mm · 8.9× coarser on Snapshapy
  • Unzip step — Meshy yes · Snapshapy none

The wireframe makes the trade visible. On the same kind of close-up, Snapshapy's triangles are individually visible, which is the 8.9× coarser edge length in a picture.

Snapshapy STL wireframe: 59,928 faces, individual triangles visible.

Ten of these files add up to 30 MB, 7.7% of one Meshy STL.

Where the 7.75 million faces came from: a 262.4 MB GLB

The weight starts at message 2. Meshy's approval card read Image to 3D, Meshy 7.1, Standard, texture 4096, Est. Cost 30. The result, ≈403 s later, was one figure with 7,754,488 triangles in a 262.4 MB GLB.

My offline render of Meshy's 3D model (7,754,488 triangles, 262.4 MB).

Message 3 sent that model through Meshy's repair for 10 credits and ≈363 s. The STL I downloaded afterwards had 7,754,470 faces, against 7,754,488 triangles in the GLB. The textures were removed, yet the STL ended up 387.7 MB, 1.5× the 262.4 MB GLB that still carried a 4096 texture.

Snapshapy's model from message 2 was 1,500,000 triangles in a 106.6 MB GLB, finished in 331 s for 3 credits. Its print step ran as a free 6.6 s job and reduced the mesh before writing the file.

Snapshapy's print card: "60k triangles · from 1.5M · textures dropped · watertight".

  • Model GLB — Meshy 262.4 MB, 7,754,488 triangles · Snapshapy 106.6 MB, 1,500,000 triangles · 2.5×
  • Faces in the print file — Meshy 7,754,470 · Snapshapy 59,928 of 1,500,000, 25× fewer
  • STL vs its own GLB — Meshy 1.5× heavier · Snapshapy 35.5× lighter
  • Print step — Meshy 10 credits ($0.20), ≈363 s · Snapshapy 0 credits, 6.6 s

Snapshapy's print reply said it would report "the real triangle count and whether the mesh is watertight" afterwards, and no follow-up message came; the card itself read "watertight".

The Height field that still said 12.0 cm

Meshy's answer to message 3 started well: tilt 30°–45°, supports on the beard tips, axe edge and shield rim, and print solid, which is specific resin advice. Then came a "Repair Geometry for Resin" choice card (select, then Submit) and a 10-credit approval card.

After the repair, I opened the download dialog. Resize was OFF and Height read 12.0 cm, though my message had asked for 32 mm.

Meshy's download dialog: it still says 12.0 cm.

I switched Resize on, typed 3.2 cm, chose STL and clicked Download: 4 clicks and a typed number. The dialog's starting value, 12.0 cm, is 3.75× the height in my prompt.

The same dialog after I typed 3.2 cm and picked STL.

Snapshapy's reply to the same message put the size inside the job: "The print prep is running (free, ~30 s): textures stripped, mesh reduced for print and sized so the STL/3MF comes out exactly 32 mm tall with no slicer scaling." There was no size dialog. I clicked Export, then STL.

Snapshapy's reply to the print message: free, "exactly 32 mm tall with no slicer scaling".

  • Height in the file by default — Meshy dialog at 12.0 cm, Resize off · Snapshapy 32.00 mm
  • Clicks to download — Meshy 4 in the dialog · Snapshapy 2 (Export → STL)
  • Size typed by me — Meshy 3.2 cm · Snapshapy nothing

My mesh tool's verdict: both dwarfs will print

I loaded both STLs into the same mesh tool. Said plainly: both are valid resin prints. Neither needs a repair before slicing.

Meshy reports the repaired mesh as fully watertight.

  • Watertight — Meshy yes · Snapshapy yes
  • Bodies — Meshy 1 · Snapshapy 1
  • Non-manifold edges — Meshy 0 · Snapshapy 0
  • Bounding box — Meshy 32.24 × 22.20 × 32.00 mm · Snapshapy 27.75 × 19.57 × 32.00 mm
  • Volume — Meshy 4.58 cm³ · Snapshapy 2.47 cm³
  • Overhang > 45° — Meshy 629.7 mm² (15.5 % of surface) · Snapshapy 471.0 mm² (19.1 % of surface)

Meshy's own message, "fully watertight with 0 holes or non-manifold edges", matched what my tool found. Snapshapy's STL also reported 0 boundary edges.

Snapshapy's 32 mm STL, front view.

Meshy's print mesh is far denser, 7,754,470 faces with a 0.035 mm mean edge against Snapshapy's 59,928 faces at 0.309 mm, so Meshy's file keeps more of the fine chainmail and beard texture on a 32 mm figure. The two figures are different sculpts from different concepts, which is why the volumes differ by 1.85×.

≈129.5 seconds per dwarf before the slicer opens

On a 12 Mbps connection, the Meshy zip takes ≈129.5 s to arrive. Snapshapy's STL takes ≈2.0 s, about 65× less waiting. Then Meshy's archive still needs unzipping to its full 387.7 MB.

Meshy converted its STL in ≈10 s against Snapshapy's 40.1 s browser export, and its concept retry finished in ≈28 s against Snapshapy's 52.7 s.

Snapshapy chat while exporting the STL from the card (40.1 s).

  • Download on 12 Mbps — Meshy ≈129.5 s (zip) · Snapshapy ≈2.0 s · ≈65×
  • Archive step — Meshy unzip 194.2 MB → 387.7 MB · Snapshapy none

The gap repeats every time the file moves to another computer or to the printer's drive: 194.2 MB zipped or 387.7 MB raw for each Meshy dwarf.

A ten-dwarf warband: 3,877 MB against 30 MB

A tabletop army is rarely one figure. Here is the same file math for ten dwarfs, each made with the same three messages.

Snapshapy's 32 mm STL, back view.

  • STL storage — Meshy 3,877 MB · Snapshapy 30 MB · 129×
  • Zips to download — Meshy 1,942 MB · Snapshapy no zips, 30 MB total
  • Download on 12 Mbps — Meshy ≈1,295 s, about 21.6 minutes · Snapshapy ≈20 s
  • Heights typed in a dialog — Meshy 10 · Snapshapy 0
  • Download clicks — Meshy 40 in the dialog · Snapshapy 20 (Export → STL each time)
  • Credits — Meshy 760 · Snapshapy 110

On Meshy Pro, 760 credits is 76% of a 1,000-credit month for ten files that fill almost 4 GB. The Snapshapy ten fit in 30 MB.

Side notes: 76 credits, three Approve cards, a six-minute hang

These are not the file story, but they shaped the run. My first try at message 1 on Meshy showed four "Creating image" lines for about 6 minutes; after a reload the reply was gone, no images appeared, and 0 credits were charged.

Meshy's first try at message 1: four "Creating image" lines that ran for about 6 minutes.

I re-sent the same message, approved 4 paid actions at Est. Total Cost 36, and then approved 30 for the model and 10 for the repair. Meshy's four concepts were all fully painted and each held an axe and a round shield; Snapshapy's second concept was unpainted grey with no axe in view.

  • Credits — Meshy 76 (36 + 30 + 10), $1.52 · Snapshapy 11 (8 + 3 + 0), $0.52 · 6.9×
  • Approvals — Meshy 3 Approve clicks + 1 choice card · Snapshapy 0
  • Failures — Meshy 1 (message 1 hung) · Snapshapy 0

Meshy credits panel after the run: 925 left; Print repair −10, Image to 3D −30, 4 × Text to Image −9; Premium upsell beside it.

The credits panel matched my ledger to the credit, and beside it sat "Get 3× more credits with Premium benefits".

Final verdict: Meshy 3D Agent scores 56/100 for a 32 mm resin miniature

For this job, Meshy 3D Agent's output is correct and too heavy. The 32 mm dwarf arrives as a 387.7 MB STL, 129× the 3.0 MB Snapshapy file, after a 10-credit repair, still at 7,754,470 faces. The dialog defaulted to 12.0 cm with Resize off, so the size I asked for in message 3 depended on me typing 3.2 cm. One dwarf costs ≈129.5 s of download on 12 Mbps; ten cost about 21.6 minutes and 3,877 MB of disk.

Meshy earns its points on print validity and mesh density, both scored in the card above. Neither point explains why a figure 32 mm tall has to travel as a 387.7 MB file.

Which one I would use for this job

For a 32 mm resin miniature, I would use Snapshapy. The file came out at 32.00 mm by itself, weighed 3.0 MB, passed the same watertight, one-body check, and cost 11 credits for the whole dwarf. Snapshapy plans are at snapshapy.com.

If you want the densest possible mesh straight from the tool and do not mind a 194.2 MB zip per figure, Meshy Pro at $20 delivers that, at 76 credits per dwarf.