Meshy AI 3D Review 2026: The Wrench Jaw at 2x, Frame by Frame

Independent review: both products were tested on my own accounts — free where offered and paid where not — with no vendor-provided access.

There's a moment on every product page where somebody pinches the screen and zooms.

That's the moment a 3D model either holds up or falls apart.

I had one photo of a brushed-steel adjustable wrench and needed a 3D version of it. Asking around got me the same two answers every time — Meshy and SupaVoxel — so I ran the same picture through both and then did the only test that matters: I zoomed in until it hurt.

My verdict in 60 seconds — Meshy 62/100, SupaVoxel 88/100

Those scores are my opinion about this one job. The pictures below are the evidence, all shot at the same camera angles and the same crop boxes.

• Detail carved as shape, not painted on — Meshy 199,434 triangles vs SupaVoxel 1,500,000 · Meshy 6/10 · SupaVoxel 9/10 — Meshy runs out of surface and starts leaning on the texture; SupaVoxel has roughly 7.5× as much to carve the knurl and the groove lip out of
• Points holding the shape together — Meshy 111,498 vertices vs SupaVoxel 816,916 · Meshy 6/10 · SupaVoxel 9/10 — Meshy's sparser points are what round off the edges in the crops below; SupaVoxel keeps those corners as corners
• The wheel recess at 2× — Meshy soft, blurring ridges vs SupaVoxel harder ridges with visible gaps · Meshy 6/10 · SupaVoxel 9/10 — Meshy's knurl smears together under magnification; SupaVoxel keeps light and shadow between the ridges, which is what makes it read as metal
• The handle groove edge up close — Meshy softened lip vs SupaVoxel crisp lip · Meshy 6/10 · SupaVoxel 9/10 — Meshy rounds the one edge that runs the length of the tool; SupaVoxel holds it sharp all the way down
• What the model weighs while looking better — Meshy 11,603,384 bytes vs SupaVoxel 8,842,180 bytes · Meshy 6/10 · SupaVoxel 9/10 — Meshy charges you 2.76 MB more for the softer model; SupaVoxel is sharper and smaller at the same time
• Deliverables from the one run — Meshy 1 GLB vs SupaVoxel 2 GLBs · Meshy 7/10 · SupaVoxel 9/10 — this Meshy run gave me one file to work with; SupaVoxel had a compressed 8,842,180-byte GLB and a full 68,718,876-byte original-size GLB waiting together
• Textures baked into the file — Meshy 3 vs SupaVoxel 3 · Meshy 7/10 · SupaVoxel 7/10 — a real tie, and a useful one: the sharpness gap in the crops isn't one tool shipping more image files
• True colour with the lights off — Meshy grey-silver vs SupaVoxel grey-silver · Meshy 8/10 · SupaVoxel 8/10 — level: neither one turned your brushed steel into plastic, so the dark look in the lit shots is the lighting, not either tool's texture

Four things worth knowing before you scroll:

• Meshy builds this wrench out of 199,434 triangles. At arm's length that's plenty. At 2× it isn't.
• Meshy's back side can't be graded by anyone, including me. The photo never showed it.
• Meshy keeps the jaw faces smooth, exactly like the real thing. The denser file invents a serration. That's a point for Meshy and it gets its own section further down.
• Both files come back dark under the same lighting. That's the lighting, not Meshy.

For a product shot that people are going to zoom into, SupaVoxel is the file I'd ship — it came from https://supavoxel.com and it survives magnification better.

One image, one run on each side. Not a lab study.

First question: does it even look like the photo?

The only input: one photo of a brushed-steel adjustable wrench, jaw open, knurled adjusting wheel, groove down the handle, hang hole at the end.

Everything either tool knows about this wrench is in that frame.

Which means the back, the inside of the jaw throat, and the far end of the screw all had to be invented. By Meshy and by SupaVoxel alike.

Half the "flaws" people report in 3D generators are just parts the photo never showed.

Straight on, both pass. Now lean in.

Meshy from the front: head, jaw opening, groove, hang hole — all there.

SupaVoxel from the identical camera. The two files sit a little differently in frame, so compare shapes rather than pixels.

Credit to Meshy: this is the wrench. Head proportion, handle taper, the oval relief, the ring at the end. Meshy got the object, not a vague impression of it.

At this size you would happily put either one on a page.

So the interesting question isn't "does Meshy work". It's "how far can you zoom before it stops working".

The close-up test: what's still there at 2×?

Meshy, right in on the handle and the wheel recess.

SupaVoxel at the identical close-up angle. Harder edges around the recess, brighter metal visible between the ridges.

Here's where it separates.

Meshy's groove edge goes soft. The ridges on the wheel lose their corners and start to blur together. The SupaVoxel file keeps the edges crisp and keeps real contrast between the tops of the ridges and the gaps behind them.

