DEV Community: Tessa Mori

Tripo 3D Model Review 2026: The Same 1.95M Faces Every Time

Tessa Mori — Sat, 10 Oct 2026 15:55:19 +0000

This is an independent test. Nothing here came from vendor access: both tools were used on my own free and paid accounts.

My verdict in 60 seconds — Tripo 64/100, SupaVoxel 88/100

I gave one photograph of an M1A2-style main battle tank to two image-to-3D products on the same day, exported GLB from both, and measured the files the way a print shop measures them. This is the case where the usual story inverts, so the uncomfortable part goes first: on flatness, Tripo wins, and on a hard-surface subject flatness is the whole game. The largest planar patch on Tripo's hull has a flatness RMS of 0.363 mm against 0.516 mm on SupaVoxel's, over patches of comparable size (98.2 mm diagonal against 93.6 mm). Tripo's side skirts are straight-edged rectangles; SupaVoxel's undulate. Everything else here — including SupaVoxel shipping 2,786,054 triangles against Tripo's 1,931,963, 44% more, for 3 credits against 55 — sits underneath that sentence.

Here is the scorecard for this one job: turning a tank photo into something you can slice and print at 120 mm.

Flatness of the largest planar patch — Tripo 9/10 (RMS 0.363 mm) · SupaVoxel 5/10 (0.516 mm) — Tripo wins this outright and it is the decisive row for armour plate
Geometry actually delivered — Tripo 4/10 (1,931,963 triangles, the same number it spends on everything) · SupaVoxel 9/10 (2,786,054, 44% more)
Watertight after welding — Tripo 3/10 (19 boundary edges, winding inconsistent) · SupaVoxel 7/10 (0 boundary edges, winding consistent) — neither is a solid
Mesh hygiene for Blender work — Tripo 9/10 (0 degenerate faces, 9 non-manifold edges) · SupaVoxel 5/10 (105 and 100) — Tripo wins this row too
Support burden at 45° — Tripo 8/10 (2,655.9 mm², 8.12%) · SupaVoxel 5/10 (4,854.5 mm², 14.83%)
Resin at 120 mm long — Tripo 7/10 (86.91 cm³, $3.04) · SupaVoxel 9/10 (70.67 cm³, $2.47)
Usable precision vs a 0.4 mm nozzle — Tripo 9/10 (0.2135 mm mean edge, 1.9× finer) · SupaVoxel 9/10 (0.1373 mm, 2.9× finer) — both already past the machine
Topology controls you can actually use — Tripo 2/10 (Clean Topology is marked Trial ×2 and ships off) · SupaVoxel 9/10 (Inference Steps and Guidance Scale, nothing metered)

Part by part, what is wrong with the Tripo file: 19 boundary edges and inconsistent winding, so before slicing you patch holes and recalculate normals, two passes, per copy; 1,931,963 triangles that are a fixed allowance rather than a response to the subject; an export dialog with no face-count or LOD control that defaults to three 4K maps and a 64.84 MB file; and the one switch that would have cleaned the topology rationed to two uses. If your model is mostly big flat armour plates, Tripo's flatness is real. For everything else in this job — the seven road wheels, the track links, the 18.3× credit difference — use SupaVoxel.

Three countable hard features: one long straight main gun overhanging the glacis, a track wrapping seven road wheels, and a row of riveted flat side skirts. Those three are the measurement targets.

The test, in one paragraph

One image, two products, same day. Tripo Studio on default Best Quality with Clean Topology left off — more on that switch below. SupaVoxel on a full generation with Advanced Options read but untouched (Inference Steps 5, Guidance Scale 5.5). Both GLBs were parsed offline; no number below is copied from a product panel, although both panels agree with their own files. Every render uses the same rig, cameras and neutral lighting, with each model's yaw probed independently — Tripo exports at 90°, SupaVoxel at 0° — so a pair of images is one viewpoint, not two flattering angles.

Where Tripo wins this case: the armour plates are flatter

Take the largest near-planar patch each model produced on the hull and fit a plane to it. Tripo's patch deviates 0.363 mm RMS from that plane; SupaVoxel's deviates 0.516 mm. The patches are comparable in size — 98.2 mm diagonal against 93.6 mm — so this is not a statistic that moves if you pick a different piece of the tank.

