Text to 3D: One Prompt, Every Engine
Write a description with a form, a size and a material, run it on the local engine and any configured third-party engine, and compare the meshes before you spend more credits.
How a prompt becomes geometry
Text is turned into a shape first and a surface second. The engine fixes a silhouette and a scale, builds the volume, then unwraps UVs and bakes PBR maps on top. That order matters: if the silhouette is wrong, no amount of texture quality will save the model, which is why Speed mode exists as a cheap first pass.
The pipeline is reported stage by stage — geometry, UV unwrap, texturing, finalising — so a slow generation is visibly slow in one specific stage rather than looking stalled.
| Item | Speed mode | Quality mode |
|---|---|---|
| Typical use | Shape and composition checks | Final asset for export |
| Geometry detail | Lower face budget, simpler surfaces | Higher face budget, denser surfaces |
| Credit cost | Base cost, about 10 credits | Higher base cost |
| What to do next | Keep the framing, rerun in Quality | Add texture or HD texture, then export |
Prompts that reconstruct well
A prompt that works names the object, its style, its material and its scale. "A cast-iron frying pan, 260 mm across, thick rim, worn seasoning on the cooking surface, game-ready" gives the engine four independent decisions it can get right. "A cool pan" gives it none.
Abstract briefs fail in predictable ways: gnarled or furry shapes collapse, very thin parts disappear, and anything that depends on a mechanism — hinges, threads, moving joints — usually needs to be modelled as separate parts.
When one engine is not enough
Engines differ on hard cases. One returns a cleaner low-poly silhouette, another keeps fine relief detail, a third textures better on a flat prop. Sending the same prompt to several engines and keeping one result turns that variance from a re-roll into a choice — and the credit pool is shared, so you are not paying for three subscriptions to find out.
From prompt to a file your tool reads
GLB for the web and engines
geometry, PBR materials and textures in a single file that three.js, Unity and Unreal import directly.
STL or 3MF for printing
STL is the universal handoff; 3MF keeps units, colour and several objects in one archive.
OBJ with MTL for DCC tools
text-based and editable, with a companion material file for Blender, Maya or ZBrush.
PLY for scans and dense meshes
per-vertex colour and custom properties when the target pipeline expects scan-style data.
Frequently Asked Questions
How long should a prompt be?
One or two sentences is enough. Name the object, the style, the material and a size. Longer prompts help only when they add decisions the engine can act on, such as wall thickness or a flat base.
Should I write the prompt in English?
Most engines score better on English prompts, and the prompt box says so. Chinese prompts work but often need the material and dimension spelled out more explicitly.
Why did one engine return a better mesh than another?
Engines optimise for different targets — low-poly silhouette, fine relief, or texture quality on flat surfaces. That is the reason multi-model mode exists: it makes the difference visible on your own input instead of in someone else's gallery.
Can I turn a text generation into a printable part?
Often yes, for solid single-piece objects. Check the watertight and manifold flags, then export STL or 3MF. Thin or hollow shapes may need wall thickness adjustments in the editor before slicing.
Do I lose the prompt if I switch engines?
No. The mode, style preset, texture options and prompt stay filled in when you change engine, so a comparison run is one click rather than retyping.