Independent review: both products were tested on my own accounts — free where offered and paid where not — with no vendor-provided access.
I opened Hyper3D with a picture of a small seated winged figure and a simple requirement: leave with a textured model I could inspect in my own software. I watched a Gen-2.5 preview appear, confirmed the geometry and pressed Download. That is where the experiment changed. The file would not leave a Free account without a subscription. So I ran the same image through a separate Gen-1.5 path, then through SupaVoxel, and kept each debit attached to its own job.
My verdict in 60 seconds — for a first-time user seeking a textured digital download, I would take the measured SupaVoxel export over Hyper3D’s initially gated Gen-2.5 preview. That is a judgment about this recorded route, not about the cash value of different credits. Hyper3D's Gen-2.5 spent 0.5 Hyper3D credit for an inaccessible export, then Gen-1.5 spent a separate 0.5 credit on geometry confirmation before yielding a textured PBR member in a ZIP. SupaVoxel used one matched 3-SupaVoxel-credit transaction and delivered an actual Original size GLB. If the job is an unmodified print starting mesh, I would instead take Hyper3D's Gen-1.5 solid shell; its print win is real and separate from this access verdict. SupaVoxel is the direct export route I would start with when a digital delivery, not a subscription-gated preview, is my immediate brief.
My eight-line decision card is about transaction and delivery clarity. The values are the observed evidence, and each line gives the consequence for this particular job:
- First preview to file — Hyper3D Gen-2.5 blocked vs SupaVoxel completed — an apparently finished preview did not grant a Hyper3D Free-tier file.
- Charge attributable to that first job — isolated 0.5 Hyper3D credit vs matched 3 SupaVoxel credits — not a price ranking.
- Alternative route — another Hyper3D Gen-1.5 generation required vs no version switch in SupaVoxel — two attempts are not one product.
- Geometry confirmation — Hyper3D Gen-1.5 deducted 0.5; SupaVoxel's one request debited 3 — unrelated currency units.
- Material debit — Hyper3D Generate 0 and Confirm 0 more in this case vs one SupaVoxel transaction already recorded — no invented surcharge.
- Textured delivery — ZIP containing PBR and Shaded GLBs vs single Original size GLB — both delivered, but only one arrived as the selected standalone file.
- Working print shell — Gen-1.5 welded watertight vs SupaVoxel 471 nonmanifold edges — Hyper3D's genuine counterweight.
- Rear-view digital detail — connected white back wings vs raised, separate feather tiers — SupaVoxel earns its digital preference.
A cash-cost ranking would require a dollar exchange rate and plan conditions I did not measure. A print-shop decision instead hinges on the welded-shell row.
Why did I photograph the balance before making anything?
The Free-account Gen-2.5 studio showed a 0.5-credit tariff and a 3.0-credit balance before this generation.
The isolated account moved 3.0→2.5 across Gen-2.5 generation and remained at 2.5 through confirmation and refused download. That proves a 0.5-credit debit for this run, not an independently parsed million-face file. The same 1,650,798-byte PNG went into both products; their internal processing differed. Publication/reuse rights to this reference-influenced source have not been cleared.
What did the Gen-2.5 preview actually buy?
Sword, shield and wings appeared in a completed Hyper3D Gen-2.5 viewer; no Gen-2.5 GLB was obtained for file analysis.
This looked finished. Geometry Confirm took 24.940 seconds without another debit. The panel claimed one million faces and 676,844 vertices; neither topology nor print badges could be verified without an export. Gen-2.5 preview-generation time was not captured—the “about 40 seconds” estimate was not a measurement. “I can orbit it” proved different from “I own the file.”
Where was the paywall hiding?
After geometry Confirm, Pack Download appeared available; the unchanged 2.5 balance did not establish download entitlement.
The final Download action said: “Subscribe to download Rodin Gen-2.5 models. Gen-1.5 downloads stay free!”
The second screen is the decision, not the first. I selected GLB, pressed the real Download control and got an explicit subscription boundary. I did not fetch internal preview resources to manufacture a supposed file. The Gen-2.5 path produced zero legitimately downloaded GLBs after one verified 0.5-credit debit on this Free account. That does not prove all plans deny downloads, and I did not measure the subscription price or licensing. It proves the specific access flow I tried. An enabled-looking button after a paid-in-credits generation is no substitute for an actual exported file. For a workshop with a deadline, that difference is bigger than any polygon-count headline.
Was Gen-1.5 a retry of the same result?
Hyper3D Gen-1.5 Detail started a different task from the same source image, rather than unlocking the old million-face preview.
No. It used a different model generation and Detail configuration. The Gen-1.5 preview itself cost zero verified additional credits and lasted 25.064 seconds. After a browser interruption, I recovered that existing preview from Mine history, not a new generation. Roughly nine hours of operator/browser downtime between preview and later confirmation are not nine hours of vendor processing. I mention that because a naive wall-clock subtraction would punish the wrong party. A buyer starting in Gen-1.5 from the outset would not incur the Gen-2.5 detour I did. Conversely, pretending the recovered 120,000-face PBR member was an unlocked version of the Gen-2.5 million-face preview would describe a product that never existed in my downloads.
When did the accessible model cost another credit?
Gen-1.5 Triangular/Simplify geometry confirmation took 14.299 seconds and changed this account's balance from 2.5 to 2.0.
The free preview was not the charge. Geometry Confirm was: 0.5 Hyper3D credit on the second run. Its first downloadable GLB was 5,092,448 bytes, with UV coordinates but no embedded texture images. The measured preview plus Confirm phases sum to 39.363 seconds. They exclude material processing, image upload, operator actions and downloading, so I will not call Hyper3D a “39-second complete PBR generator.” This is a useful bit of accounting for anyone testing several poses: if you only need to examine previews, the observed Gen-1.5 preview had no debit; taking a result through geometry confirmation did. Whether another account or future plan has the same behavior was not tested.
Did the material steps really charge extra?
Material Generate was a separate action. The checked balance stayed at 2.0 during this step in the recorded case.
Material Confirm also left the checked balance unchanged at 2.0; the PBR path then became selectable.
No extra debit in this case. Both Generate and Confirm were separately checked at 2.0→2.0. It would be dishonest to label the finished Gen-1.5 PBR model “geometry 0.5 plus an unknown material charge” once those checks exist. It would be equally dishonest to promote a one-account result into a permanent pricing promise. These two material actions did take workflow steps whose complete timings were not measured. The actual Gen-1.5 file I compare has three embedded 2048 × 2048 PNG maps; the earlier 5.09 MB geometry-only download does not. A textured-vs-textureless size comparison may flatter one tool, but it would tell a producer absolutely nothing about two finished colored assets.
What arrived when I finally clicked Download?
The successful Gen-1.5 handoff chose GLB with Shaded and PBR at 2K, then delivered a two-variant ZIP.
The actual browser transfer was 24,544,968 bytes. I extracted the 15,247,868-byte PBR GLB for the visual and geometric comparisons. Those two figures answer two different questions: how much the Hyper3D page transferred and how large one independently hosted textured model would be. The post-geometry route required Material Generate, Material Confirm, GLB selection and Download, four recorded interface actions, plus extracting the PBR member. Hyper3D thus does provide a legitimately downloadable full-material file from Gen-1.5; my complaint is the detour and the misleading intuition that the earlier Gen-2.5 preview was already mine. The full PBR ledger for this specific Gen-1.5 run is 0.5 credit at geometry Confirm and zero extra at both material stages.
What did SupaVoxel actually charge and export?
SupaVoxel showed Generate (3 credits) for the single Main image; extra angle slots were empty in this run.
The completed request's result panel showed 946,166 triangles; parsing the downloaded GLB confirmed that count.
The uploaded image bytes matched one successful request and its linked 3-SupaVoxel-credit transaction. Its database lifecycle was 193.746 seconds including queue, excluding upload and export. The transaction, rather than a shared account's later balance, ties the debit to this case. Those credits are not priced against Hyper3D's, and this lifecycle is not comparable to Hyper3D's 39.363 seconds of selected phases.
Did the export-menu choice matter?
Export → GLB → Original size was the tested three-action route; the menu also offered Compressed, which this case did not measure.
The browser delivered a 36,589,892-byte Original size GLB with three 2048² PNG maps; that UI label does not prove lossless source fidelity. File parsing confirms 946,166 triangles. At hypothetical ideal 12 Mbps, pure transfer is 24.39 seconds versus 16.36 seconds for Hyper3D's ZIP—not measured phone load. Hyper3D wins delivery bytes; SupaVoxel's stronger digital feathers add 12.04 MB to that UI payload and would need repair of 471 nonmanifold edges if printed.
How many credits would a hundred figures require?
Assume—only for arithmetic—that every run repeats this one charge, both material stages again add zero, and there are no failures or plan caps. One hundred successful Gen-1.5 PBR outcomes would imply 50 Hyper3D credits; one hundred matched SupaVoxel requests would imply 300 SupaVoxel credits. Those are two denominated ledgers, not “six times cheaper.” This two-run learning detour cost 1.0 Hyper3D credit for Gen-2.5 plus Gen-1.5 together; a user who starts correctly at Gen-1.5 did not make the wasted first attempt. A one-time five-credit free balance could theoretically cover at most ten similar 0.5-credit confirmations if nothing else changes—it cannot fund one hundred. For export traffic, one hundred actual UI handoffs at the measured file sizes imply 2.4545 GB of Hyper3D ZIPs and 3.6590 GB of SupaVoxel GLBs. None of these is a completed batch or a purchasing guarantee.
Where does Hyper3D win beyond download size?
The Hyper3D model joins the back-wing roots into a flatter white span; its coherent shell is still a genuine print-workflow advantage.
SupaVoxel shows separate feather tiers and the exposed gold collar, but this file has 471 nonmanifold edges after seam welding.
After fair UV welding, Hyper3D's delivered Gen-1.5 mesh has one watertight face-connected shell and zero nonmanifold edges. SupaVoxel's original-size mesh has 315 face-connected regions and 471 nonmanifold edges. This is not a minor rival point; it reverses my choice for a fabrication-first buyer. Hyper3D also offers the smaller file, by 21.34 MB when comparing standalone PBR GLBs. The price for those wins in this model is an obvious connected panel where distinct rear feathers would have helped the digital shot. SupaVoxel buys a more articulate invented back with more bytes and an unsolved print-repair task. No back reference was supplied, and no figure was sliced or printed, so I am choosing between delivered images and measured topology, not certifying an historically correct angel or a ready-made statue.
Final verdict: what did I get for the two debits?
The 0.5-credit Gen-2.5 debit got me a preview that the Free account could not download. The separate 0.5-credit Gen-1.5 geometry Confirm led, after two zero-extra-credit material actions in this recorded case, to a real PBR GLB in a two-file ZIP. SupaVoxel's one matched 3-credit request produced an actual GLB in the tested export branch. Hyper3D lost my first-time digital delivery decision because Gen-2.5 blocked the file, not because 0.5 can be priced against 3 or its usable Gen-1.5 file is worthless. A print buyer should start with the Gen-1.5 shell here; a digital collector wanting the stronger back treatment has a reason to take the bigger SupaVoxel file. That is a decision, not a global ranking.
Use SupaVoxel when your next file must actually leave the page
If a digitally presented winged figure with layered rear feathers is the commission, try your own source in SupaVoxel, verify a real GLB download and inspect it beyond the viewer. In this run the accessible export and rear detail justify that choice. If the same figure must go to a printer, budget and validate repair first; the original SupaVoxel shell failed a manifold check. If you choose Hyper3D's Free route instead, select the downloadable Gen-1.5 generation deliberately rather than counting on Gen-2.5's attractive but gated preview.
How I tested it. I logged the isolated Hyper3D Free balance around each generation and material action, matched the SupaVoxel request to the exact input PNG and its own transaction, inspected the actual downloaded ZIP and GLB and parsed the PBR member offline. Credit amounts are measured in separate products' units. The 12 Mbps transfer numbers and ×100 batch values are arithmetic with the assumptions stated above. Subscription price, dollar-per-credit equivalence, the full upload-to-file timing on both sides, local repair duration, actual printability and rights to publish the reference-influenced source were not verified.
Top comments (0)