> For the complete documentation index, see [llms.txt](https://developer.singular.live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.singular.live/singular-basics/building-overlays-in-composer/animating-overlays.md). # Animating overlays Animation is important for creating dynamic and compelling overlays. It defines how an overlay behaves when taken on-air or off-air, or sitting on screen. The three methods of animating in Singular's Composer are: * [Timeline animations](#timeline-animations) * [Behavior animations](#behavior-animations) * [Update animations](#update-animations) ### Timeline animations The most important and necessary of the three types of animations is the timeline animation. Timeline animation defines what an overlay does when taken on and off air. Does an overlay fade, slide, or twirl when you take it on or off air? [Click here for a tutorial on how to create timeline animations](/singular-basics/building-overlays-in-composer/animating-overlays/how-to-create-timeline-animations.md). ### Behavior animations Behavior animations allow you to add looping animations to Composer elements. This is useful for adding things like a flare or other living holds to an overlay. The purpose of behavior animations is to make overlays more alive while they are on-air. How do your overlays behave on air? [Click here for a tutorial on how to create behavior animations](/singular-basics/building-overlays-in-composer/animating-overlays/how-to-create-behavior-animations.md). ### Update animations Update animations are triggered when new data is pushed to overlays. If an update animation is enabled, any new information sent to your overlay will update with an animation of your choosing. Think of a fade out and then a fade in when the score of your favorite sports team goes from 0 to 1 on the scoreboard. [Click here for a tutorial on how to create update animations](/singular-basics/building-overlays-in-composer/animating-overlays/how-to-create-update-animations.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://developer.singular.live/singular-basics/building-overlays-in-composer/animating-overlays.md?ask=&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.