> 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/build/object-details.md).

# Object details

The Details panel on a selected object holds the metadata that reaches the visualizer at render time. Name and description feed the auto-prompt's \[Subjects] block; image reference attaches the visual truth; LoRA gates a fine-tuned model.

![Object Details panel docked on the left side of Build mode showing the Name "Lamborghini Revuelto", a long photoreal-style Description prose, and a Reference images section with Upload and Add from Media Library buttons](/files/UWRuk4o4WJ575wr9rsbc)

## What it does

Without details, every object is "object-N" to the visualizer. With details, the visualizer reads what the object actually is and what it should look like. This is the difference between a render that produces a generic chair and a render that produces the specific Adirondack chair from the brief.

The visualizer stacks these inputs, each overriding the one below: the **3D geometry** is the base, the **image reference** defines the surface on top of it, and the **name and description** – which feed the final prompt – override both. That last point is the catch. A specific name like "Gulfstream G550", or a description that fights the photo, makes the model imagine its own version and override the reference image you attached. Keep the name generic ("private jet") and let the image reference carry the specifics; don't have the description and the reference describe the same thing differently. See [Image reference](/overview/concepts/image-reference.md#what-overrides-what).

## How to use it

Open the contextual menu's **Details** icon (or right-click a row in the [Scene Outliner](/build/scene-outliner.md) → Edit Details). The Details panel docks on the left side of Build mode.

### Reference images (the lever that does the most)

**Spend your time here.** Reference images are the single biggest determinant of brand-true output. Drag a file from your desktop or click **Upload**, or click **Add from Media Library** to pull from existing project assets. JPEG and PNG formats are supported.

Think quality over quantity. A few well-chosen images covering the parts of the object you care about most will outperform a large dump of similar shots. For a car: a three-quarter front, a three-quarter rear, and an interior shot cover more ground than twenty near-identical exterior angles. Each image should contribute something the others don't. More images of the same view doesn't improve results – it overloads the model the same way a too-long description does.

Full guidance on what to attach and why in [Image reference](/overview/concepts/image-reference.md).

Once an image is attached, the object keeps its greyboxed look in the Build viewport, picking up a base color at most. The reference doesn't repaint the object in the viewport; it resolves at render time. The visualizer reads both the image and the rest of the prompt at generation time and renders the object accordingly.

For the conversational shortcut, type the same intent into the AI Composer at the bottom of Build: *"Attach this as a reference image to the chair: \<URL>"*. The composer finds the matching object and attaches the image without you opening the Details panel.

### Name

Short, descriptive. Reads into the auto-prompt verbatim. Naming an object "Adirondack chair, weathered teak" feeds the visualizer that exact phrase. Naming it "object-7" feeds nothing useful.

For characters specifically, vanilla names hold their look better than descriptive names – see the naming tip in [Image reference](/overview/concepts/image-reference.md#tips-that-level-up-the-result). The image reference does the heavy lifting on look; the name keeps that look from drifting between renders.

### Description

Longer prose. One to three sentences max. Used by the visualizer when the name alone isn't enough. Example: a Jeep object whose name is "2024 Bronco" and whose description is *"matte olive green paint, lifted suspension, light bar, winch, tow hooks, black beadlock wheels"*.

{% hint style="info" %}
Long descriptions get truncated by the visualizer. Keep it under a few hundred characters. **If you have more to say, attach a reference image instead.** The model honors images more strongly than long prose.
{% endhint %}

### LoRA

For objects where you need a fine-tuned model rather than (or alongside) a reference image. LoRAs are attached via the contextual menu's **More Options (⋯) → Add LoRA** action on the selected object, not from this Details panel. Upload a LoRA file or paste a URL, and set a trigger word if your LoRA was trained with one.

Reference images cover most use cases with less work. Reach for LoRAs when you need consistent style across many renders or when the team has an internal trained model that already encodes the look. See [LoRAs](/build/loras.md).

## How details flow into the render

```mermaid
flowchart LR
    A[Object in scene] --> B[Name field]
    A --> C[Description field]
    A --> D[Image reference]
    A --> E[LoRA]
    B --> F[Visualizer Subjects block]
    C --> F
    D --> F
    E --> F
    F --> G[Diffusion model]
    G --> H[Render that honors the object]
```

The auto-prompt assembles all four fields into the \[Subjects] block. The model receives the prompt text plus, if attached, the image reference and the LoRA file at generation time.

## Common mistakes

* **Empty names.** A scene of "object-1" through "object-23" produces a prompt full of "object" mentions and a confused render. Rename anything that's a hero or a recurring character.
* **Description duplicating the name.** Skip it. If the name is "matte olive 2024 Bronco" the description doesn't need to repeat the model.
* **Too many redundant images.** Attaching 30 images of the same car from slightly different angles doesn't improve the result – it overloads the model. Pick the angles that cover the surfaces you care about and stop. Fewer, better images outperform many mediocre ones.

## Related

* [Working with objects](/build/working-with-objects.md)
* [Image reference](/overview/concepts/image-reference.md)
* [LoRAs](/build/loras.md)
* [How the visualizer thinks](/overview/concepts/how-the-visualizer-thinks.md)
* [Auto-prompt](/visualize/auto-prompt.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.intangible.ai/build/object-details.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.