> For the complete documentation index, see [llms.txt](https://animoia.gitbook.io/animoia-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://animoia.gitbook.io/animoia-docs/guide/project-and-file-workflow.md).

# Project and file workflow

## New project

Choose **File > New** or use the configured **New project** shortcut. Animoia asks before replacing the current project because unsaved work will be lost. A new project contains one empty 1920×1080, 30 fps, 10-second composition named `Comp 1`.

## Open project

Choose **File > Open project file** and select a `.moia` file. Ordinary media can be stored as file references to keep projects small; image sequences converted to videos and SVG assets remain embedded.

{% hint style="warning" %}
**Warning:** If referenced media has moved, the project still opens but that asset remains offline until you right-click it and choose [**Re-import from File**](/animoia-docs/guide/project-panel.md#project-item-actions)**.**
{% endhint %}

## Save, Save As, and Save Increment

**Save project file** overwrites the current file on disk or asks for a destination the first time. **Save As…** always asks for a new destination. **Save Increment** appears after the project has a filename and writes a numbered copy, then continues work in that copy. The status bar adds `*` after the filename while changes are unsaved.

## Pack Project

**File > Pack Project** writes a single `.zip` containing everything the project needs, and is the right way to archive a project or hand it to someone else.

Everything sits inside a single top-level folder, so unzipping never scatters files into whatever directory you happened to be in:

```
<name>/
  <name>.moia    fully self-contained project, all media embedded
  assets/        the original media, browsable
```

{% hint style="info" %}
**Tip:** Packing is the most reliable way to hand a project over, because it does not depend on file references at all. A plain `.moia` may still point at media on your own disk; a packed project never does.
{% endhint %}

## Autosave and closing

Animoia restores its autosaved session during startup, and **File > Restore Last Session** brings that autosave back on demand — useful if you started something new and want the previous session again. Closing a project with unsaved changes offers **Save**, **Don't Save**, and **Cancel**. `Enter` chooses Save; `Escape` cancels closing. If a render is active, Animoia instead offers **Keep Rendering** and **Stop and Close**; there is deliberately no destructive Enter shortcut.

## GPU frame cache readout

The File menu carries a live meter showing how much of the GPU frame-cache budget is in use, as `used / budget` in gigabytes. Both numbers come from the cache that actually performs eviction, so the readout reflects real pressure rather than an estimate: when it sits near the budget, cached frames are being evicted and previews will re-render more often. Raise or lower the budget itself under [Performance preferences](/animoia-docs/guide/preferences.md#performance).


---

# 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://animoia.gitbook.io/animoia-docs/guide/project-and-file-workflow.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.