> 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/control-lighting-in-renders.md).

# Control lighting in renders

How to control lighting in AI renders with Visualize lighting presets, and how the Build-mode sun and time of day feed the render when no preset is set.

Pure prompt tools roll the dice on lighting. "Golden hour" generates an approximation of golden hour, sometimes. "Stormy night" generates whatever the model's training data clustered under that phrase. The lighting drifts between renders even when the prompt doesn't.

Render lighting in Intangible comes from two places. Every render starts from a capture of the shot as the 3D viewport draws it, sun, shadows and sky included. With no preset set, that capture decides the light: a low orange sun in Build renders as a sunset. Pick a preset in the **Lighting Presets** picker in Visualize and the preset decides instead: the same low-sun scene with a midday preset renders as bright midday.

So the move is: pick the preset when you want control or a matching sequence. Without one, the Build sun is your lighting, and the viewport is a fair preview of it.

## Steps

1. **Switch to Visualize mode and open the Lighting tab.** The Visualizer panel on the right has Scene / Style / **Lighting** tabs. Click Lighting. This is the surface that controls rendered lighting.
2. **Pick a preset.** The picker opens a grid of dozens of named atmospheres covering times of day, weather, and locations. Each preset is a named lighting look the model has been tuned to honor; the in-product picker is the source of truth for the current set. See [Lighting presets](https://help.intangible.ai/visualize/lighting-presets.md).
3. **Filter to find the right one.** The filter row supports time of day, environment, and location filters, plus a search field. Faster than scrolling.
4. **Apply the same preset across shots.** Consistent lighting in a sequence comes from reusing one preset, not from any Build setting. Pin the preset and reapply it shot to shot.
5. **Render.** The preset is what lit it.

Without a preset: in Build, open Environment mode from the sun icon and set **Time of Day** on the **Main Light** panel. The sun position and color temperature change in the 3D viewport, and a render with no preset follows them. Once a preset is set, the preset wins. See [Environment](https://help.intangible.ai/build/environment.md).

## Where render lighting comes from

Render lighting is interpretive, and it's the preset's job. The preset feeds the model detailed lighting prose without you writing it: mood, color cast, the way fog reads, atmospheric perspective. The preset can change per shot if the brief calls for it.

Build's sun reaches the render through the capture. The image model starts from the shot as the viewport draws it, so the sun's direction, its color and the shadows it casts are in that picture. With no preset, the render keeps them. With a preset, the preset's prose relights the scene and the Build sun stops deciding the look. Ground color comes through the same capture: the vision model reads it as a material (green as grass, gray as asphalt). See [Environment](https://help.intangible.ai/build/environment.md) for that detail.

## Tips

* **The lighting preset picker is much richer than the docs imply.** Filter by location ("Coastal", "Urban", "Forest") to find atmospheres that fit the scene. Try presets you wouldn't pick by name – the thumbnails surface options the search wouldn't find.
* **Custom Styles can override the lighting preset.** If a brand has a specific lighting language (warm and overexposed, cool and shadowed), build a [custom style](https://help.intangible.ai/visualize/custom-styles.md) and apply it instead of a preset. The custom style takes precedence.
* **Consistent lighting across a sequence comes from the preset.** Reuse the same preset shot to shot. Without one, each render reads the Build sun again, and the model's reading of it can drift between renders.

## Limits

* **No manual key/fill/back light placement.** Intangible doesn't expose individual light sources for placement (no three-point lighting rig). Render lighting is set holistically through the preset.
* **Preset behavior varies by image model.** Some models honor the lighting preset prose more tightly than others. If a preset isn't reading on a render, switch the image model.
* **No environment animation within a shot.** Sun position and time of day are scene-level, so drive lighting changes with the preset, and to vary the look across a sequence, change the preset per shot or render variants and cut between them. See [Animation and shot time](https://help.intangible.ai/learn-more/concepts/animation-and-shot-time.md).

## Related

* [Lighting presets](https://help.intangible.ai/visualize/lighting-presets.md)
* [Render an architecture model with AI](https://help.intangible.ai/learn-more/how-to/render-an-architecture-model-with-ai.md)
* [Environment](https://help.intangible.ai/build/environment.md) – Background, Main Light, Ambient Light, Shadows, Terrain.
* [Fog](https://help.intangible.ai/build/fog.md) – haze placed as objects, viewport only.
* [Custom styles](https://help.intangible.ai/visualize/custom-styles.md)
* [Style presets](https://help.intangible.ai/visualize/style-presets.md)
* [Models](https://help.intangible.ai/visualize/ai-models.md)
* [Controlling AI output](https://help.intangible.ai/learn-more/concepts/control-ai-output.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/control-lighting-in-renders.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.
