Independent review. I ran both tools on my own accounts, free and paid, with no vendor-provided access or early access of any kind.
A photograph of crumpled foil should produce an object that looks like chance made it. The blue container in my source picture has crossed ridges, different-sized recesses and no repeated central motif. I gave the same picture to Hyper3D and SupaVoxel, downloaded the textured models and took off their paint. Hyper3D had preserved folds, but arranged them like a face. SupaVoxel kept the mess. Then I looked inside and found the limit of that visual win.
My verdict in 60 seconds — for an irregular foil digital asset, I would choose SupaVoxel’s crossed ridges over Hyper3D’s near-mirrored mask. This is a paired-render art-direction judgment from one source, not ground-truth 3D reconstruction or a finished-planter endorsement. The downloadable Hyper3D Gen-1.5 PBR turns the foil into near-mirrored creases around a central spine. The actual 58,065,236-byte browser Original size file from SupaVoxel keeps varied crossing ridges on the front and on its invented back. But its top view shows white background through the interior opening; Hyper3D shows a blue floor. I would pick SupaVoxel for a digital close-up whose outside sells irregular foil. I would not call it a ready-to-use soil or water container without designing and testing a base.
My eight-row decision card addresses the digital surface brief while keeping measured values separate from visual judgments:
- Front fold irregularity — Hyper3D paired central ridges vs SupaVoxel varied crossings — the main art-direction difference.
- Invented rear surface — near-mirrored Hyper3D spine vs SupaVoxel differently angled ridges — useful for a rotating asset, not verified photo truth.
- Clay-render relief — both have real geometry; SupaVoxel keeps more uneven intersections — not merely blue paint.
- Exterior sampling — 120,000 vs 1,500,000 triangles — face count supports but does not prove observed fold quality.
- Three PBR maps — both yes, Hyper3D 204⁸² vs SupaVoxel 409⁶² — resolution alone is not a fidelity score.
- Standalone textured file size — 14.039 vs 58.065 MB — Hyper3D is genuinely easier to serve as tested.
- Welded topology and face hygiene — both watertight, Hyper3D 0/610 vs SupaVoxel 12/8,408 degenerate/sliver faces — a real rival win.
- Interior floor visibility — Hyper3D blue floor vs SupaVoxel see-through passage — a gate if the object must hold material.
For a digital close-up I accept more file bytes for SupaVoxel’s folds. For an as-delivered planter candidate I start with Hyper3D’s visible floor. Neither file was printed or leak-tested.
What did the reference demand — and what did it leave unknown?
The identical 1,647,256-byte independent input PNG shows blue crossing folds and a dark cavity, but no back view or proven physical floor.
I compared an exported Gen-1.5 Hyper3D PBR member with an actual SupaVoxel UI Original size GLB. Source-image publication/reuse rights remain uncleared. Matching upload bytes do not control the products’ captions or hidden preprocessing. The inaccessible Gen-2.5 Hyper3D preview is not pictured here. No true back view or provable base exists in the source; my judgment concerns the delivered objects’ visual shapes.
Did SupaVoxel keep the original folds from the front?
The actual browser-exported SupaVoxel GLB shows crossing ridges of different lengths and depths rather than one repeated vertical motif.
Triangular recesses intersect at varied angles instead of mirroring a centerline. That is a paired-render observation, not 3D-scan registration. The file has 1,500,000 triangles, 803,054 file vertices and a 0.3841 mm estimated mean triangle edge at 120 mm longest-side scaling. Density alone does not prove fidelity, and a 0.4 mm printer nozzle does not guarantee every fold survives. For a digital rotating view, the ridges — not the count — make the choice.
What exactly went wrong on Hyper3D’s front?
The downloadable Gen-1.5 PBR file does have folds; they meet at a stronger center ridge and paired hollows that read almost like a mask.
Hyper3D did not smooth the foil flat; it made sharp planes and a rim. Its flaw is the arrangement: big ridges meet at center and side hollows nearly mirror each other. Its downloaded Gen-1.5 PBR has 120,000 triangles, not the inaccessible Gen-2.5 preview’s claimed million. Fewer faces do not logically cause symmetry. But this delivered file reads like a mask where the tested brief demanded accidental foil; I would resculpt the center or use SupaVoxel.
Does that difference persist behind the object?
Hyper3D’s back close-up again gathers broad folded planes around a near-mirrored central spine.
SupaVoxel invents cross-cutting recesses of varied sizes instead of repeating the same centerline pattern.
Yes. A rotating digital object needs an invented back even without a rear source. SupaVoxel continues varied intersections; Hyper3D continues its near-mirrored spine. That is an art-direction preference, not ground-truth backside accuracy. For a hero turntable I would accept 58.065 MB of SupaVoxel Original size GLB versus Hyper3D’s 14.039 MB extracted PBR, or separately validate an optimized delivery. For a fixed front thumbnail, that transfer premium buys little.
Is SupaVoxel’s relief in geometry or in its blue maps?
Without color or normal texture, SupaVoxel still has varied ridge angles and recessed intersections.
Hyper3D’s untextured view retains its central ridge; the mask-like shape cannot be blamed solely on material colors.
The large crossed ridges remain when maps come off, as does Hyper3D’s orderly center. A normal map alone cannot explain this contrast. Here one file has an irregular outer mesh and the other a stylized near-bilateral pattern. A different reference or rerun may change the result; I did not test repeatability or reconstruct a ground-truth 3D scan.
What do the three texture maps actually carry?
The real SupaVoxel Original size file embeds three 4096 × 4096 PNG maps; only one serves the baseColor slot.
Each final file embeds baseColor, normal and metallicRoughness PNGs. Hyper3D uses 204⁸² maps; SupaVoxel 409⁶², four times the pixels per image, not automatically four times the quality. BaseColor bytes: 2,956,017 vs 9,275,983; the other two total 6,597,825 vs 5,089,454. Normal/roughness can matter in a digital metallic render. In monochrome resin, stripping maps during repackaging might avoid payload — but the downloaded GLBs do not shrink themselves. Hyper3D’s earlier 4,484,160-byte geometry-only GLB had no maps and is not the compared PBR file.
How many bytes did each product actually hand me?
Hyper3D’s browser transferred a 21,471,080-byte ZIP with Shaded and PBR GLBs; 14,038,528 bytes is the extracted PBR member.
SupaVoxel’s selected Export → GLB → Original size branch really yielded a 58,065,236-byte browser GLB from the existing project.
The tested Hyper3D browser delivered 21.471 MB of ZIP, including the 14.039 MB PBR and 7,432,300-byte Shaded GLB. SupaVoxel’s Original size menu delivered a 58.065 MB standalone GLB. Actual UI payloads differ by 36,594,156 bytes; separately hosting just Hyper3D’s extracted PBR yields a different 14.039-vs-58.065 MB comparison. At ideal 12 Mbps, UI transfers are 14.31 vs 38.71 seconds; independently hosted Hyper3D PBR alone is 9.36. These are transfer floors, not measured mobile first frame.
Is the smaller 8.5 MB SupaVoxel asset the UI download?
No. A separate 8,499,144-byte compressed CDN resource from the same job is 5,539,384 bytes smaller than Hyper3D’s extracted PBR, but requires compression extensions. It was not a witnessed UI Compressed-menu export. A 44,556,092-byte local analysis derivative was not browser-downloaded either. The actual tested SupaVoxel menu produced 58.065 MB. An 8.5 MB hosting experiment needs a compatible viewer and its own validation; it cannot retroactively turn the observed Original size transfer into a 5.67-second download.
What does serving ten thousand looks cost?
The Hyper3D PBR member is the standalone model in the hosting calculation; the browser ZIP is larger and has its own transfer denominator.
Hypothetically host the 14,038,528-byte extracted Hyper3D PBR member and the 58,065,236-byte SupaVoxel Original size GLB separately. With 10,000 complete uncached loads and an illustrative $0.085 per decimal GB, pure transfer charges work out to about $11.93 vs $49.36. That is a $37.42 hypothetical monthly premium for SupaVoxel’s stronger irregular surface, not an invoice or a subscription-price comparison. Caching, partial loading, origin traffic, storage and renderer decoding are excluded. Geometry memory under an illustrative 32 bytes per vertex plus 4 bytes per index works out to 4.48 vs 43.70 MB before textures, buffers and allocator overhead. At a 100 Mbps line, pure standalone transfer is roughly 1.12 vs 4.65 seconds. This is the rival’s strongest digital counterargument. If most viewers only see a small static photo, I would not pay it; if they rotate the asset for its irregular foil folds, I might.
Does the shell check settle whether either model is a pot?
White background is visible through SupaVoxel’s lower interior opening despite its seam-welded mesh being topologically watertight.
Hyper3D shows a blue inner floor; that appearance still has not been physically leak-tested.
Both exported meshes weld into one watertight, consistently wound, face-connected shell with zero boundary and nonmanifold edges. That is not evidence that both containers can hold material. SupaVoxel’s top view has a through-passage where a soil-holding planter would need a floor. A watertight surface can enclose a tube without sealing its center. Hyper3D has a visible blue interior bottom and a cleaner triangle-hygiene result: zero degenerate / 610 sliver faces, against SupaVoxel’s 12 / 8,408. For a printable pot candidate, those are genuine Hyper3D wins, and no clever scorecard should bury them. The exchange rate for SupaVoxel’s outside is a real base-design task with unknown labor and revised volume, not merely the 44 MB extra standalone file. No one printed, sliced, loaded soil or tested water retention.
Could more triangles automatically fix those faults?
No. SupaVoxel has 1,500,000 triangles versus Hyper3D’s 120,000, and average triangle edges at 120 mm longest-side scaling are 0.3841 vs 1.1448 mm. The finer surface accompanies the more varied visible folds. But more samples also accompany 8,408 sliver faces, 12 degenerate faces and the missing visible floor in this particular asset. Under one orientation screen (world Y up, faces within 45° of downward −Y), SupaVoxel has 1,703.2 mm² potential downward-facing area versus Hyper3D 5,524.6 mm². That is not generated printer supports or a promised saving in resin. Adding a base changes the shape and may change both the volume and the support screen. If the eventual goal is a monochrome print, both PBR color treatments may be discarded in the slicer. The creator’s question should be: what geometry must I finish after download?
Final verdict: why choose the heavier, flawed file for the digital shot?
Because the jagged, varied folds are the digital shot. SupaVoxel preserved the source’s irregular visual grammar better across front, rear and clay views; Hyper3D’s downloadable Gen-1.5 file looks strongly organized around a central mask-like motif. This is not an endorsement of SupaVoxel as a finished vessel. Hyper3D wins standalone bytes, actual UI transfer bytes, a visibly bottomed cavity and narrow triangle hygiene. SupaVoxel wins the visual brief and pays for it with a 58.065 MB Original size browser GLB and an unresolved functional opening if the model becomes physical. Gen-2.5’s one-million-face Hyper3D preview was subscription-blocked on the tested Free tier after a separate 0.5-credit debit; it cannot substitute for the Gen-1.5 file in this comparison. My verdict is strong precisely because it is tied to the intended deliverable.
Use SupaVoxel for irregular foil, then inspect the interior
For a digital product render or editable blue-foil sculpture that needs accidental-looking crossing creases, start from SupaVoxel and use your own reference. Compare the front, back and clay view, then turn it over. The output I measured gives you the better-looking outer surface, not a ready-to-fill pot. If a planter is your deliverable, add and measure a floor, slice and test a physical sample before promising it will hold soil or water. If your client needs a visible floor immediately, Hyper3D Gen-1.5 supplied the better initial shape in this pair.
How I tested it. Same independently generated PNG bytes went into both products. The compared Hyper3D file is the legally exported Gen-1.5 ZIP’s PBR member, and the compared SupaVoxel file is the independently recovered actual browser Original size GLB; all pictured SupaVoxel fixed-angle renders were made from that actual export. File sizes, map dimensions/bytes, mesh counts and seam-welded topology are measured. Transfer seconds, CDN charges and geometry memory are arithmetic under stated bandwidth, tariff and layout assumptions. The back is invented by both tools; aesthetic irregularity is my judgment, not an objective color or 3D reconstruction metric. No actual planter, physical leak, slicer output, compressed-menu click, reliable UV occupancy or reference-image publication rights were verified.
- Also in this series
- Hyper3D Rodin Planter Review 2026: A Base Matters More Than a Mesh
- Hyper3D Rodin Cost Review 2026: 0.5 Credit, Then a Download Wall
Top comments (0)