> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/properties/effects.md).

# Effects

<figure><img src="https://3019081569-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZBycFFNxrdS0X9OsGtmT%2Fuploads%2Fgit-blob-9916d35a27eab5ee8b2d99e11acf543dee5dd289%2Feffects-overview.png?alt=media" alt="The Effects section in the Properties Panel, below Interactions and Animations"><figcaption></figcaption></figure>

**Effects** let you apply visual effects to a layer directly in PLAY, non-destructively. Instead of baking an effect into the source art in Photoshop or After Effects and re-importing it every time something changes, you apply the effect to the layer in the editor and adjust it whenever you like. The original asset is never modified.

Effects render in the exported playable exactly as they appear in the editor preview.

***

#### Available Effects

* [**Opacity**](/play/properties/effects/opacity.md) - control a layer's transparency, from fully opaque to fully transparent
* [**Color Overlay**](/play/properties/effects/color-overlay.md) - fill a layer's visible pixels with a color or gradient, on top of the art
* [**Color Underlay**](/play/properties/effects/color-underlay.md) - fill a layer's box with a color or gradient, behind the art
* [**Blend Mode**](/play/properties/effects/blend-mode.md) - change how a layer mixes with the layers and background beneath it

***

#### Where to Find Effects

Effects live in each layer's Properties Panel, in the **Effects** section directly below **Animations**. Each layer manages its own effects. A layer can hold several effects at once, one of each type.

Effects are supported on every layer type except hotspots, scenes, components, code layers, games, groups and parent layers.

{% hint style="warning" %}
*Effects are a feature of interactive playables and are not available in Animated Banners.*
{% endhint %}

***

#### Adding an Effect

{% stepper %}
{% step %}

### Select a layer

Select the layer you want to add the effect to and open the Properties Panel.
{% endstep %}

{% step %}

### Click the "+" in the layer's Effects section

This adds an effect module and opens the effect properties popup. The "+" adds the first effect type the layer doesn't have yet, and is disabled once the layer has one of every type.
{% endstep %}

{% step %}

### Choose an effect from the dropdown

The dropdown lists the effect types the layer doesn't already use. Each effect type has its own settings, which appear below the dropdown. Changing the type resets the effect to the new type's default settings.
{% endstep %}

{% step %}

### Configure the effect

The viewport updates as you adjust the effect's settings, so you always see exactly what will render in the exported playable.
{% endstep %}
{% endstepper %}

To remove an effect, click the "-" next to it in the Effects section. Because effects are non-destructive, removing one returns the layer to its original appearance.


---

# 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.craftsmanplus.com/play/properties/effects.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.
