# Your videos

> Where your clips go, the one file that lists them, and how a day is planned from it.

Source: https://runfoundry.app/docs/operations/videos/

## Where clips go

Your videos stay on your Mac. Put each day's clips in one folder, for example `content/2026-10-20/`. Vertical 9:16 MP4 or MOV, the file you would post by hand. Photos for Instagram carousels, photo posts and stories go in the same folder as JPG, PNG or HEIC.

Foundry copies a clip to the phone only when its post is due, through its own Photos importer, then posts it in the official app. Nothing is uploaded to us.

## The list: videos.json

One line per clip: a short key, the file, an optional topic and the caption. The caption is typed exactly as written; the topic is a short label kept on the post's receipt.

A `path` is read from the folder `videos.json` sits in (a full path works too). Run `foundry plan` from any folder: give `--videos` the path to `videos.json` (relative to where you are, or full). The plan stops and writes nothing if a listed file is missing. The written plan keeps each clip's full path, so leave the clips where they are until they have posted. `clip_format` is optional: it names the clip's format for the [Formats](https://runfoundry.app/docs/operations/formats/) report (the plan file's own `format` field is internal).

A carousel, photo or story is one line too, with `kind` and its files under `media`. Every kind, its limits and its status are on [What Foundry posts](https://runfoundry.app/docs/operations/post-kinds/).

videos.json:

```json
[
  { "key": "M1", "path": "content/2026-10-20/41_whowon_9x16.mov", "topic": "Who won the debate", "caption": "Who won? #debate" },
  { "key": "M2", "path": "content/2026-10-20/M2.mov", "topic": "Hot take", "caption": "Agree or not?", "clip_format": "hottake" }
]
```

## Plan the day

Run this once in the morning, or have your agent run it. It gives every enabled account its posts at random times and writes the day's plan.

Terminal:

```bash
foundry plan --date 2026-10-20 --videos videos.json --write
foundry status
```

One account never posts the same clip `key` twice, so `--posts 2` needs at least 2 different clips in `videos.json` for that platform; with fewer it stops, writes nothing and says how to fix it.

Posts on one phone are at least 18 minutes apart and clear of warm-ups. Warm-ups always win.

Your dashboard **Queue** shows each written slot from the day before it posts (today's and tomorrow's slots), with the clip, caption and account.

It prints one line per post with its account and time, in this Mac's local time. **nothing to schedule** means no account can post that day; the lines under it name each account and what it is missing (a phone that isn't enrolled, a lane that isn't enabled, or no accounts added yet), with the command that fixes it.

After a written plan it lists anything still needed before the slots post (the post-runner not installed, no signing profile because `lane up` never ran, a phone that is down or off the cable, posting paused), each with its command.

## Change or stop a day

Edit `videos.json` and run the plan again with `--force` to replace a day that is already written (without it the plan refuses to overwrite). To stop posting, run `foundry pause` on the Mac, or press **Pause posting** on your dashboard and the Mac picks it up within a couple of minutes. `foundry resume` starts it again. Warm-ups keep running either way.
