Image to STL: Hyper3D Rodin Credits and Download Wall

If you're looking for an image to stl workflow, being able to download a usable model matters as much as seeing a preview. This review tracks Hyper3D Rodin's credit charges and file access, then compares the files obtained with SupaVoxel.

Disclosure: this is an independent hands-on test. Both tools were run on ordinary customer accounts; neither company supplied review access or saw this piece before publication.

I did not set out to investigate a paywall. I needed a textured model of a crumpled blue container I could carry out of the product and inspect. Hyper3D’s Gen-2.5 preview appeared; the account had paid 0.5 of its credits; the Download button looked actionable. I clicked it and got a subscription demand. The usable file came only after I ran the image again in Gen-1.5. I kept every balance check and downloaded artifact separate, because the entire buying decision turns on which job actually produced a file.

My verdict in 60 seconds — for a straightforward textured digital delivery, I would take the SupaVoxel GLB rather than gamble on Hyper3D’s Gen-2.5 Free-tier preview becoming a file. That reflects this recorded access path, not a credit exchange rate or a planter-suitability certificate. On the tested Hyper3D Free account, Gen-2.5 used an independently isolated 0.5 Hyper3D credit but blocked its GLB download. A separate Gen-1.5 generation spent another 0.5 Hyper3D credit at Geometry Confirm, then delivered textured PBR and Shaded variants in a ZIP; both material actions cost zero additional credits in this case. SupaVoxel’s matched one-request transaction deducted 3 of its own credits and produced a real 58,065,236-byte Original size GLB. Those denominations do not make SupaVoxel six times the cash cost. If the deliverable is irregular foil as a digital asset, SupaVoxel gives the stronger surface in this pair. If the deliverable is a planter whose first file shows a bottom, Gen-1.5 Hyper3D earns that different choice.

My eight-line decision card is about what reached my drive. Each line separates observed facts from their consequence for a digital-asset workflow:

Gen-2.5 Free-tier file access — Hyper3D blocked vs SupaVoxel’s tested route delivered — a preview is not an export.
Gen-2.5 credit attribution — isolated 2.0→1.5 Hyper3D credits — charged preview, no file.
Gen-1.5 route required — separate Hyper3D generation vs one SupaVoxel request — the detour was real, though avoidable if you choose Gen-1.5 first.
Gen-1.5 confirmed cost — Hyper3D geometry 0.5; material Generate 0, Confirm 0 extra — no fabricated surcharge.
SupaVoxel case debit — one request-linked 3-credit transaction — not an inter-platform price score.
Actual browser delivery — Hyper3D 21.471 MB ZIP vs SupaVoxel 58.065 MB GLB — Hyper3D wins bytes decisively.
Usable exterior irregularity — Hyper3D broad paired folds vs SupaVoxel varied crossings — SupaVoxel wins the visual brief.
Visible planter floor — Hyper3D blue floor vs SupaVoxel through-passage — Hyper3D wins the functional-shape candidate, with no leak test.

The decision turns on which deliverable you need — and whether your plan actually lets you take it away.

What did the Hyper3D balance say before Generate?

The tested Free account was independently checked at 2.0 credits before the case’s Gen-2.5 generation; the Generate tariff displayed 0.5.

The same independently generated 1,647,256-byte PNG went into both products. That controls input bytes, not each product’s preprocessing or plan. Publication/reuse rights to the reference-influenced source remain uncleared. Hyper3D’s Free balance began at 2.0; its assigned account had no other work in the isolated test interval. I checked the balance rather than equating a displayed tariff with a real debit.

Did Gen-2.5 charge at the download click?

During preparation/generation the checked balance still read 2.0; after the preview it read 1.5.

No. The isolated balance changed 2.0→1.5 by completed preview; Confirm and refused download left it at 1.5. Generation took 66.417 seconds and Confirm 21.066, or 87.483 seconds of known server stages, with no second debit. That is not upload-to-export time: no export happened. On this Free account, the charge arrived before the subscription gate. Other plan entitlements remain untested.

Why did one million faces fail my practical test?

Gen-2.5 displayed a million-face preview in the browser; that number belongs to its product panel, not to an inspected download.

The UI claimed 1,000,000 faces and 587,083 vertices. I could not verify that mesh because no Gen-2.5 file arrived; I did not substitute internal preview resources. SupaVoxel’s 1,500,000 triangles were read from its actual GLB. The Hyper3D file analyzed in this series is a different Gen-1.5 generation at 120,000 triangles. A viewer’s preview badge and a parsed downloadable mesh are different evidence classes.