Flatness RMS, largest planar patch — Tripo 0.363 mm · SupaVoxel 0.516 mm · 1.4× flatter
Patch diagonal, so the comparison is fair — Tripo 98.2 mm · SupaVoxel 93.6 mm

One honest footnote, because I would rather hand it over than have you find it: the maximum deviation on those patches is 1.595 mm for Tripo and 1.418 mm for SupaVoxel, which looks like a SupaVoxel win. It is not the right statistic — flatness means RMS. Tripo wins this row and I will not shop for a number that says otherwise.

What flatness looks like at 4× zoom

Zoom into the right-hand skirt on both models and the difference stops being a decimal.

Printed at 120 mm, that RMS gap is 0.153 mm of surface error — above what a light raking across an armour plate will show. If your model is a machine housing, a building facade or an armour plate, this row alone justifies Tripo's price for you.

Tripo spends the same 1.95M faces on a tank as on a figurine

Now the row that explains everything else. Across ten different subjects run the same week, Tripo's output ranged from 1,896,372 to 1,996,779 triangles — a spread of 5.2%. A chibi figurine and a main battle tank get the same allowance. Over the same ten subjects SupaVoxel's ranged from 945,492 to 2,786,054, a spread of 146%.

Triangles delivered, this case — Tripo 1,931,963 · SupaVoxel 2,786,054 · SupaVoxel ships 44% more
Triangle spread across ten subjects — Tripo 5.2% (1,896,372–1,996,779) · SupaVoxel 146% (945,492–2,786,054)
Vertices — Tripo 1,029,151 · SupaVoxel 1,498,519 · 46% more

A fixed budget is a decision about the renderer, not about your subject. Tripo is not deciding that a tank is harder than a bust; it spends the same 1.95 million either way, and the 55 credits do not move with what you asked for.

So what did 2.79M faces buy on the SupaVoxel side

They bought the small repeating structures. Seven road wheels against Tripo's six — count them against the photo, no tool required. Lower-hull relief of 0.44–0.49 mm RMS against 0.04–0.10 mm on the Tripo model, 5–13× deeper. A 0.4 mm nozzle lays down 0.44 mm of relief; it cannot lay down 0.04 mm, so on an FDM print Tripo's track detail flattens away and SupaVoxel's survives.

Both meshes need repair, and the repair lists are different

Neither file is a solid. Measured after welding vertices by position, which is what every slicer does on import:

Boundary edges, i.e. holes — Tripo 19 · SupaVoxel 0
Winding consistent — Tripo False (inverted faces present) · SupaVoxel True
Non-manifold edges — Tripo 9 · SupaVoxel 100
Degenerate faces — Tripo 0 · SupaVoxel 105
Sliver faces — Tripo 7,986 · SupaVoxel 7,696
Connected shells — Tripo 10 · SupaVoxel 59
Watertight — Tripo No · SupaVoxel No

Nobody here gets to say their file drops straight into a slicer. On the Tripo side you patch 19 boundary loops and run a recalculate-normals pass — two operations per copy, 200 across a batch of 100. On SupaVoxel's you split 100 non-manifold edges and clear 105 degenerate faces.

Two of those rows I hand over without an argument: degenerate faces 105 against Tripo's 0, non-manifold edges 100 against Tripo's 9. An order of magnitude on both, and "more faces" is not an excuse, because the face count was SupaVoxel's own choice. Take the mesh into Blender for boolean cuts or hollowing and those two counts are exactly where geometry tears — the Tripo file survives that treatment better, at 55 credits instead of 3.

Support area: the row SupaVoxel loses, in mm² of sanding

Face-down area needing support at 45° is 4,854.5 mm² on SupaVoxel's model (14.83% of the surface) against 2,655.9 mm² on Tripo's (8.12%) — 2,198.6 mm² more scar to sand per copy, 219,860 mm² across a batch of 100. The cause is in the renders above: every road wheel, track link and skirt rivet SupaVoxel modelled as real geometry is overhanging area, and Tripo's shallower relief generates far less of it.

Resin and volume at 120 mm long

