If you need an stl viewer to judge whether a generated model is more than a preview, this comparison follows Hyper3D Rodin and SupaVoxel from credit charges to downloadable files. It also notes mesh quality and inspection options relevant to print preparation.
Independent review: both products were tested on my own accounts — free where offered and paid where not — with no vendor-provided access.
I tested what it would take to obtain a purple Z-rod cleaner as an actual model, not just a thumbnail. The first Hyper3D preview looked complete. Then I pressed Download. The Free account asked for a subscription after a confirmed 0.5-credit debit, so I ran a separate generation using Gen-1.5.
The separately made Gen-1.5 version did download as a textured PBR model after a different 0.5-credit geometry charge; both material stages showed unchanged account balance in this run. SupaVoxel displayed a 3-credit Generate quote and the request-linked ledger recorded −3 of its own credits. Its Original size GLB actually reached the browser. Credits belong to different plans, so the figures are not a dollar race.
My verdict in 60 seconds — SupaVoxel wins the visible-price, one-project design-to-file route; Hyper3D Gen-1.5 wins the lighter and cleaner starting mesh. SupaVoxel showed “Generate (3 credits)” at the action, delivered one actual Original size GLB and offered four ways to inspect the clip. Hyper3D's Gen-2.5 preview consumed 0.5 of its own credits but could not be downloaded on Free; its separate Gen-1.5 run consumed another 0.5 and delivered a ZIP. If the next step is print preparation rather than choosing a purple visual concept, Hyper3D's zero nonmanifold edges beat SupaVoxel's 412. No cross-service credit-price or end-to-end speed winner follows from this test.
Eight paired observations beside the actual receipts:
- Quote at Generate — Hyper3D: later stage debit recorded · SupaVoxel: 3-credit action visible up front.
- Higher-generation Free route — Hyper3D: charged Gen-2.5 preview, download blocked · SupaVoxel: no matching model-tier route tested.
- Actual file delivered — Hyper3D: Gen-1.5 ZIP · SupaVoxel: Original size GLB.
- Case-attributable charge — Hyper3D: separate half-credit debits on two runs · SupaVoxel: one request-linked −3 transaction in a different unit.
- Material work — Hyper3D: Generate and Confirm after geometry · SupaVoxel: its single completed textured project.
- Tested website payload — Hyper3D: 17.54 MB ZIP · SupaVoxel: 87.17 MB GLB; alternative Compressed size unknown.
- Entitlement surprise — Hyper3D: Gen-2.5 Free download gate appeared only at Download · SupaVoxel: tested Original size export arrived.
- Starting mesh for slicing — Hyper3D: zero nonmanifold edges · SupaVoxel: 412, requiring repair before a solid-volume claim.
Those are observations, not a conversion between credit units, cash prices or comparable end-to-end speeds.
Why did I pay for two Hyper3D runs?
The purple cleaning clip in the input shows a long handle slot and two open U-shaped jaws. Hyper3D received this same 1,529,736-byte image twice, once for Gen-2.5 and once for Gen-1.5; SupaVoxel received the identical file for its own generation. The high-resolution Hyper3D preview was not the file later inspected for file size or print topology. A Hyper3D cost ledger must keep the blocked experimental run separate from the downloadable older-generation file. Likewise, a flat balance before and after several tasks on a shared account cannot identify this specific job. We used the stage observations for Hyper3D and the request-linked SupaVoxel transaction. Claims about monthly subscription pricing, dollar-per-credit conversion, or the economics of unlimited generation are outside the evidence.
The same 1,529,736-byte clip image started two separate Hyper3D generations and one SupaVoxel generation.
When did Gen-2.5 take the first 0.5?
The Hyper3D free-tier screen displayed 5 credits before the Hyper3D Gen-2.5 job. Its High-setting geometry preview completed after 43.822 seconds in the observed service stage; the balance changed from 5.0 to 4.5 when the preview completed. After a separate 15.566-second geometry-confirm stage it remained at 4.5. The case's independently checked debit is 0.5 credit, not a guessed charge calculated from some later mixed balance. The UI later reported 1,000,000 triangles and “Watertight” and “Print-Ready,” but those are preview-side interface claims. Because no file was obtained for this generation, we could not parse that million-face mesh or validate its tags. Paying for a preview and obtaining an export are separate entitlements.
Hyper3D Gen-2.5's preview appeared after its 0.5-credit debit; this screen is not proof of a downloadable file.
When does the download gate appear?
After confirming the preview, we selected .glb and pressed Download. The visible message explicitly required a subscription to download Hyper3D Gen-2.5 models, while stating Hyper3D Gen-1.5 downloads remain free. No Hyper3D Gen-2.5 GLB landed on disk. The 0.5-credit experimental outlay bought a preview in this case, not the artifact needed for topology, file-size or print-fitness tests. This is not evidence of an extra hidden export debit and not a statement about what a paid account can retrieve. It is a measured access boundary on the tested Free account. For a cost-conscious free-tier user, discovering that boundary after the charge is the decisive workflow detail; model-quality claims should not replace the missing file.
The Hyper3D Gen-2.5 GLB click produced a subscription prompt; the debit had already occurred.
Does switching to Gen-1.5 undo the first charge?
We switched to Hyper3D Gen-1.5 and uploaded the same picture again. The balance before this job was 4.5 credits, reflecting the earlier blocked experiment. Its preview stage took 25.480 seconds and, unlike the newer generation's preview, did not change the observed 4.5 balance. This is a specific difference in when the charge appeared in these two runs; it is not an assertion about every account or later policy. The downloaded file's limit of 120,000 triangles belongs to the Hyper3D Gen-1.5 confirmation, not a lossy export of the 1,000,000-triangle Hyper3D Gen-2.5 preview. The automatic descriptions also differed between jobs, so we cannot attribute all visual differences solely to their generation labels.
The independent Hyper3D Gen-1.5 preview arrived while the observed balance stayed 4.5; material work had not begun.
What did Geometry Confirm cost?
Geometry confirmation on Hyper3D Gen-1.5 took 22.898 seconds, and the observed account balance moved 4.5 → 4.0. The independently attributable geometry cost for this task is 0.5 Hyper3D credit. The preliminary downloadable geometry-only GLB was 3,971,968 bytes and had no image textures, so pricing that file as a finished purple PBR model would silently change the product under comparison. There were still two material actions to perform. The geometry stage plus preview totals 48.378 seconds, an accurate number for those two measured stages only. It excludes material processing, idle time between clicks, upload, and final export. Any copy calling 48.378 seconds the total time to a textured GLB would understate the recorded work by 24.055 seconds of material stages alone.
Hyper3D Gen-1.5 Confirm is the observed 4.5-to-4.0 credit event; the preview itself left the balance unchanged.
Was the purple material another charge?
Material Confirm followed and lasted 0.455 seconds in the recorded service stage. Its visible balance also stayed 4.0 → 4.0, with before/after images for both material actions. These are four-point UI balance observations, not an itemized independent invoice for texture generation. The total attributable this-case Hyper3D Gen-1.5 PBR outlay is therefore 0.5 credit: 0.5 at geometry confirmation, with no further balance change across measured material Generate and Confirm. Hyper3D Material Generate took 23.600 seconds and Confirm 0.455 seconds: 24.055 seconds added to the 48.378-second geometry subtotal, for 72.433 seconds of known stages. Again, this is neither stopwatch time from upload to Download nor proof that material costs stay zero for the next hundred jobs.
Hyper3D Material Confirm finished with balance 4.0; only this observed PBR file has a reconciled 0.5-credit total.
What file did the browser actually receive?
After material confirmation, selecting GLB with PBR and Shaded enabled yielded an actual 17,543,700-byte ZIP from Hyper3D. Inside it, the measured PBR model is 10,724,844 bytes with three embedded 2048 × 2048 PNG textures; another member is Shaded. The ZIP and its PBR member answer different cost questions. The actual website download transfers the whole 17.54 MB ZIP, even though a site separately hosting just the PBR model would transfer 10.72 MB. Counting the ZIP as a pair of PBR deliverables, or the earlier untextured 3.97 MB mesh as the final textured file, would corrupt a “price per completed asset” calculation. This tested file is Hyper3D Gen-1.5, never the paywalled Hyper3D Gen-2.5 preview.
The free Hyper3D Gen-1.5 PBR route actually returned 17,543,700 bytes in a ZIP containing the 10,724,844-byte measured model.
Can I compare three credits to half a credit?
SupaVoxel's Hobbyist flow displayed 3 credits at Generate and yielded exactly one −3-credit transaction linked to this generation request. That identified transaction, not a difference between shared account balances, is the basis for the stated 3 SupaVoxel credits. The interface also provided a textured GLB downloaded through Original size. We did not isolate precisely whether that debit occurred at button submission or after completion, so its charge moment is not captured. A “3 versus 0.5” numeric display has no monetary meaning without each service's cash conversion, entitlement rules, and access to equivalent usable artifacts. In fact, the SupaVoxel model in this test had 412 nonmanifold edges after welding; delivery is not the same as immediate suitability for functional printing.
The SupaVoxel generation cost 3 of its own credits; Hyper3D's separate PBR file cost 0.5 of its credits. Neither figure is a cash price.
Was one service genuinely faster?
SupaVoxel's database request lived 259.965 seconds between createdAt and updatedAt. That interval includes queue time but excludes work before request creation and download/export after completion. Hyper3D's 72.433 seconds sums its four individually measured Hyper3D Gen-1.5 processing/confirmation stages, not waiting between clicks, pre-task upload or downloading the ZIP. A direct “Hyper3D is 3.6 times faster” claim would compare unlike intervals and would be unsupported. The earlier 48.378-second Hyper3D subtotal is geometry only; the later 72.433 includes material Generate and Confirm. This difference is especially relevant when comparing two textured deliverables. SupaVoxel's Original size browser export finished after the generation request and is not included in its 259.965-second database lifecycle. Neither side has a measured true wall-clock upload-to-final-file duration.
This SupaVoxel progress screen, unlike a Hyper3D stage timer, belongs to a 259.965-second DB request window, not a measured upload-to-download stopwatch.
What happens if the project needs a hundred clips?
Multiply the single-file charge by 100 and you get 50 Hyper3D credits for Gen-1.5 geometry confirmations—also 50 for PBR if the observed zero-debit material behavior repeated—and 300 separate SupaVoxel credits. These are unlike currencies, not comparable dollars; neither batch ran. The tested Hyper3D Free account began at 5 credits, enough for at most 10 such confirmations without other charges or replenishment. Our blocked Gen-2.5 run already consumed 0.5. The remaining theoretical 90 require entitlement or funding not verified here.
The tested free account began at 5 Hyper3D credits; 100 files were never made or funded.
Final verdict: preview rights are not file rights
The bad surprise was Hyper3D Gen-2.5: 0.5 Hyper3D credit spent, preview on screen, Free-account Download blocked. Gen-1.5 was another run, another 0.5 credit, this time delivering a 17.54 MB ZIP after material stages that showed no further debit here. SupaVoxel showed its 3-credit quote at Generate, recorded one request-linked −3 transaction and gave me an 87.17 MB Original size GLB. The latter still has 412 nonmanifold edges, so file delivery is not fit for use. Two different credit currencies do not make a cash ranking; incompatible stage clocks do not make a speed ranking.
The Gen-1.5 PBR file, unlike the Gen-2.5 preview, was in hand.
For this single-project concept-to-file flow, SupaVoxel's visible quote and completed Original size download earned my workflow preference. Hyper3D Gen-1.5 wins initial mesh cleanliness and file weight—strong reasons to choose it when print preparation or a low-data web page is the next stop. SupaVoxel wins the visible upfront generation quote and lets me inspect the purple prototype without finding a newer-model download gate at the end. The fair trade is between these tested routes, not a pretend sixfold price spread.
Use SupaVoxel for this job
The single-image generation quote was visible before the job began.
If you need a clearly quoted one-image generation and an actual Original size model for appearance review, SupaVoxel delivered those in this run. Open its Mesh view and budget topology repair before quoting a physical cleaner. If you value the lighter downloadable starting solid over the color, use Hyper3D Gen-1.5 instead of assuming the charged Gen-2.5 preview can be exported on Free.
How I tested this
A single independently generated 1,529,736-byte PNG was used across one SupaVoxel job and two separate Hyper3D generations. Hyper3D Free started at 5.0 credits, changed to 4.5 at Gen-2.5 preview completion and did not change again on that confirmation. The independent Gen-1.5 preview left 4.5 unchanged; Geometry Confirm moved it to 4.0; Material Generate and Confirm each left 4.0 unchanged. The SupaVoxel bill is from the exact request-linked −3 transaction rather than a shared account balance. Hyper3D's 72.433 seconds sum four known processing stages, omitting upload, hand-click gaps and export. SupaVoxel's 259.965 seconds span database request timestamps, including queue but excluding upload and export. No equal-window speed comparison, dollar-per-credit conversion, paid hundred-run entitlement or Compressed-export size was measured. The 100-file and CDN numbers are explicit arithmetic scenarios, never actual bulk production invoices.
Originally published on Medium: Hyper3D Rodin Credits Review 2026: 0.5 Spent, Download Blocked.