What exactly happened at Download?

After choosing GLB and pressing Download, the Free account was told to subscribe for Gen-2.5; Gen-1.5 downloads remained free.

I used the visible Pack → GLB → Download path. The product explicitly demanded a subscription for Gen-2.5 files after the verified 0.5-credit debit: one charged attempt, zero downloadable Gen-2.5 GLBs on this Free account. Dollar value, subscription price and paid-plan access were not measured. The operational problem is specific: a finished preview and enabled-looking Download control did not deliver a file on this tier.

Was Gen-1.5 a free unlock of that preview?

The image entered a separately configured Gen-1.5 Detail task; this was a new generation, not the former preview converted to an allowed file.

No. Gen-1.5 was a new task; it even auto-described the container as a drinking cup, unlike Gen-2.5’s caption. Its observed preview took 25.955 seconds and left the balance 1.5→1.5. Our two-task route ultimately spent 1.0 Hyper3D credit, but someone choosing Gen-1.5 immediately would avoid the first 0.5-credit detour. Neither its model settings nor its caption matched Gen-2.5 exactly, so visual differences cannot be assigned solely to version.

Where did the Gen-1.5 half-credit go?

Geometry Confirm took 24.499 seconds and changed the isolated Hyper3D balance from 1.5 to 1.0.

Preview plus confirmation took 50.454 seconds, excluding material, upload, pauses and delivery — not “a full PBR in 50 seconds.” The first legal Gen-1.5 geometry GLB was 4,484,160 bytes with zero embedded maps. Comparing that white-stage file to SupaVoxel’s textured 58.07 MB export would be dishonest. I continued through both material actions to obtain a comparable colored file.

Did Material Generate and Confirm cost extra?

The verified balance was 1.0 before the separate material actions and remained 1.0 after both.

After Material Confirm at unchanged 1.0 credits, PBR export was enabled for this case.

Zero additional credits in this run: separately checked 1.0→1.0 across both Material Generate and Confirm. Thus the completed Gen-1.5 PBR file follows one verified 0.5-credit geometry debit here. We did not measure the material stages’ complete durations or prove they are always free. The finished PBR has three 204⁸² PNG maps, unlike its textureless geometry sibling.

How many bytes left Hyper3D’s website?

The tested GLB export with Shaded and PBR selected delivered a ZIP containing two variants, not just the standalone PBR member.

21,471,080 bytes — the full browser ZIP. Inside it is a 14,038,528-byte PBR GLB and a 7,432,300-byte Shaded GLB. The PBR file is what I used for the comparable textured renders and parsed mesh counts. After geometry confirmation, the route was Material Generate → Material Confirm → GLB choice → Download, four recorded interface actions, then extraction to obtain the standalone PBR member. At a hypothetical ideal 12 Mbps, the entire ZIP’s pure transfer floor is 14.31 seconds; if I host only the extracted PBR member separately, its different 9.36-second floor applies. Swapping those denominators would understate the payload a Hyper3D user actually received. There is a real byte win here against SupaVoxel’s chosen Original size branch, even after counting the whole ZIP.

What did SupaVoxel’s own transaction say?

The image-matched SupaVoxel request was linked to exactly one −3-credit transaction; the recorded request interval was 328.196 seconds.

One source-PNG-matched request, one successful outcome, one linked 3-SupaVoxel-credit debit. Its database created-to-updated delta is 328.196 seconds, including its queue and excluding upload and export. That is not equivalent to Hyper3D’s 50.454-second subset of Gen-1.5 preview plus confirm; any full-delivery-speed ranking from these different time windows would be fiction. These are also two different companies’ credits. Multiplying 3 by 100 and 0.5 by 100 creates two ledgers in different units, not a relative dollar price. The SupaVoxel interface estimated five to ten minutes, a forecast consistent with this single request’s narrower lifecycle; it was not a promise of total time to file. I would use the actual transaction for this shared testing account rather than its later top-bar balance, which included other cases.

Did its GLB menu deliver the file in my comparison?

The existing SupaVoxel project was reopened without regeneration and the UI’s Original size option yielded the actual 58,065,236-byte browser blob.

