# My footage and storage

**My footage** collects reusable assets. **Projects** organize specific videos. You can use the same asset in several projects without turning every file into a new project.

In [Storage](https://editorbrain.com/app/storage) you can see your workspace usage and limit, review saved files, free space and choose what to keep after you approve the final. It is available when you are signed in, according to your account permissions.

## What is worth saving

- Headshot, logo and versions of your brand.
- Your own B-roll, demonstrations and real product captures.
- The Instagram profile or header photo for "follow me."
- A closing clip or call to action.
- Photos of the place, team, catalog, offers or facilities.
- Confirmed product facts and terms of use.

Say **when to use it**, what it represents and what to avoid. For example: "Use this header when the close invites people to follow my account. Do not use it for business offers." Archive expired offers so they do not come back.

## Scope and approval

Assets belong to a brand or are deliberately shared in the workspace. A draft asset is not automatically approved footage. The agent checks context, state and conditions before it includes one.

If My footage is empty, it should say so and use the allowed sources, or ask for what is essential according to your preferences. It cannot invent that it found your logo or take another client's.

## Local does not mean uploaded

```sh
editorbrain resources register --file ./portrait.jpg --brand my-brand --kind image --tags headshot,portrait --description "Talking to camera, white background" --moments identity,opening
editorbrain resources register --file ./broll.mp4 --brand my-brand --kind broll --title "Work in the studio" --upload
editorbrain resources search --brand my-brand --query "headshot"
editorbrain resources locate UUID
editorbrain resources attach UUID --project my-project
```

Registering ties an asset to its fingerprint and stores its location **on this computer**: any working folder on the same Mac can find it with `resources locate`. The path never leaves your computer and does not become a public URL. `attach` relates the asset to a project; it does not prove it was already used in the render.

Search is literal: it finds words in the title, description, tags and usage notes. Put the words you would search for in `--tags` and `--description` ("headshot", "portrait", "logo"). If the file was already registered, its data does not change: edit it with `resources get` and `resources save`.

Without `--upload`, the original stays only on your computer. With `--upload` a private cloud copy is also stored, useful for web reviews and agents connected over MCP. Before registering, the agent checks your upload preferences and your storage: if they do not allow an upload, nothing is registered and nothing is uploaded. The limit is 90 MiB per file.

iPhone HEIC photos are registered as they are. With `--upload`, a JPEG copy made on your computer is uploaded (on a Mac, with `sips`), which the web and renders can open. On the web, "Add footage" also accepts HEIC when the browser can open it (Safari); otherwise export it as JPEG or ask your agent to register it.

From a chat connected over MCP, an attached image is first saved on the project (`import_project_attachment`) and then registered in My footage with its fingerprint.

Indexing can store segments, descriptions and times. Reusing a compatible index avoids analyzing everything again. Transcription and visual analysis are different evidence.

## What syncs

`push` and `pull` sync portable documents. Media is uploaded with `assets upload`; it is not uploaded just because it sits in `assets/` or `renders/`.

```sh
editorbrain storage status
editorbrain media preview --file ./renders/final.mp4 --out .editorbrain-local/previews/revision.mp4 --quality 720
editorbrain assets upload .editorbrain-local/previews/revision.mp4 --project my-project --purpose preview
```

This example is the manual preparation. For a recoverable sample in one step, use `production submit --project my-project --file renders/revision.mp4 --title "Sample"`, which prepares, uploads, registers and keeps a receipt for retries. If the file is already registered, reuse it for review. See [Studio](https://editorbrain.com/en/docs/revision).

Upload a light copy only if you need a web review. Keep the original and the master. `original`, `preview`, `final` and `temporary` are not interchangeable labels: they help protect files during cleanup.

## Free up space

Check the status and the files before you choose what to delete. `storage cleanup --ids ... --confirm` requires specific IDs; the server applies its protections. Do not use it as a "delete everything," and do not mark a final as temporary to skip those protections.

### After you approve the final video

Check that the screen and the API announce this option. The following local commands and instructions require **CLI 0.52.0**, already published; update the skills too. An older install does not gain these options just because the web was updated. [Versions](https://editorbrain.com/en/docs/versiones).

In [Storage](https://editorbrain.com/app/storage) you choose what we keep when you approve the final:

- **Ask me** (the default): when you approve, the agent tells you how much space would be freed and you choose. It can remember your answer.
- **Keep only the final video**: enables cleanup of eligible previews and local intermediates; it does not indiscriminately delete the whole project folder.
- **Keep everything**: nothing is deleted.

You also choose when cloud previews are deleted: on approval, 24 hours later or 7 days later. Originals and the approved final are never deleted.

```sh
editorbrain storage after-approval
editorbrain clean --project my-project --intermediates
editorbrain clean --project my-project --intermediates --confirm
editorbrain storage preview-cleanup --project my-project --user-confirmed
```

`clean --intermediates` only works inside `.editorbrain-local/my-project/`; without `--confirm` it shows the plan. Deleting requires approval and preserves sources, the approved final, receipts, files that are still needed and concurrent changes. The agent runs this part locally; the cloud cron cannot clean your computer.

Cloud cleanup runs in the background after the configured delay; "on approval" does not guarantee instant deletion. The review history is kept even when its preview expires: `preview_expired` or HTTP 410 means those bytes are gone, not that you should automatically render again.

Current limits are read from the account. They do not depend only on the number of videos: bytes, copies and files reserved by jobs in progress also matter.
