For readers looking for an stl viewer, this review addresses a step before inspection: whether a generated model can actually be downloaded. It compares Hyper3D’s credit charges and delivery outcomes with SupaVoxel’s quoted charge and failed browser export.
This is an independent test. Nothing here came from vendor access: both tools were used on my own free and paid accounts.
I set out to obtain one knitted-tray model and record what the tested workflows actually charged. I ended up with two Hyper3D generations, one real ZIP, one blocked Download button and two charges that must stay on separate lines.
The first run used Hyper3D Gen-2.5. It took 0.5 Hyper3D credit, produced a preview, and then the tested Free account was told to subscribe before downloading it. I tried again with Gen-1.5 and the same picture. Its preview cost nothing on the observed balance; Geometry Confirm cost another 0.5; Material Generate and Confirm caused no further recorded debit. That second run really did deliver a PBR file. SupaVoxel quoted 3 of its own credits before generation and a request-linked transaction confirms exactly that debit; its Original size browser export subsequently failed.
My verdict in 60 seconds — SupaVoxel wins the pre-submit quote and concept-inspection loop; Hyper3D Gen-1.5 wins this tested delivery. SupaVoxel showed “Generate (3 credits)” before I uploaded the image, made one model and offered Textured, Mesh, Wire and Normals views. The request-linked −3 transaction matched the quote. But the Original size browser export failed, whereas Hyper3D's separate Gen-1.5 run put a ZIP on disk. For choosing and inspecting a direction with a visible charge first, SupaVoxel is my pick; for this exact Free-tier requirement of a file in hand, use the Hyper3D branch that actually downloaded. These credits cannot be exchanged or treated as comparable dollars.
Eight paired observations, not a weighted price score:
- Pre-submit quote — Hyper3D: stage-specific debit observed later · SupaVoxel: 3-credit Generate quote visible before upload.
- Number of generations in this journey — Hyper3D: blocked Gen-2.5, then separate Gen-1.5 · SupaVoxel: one identified project.
- Higher-generation access — Hyper3D: Gen-2.5 charged 0.5, then download-gated · SupaVoxel: no comparable generation-tier gate tested.
- Requested browser file — Hyper3D Gen-1.5: ZIP received · SupaVoxel Original size: export failed.
- Attributable debit — Hyper3D: separately reconciled half-credit stages · SupaVoxel: request-linked −3 transaction.
- Material work — Hyper3D: Generate then Confirm, no added debit here · SupaVoxel: completed textured project under its one transaction.
- On-screen inspection — Hyper3D: model preview and mesh information · SupaVoxel: Textured, Mesh, Wire and Normals modes.
- Format menu versus receipt — both showed options; only Hyper3D's selected Gen-1.5 route delivered the requested file.
Do not divide three credits by half a credit to choose a subscription. Each platform's own observed charge and actual entitlement are the only supported billing facts.
The invoice starts with two separate runs
The image file was byte-identical for the two products, but Hyper3D was tested twice: Gen-2.5 first, Gen-1.5 after its download gate. SupaVoxel was tested once. Hyper3D generated different automatic descriptions and used different generation settings between its two versions, so we do not treat these as the same pipeline at two selectable output resolutions. The exact shared source was a 1,862,608-byte PNG showing a shallow knitted tray with an oval opening on one visible side. Two Hyper3D geometry debits sum to 1.0 credit for this researcher's two-run journey; dividing that by the single accessible PBR file gives a journey cost, not a universal per-file tariff.
One shared input; the separate Gen-2.5 and Gen-1.5 attempts must remain separate billing lines.
Gen-2.5 spent a credit fraction before its export gate
The Hyper3D account showed 1.5 credits before the Gen-2.5 run and 1.0 after generation and confirmation: a verified 0.5 debit attributable to this attempt. We retained separate task intervals of 56.930 seconds for its preview generation and 32.878 seconds for geometry confirmation. Neither includes upload, hand-clicks, material work or download. A one-million-face number on a Gen-2.5 information panel is not a measured asset here because the Free account never received that generation's model. This is precisely the access surprise: a visible, paid-for preview need not be a downloadable file.
The Gen-2.5 choice and 1.5-credit starting balance are visible before this distinct run.
The separate confirmation phase is in progress; do not relabel the two measured intervals as end-to-end delivery.
The download button was not the entitlement
The Gen-2.5 preview looked like the end of the job. The Pack screen showed Download. I clicked it and found the real condition: subscribe to download Gen-2.5; Gen-1.5 stays free. By then this run had used 0.5 credit, but there was no Gen-2.5 GLB to send to a product photographer or web developer. I did not use another route to fetch it. That spent half-credit is this particular false start, not a standard surcharge on every Gen-1.5 tray. If you're building a client listing, learn the file entitlement before polishing the preview.
The actual click exposed the subscription restriction after this Gen-2.5 attempt had spent 0.5 credit.
Gen-1.5 preview cost zero in this ledger
We selected the older Gen-1.5 mode and submitted the same PNG anew. The recorded Hyper3D balance was 1.0 before the preview, 1.0 once the preview had finished and 0.5 only after Geometry Confirm. Thus this case supports “the Gen-1.5 preview itself did not debit” and “confirmation debited 0.5,” not “generating always costs 0.5 at submission.” Its task/card intervals are 31.281 seconds for preview and 24.773 for Geometry Confirm, or 56.054 seconds for those two known stages together. No complete material-generation interval was captured, so 56.054 seconds is deliberately not the total time to a textured export.
Gen-1.5 Preview was still in flight at the unchanged 1.0 balance.
The 1.0-to-0.5 change belongs to Geometry Confirm, before the material path was finished.
Material was a workflow gate, not an extra debit here
A Material panel asked for a distinct Generate click and then a Confirm click. We checked the same account around each step: before and after Generate, 0.5 to 0.5; before and after Confirm, 0.5 to 0.5. The delivered Gen-1.5 PBR file in this case therefore incurred 0.5 verified Hyper3D credit including those two zero-debit material steps. This does not establish a universal free-material tariff. No pre-material geometry-only file was saved, so its size is unknown. The observed downloadable material option was 2K, with Shaded and PBR selected; the visible 4K option was unavailable to the Free account.
Material Generate adds an action and unmeasured total wait, not an observed extra charge in this run.
Confirmed material unlocks the 2K PBR and Shaded selections while this tested balance remained 0.5.
Asking for GLB delivered a ZIP
The Hyper3D sequence after geometry confirmation was Material Generate, Material Confirm, select .glb, then Download: four observable actions. SupaVoxel displayed a three-step menu path to its Original size option, but the browser conversion failed at that last action. “Three beats four” would therefore be a misleading delivery claim. The Hyper3D browser actually received a ZIP of 27,809,936 bytes. Its two contained files are not interchangeable: an 18,642,076-byte PBR GLB used for material and geometry measurements, plus a 9,167,608-byte Shaded GLB. If a publishing workflow requires just PBR, it must receive and unpack the ZIP first. The webpage transfer is the ZIP's 27.81 MB, not the extracted PBR member's 18.64 MB.
GLB with PBR and Shaded selected was the actual Export interaction that yielded the verified ZIP.
SupaVoxel's debit has a narrower, stronger identity
The SupaVoxel interface showed “Generate (3 credits)” before the test image was placed into its one primary slot, and still showed 3 after upload. The completed request was matched to the uploaded image's SHA-256 and an independent debit transaction of -3 SupaVoxel credits. This is stronger evidence for this one job than subtracting a shared test-account header balance used across many cases. We did not capture its precise charge moment relative to submission and completion; claiming it billed at either instant would invent a timeline. The transaction establishes what this case cost in its own internal units, while the UI established that its quoted price was visible at the start.
The quoted 3-credit Generate action is present before the image upload.
After loading the matching image, the displayed quote remains 3; the bill is verified by the separate transaction.
The two clocks measure different intervals
SupaVoxel's request was created and last updated 329.805 seconds apart, measured by subtracting its two stored timestamps. That interval includes queue time but excludes the preceding upload and subsequent export. Hyper3D's Gen-1.5 known 56.054 seconds combines only preview generation and geometry confirmation and lacks the material-generation span, interface actions and download. Hyper3D's Gen-2.5 56.930 plus 32.878 seconds are likewise just two stages of a different, blocked run. Comparing 56.054 to 329.805 to declare a 5.9-fold end-to-end speed victory would compare nonmatching phases. The elapsed time from image upload to both completed files was not captured; in particular, no SupaVoxel Original size file completed the browser export.
SupaVoxel's progress and estimated minutes are a waiting-state screenshot, not the measured end-to-end time.
Free account capacity is a limit, not a bulk promise
A new Hyper3D Free account's 5-credit starting grant would fund at most ten 0.5-credit Gen-1.5 confirmations, assuming no Gen-2.5 attempt, other debits or replenishment. This case's zero-debit material stages are not a bulk entitlement. One hundred hypothetical copies at the same charge require 50 Hyper3D credits, not a five-credit Free grant. We neither bought that entitlement nor ran the batch.
The downloadable Gen-1.5 PBR asset is the actual file behind the hypothetical ten-confirmation arithmetic.
The SupaVoxel model shown in the generation workspace; the analysis GLB pictured here was rebuilt locally after Original size browser export failed.
Multiply the right costs, never the wrong currencies
For 100 identical successful jobs at this case's charge, the hypothetical bills would be 50 Hyper3D credits for PBR files if both material stages stayed zero-debit, and 300 SupaVoxel credits. That is not a sixfold dollar comparison: tariffs and entitlements differ, and neither batch was run. The blocked Gen-2.5 debit belongs to this experiment, not every future Gen-1.5 file.
The higher-generation preview was visible; it was not one of the 100 hypothetical downloadable PBR files.
Delivery risk remains on both sides of the ledger
The Hyper3D Gen-1.5 PBR was obtained and independently parsed; its webpage transfer is known. Gen-2.5 was previewed and charged but cannot be called delivered. The SupaVoxel generation itself succeeded and its compressed project source was retained, yet the Original size browser export conversion crashed. A 74,362,796-byte GLB was reconstructed locally from that retained source for analysis; we did not receive those bytes through the site's Original size download action, nor can we promise byte-identical output from a working browser. The downloadable format row in a menu is not a receipt. When budgets require deliverables rather than previews, this single tested workflow favors the actual Hyper3D Gen-1.5 ZIP, while telling a SupaVoxel user to validate the chosen export route before planning downstream work.
SupaVoxel offers Compressed and Original size choices; this test did not successfully save the latter from the browser.
Final verdict: bill a deliverable, not a preview
I would not call Hyper3D's two runs a one-credit tariff. One 0.5-credit Gen-2.5 run led to a blocked Free Download; a separately created 0.5-credit Gen-1.5 model yielded the real ZIP, and its two material steps made no additional debit in this case. The late gate is worth knowing before spending either time or credits. SupaVoxel's single identified request cost 3 of its own credits, visible as a quote before submission, and exposed four model-inspection modes. Its intended Original size browser export failed this time, so the 74.36 MB analysis reconstruction must never enter the ledger as delivered bytes.
For concept inspection, SupaVoxel's one project and visible pre-submit quote matter. For delivering this exact file from the tested browser, reverse the preference: Hyper3D's ZIP is in hand and SupaVoxel's Original size export is not. Neither internal-credit unit translates into the other's cash cost.
Use SupaVoxel for this job
Start with SupaVoxel if you need to quote the 3-credit action up front, generate one tray and inspect its textured and mesh views before deciding whether the knit is worth refining. Test your required download path right away; my Original size attempt crashed. If an actual Free-tier PBR file today is the binding constraint, use Hyper3D Gen-1.5 rather than assuming Gen-2.5's paid preview includes export rights.
How I tested this
Both products received the same independently generated 1,862,608-byte PNG. Hyper3D Gen-2.5 moved from 1.5 to 1.0 credits in its first, download-blocked run; a second Gen-1.5 run held at 1.0 through preview, fell to 0.5 at Geometry Confirm, and held at 0.5 through Material Generate and Confirm. A 27,809,936-byte ZIP was browser-downloaded for that second run. SupaVoxel's −3 debit was linked to the input-matched project transaction; a shared account header is not a case ledger. Its 329.805-second database request interval includes queueing but excludes upload and export; Hyper3D's 56.054 seconds are only known Gen-1.5 preview and geometry-confirm stages, with the material-generation span missing. There is no comparable end-to-end timer, cash conversion or measured hundred-job entitlement. All batch numbers here are one-sample multiplications, not an executed order.
Originally published on Medium: Hyper3D Credits Review 2026: Half a Credit, No Gen-2.5 Download.