Hunyuan3D Space Ecosystem
This hub exists to separate the real Hunyuan3D-2.1 ecosystem from the noise around it. The screenshot cluster includes a few genuinely different workflows, but a large share of the visible Spaces are mirrors, forks, or thin wrappers around the same core demo.
Main grid
11
Screenshot-linked Spaces worth mapping directly on the page.
Clone cluster
5
Entries that mostly republish the same Hunyuan3D-2.1 shell.
Expansion picks
2
Spaces that deserve full briefs before any more clones do.
Core read
How to use this page
Treat this as an ecosystem map, not a flat list of demos. The point is to understand which screenshot links add a new workflow and which ones simply keep Hunyuan online under another owner.
Official source
The canonical Tencent demo matters as the reference point, even when it is not healthy enough to use inline.
Official publisher Space
tencent/Hunyuan3D-2.1
This is the canonical Tencent demo, but it was paused and flagged when rechecked on March 26, 2026, so it works better as the reference node than as the live demo anchor.
Evidence date: 2026-03-26
Open SpaceMirror and clone cluster
These entries mostly repackage the same Hunyuan3D-2.1 demo shell, so they belong in one cluster instead of becoming separate model briefs.
Straight mirror clone
painter3000/Hunyuan3D-2.1
A close-running clone of the official Hunyuan3D-2.1 Space that keeps the same demo framing instead of adding a distinct workflow.
Evidence date: 2026-03-26
Open SpaceBranded mirror clone
Gemini899/Dream-Hunyuan3D-2.1
Another live clone that stays very close to the official Hunyuan3D-2.1 shell and therefore adds availability, not a new product layer.
Evidence date: 2026-03-26
Open SpaceClone with runtime failure
Bton/Hunyuan3D-2.1
This clone still points at the same Hunyuan3D-2.1 app shape, but the Space was failing at runtime on the latest recheck.
Evidence date: 2026-03-26
Open SpaceClone with build failure
victor/Hunyuan3D-2.1
Another near-direct clone of the official demo, except this one was stuck in a build failure instead of exposing a usable app.
Evidence date: 2026-03-26
Open SpaceWhite-label mirror
duranponce/ai-default
A branded Hunyuan3D-2.1 mirror that republishes the Tencent app and README shape under another identity rather than adding new generation logic.
Evidence date: 2026-03-26
Open SpaceWhy this stays one cluster
The mirror group is useful as availability evidence, but not as a pile of new model briefs. Most of these pages reuse the same Hunyuan3D-2.1 demo shell, the same linked model IDs, and in some cases the same README almost verbatim. They belong here as one ecosystem pattern, not as five separate editorial destinations.
Derivative workflows
These are the spaces that actually add a new product layer, pipeline step, or use case on top of Hunyuan.
Derivative character pipeline
aptol/genshin
This Space uses Hunyuan3D-2.1 inside a larger pipeline for pixel-to-Genshin character conversion, redraw, multi-view processing, and downstream rigging steps.
Evidence date: 2026-03-26
Open SpaceThin inference wrapper
mfurkanyener/hunyuan3d-demo
A much thinner wrapper that calls the Hunyuan3D-2.1 model endpoint directly, useful as ecosystem evidence but not nearly as differentiated as the stronger workflow spaces.
Evidence date: 2026-03-26
Open SpaceHybrid relightable 3D workflow
luh0502/NeAR
NeAR combines a TRELLIS-style relightable pipeline with optional Hunyuan geometry generation, making it the strongest screenshot-linked example of a genuinely different downstream workflow.
Evidence date: 2026-03-26
Open SpaceBackend and service wrappers
These entries are operational wrappers, not creator-facing demos. They still matter as ecosystem evidence, but not as standalone model pages.
Backend service wrapper
HKBUniverse/riasad_fyp_backend
This entry exposes a VR image and 3D object generation backend that references Hunyuan3D-2.1, but it behaves like an application service, not a public creator-facing demo.
Evidence date: 2026-03-26
Open SpaceBackend service mirror
risuwu/riasad_fyp_backend
A mirrored backend wrapper of the same service idea above, useful to map the ecosystem but not something that deserves a normal model brief.
Evidence date: 2026-03-26
Open SpaceBest next briefs
The next detailed pages should explain the strongest derivative branches, not keep cataloging mirrors. That means prioritizing the spaces that actually change the Hunyuan pipeline or introduce a different downstream capability.
Priority follow-up
This Space uses Hunyuan3D-2.1 inside a larger pipeline for pixel-to-Genshin character conversion, redraw, multi-view processing, and downstream rigging steps.
Review the SpacePriority follow-up
NeAR combines a TRELLIS-style relightable pipeline with optional Hunyuan geometry generation, making it the strongest screenshot-linked example of a genuinely different downstream workflow.
Review the SpaceExcluded from the main grid
This section keeps screenshot-adjacent items visible without pretending they belong in the main Hunyuan3D Space grid.
BenjaminPittsley/ai-specialist-trainer
This Space is a trainer for custom AI assistants and only mentions Hunyuan3D alongside other tools, so it should stay outside the main Hunyuan3D ecosystem grid.