> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/learn-more/how-to/import-from-blender-maya-or-houdini.md).

# Import from Blender, Maya, or Houdini

How to import 3D models from Blender, Maya, Houdini, Cinema 4D, or Unreal into Intangible for AI rendering. Smart Import for FBX, OBJ and GLB.

To bring a Blender scene into Intangible, export it as GLB, the most reliable path, or as FBX, then import it.

Pure prompt tools can't ingest a 3D file. The brief came with a client CAD asset; the prompt tool has no way to use it. The agency's existing pipeline lives in Maya or Blender; the AI tool acts like the pipeline doesn't exist. Workflows fork, time gets lost on rebuilding what already exists.

Intangible's Smart Import takes the common 3D exchange formats from any DCC, FBX, OBJ and GLB, and lands them in the scene. Smart Import does the cleanup work that usually eats an hour: scale correction, axis alignment, category metadata, sometimes light unwrapping. The asset is ready to compose against in minutes, not after a day of cleanup.

## Steps

1. **Export from your DCC in a supported format.** FBX is the most common. OBJ for static geometry, GLB for web-aligned exports.
2. **Bring the file in.** For a new project, add it on Home with your prompt and the agents use it. In an open project, upload it from the canvas's bottom toolbar, or open Build and import it from the asset library to place it in a scene.
3. **Drag the file into the viewport, or use Import Asset.** The Asset Library's footer has an **Import Asset** button. Drop or pick the file.
4. **Smart Import opens an editing environment.** A new view shows the imported geometry in isolation, with controls for:
   * **Scale** – auto-detected, but adjustable. A Maya export at 1 cm and a Blender export at 1 m need different scale corrections.
   * **Orientation / Up axis** – check which way is up. If the model arrives lying down or facing the wrong way, turn it upright here, before it moves into the asset library. You don't need to change your DCC's export axis settings first.
   * **Category** – tag the asset (Vehicle, Character, Furniture, Set Piece). Used by populators and the asset library's filters.
5. **Confirm and import.** The asset lands in the scene at the cursor or center, and is added to **My Assets** in the Asset Library for reuse in this project and others.
6. **Optionally attach an Image Reference.** Open Object Details on the imported asset and attach a hero photograph. The geometry provides the shape; the reference provides the surface. Together they're the brand-true workflow.
7. **Compose and render.** Treat the imported asset like any other library asset. Position, frame, render in Visualize.

## DCC-specific notes

* **Blender** – use **File → Export → FBX** with default settings. If the model arrives on its side, turn it upright in the editing environment. Materials don't carry through – the model arrives gray; attach an Image Reference for surface.
* **Maya** – **File → Export Selection → FBX**. Y-up by default. Bake transforms before export to avoid scale surprises.
* **Houdini** – **File → Export → ROP FBX Output**. Multi-asset exports work, but consolidating to a single FBX simplifies the import.
* **Cinema 4D** – **File → Export → FBX**. Watch for axis flipping; the Smart Import editing environment lets you correct.
* **Unreal Engine** – exports via Datasmith or FBX. For Unreal-bound work specifically, think about whether you're going Intangible → Unreal (USD export from Intangible) or Unreal → Intangible (FBX import here). Both directions work.

## Why this works

Smart Import does the boring half of asset onboarding so you can spend time on the brief instead of the import. Scale correction, axis alignment, category metadata – work that used to live in a hidden cleanup pass is exposed and quick.

The imported asset becomes part of the structured scene the visualizer reads. Geometry, position, scale, orientation – all passed to the model as input alongside the prompt. The render reflects the actual asset's shape, not a generic interpretation.

## Tips

* **Prefer GLB when you can.** OBJ and FBX can carry hidden nodes and cruft that trip the importer. A Blender → GLB export is the most reliable path and almost never fails on import; if an FBX or OBJ misbehaves, convert it to GLB through Blender and try again.
* **Bake transforms in your DCC before export.** Especially for animated assets or rigs. Frozen transforms import cleaner than world-space matrices.
* **Strip what you don't need.** A 5-million-poly architecture model is over the 2-million-vertex cap and won't import, and a model near the cap imports slowly. Decimate or LOD-down in your DCC if the brief doesn't need every triangle.
* **Group sensibly.** A vehicle as a single FBX with body / wheels / interior as nested groups imports cleanly. The same vehicle as a hundred unparented meshes is harder to work with.

## Limits

* **No animation import yet.** Smart Import handles geometry and basic transforms, not skeletal animation or simulation cache. Animate inside Intangible's Compose mode for shot-bound animation.
* **Materials don't carry through.** All imported models arrive as gray meshes – materials are stripped on import regardless of format or shader type. Attach an Image Reference for surface fidelity. The geometry is reliable; the surface is what the AI render fills in.
* **Animation doesn't import.** A skinned GLB or FBX keeps its skeleton and lands as a character you can pose, but its animation stays behind. Animate it in Compose.
* **A model over 512 MB or 2 million vertices is rejected.** Decimate first.

## Related

* [Import your own models (reference)](https://help.intangible.ai/build/import-your-own-models.md)
* [Generate a 3D model from an image](https://help.intangible.ai/learn-more/how-to/ai-3d-model-from-image.md) – when you don't have a CAD file, generate one from a photograph instead.
* [Match a client's product exactly](https://help.intangible.ai/learn-more/how-to/brand-true-ai-render.md) – the full agency workflow.
* [Supported file formats](https://help.intangible.ai/learn-more/reference/supported-file-formats.md)
* [Render an architecture model with AI](https://help.intangible.ai/learn-more/how-to/render-an-architecture-model-with-ai.md)
* [Blender MCP and Intangible MCP](https://help.intangible.ai/intangible-mcp-agents/what-your-agent-can-do/blender-mcp-and-intangible-mcp.md) – what each agent server does, and how a Blender model moves across.
* [Image reference](https://help.intangible.ai/learn-more/concepts/image-reference.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.intangible.ai/learn-more/how-to/import-from-blender-maya-or-houdini.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