That's what those triangle counts actually mean in practice. Meshy has 199,434 flat plates to build every surface out of; the other file has 1,500,000. When you magnify, the file with more plates has more to show.

Here's the scenario that made me care. A customer lands on the listing, spins the wrench, and pinches in on the adjusting mechanism — because that's the part they're actually buying. On a hardware product, the mechanism is the sales pitch.

At that zoom level, Meshy's softened ridges read as "render", and the crisper ones read as "photo of a real tool". Same wrench, same photo, same afternoon. The only thing that changed is how much geometry Meshy had to spend versus the other one — 199,434 plates against 1,500,000.

If your product is a flat panel or a plain box, Meshy's budget is fine and you can stop worrying. It's the knurls, threads and fine edges where Meshy runs out of road.

Meshy's model looks great until the exact moment your customer decides to inspect it.

The knurled wheel is the hardest thing in the frame

Meshy's adjusting wheel, blown up 2× from a fixed crop box.

The same crop box and blow-up on the SupaVoxel file. It sits lower in frame because the two files carry different internal orientations.

Look at the real wrench and the wheel has a fine knurl — lots of shallow ridges, tightly packed.

Meshy turns that into a handful of coarse bands. So does SupaVoxel, honestly. Neither one gives you a true knurl from a single photo, and I'm not going to pretend Meshy failed at something its rival nailed.

What both do get right: the wheel is modelled as a real recess with real geometry, not painted onto a flat surface. That's the difference between an object your customer can rotate and a sticker.

And when you compare the two recesses side by side, Meshy's is the shallower, softer one.

The view that actually goes on the page

Meshy's three-quarter hero. Three textures baked into an 11.60 MB file.

The SupaVoxel hero at the same angle. Three textures too — in an 8.84 MB file.

Both bake in three textures, so that row is a genuine tie.

But look at what the two files weigh. Meshy: 11,603,384 bytes. SupaVoxel: 8,842,180 bytes.

The file with roughly seven and a half times the detail is also 2.76 MB smaller to download. On a phone that's 5.9 seconds of waiting instead of 7.7.

You normally trade detail for weight. Against Meshy, this time, you don't have to.

The side nobody photographed

Meshy's back face — a surface the input photo never showed.

SupaVoxel's back at the same angle. Also invented, also ungradeable.

This is the part of the review where I'm supposed to say Meshy got the back wrong.

I can't. Nobody can. There is no correct answer for the back of this wrench, because the photo doesn't contain one.

What I can say is that Meshy's invented back is clean: the groove carries through, the wheel recess opens on both sides, no holes, nothing collapsed. Meshy didn't panic when it ran out of information.

If you need a verified back, take a second photo. No amount of triangles replaces one.

One run, two files to hand out

There's a second thing in SupaVoxel's favour that has nothing to do with the crops, and it only showed up at the export step.

One generation produced two finished files. The compressed 8,842,180-byte GLB is the one that goes on the page — it's behind every close-up in this article. The original-size export is the complete, unsqueezed version at 68,718,876 bytes, with textures stored as PNG rather than the compressed build's WebP. Bigger, naturally: nothing has been compressed out of it.

That's handy when the same wrench has two audiences. Marketing wants the light file for the listing. The engineer who asks for "the real model" wants the full one. Both were sitting in the same menu, from the same job.

You choose per destination, not per generation — no re-run, no conversion tool, no going back to the start screen.

Where Meshy actually wins

Meshy's jaw at 2×, from the same crop box used on both files. Smooth faces, like the photograph.

The SupaVoxel jaw, same crop box. Notice the serrated strip along the lower face — the real wrench doesn't have that.

Here's the row that goes to Meshy, and it's a good one.

In the photo, both jaw faces are smooth machined steel. Meshy kept them smooth. The denser file added a gripping serration that simply isn't on the real tool.

More detail is not the same thing as more accuracy. Give a model 1,500,000 triangles and you've given it more room to describe the object — and more room to make things up.

Two more in Meshy's column while we're here. Meshy's file asks nothing special of your 3D software, while the compressed SupaVoxel file needs a decoder called meshopt before it will open — switch to SupaVoxel's original-size export from the same menu and that decoder isn't needed either. And Meshy's geometry wants about 6.0 MB of memory against 44.1 MB, a 38.1 MB gap in Meshy's favour — on a cheap phone, that's the row that decides it.

If your software is fussy or your device is slow, Meshy is the right answer and the crops don't change that.

The numbers behind everything you just looked at

Pictures are the argument in this article, but every one of them is backed by a number out of the file. Here's the whole set, both sides, including the gaps.

Triangles. Meshy 199,434 against 1,500,000. That's the single number that explains every close-up above — how much shape each tool had available before it had to start painting detail on instead of building it.