Yes. Export → GLB → Original size produced a real 58,065,236-byte GLB, with 1,500,000 triangles and three 4096 × 4096 PNG maps. This is the one behind the article’s paired model renders. A smaller 8,499,144-byte compressed CDN resource exists for the same task, but nobody in this test measured that as a click on the UI’s Compressed option. A 44,556,092-byte local analysis derivative is not a browser export either. The extra files cannot silently shrink the cost of my selected route. On a hypothetical ideal 12 Mbps line, 58.065 MB takes 38.71 seconds of pure transfer against Hyper3D’s 14.31-second ZIP — a 24.40-second difference before protocol or decoding. Hyper3D wins this part. SupaVoxel’s better irregular foil costs more bytes with this exact export choice.

Does one hundred modeled planters change the bill?

Only as a scenario, not a completed batch. Repeat these exact charges and export selections 100 times, assume no failures or caps: Hyper3D Gen-1.5 implies 50 Hyper3D credits and 2.1471 GB of UI ZIP downloads; SupaVoxel implies 300 of its own credits and 5.8065 GB of Original size GLBs. Those are separate internal currencies and decimal byte totals. If I hosted only extracted Hyper3D PBR members, that would instead be 1.4039 GB; the clients’ browser ZIP transfers do not disappear retroactively. The one-off Free allowance and future account policies are not proven to cover 100 successful exports. Extrapolating Hyper3D’s known 50.454-second preview/confirm subset gives 1.4015 hours, and SupaVoxel’s 328.196-second request lifecycle gives 9.1166 hours, but those clocks omit different stages; they are not rival batch delivery estimates. The calculation helps plan storage while warning me not to invent a throughput winner.

Where does Hyper3D genuinely win the shape decision?

Hyper3D Gen-1.5 shows a blue inner floor in the rendered cavity; no physical leak test was performed.

SupaVoxel’s more irregular model shows white background through the cavity’s lower opening despite a topologically watertight welded shell.

Hyper3D’s blue floor is the better initial geometry if the job is a container candidate. Both meshes are watertight, consistently wound and one face-connected shell after UV welding, but topological watertightness does not mean a pot can hold soil or water. SupaVoxel’s through-passage is visually obvious; it would need a deliberately modeled base before this specific file meets a vessel brief. No print, slicer or water test was done on Hyper3D either, so I will not call its apparent bottom leakproof. The exchange for SupaVoxel’s attractive uneven exterior is therefore unknown base-design and validation labor plus a 58.065 MB Original size file. For a digital prop the missing base may be a simple art-direction change; for an actual planter it is the primary unresolved requirement.

Final verdict: which credit purchase led to a useful file?

My Gen-2.5 Hyper3D half-credit bought a preview but no Free-tier download. Another half-credit on a separate Gen-1.5 run, plus two independently zero-extra-credit material actions, led to a real textured ZIP. The SupaVoxel request’s separate three-credit transaction led to a genuine GLB with stronger irregular folds. Hyper3D gave a smaller download and an apparent interior bottom; SupaVoxel gave the better foil surface and a simpler recorded one-job digital delivery. For the recorded digital acquisition path, SupaVoxel won without erasing the difference between the two deliverables. To quote either as a purchasable, leakproof planter would be getting ahead of every physical test we did not run.

Use SupaVoxel if the deliverable is visual foil first

For an irregular blue foil study you will rotate on screen or edit before fabrication, try your image in SupaVoxel and inspect the actual exported file, not only the result card. This tested route delivered the crossed, uneven folds in the visual brief. If you intend to put soil in it, add a real base-design and leak-validation stage before making promises. If your immediate requirement is an apparently bottomed file on a Free Hyper3D account, go directly to tested Gen-1.5, not Gen-2.5’s gated preview.

How I tested it. I isolated Hyper3D balance changes around each task and material step, matched the SupaVoxel transaction to this exact input’s request, and measured each browser-delivered artifact separately from the extracted PBR member and other derivative copies. Credit numbers are measured within their own services only. Transfer and ×100 scenarios are arithmetic using explicitly stated bandwidth and identical-repeat assumptions. Full upload-to-file elapsed time, cash cost, subscription entitlement beyond this Free account, floor thickness, a successful physical pot and publication rights for the reference-influenced source were not measured.

Also in this series
Hyper3D Rodin Planter Review 2026: A Base Matters More Than a Mesh
Hyper3D Rodin 3D Review 2026: The Foil Folds Turn Into a Mask

Originally published on Medium: Hyper3D Rodin Cost Review 2026: 0.5 Credit, Then a Download Wall.