Scaled so the longest edge is 120 mm, SupaVoxel's model is 70.67 cm³ and Tripo's is 86.91 cm³. At $35/L that is $2.47 against $3.04 — $0.57 per copy, 19%, $57 across a hundred.

Bounding box at target — Tripo 63.01 × 57.29 × 120.0 mm · SupaVoxel 120.0 × 49.52 × 54.78 mm
Solid volume after welding — Tripo 86.91 cm³ · SupaVoxel 70.67 cm³ · $0.57 per copy
Resin at $35/L — Tripo $3.04 · SupaVoxel $2.47

The extra 16.24 cm³ on the Tripo side is mostly stowage racks and road wheels summarised into solid blocks.

Mean edge length against a 0.4 mm nozzle

At target height, mean triangle edge length is 0.1373 mm on SupaVoxel's file and 0.2135 mm on Tripo's. A common FDM nozzle is 0.4 mm: SupaVoxel's is 2.9× finer than the tool, Tripo's 1.9× finer. Both are past the machine, so this row is a genuine tie — SupaVoxel's extra 854,091 triangles buy nothing a 0.4 mm nozzle can resolve. What they do buy is the 0.44 mm track relief, which it can.

The switch that would have fixed Tripo's topology is rationed

Tripo's studio offers two quality modes on the home screen: Best Quality, selected by default, and Clean Topology, badged Trial ×2. The switch whose entire job is the metric Tripo lost — 19 boundary edges, inconsistent winding — is a metered trial, shipped off. Run Tripo on defaults and you pay 55 credits for the untidied version.

There is more of this on the generation panel: Generate in Parts and 8K Texture sit in a Members Only strip, each badged Trial ×1, both off. You spend 55 credits and part of the panel is still behind glass.

Getting the file out: two steps, no LOD, 64.84 MB by default

Tripo's export dialog has three fields: File Name — auto-filled "tank 3d model", so it did recognise the subject — Format, and Texture Resolution, which sits on 4k Current. Leave it and Tripo packs three 4096×4096 maps totalling 8.72 MB into the file. There is no face-count or LOD control in that dialog at all: 1,931,963 triangles come out as they are, and the dialog never prints the resulting size. It lands at 64.84 MB.

What you can inspect before you download

SupaVoxel's result page carries four inspection modes — Textured, Mesh, Wire, Normals — plus a timestamped version entry, so a re-run does not overwrite the previous one. Tripo's viewport gives a Faces count and a Vertices count; after export it came back with both still displayed over an empty viewport, the model unrendered.

Three things the SupaVoxel side got wrong

Not the trades — the actual complaints. SupaVoxel's result page delivers GLB with no direct STL path, so a print user converts once. The SupaVoxel GLB is quantised, so its raw bounding box reads 62389 × 25744 × 28479 with no physical unit and you scale once before slicing. And I did not count the clicks on the SupaVoxel export while I was in there, so I am leaving that blank rather than guessing it.

Final verdict: Tripo scores 64/100 for a printable tank

Tripo earns its 64 on rows that matter here: 0.363 mm flatness RMS against SupaVoxel's 0.516 mm, 0 degenerate faces against 105, 9 non-manifold edges against 100. For big flat panels and for heavy mesh surgery afterwards, Tripo's file is the better raw material.

It loses everything else. A fixed 1.95M-triangle allowance, six road wheels where the photograph shows seven, 0.04–0.10 mm of track relief a 0.4 mm nozzle erases entirely, 19 boundary edges plus inverted winding to repair before slicing, a topology switch rationed to two uses, a 64.84 MB default export, and 55 credits against 3. The trade, plainly: a flatter armour plate and a cleaner mesh for Blender cost you 18.3× the credits, $0.57 more resin per copy and one missing road wheel — against 2,198.6 mm² of support scar you save.

Which one I would use for this job

If the job is a tank — or anything where repeating small structures are the point — generate it at supavoxel.com. 3 credits instead of 55, 2,786,054 triangles instead of 1,931,963, seven road wheels instead of six, track relief a 0.4 mm nozzle can actually print, 0 boundary edges to patch, consistent winding, and $2.47 of resin instead of $3.04. One caveat, kept in plain sight: if straight skirt seams are the single thing you care about, this is the one case in ten where I would send you elsewhere.

