> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/gum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/gum/gum-tool/animations.md).

# Animations

The **Animations** tab lets you create state-based animations — timelines that move an element between its [States](/gum/gum-tool/tutorials-and-examples/intro-tutorials/states.md) over time. An animation is a sequence of keyframes, where each keyframe applies one of the element's states at a particular point in time, and Gum interpolates between them during playback.

By default the **Animations** tab is hidden. To show it, select **View** ▸ **View Animations** from the main menu.

{% hint style="warning" %}
**TODO:** Screenshot of the **Animations** tab.
{% endhint %}

## Creating Animations

Animations are defined per element (Screen, Component, or Standard element) and are saved alongside that element. For a step-by-step walkthrough of creating an animation, adding keyframes, looping, and nesting animations inside one another, see the [Animation Tutorials](/gum/gum-tool/tutorials-and-examples/animation-tutorials.md).

## Named Events

The **Add Named Event** option places a named marker at a point in time on an animation.

{% hint style="info" %}
**Named Events** are not used by Gum's own runtimes (MonoGame, KNI, FNA, raylib, SkiaSharp, Silk.NET) — they are saved and loaded but never raised. They exist for integration with FlatRedBall (FRB1). Unless you are using Gum with FlatRedBall (FRB1), you can ignore the **Add Named Event** option.
{% 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 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://docs.flatredball.com/gum/gum-tool/animations.md?ask=<question>&goal=<endgoal>
```

`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.