How I built a pipeline that turns text prompts into printable 3D objects in under 60 seconds — handling mesh repair, manifold enforcement, and format conversion automatically.
AI-generated 3D models look compelling on screen but almost never survive contact with a printer. The gap between "good render" and "printable mesh" is where most text-to-3D pipelines fail.
AI-generated models have open edges, non-manifold geometry, and inverted normals. They look right in the viewer but fail every slicer check.
Different AI models output different formats (GLB, OBJ, PLY). Printers need STL. Manual conversion is tedious and error-prone.
Using multiple AI 3D generators means juggling different UIs, APIs, and workflows. No single entry point for text-to-printable pipeline.
A browser-based pipeline that chains AI generation, mesh repair, and format conversion into a single seamless flow.
The pipeline supports multiple AI 3D generation engines, with automatic fallback and quality-based routing. Results are cached and versioned.
The critical step that makes AI-generated models actually printable. Automated manifold enforcement, hole filling, and format conversion.
User Input (Text Prompt)
├── "a geometric owl sculpture, 10cm tall"
├── Engine Selection (auto or manual)
│ ├── Tripo AI — quality mode (slower, better detail)
│ └── Hunyuan3D — speed mode (faster, lower quality)
├── AI Generation
│ ├── Returns: raw mesh (GLB/OBJ)
│ └── Cached for repeat requests
├── Mesh Post-Processing
│ ├── Manifold enforcement
│ ├── Hole filling & edge repair
│ ├── Normal recalculation
│ └── Triangle decimation
├── Format Conversion
│ ├── STL (printers)
│ ├── OBJ (editors)
│ └── GLB (web viewers)
└── Output to User
├── Download printable file
├── Preview in 3D viewer (WebGPU)
└── Print settings suggestion
Real metrics from a production text-to-printable pipeline.
From text prompt to printable STL in under 60 seconds
STL for printers, OBJ for editors, GLB for web viewing
Tripo AI (quality) + Hunyuan3D (speed) with auto-routing
Manifold, fill, normals, decimation — all automated
Browser-based 3D preview before download
All post-processing runs in the browser — no server load
ESM imports, no build step, deploys by rsync
Full bilingual interface
A complete text-to-printable pipeline — not just generation, but production-ready output.
Describe what you want in natural language. The AI generates a complete 3D model. Supports detailed specifications like dimensions and style.
AI-generated meshes are never print-ready. The repair pipeline automatically fixes open edges, non-manifold geometry, and inverted normals.
Export as STL (printers), OBJ (3D editors), or GLB (web). Each format is optimized for its target use case.
WebGPU-powered 3D viewer in the browser. Orbit, pan, zoom, and inspect the model before downloading.
Generate the same prompt with both engines side by side. Compare results before choosing which to download.
The entire pipeline runs as a client-side SPA. No backend, no database, no queue. AI APIs are called directly from the browser.
Mesh repair is computationally expensive. Running it on the server would mean provisioning GPU instances, managing queues, and paying for idle time. Running it client-side means zero server cost and instant scaling — every user brings their own compute.
Mesh repair, format conversion, and 3D preview all run in the browser. The only server cost is static file hosting.
Every user's browser does the work. No queue, no throttling, no provisioning. The pipeline scales with zero infrastructure changes.
User's 3D models never touch the server. Processing happens locally. The AI API receives only the text prompt — not the user's IP or identity.
I build AI-powered generation pipelines that bridge the gap between "AI can do it" and "it actually works in production." From text-to-3D to custom generation workflows.