> For the complete documentation index, see [llms.txt](https://support.skylum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.skylum.com/luminar-for-web/how-to-use-luminar-for-web/editing-tools/creative/light-depth.md).

# Light Depth

**Light Depth** adds natural depth and dimensional lighting to your photo using AI-powered depth mapping. It analyzes the scene to distinguish between near and distant areas, helping you shape the light and create a stronger sense of depth.

**How to Use:** Select Light Depth and increase the **Amount** slider to apply the effect. Use the marker on the **depth map** to position the effect within the scene, then adjust **Softness** to control how smoothly it blends across different depth areas.

**When to Use:** Ideal for adding dimension to flat or evenly lit photos, creating more separation between the subject and background, or guiding attention toward a specific area of the image.

{% hint style="success" icon="circle-info" %}
**Pro Tip:** Keep the effect subtle for a natural result. A moderate Amount combined with higher Softness can create depth without making the lighting look artificial.
{% endhint %}


---

# 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://support.skylum.com/luminar-for-web/how-to-use-luminar-for-web/editing-tools/creative/light-depth.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.