Vertices. Meshy 111,498 against 816,916. Same story from the other direction.

Textures baked in. Three on Meshy, three on SupaVoxel. So the sharpness difference in those crops isn't "one of them shipped more images" — it's geometry.

File size. Meshy 11,603,384 bytes against 8,842,180. The denser file is the smaller download.

Format. GLB both sides — one file with shape and textures inside, openable without converting anything.

Credits the job recorded. Meshy 35, SupaVoxel 3. Two different plans, two different units. Not a price comparison.

Run time. SupaVoxel 215.462 seconds. Meshy didn't record one, so there's no speed claim anywhere in this article.

Retries. Zero and zero — Meshy needed no second attempt, and neither did the other one.

Failures. Not recorded on either side, so nobody gets a reliability verdict out of this.

Required extensions. Meshy: none. SupaVoxel: EXT_meshopt_compression and KHR_mesh_quantization.

The alternative export. SupaVoxel also offers this wrench at original size — 68,718,876 bytes, no special requirements, textures as PNG rather than the compressed build's WebP. Meshy wasn't run in a second export mode, so there's no number to put beside it.

Three blank rows. They stay blank.

The sums, and what I assumed to get them

Nothing below came off a stopwatch or out of a profiler. It's arithmetic on the measured numbers, written out so you can redo it.

Download on a phone: bytes × 8 ÷ 12,000,000, assuming a steady 12 Mbps and ignoring handshakes, decoding and caching. Meshy 7.7 seconds, SupaVoxel 5.9.

Download at a desk: same sum at 100 Mbps. Meshy 0.93 seconds, SupaVoxel 0.71. On fibre this whole row stops mattering.

A hundred of them on disk: this file × 100. Meshy 1.16 GB, SupaVoxel 0.88 GB. A capacity sketch, not a hundred real jobs.

A hundred runs on each meter: Meshy 3,500, SupaVoxel 300 — each in its own units, still not a price ratio.

Memory the geometry wants: 32 bytes per vertex plus 4 bytes per triangle index, textures excluded. Meshy 6.0 MB against 44.1 MB. Meshy wins that by 38.1 MB, and on a phone juggling several products it's the row that decides whether the page survives.

And one thing I did not do: import either file into a specific piece of 3D software. The extension requirements above are read out of the files — what each one declares it needs — not a record of what opened and what didn't.

Every figure in this section is arithmetic on measured bytes and counts. Change the assumptions and the numbers move; the files don't.

Is that dark, flat look a Meshy problem?

Both wrenches come back looking much darker than the bright steel in the photo. It's the first thing you notice and it looks damning.

It isn't. Render both files with the lighting switched off and you see the raw texture colour: grey-silver on Meshy, grey-silver on SupaVoxel. The darkness comes from the lighting setup used on both, not from anything Meshy painted.

That's the easiest cheap shot in this review, and it happens to be wrong.

So which file goes on the page?

If people will zoom — and on a hardware product they will — SupaVoxel. The recess stays crisp, the ridges keep their gaps, and the file is smaller while doing it.

If the file has to open in software you don't control, or run on a low-end phone, Meshy. Compatibility and memory beat sharpness every time they actually come up.

And on cost, the job recorded 35 credits on Meshy's meter and 3 on SupaVoxel's. Two different plans, two different units. That's not a price comparison and I won't turn it into one.

Try it with your own photo

Take the product you actually sell, photograph it once, and run it through https://supavoxel.com and through Meshy on the same afternoon.

Then do the only test that counts: open both files, zoom all the way in on the detail your customers care about, and see which one is still there.

How I tested this

One photo of an adjustable wrench, uploaded to both tools in the same session, no text prompt on either side. Meshy ran on its 7.1 Flagship model at High Detail and Ultra 2K with texture and image enhancement on; SupaVoxel ran at 5 steps, guidance 5.5, background removal on, octree 256. One run each, on each tool's own defaults.

Every picture above is an offline render of the downloaded file, using the same viewer, the same lighting and the same numeric camera angles for both. The two files carry different internal orientations and scales, so matching camera numbers doesn't mean matching pixels — compare shapes, not overlays. The 2× close-ups use an identical crop box on both sides: x 0.14 / y 0.30 / w 0.20 / h 0.29 for the jaw, x 0.27 / y 0.40 / w 0.12 / h 0.14 for the wheel.

Triangle counts, vertex counts, texture counts, file sizes and software requirements were read out of the two downloaded files. The download seconds are arithmetic — file size × 8 ÷ 12,000,000 — assuming a steady connection and ignoring decoding and caching. The memory figures are arithmetic too, at 32 bytes per vertex plus 4 bytes per triangle index, textures excluded.

Both tools recorded zero retries. Neither recorded a failure count, and Meshy's run time wasn't recorded at all, so those stay blank.