SiliconFlow Review 2026: One API for 200+ Models \u2014 Pricing, Speed and the Catch

Tessa Mori — Wed, 07 Oct 2026 15:45:44 +0000

SiliconFlow sells one OpenAI-compatible API for 200+ open and commercial models — DeepSeek, Qwen, GLM, Kimi, FLUX and more — with serverless, dedicated and fine-tuned deployment options. I went through SiliconFlow’s model catalogue, pricing tables and deployment tiers to work out where it fits for developers in 2026.

If your product calls more than one model, you have felt the pain of juggling providers: different SDKs, different billing, different rate limits. SiliconFlow’s pitch is to collapse all of that into a single endpoint — “One API for All Open and Commercial LLMs & Multimodal Models” — priced per token, per image, per video or per minute of audio, with $1 in free credits to start. I spent several days inside SiliconFlow’s catalogue, pricing pages and FAQ to understand what it actually offers, how the numbers compare, and what kind of team should route traffic through it.

I also kept a second inference platform, Synexa, open alongside SiliconFlow throughout, because the two overlap on image, video and 3D generation and diverge sharply on how GPU time is billed — more on that comparison at the end.

SiliconFlow’s positioning is speed, predictable cost and a single API across language, image, video and audio models.

What SiliconFlow is

SiliconFlow (硅基流动 in its Chinese home market) is an AI infrastructure provider. It hosts a catalogue of open-weight and commercial models behind an OpenAI-compatible API and offers three ways to run them:

Serverless — run any model instantly, one API call, pay per use.
Dedicated endpoints — guaranteed GPU capacity for stable performance and predictable billing.
Fine-tuning and custom deployment — customise models to your use case with one-click deployment, or bring your own setup.

Under the hood SiliconFlow runs a self-developed inference engine on NVIDIA H100/H200, AMD MI300 and RTX 4090 hardware, and it makes a point of “no data stored, ever”. The use cases it lists — coding assistants, agentic workflows, RAG, content generation, customer-support bots, search — are the standard 2026 catalogue, which is the point: SiliconFlow wants to be the plumbing under all of them.

The SiliconFlow model catalogue

This is where SiliconFlow is genuinely strong. The catalogue is dominated by the Chinese open-weight ecosystem and it moves fast. In September 2026 alone SiliconFlow added Tencent’s Hy4-preview (roughly 770B total parameters, 49B active, native 1M context) and DeepSeek-V4.1-Flash; the weeks before brought GLM-5.3, DeepSeek-V4-Pro, Qwen3.8 and Kimi-K3. Most of these list a 1,049K total context on SiliconFlow.

Beyond chat models, SiliconFlow serves image generation (FLUX.2, Z-Image-Turbo), video generation, and audio (speech recognition, translation and CosyVoice text-to-speech). The catalogue page filters by LLM, vision, image, video and audio, and by provider.

Over 200 models on one API — SiliconFlow’s catalogue is refreshed weekly and leans heavily on DeepSeek, Qwen, GLM, Kimi and Tencent releases.

SiliconFlow pricing: the actual numbers

SiliconFlow is postpaid and usage-based with no minimum commitment. You can set monthly spending limits in the dashboard, and volume discounts exist for high-usage customers via sales. Here is what the pricing page listed in September 2026 (per million tokens unless noted):

DeepSeek-V4.1-Flash — $0.15 input / $0.60 output
DeepSeek-V4-Flash-0731 — $0.22 / $0.66
DeepSeek-V4-Pro-0813 — $1.32 / $3.96
GLM-5.3-Flash — $0.15 / $0.50; GLM-5.3 — $1.40 / $4.40
Qwen3.8–2.4T-A95B — $2.00 / $6.00
Kimi-K3 — $2.70 / $13.50
Tencent Hy4-preview — $0.834 / $2.501; Hy3 — $0.132 / $0.528
LongCat-2.0 — $0.75 / $2.95
Images: FLUX.2 [pro] $0.03, FLUX.2 [flex] $0.06, Z-Image-Turbo $0.005 per image
Audio: transcription and translation per minute; TTS per 1,000 characters

