Disclosure: this is an independent hands-on test. Both tools were run on ordinary customer accounts; neither company supplied review access or saw this piece before publication.
My verdict in 60 seconds — Tripo 60/100, SupaVoxel 90/100
I fed one photo of a minimalist cantilever watch stand into Tripo and into SupaVoxel, took both GLB files offline, welded the vertices by position and measured them with the same script. Tripo charged 55 credits and handed back a 1,995,520-triangle mesh that is watertight — and whose face winding is inconsistent, meaning some faces point inward. The SupaVoxel file is watertight too, and its winding is consistent. For a print job that single boolean is the difference between "slice it" and "fix it first, every single time."
- Watertight after welding — Tripo yes · SupaVoxel yes · tie
- Boundary edges (holes) — Tripo 0 · SupaVoxel 0 · tie
- Non-manifold edges — Tripo 0 · SupaVoxel 0 · tie
- Winding consistent (normals) — Tripo false · SupaVoxel true · one repair pass per Tripo model
- Sliver faces — Tripo 259 · SupaVoxel 5,072 · Tripo wins by an order of magnitude
- Degenerate faces — Tripo 1 · SupaVoxel 49 · Tripo wins
- Support area at 45° — Tripo 3,466.7 mm² (11.91%) · SupaVoxel 4,742.7 mm² (15.32%) · Tripo wins
- Resin at 120 mm tall — Tripo $3.59 · SupaVoxel $3.95 · Tripo wins by $0.36
Five things that decide this case:
- Tripo's welded mesh has flipped faces. You cannot see that in Tripo's own viewer — it has no normals mode — so you find out in the slicer or after the print fails.
- Tripo's triangle quality is genuinely better here: 259 slivers and 1 degenerate face against SupaVoxel's 5,072 and 49. That is a real loss for SupaVoxel and I am not going to dress it up.
- Tripo ships 1,995,520 triangles against SupaVoxel's 1,500,000, and at 120 mm tall its average triangle edge is 0.1956 mm — against a 0.4 mm nozzle, both files are already past the point where more triangles buy anything.
- Tripo's export dialog has three fields: file name, format, texture resolution. No face count, no LOD. The 1,995,520 faces leave the building as-is.
- The whole Tripo geometry advantage costs 55 credits against 3, a 60.77 MB download against 7.70 MB, and one manual normals flip per model.
If the job is "turn a product photo into something I can slice tonight," SupaVoxel is the one to use. If the job is "take this into Blender and do boolean surgery on it," Tripo's cleaner triangles are worth the 18.3× credit bill — I say so again at the end, in the one row where Tripo wins outright.
The test: one photo, one target height, two products
The single input both products were given: a 1,518,703-byte PNG, sha256 645af033…, one white cantilever watch stand shot three-quarter front. Neither product ever saw the back.
Same file, same defaults, one run each. Everything below was parsed out of the downloaded GLB, not read off a product panel. Print metrics are computed after welding vertices by position — both exports split vertices along UV seams, so measuring before welding measures seams, not topology. I normalised both models to 120.0 mm tall first.
Watertight is not the finish line
The SupaVoxel result page reports Triangles 1,500,000; the parsed GLB reports 1,500,000. Panel and file agree to the digit.
Both meshes pass the checks most people run. Tripo: watertight, 0 boundary edges, 0 non-manifold edges, 1 connected component. SupaVoxel: the same four. On that checklist the case is a tie, and most reviews would stop here and call Tripo fine. The fifth check is the one that costs money.
- Connected components — Tripo 1 · SupaVoxel 1 · both a single shell, not a pile of patches
- Euler characteristic (SupaVoxel) — 2, from 750,002 welded vertices · a closed solid
Tripo's flipped normals are a repair step per model
SupaVoxel's in-product Normals view: one continuous gradient across the arch — teal on the base, blue-to-magenta up the column — with no patch where adjacent faces disagree. That is what consistent winding looks like before you download anything.
welded_winding_consistent is false for Tripo and true for SupaVoxel. Tripo built a closed shell and left some of its faces pointing the wrong way. Most slicers will guess their way through it; boolean operations and shelling will not. The cost per model is small — one recalculate-normals pass — but you owe it on every model. A hundred product photos through Tripo is a hundred unscheduled repairs, at 5,500 credits for the batch.
Tripo's viewer gives you no way to catch this: a textured model and a material strip, no normals mode, no wireframe, no mesh view. You spend 55 credits, you get a picture of what you bought, and the defect that matters stays invisible until the file is on your disk.
Where Tripo genuinely wins: triangle hygiene
Tripo's untextured mesh at the same camera. 259 sliver faces and 1 degenerate face in 1,995,520 triangles.
This is SupaVoxel's clear loss and it is not close.
- Sliver faces — Tripo 259 · SupaVoxel 5,072 · 19.6× worse on the SupaVoxel side
- Degenerate faces — Tripo 1 · SupaVoxel 49 · 49× worse on the SupaVoxel side
- Triangle count — Tripo 1,995,520 · SupaVoxel 1,500,000 · Tripo has 33% more faces, so "they simply have more triangles" does not explain the gap
Across ten objects I ran through both products, Tripo's triangle count barely moves: 1,896,372 to 1,996,779, a 5.2% spread whatever the subject. SupaVoxel ranges 945,492 to 2,786,054 — a 146% spread — because it follows the shape; the run that gave this watch stand 1,500,000 gave an armoured vehicle 2,786,054. This case is simply where the two land closest. The flat 1,500,000 reads as a quantisation step, not a limit. Ten subjects is a sample, not a statistic.
Slicers will almost certainly eat both files. Blender is less forgiving: needle-thin triangles are where a boolean opens a crack or a shell operation self-intersects. If your pipeline is generate-then-heavily-modify, this row alone should send you to Tripo — the trade ratio is 52 extra credits and 53.07 MB per model.
The cantilever is real on both sides
SupaVoxel's side view: the arch leaves the column, crosses its apex and drops, with open air underneath. The tip closes in a rounded lip with visible thickness.
Tripo at the same camera: a longer, flatter arch that tapers to a much thinner, nearly pointed tip, with a small notch on the underside. The overhang is genuine here too.
Neither product cheated the hard part. A watch stand is a cantilever or it is a paperweight, and both files have air under the arch. Tripo's tip is thinner and crisper; SupaVoxel's is blunter. Which one holds a strap better is a wall-thickness question, and I did not measure wall thickness — see the last section.
Support area: Tripo 3,466.7 mm², SupaVoxel 4,742.7 mm²
The flatter Tripo arch in the side render above presents less area below the 45° threshold, which means fewer support scars to sand off the underside.
- Overhang area at 120 mm — Tripo 3,466.7 mm² · SupaVoxel 4,742.7 mm² · +1,276 mm² on the SupaVoxel file
- Overhang as a fraction of surface — Tripo 11.91% · SupaVoxel 15.32% · Tripo wins
An extra 1,276 mm² of support contact is real sanding time on the arch underside — the second of exactly three numbers in this case that go against SupaVoxel, and I would rather name it than let a reader find it.
Resin at 120 mm: $3.59 against $3.95
Tripo's arch is narrower and the column straighter, which is where the 10 cm³ of volume goes.
- Volume at 120 mm — Tripo 102.43 cm³ · SupaVoxel 112.75 cm³ · Tripo 9% leaner
- Resin at $35/L — Tripo $3.59 · SupaVoxel $3.95 · Tripo saves $0.36 per print
- Across a 100-piece batch — Tripo $359 · SupaVoxel $395 · Tripo saves $36
Third and last number against SupaVoxel. Now the trade, because that is the only honest way to read three losses: an extra 1,276 mm² of support scarring plus $0.36 of resin per piece, against 53.07 MB of download per model, 52 credits per model, one normals flip you do not have to perform, and $45.1 per 10,000 page loads of CDN spend. Over a hundred pieces that is $36 of resin against 5,200 credits and 5.3 GB.
Average edge length against a 0.4 mm nozzle
SupaVoxel's untextured mesh, same camera. 1,500,000 triangles, average edge 0.2352 mm at target height.
- Mean triangle edge at 120 mm — Tripo 0.1956 mm · SupaVoxel 0.2352 mm · both finer than a 0.4 mm nozzle
- SupaVoxel's margin over the nozzle — 1.7× finer · already past useful
Tripo's triangles are 20% shorter. On a 0.4 mm nozzle neither number is reachable, so what those extra 495,520 Tripo triangles mostly buy is file size. On resin the extra density has a theoretical edge — and you still pay for it in bytes, at 30.45 per triangle against 5.14.
Tripo's export dialog: three fields, none of them geometry
Tripo's export dialog auto-named the file "curved display stand 3d model" — it had recognised the object class — and parked Texture Resolution on "4k Current".
Same dialog, closer. File Name, Format, Texture Resolution. Nothing else.
No decimation control, no LOD dropdown, no "print-ready" preset. Tripo inferred the object class well enough to name the file correctly, then offered no way to act on it. Viewport to disk is 2 clicks in Tripo. SupaVoxel's export is a dropdown in the result page top bar; I did not record a click count this run, so that cell says not captured rather than a guess.
What each model invented where the photo had nothing
SupaVoxel's back: the underside of the arch became an oval engraved plaque with concentric rings and illegible pseudo-text. The input photo has no label anywhere. That is SupaVoxel's invention.
Tripo at the same camera: the arch underside is a blank panel — more restrained — but the column meets the base in a hard crease, as if the foot were pushed into the disc with no fillet.
Both products invent where the three-quarter photo gave them nothing. The SupaVoxel plaque is a thing you sand off; Tripo's missing fillet at the column foot is a stress riser at the one joint carrying the cantilever. Neither is measured — both are visible at the same camera.
The bounding box at 120 mm
Tripo from above: a narrower band that overhangs the disc at both ends.
SupaVoxel from above: a wider band across a clean circular base, the tip reaching past the rim.
- Bounding box at 120 mm tall — Tripo 83.3 × 120.0 × 103.05 mm · SupaVoxel 85.51 × 120.0 × 91.3 mm
- Plate footprint — Tripo narrower and longer · SupaVoxel wider and shorter by 11.75 mm
SupaVoxel is 2.2 mm wider on the plate — noise on any printer that fits a 120 mm object. The three numbers that actually hurt are above.
Checking the mesh before you download it
Reopening the same SupaVoxel result from Projects: version history intact, Triangles 1,500,000, millimetre dimensions, and Textured / Mesh / Wire / Normals still one click apart.
Four inspection modes in the browser means the winding check that decides this article takes one click and no download. Tripo's result page gives you the model, a material strip, an Export button — and an interstitial: the moment generation finishes, a "View Your Model" dialog covers the thing you just paid 55 credits for.
What I did not measure
Tripo reports 1995520 faces / 1015351 vertices in the corner, exactly matching the parsed GLB. On the reporting front Tripo is honest.
- Wall thickness — not captured. There is no thickness field in my metrics, so I will not tell you which arch holds a watch better. The side renders show both tips have real thickness; that is as far as the evidence goes.
- Export click count on the SupaVoxel side — not captured this run.
- Charge timing (on submit or on completion) — captured for Tripo only: its balance fell 990 → 935 while the job was still generating.
- Two wireframe zoom renders — discarded. At 1.5–2 M triangles they render as near-solid black; I opened both to confirm that is real density and not a blank frame, and I am not using either as evidence.
Final verdict: Tripo scores 60/100
Tripo delivered a watertight single-shell cantilever, the cleaner triangle population, the smaller support footprint and the cheaper resin bill, and it reported its own face count honestly. Then it shipped flipped normals in a file with no way to notice them, 1,995,520 triangles with no decimation option, and a 60.77 MB download, for 55 credits. The SupaVoxel file needs no repair pass and costs 3 credits, and it loses triangle hygiene by an order of magnitude — one real loss, stated once at the top and again here.
One run each, product defaults, sample size one. Every number above comes out of the two downloaded GLB files or off the screenshots in this article.
Which one I would use for this job
For turning a product photo into a file you slice the same evening, SupaVoxel is the one I would hand you: watertight, consistent winding, 0 boundary and 0 non-manifold edges, 3 credits, 7.70 MB, and a Normals view that proves the mesh is right before you download it — supavoxel.com. Take Tripo instead if the model is headed straight into Blender for boolean work — 259 slivers against 5,072 is worth 52 credits to that workflow, and I would not pretend otherwise.
Top comments (0)