> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/design-process/materials-and-textures/basic-materials/opacity.md).

# Opacity

Adjusts the transparency of a material. A value of 100 makes the material fully opaque, while lower values make it more transparent.&#x20;

A black-and-white opacity texture can be imported, where black represents full transparency and white represents full opacity.<br>

Opacity supports two blending modes: **Blend** and **Mask:**

* **Blend** provides smooth transitions between transparent and opaque areas
* **Mask** works on a binary principle, meaning it does not produce intermediate transparency levels like Blend mode. It is particularly **recommended for AR**, as it ensures decals and textures display correctly.\
  Using Mask mode ensures that transparent areas do cast **shadows**, unlike Blend mode, where partial transparency prevents proper shadow formation. \
  Additionally, Mask mode improves **performance** by simplifying rendering calculations.&#x20;

The **Invert** option reverses the texture colors, turning white into black and vice versa.

{% embed url="<https://vimeo.com/769964397>" %}

* Linear gradient — HEX, RGB
* Radial gradient — HEX, RGB
* Texture — JPG, PNG, SVG, WebP
* Animation — Lottie, GIF, MP4
* Figma frame — [Figma frames import](/documentation/importing/figma-frames-import.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.vectary.com/documentation/design-process/materials-and-textures/basic-materials/opacity.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.