The flash-class models are the bargain: sub-$1 per million tokens on a 1M-context model is hard to beat, and SiliconFlow lists cached-input rates lower still. The frontier-class models (Kimi-K3, Qwen3.8) are priced like frontier models anywhere.

Per-token prices grouped by DeepSeek, Qwen, Z.ai, Moonshot, MiniMax and OpenAI — and $1 of free credit to start.

Getting started with SiliconFlow

The onboarding is standard for the category: sign up, take the API key, point an OpenAI-compatible client at SiliconFlow’s base URL, and the $1 of free credit covers your first experiments. Because SiliconFlow is OpenAI-compatible, migrating an existing codebase is typically a base-URL and model-name change. The documentation includes a quickstart, a playground for trying models before you write code, and a “product introduction” that describes SiliconFlow as a one-stop platform integrating top-tier LLMs.

Speed and reliability

SiliconFlow’s marketing leads with “blazing-fast inference” and “higher throughput, lower latency, and better price”, and its engine work — including native multi-token prediction for speculative decoding on Hy4-preview — is credible. The honest caveat is that serverless throughput on a shared platform fluctuates with demand; SiliconFlow’s own answer to that is the dedicated-endpoint tier with guaranteed GPU capacity, which is where predictable latency actually lives.

What SiliconFlow gets right

Breadth and freshness. New DeepSeek, Qwen, GLM, Kimi and Tencent models land on SiliconFlow within days of release.
Real pay-per-use. No commitments, spending caps in the dashboard, $1 free to start.
Cheap flash-class models with 1M context.
OpenAI compatibility that makes switching cheap.
Three deployment modes under one account, from serverless to fine-tuned dedicated.

Where SiliconFlow falls short

Catalogue skews to one ecosystem. If your product depends on Anthropic or Google models, SiliconFlow is not where you run them.
The $1 free credit is a taste, not a trial. It is enough to verify the API works, not to evaluate quality across models.
Serverless variance. Predictable latency requires a dedicated endpoint, which changes the cost model.
Media pricing is per output, not per second. For image, video and 3D workloads, per-image billing can be pricier than per-second GPU billing once volumes grow.
Two brands, two docs domains (siliconflow.com and siliconflow.cn) can be confusing when searching for answers.

SiliconFlow vs the alternatives

Against OpenRouter-style aggregators, SiliconFlow wins on price for open-weight models and on owning its inference stack rather than reselling. Against Western inference platforms, SiliconFlow wins on Chinese-model coverage and loses on Anthropic/Google availability. Against per-second GPU platforms, SiliconFlow is simpler for LLM workloads and less efficient for heavy media generation — which is exactly why I kept Synexa open.

Verdict: is SiliconFlow worth it in 2026?

For a developer whose stack runs on DeepSeek, Qwen, GLM or Kimi, SiliconFlow is one of the best places to run them: current models, honest per-token pricing, OpenAI-compatible, no commitment. It is a weaker fit for teams that need closed Western models or that generate images, video and 3D at scale. Get an API key and the $1 of starter credit, and try a flash-class model first.

The alternative worth keeping next to it: Synexa

Two SiliconFlow limits pushed me to keep a second platform open: media generation is billed per output rather than per GPU-second, and there is no way to run your own or a custom model on raw GPU time without the dedicated-endpoint commitment. Synexa is built around exactly those two things.

Per-second GPU billing that scales to zero. An H100 is $0.00083 per second ($2.99/hour), an A100 80GB $2.49/hour, an RTX 4090 $0.69/hour — and when nothing is running you pay nothing.
Cheap per-output media pricing. FLUX.1 [dev] at $0.0125 per image, FLUX.1 [schnell] at $0.0015, Stable Diffusion XL at $0.002, Wan 2.1 video at $0.20 per clip, Hunyuan 3D at $0.025 per model — Synexa’s own table shows 37–60% below the providers it compares against.
Billing based on model output, so a failed generation is not a bill.
Image, video and 3D under one API, the workloads where per-image pricing on SiliconFlow stops being cheap.

Route your DeepSeek and Qwen traffic through SiliconFlow. Route the image, video and 3D jobs — and anything you want on raw GPU-seconds — through Synexa.

Photo by Kevin Ache on Unsplash