# 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 Aderondack chair from the brief.

## 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. No hard limit on count, but up to around 10 reference images per object is the recommended range for multi-view references (front, three-quarter, side, and so on). Full guidance on what to attach and why in [Image reference](/overview/concepts/image-reference.md).

Once an image is attached, the gray-boxed object updates in the viewport to match. 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 – "Mark" beats "pirate captain" for cross-shot consistency. 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.
* **Image reference at the wrong scale.** Use a reference that shows the whole object cleanly. A close-up of a wheel doesn't help the model render the whole car.

## 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: 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:

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

The question should be specific, self-contained, and written in natural language.
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.