> 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/overview/how-to/control-lighting-in-renders.md). # Control lighting in renders 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 lives in one place: the **Lighting Presets** picker in Visualize. Pick a preset and the model lights the render to match. The **Sky** and **Time** controls in Build don't reach the render at all. They light the 3D viewport so you can read the scene as you work, and so you can judge which preset fits the look you're after. So the move is: pick the preset. Use Build time-of-day to see your scene, not to light the render. ## 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](/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. Optional, and not a render control: in Build, open **Edit Scene Details** and set the **Time** field (8:30am, 5:30pm, 11:00pm). The sun position and color temperature change in the 3D viewport so the scene reads the way you expect while you build and so you can eyeball which preset to reach for. None of it is passed to the render. See [Environment](/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 Time and Sky are viewport-only. They set where the sun sits in the 3D scene so you can read placement and depth, the same way you'd flood a stage with work lights before the DP lights the shot. The one Build input that does reach the render is ground color, which the vision model reads as a material (green as grass, gray as asphalt). See [Environment](/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](/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, not the Build time-of-day.** Reuse the same preset shot to shot. Changing the Build Time changes your viewport, not the render, so it won't make a sequence match. ## 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, time of day, and fog are scene-level and aren't keyframable today. Since they don't reach the render anyway, 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](/overview/concepts/animation-and-shot-time.md). ## Related * [Lighting presets](/visualize/lighting-presets.md) * [Environment](/build/environment.md) – Sky, Time, Location, Fog. * [Custom styles](/visualize/custom-styles.md) * [Style presets](/visualize/style-presets.md) * [Models](/visualize/ai-models.md) * [Controlling AI output](/overview/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 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/overview/how-to/control-lighting-in-renders.md?ask=&goal= ``` `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.