# Your files

> In short: Every production has a Files tab holding everything it has made and everything you brought in. Nine fixed folders say where each file is stored, you make your own folders to organise them, and views, boards and search help you find them. You can name, star and rate takes, download originals and put a file on the stage.

Applies to: v0.11 · Last reviewed: 2026-11-02 · Canonical: https://docs.zymcos.com/product/your-files/

Every production has a **Files** tab, next to Home, Script and Viewport. It is where everything
the production has made actually lives: the references you brought in, the frames and clips
that came out of generation, the speech, the delivery masters.

On the left are four lists: **System** (where each file is stored), **Folders** (yours),
**Views** (saved filters) and **Boards** (files you chose). Files are on the right, with a search
box above them.

## System: where each file is stored, and it never changes

The first list is nine folders, in every production, from the day you create it:

**References** · **Prompts** · **Frames** · **Clips** · **Speech** · **Music** ·
**Quality checks** · **Delivery** · **Script**

**Script** holds a copy of each locked script — see *Locking a script* in
[Writing a script](https://docs.zymcos.com/product/writing-a-script/). It is the one folder whose contents you create
deliberately rather than as a by-product of generating something.

They appear whether or not there is anything in them yet. That is deliberate — a structure that
rearranges itself as you work is one you stop being able to navigate from memory.

You cannot make, move or rename these. A file's place here is not a choice somebody made and
might make differently next time — it is a **fact about what the file is**, worked out from the
production itself. A clip generated for shot 4 is in Clips because it is a clip. This is where a
file is *stored*, and that never changes, whatever you do below.

## Your folders: put things where you want them

Under System is **Folders**, your own. Make as many as you need, nest them (up to five levels),
and drag files into them. Everyone on the production sees the same folders.

**Making one.** Click **+** beside *Folders*, type a name (up to 80 characters; two folders in
the same place cannot share a name, capital letters aside) and press **Enter**. To make one
inside another, use the folder icon on its row. A production holds up to 500.

**Filing a file.** Drag it onto a folder. Or, with the keyboard, use **Move to…** on the file: type
to find the folder, use the arrow keys, press **Enter**. Tick several files and **Move to…** in
the bar above moves them together, all or none. A file is in **one** folder at a time, like a
folder on your computer; if you want a file in several places, put it on boards. Dragging a file
onto **Unfiled** (under Views), or choosing *Unfiled* in **Move to…**, takes it out of its folder.

**Filing does not move the file.** Where it is stored, its name, its ★ and its ratings stay as
they were. Filing it somewhere does not keep it either: ★ is what keeps a take from long-term
storage, and folders only organise. A file you never starred can still be archived after ninety
days, whatever folder it is in. An archived file opens exactly as before.

**Renaming, moving, deleting.** The icons on a folder's row rename it, move it (with everything
inside it) and delete it. **Deleting a folder deletes no file.** It asks first and tells you what
will happen — "2 folders… 34 files and 1 board go back to Unfiled. No file is deleted." — and
that is exactly what happens. A folder cannot be moved into itself or past five levels.

**Seeing where a file is.** The pin on a file's row, **Where is this?**, shows three places: where
it is *stored* (System), where you *filed* it (or Unfiled), and which boards it is on. A file you
filed also says so on its row.

**Download a folder.** **Download as zip**, above the list, gives you the folder and everything
under it, with the same structure. A take made for a shot is named for it — **S01_SH04_T02** is
scene 1, shot 4, take 2 — and the title you gave it does not change that, because that is the name
an editor conforms against. Other files use their title, or their usual name. Withdrawn files are
left out. A zip holds up to 1,000 files or 2 GB; a larger folder is refused with the counts, and
you can download its subfolders one at a time. A list at the top of the zip says what was left out
and why.

**Uploading into a folder.** With one of your folders open, **Upload** files what you add in it
as it arrives. With anything else open (a view, a storage folder, All files) it arrives Unfiled,
and you can file it afterwards.

**Having a run file its results.** When you approve a run's plan, **File the results in** (beside
the Approve button, shown once you have at least one folder) says where each result goes as it is
made. Leave it on Unfiled and nothing is filed. If you delete that folder while the run is going,
the results already in it go back to Unfiled with it, the rest are kept Unfiled, and the run is not
stopped. The filing is recorded as the autopilot acting for whoever approved the plan.

The people who can arrange a production's folders are the members who can curate it; if you
cannot, the controls say so when you hover them.

## Asking CODA to organise

You can also just ask. CODA can make, rename and move folders ("make a folder called Client picks",
"rename Internal to Behind the scenes"), put takes in them ("put this in the Client folder", or
name the takes), take them out ("take this out of its folder"), and tell you what is in one. It
does these at once and says what it did, as a click on the same control would. Two things come
back as a card, and nothing happens until you press the button on it: **moving more than three takes
at once**, and **deleting a folder that has anything in it** or that CODA suggested deleting. The
delete card says what goes back to Unfiled and that no file is deleted. If you ask in your own words
to delete a folder that is empty ("delete the folder Picks"), CODA deletes it and says so. If two folders share a name, CODA asks which, or
you can say the path ("Client/Round 2").

## Views and search

Under Folders, **Views** are saved filters: **Unfiled** (files you have not put in a folder),
**Recent** (made in the last seven days), **Circled ★**, **Finals** and **Withdrawn**. *All files* is the first
row of System. Views leave out withdrawn files, except Withdrawn itself.

The search box above the list finds files whose **title**, or the **prompt** that made them,
contains what you typed (two characters at least, capital letters ignored). It searches inside
whatever you have open: a folder, a view, or everything.

## Nothing here has a filename you typed

A file reads **`Shot 4 · take 2`**, because that is what it is: the second attempt at the fourth
shot in your script. Rename the shot and the label follows. Reorder the script and the numbers
follow.

Alongside it you get what you actually choose between: the kind of file, its dimensions or
duration, its size, and when it was made.

A take made for several shots at once reads **`Shots 2–3 · take 1`** (consecutive shots are
joined with a dash, others are listed: **`Shots 2, 5`**). Its number counts the takes made for
exactly those shots, so it does not use up numbers in the shots it covers: a shot with two takes
of its own and one made across it and the next still reads "take 1" and "take 2".

When one request made several pictures, each says which it is: **`Shot 2 · take 2 · 3 of 4`**.
Withdrawing one does not renumber the others.

A file that is not attached to a shot reads **Reference** (something you brought in) or
**Unassigned take** (a take made for no shot at all).

## Two labels you may see

**"not ours yet"** — the file was just generated and still lives on the model provider's
servers. A background job copies it into our storage shortly afterwards. It works either way;
the label is there so you can tell.

**A warning triangle** — the provider's copy has expired and ours never completed. The file is
gone, and the *record* of it is kept on purpose: what was made, when, and as part of what. We
would rather show you an honest gap than quietly drop a row.

## The count under the list is the whole folder, not the page

A folder with a lot in it does not arrive all at once. The line under the files says how many
you are looking at out of how many there are — **"23 of 480"** — and **Load more** brings the
next batch.

Both numbers come from the same request, which is worth saying because they did not always.
The list used to stop at a hundred while the folder tree on the left reported the real count,
and there was no way to tell which to believe or how to reach the rest. If the tree says 480,
you can now get to all 480.

## Naming, starring and rating a take

A take is named by what made it — "Shot 4 · take 2" — and you can give it a name of your own,
up to 120 characters. The name is a label: the file, its folder and its history do not change,
and the derived name stays underneath. Clear the name and the derived one shows again. Who
named a take, and when, is kept.

**To name a take**, click the pencil beside its name in the Files tab or in the Viewport's
strip, or click the name itself under the picture on the stage. Type, then press **Enter** to
save or **Escape** to cancel; clicking away cancels too. Leave the field empty and save to go
back to the derived name. If the save does not go through, the row says so and keeps what you
typed.

**★ Circle take** marks the one the production chose. It is the star in the bar under the
picture (or beside a tall one), and it shows on the take's row in Files and in the strip. A
circled take is never moved to the archive while it is circled, however old it gets; uncircle
it and the usual rules apply again. Circling is your keeper mark, and it is not the same as a
final.

### Finals

A **final** is the take a person accepted as a shot's answer. The **Finals** view lists them. A
final is kept for good, never moved to the archive, and the ordinary routes will not move it to
another shot, withdraw it or erase it: replace it by accepting another take for the shot first. A
shot has at most one current final, and the ones it replaced stay on record.

**👍 and 👎** are yours, per take, in the same bar. Each shows how many people are for and
against, and your own verdict stays pressed. A 👎 asks why first, from a fixed list, so "it
flickers" means the same thing to you and to the platform's own checks; you can pick several,
or none. Every verdict is kept as a history, so changing your mind is a new entry rather than
an erasure. Your verdict also shows on the take's row in Files.

Above the file list, **Circled only**, **Liked** and **Disliked** narrow the list to the ★
takes and to your own verdicts, and **Circled first** puts the ★ takes at the top; the count
under the list is the count of what you asked for. **Your feedback stays inside your
workspace and is not used to train any model.**

### What CODA notices from them

Once an hour CODA reads the production's ★ and 👍/👎 and writes down what they add up to, as
short **taste notes**: "In “Launch film”, 4 of 6 turned-down takes were marked
'composition'", or "9 of 11 favoured takes came from" a particular model. A note needs at
least three takes behind it, and it only ever states a count: nothing looks at the pictures,
and no model writes them. CODA reads the notes in every conversation about the production,
so they are part of what CODA's model sees — the notes, never your individual ratings or who
gave them. Nothing is trained on either.

They are listed at the top of CODA's **Sessions** tab, under **What CODA has noticed**. Each
note shows how many takes it rests on, and a numbered button for each of them puts that take
on the stage. Hover a note to change it:

- **Edit** (the pencil) rewrites it in your own words — up to 150 characters, **Enter** to
  save, **Escape** to cancel. From then on the note is yours, marked **Your words**, and CODA
  never rewrites it, whatever the counts later say.
- **Dismiss** (the ×) removes it from CODA's context from the next message on. It does not
  come back.

When the takes behind a note stop supporting it — you circled the ones you had turned down,
say — the note is taken away by itself, and returns if the evidence does. Notes belong to
one production and are never shown in, or read by, another.

## Downloading the original

**Download**, in the bar under the picture (or beside a tall one), saves the original file as
it was made, provenance manifest and all, named after the take's title. Only files the
platform holds itself can be downloaded: a take still on the provider's servers, or one that
has been erased, is refused with the reason — and the button says so before you click, when
you hover it or a screen reader reads it. The link is signed and stops working after a short
while, like every link here.

## How the bar is laid out

The picture on the stage fills the stage's width, however wide CODA's column or the right
column leaves it; when that makes it taller than the stage, scroll down to the controls. The
controls sit on a grid, grouped by what they are for, and their columns line up. On a wide
stage they are two rows: **Edit on stage**, then ★ 👍 👎, then — apart, with a warm rule —
**Variations** and **Animate**, which are the ones that cost a generation; and on the second
row the seven controls that use the take. When a column beside the stage opens, the same groups
step down onto more rows on the same columns rather than wrapping out of line. The take's name
is in the strip beside the stage, where you rename it; hover its thumbnail to see its size.
A tall (portrait) take keeps its name and size beside the picture, where there is room.

## The rest of the bar: where a take is used

The same bar carries four more controls. None of them generates anything or spends anything.
When one cannot apply to the file on the stage, it stays where it is and says why on hover: a
file you brought in has no shot and no recipe, an erased take has nothing left, and a
withdrawn one has to be restored first.

**Assign to shot** lists the production's shots — "Shot 4", with what the Book recorded about
it — and puts the take in the one you choose. That is what names it: "Shot 4 · take 2"
becomes "Shot 7 · take 1". The takes made together in the same generation move with it, and
the shot it is already in is shown but cannot be chosen. A take that covered several shots at
once is shown as already in each of them and cannot be moved into one, and the bar says so.

Moving a take keeps its history. The continuity scores it earned in the old shot stay with that
shot, because they were measured against that shot's characters, and History says where the
take has been ("moved from Shot 4"). A take moved back to a shot it left starts a new stay
there, and the record still shows it was elsewhere in between.

**Use as reference** asks what to make from the still, and for a prompt, then puts a card in
CODA's conversation with this still as its reference. It offers only what your plan can
actually make from a still — today that is a clip animated from it; a new still made from it
appears here once a model on your plan can take one as a reference. When what you
are making gives the still a particular role, the dialog names it before you propose: for a clip,
*the still becomes the clip's first frame*, and the card shows that role too. CODA cannot
make a card without the words, so the prompt is not optional. Nothing happens until you commit
the card there, exactly as when CODA proposes something itself. Only a still can be a
reference from here; a clip or a piece of audio becomes a reference when CODA assembles a
lipsync from both.

**Add to Bible** puts the still into one entry's reference pack — Mara's, the rooftop
market's. It re-curates that pack, and re-curating a pack clears the entry's rights basis
until you affirm it again in the **Bible** tab (see *Recording the rights* in
[The production bible](https://docs.zymcos.com/product/production-bible/)); the dialog says so before you choose, and the note
afterwards has an **Open in the Bible** button that takes you to the entry. If the Bible is empty,
the dialog sends you to the tab to make a character, place, prop or look first. An entry
whose pack already holds the still is shown and cannot be chosen again.

**Edit** puts a card in CODA's conversation pre-filled from the take's own recipe — the
prompt, the settings, its references — with this take recorded as the version it came from,
so what you commit becomes the next version in its history. Change what you like on the card
or in the conversation first; the click on the card is what generates.

**Variations** and **Animate**, in the Iterate group set apart in the bar, also put a card
in CODA — drafted from the take's recipe by the server, with its quote — and only the card's
button spends. They are described in [Every version of a take](https://docs.zymcos.com/product/version-history/).

When a card or a pack is where the result went, the bar says so in a line you can dismiss.
If CODA's panel is closed, open it: the card is at the end of the production's open
conversation, or in one called "Proposals from the workspace" if none was open.

## Editing a region on the stage

In front of the bar there is one more control: **Edit on stage**. It works on a still that is
ours; a clip, a withdrawn take or one whose bytes are still the provider's says why on hover.

Click it and the picture becomes something you paint on. The bar becomes the editor: three
tools, a brush, and the words the tool asks for.

- **Edit region** — paint the part to change and say what should be there instead.
- **Remove object** — paint over the thing to remove; the background is filled in. A note is
  optional.
- **Mark up** — draw over the picture and write a note. The drawing says *where*, the note
  says *what*, and the note becomes the instruction the retake follows.

The brush paints at the picture's own size, however large or small it is on your screen, so
the edge you draw is the edge the model gets. **Paint** and **Erase** switch what the brush
does, **Size** is a share of the picture (4% to start), and **Clear** starts over. From the
keyboard: the arrow keys move the brush, Space paints, `[` and `]` size it, Delete clears.

**Propose in CODA** is live once a region is painted and the tool has its words. Like every
control on the bar, it generates nothing: it puts a card in CODA's conversation with this
take as the version it came from, the painted region as its mask, and your words. Sending
the card there is what generates. The mask itself is filed in `refs` the moment you propose —
"Edit region mask", "Remove object mask" or "Mark-up" — so it stays on the record of what the
new version was made from.

Until a model that takes a painted region is on your plan, Propose is refused with a plain
sentence — "No model on this plan takes a painted region yet. Nothing was proposed." — and
your painting stays, so nothing is lost while that is being arranged.

## Boards: files you chose

Under Views on the left is the last list, **Boards**. A board is files you
chose, in the order you put them — the keepers for a client cut, the three options for a
poster, the takes to talk through on Monday. A file can be on as many boards as you like, and
putting it on one changes nothing about the file: it stays in its folder with its name, its
★ and its ratings, and taking it off every board leaves no trace.

This is not the "board" of shots that the Script tab works from — that one is the shot list.
A board here is a selection of files. A board is not a folder: it holds files you chose, in an
order, and a file can be on many boards; a folder is a place, and a file is in one. A board can
sit inside a folder, so a client folder can hold both its files and the board they picked from: drag the
board onto the folder, or use the folder icon beside the board's name.

**Making one.** Click **+** beside *Boards*, type a name (up to 80 characters; each name
is used once per production) and press **Enter**. Or, from the bar under any picture,
**Add to board** offers your boards and a field to name a new one — the first board is
usually made from the first take worth keeping.

**Opening one.** Click its name and the file list is replaced by the board: its files as
cards, in board order, each numbered. Click a card to put that file on the stage. A withdrawn
file stays on the board, dimmed and marked; an erased one shows as erased. The board tells you
what you chose, even when what you chose has since changed.

**Arranging it.** Drag a card and a line shows where it will land (before the card you are over; drag to
the *Last on this board* box that appears to put it last), or use the **Earlier** and **Later** buttons on a
card, or Alt with the arrow keys, to move it one place. **Remove** (the ×) takes a file off the board and nothing else.
**Rename** with the pencil beside the name. **Delete board** asks you twice, because it is the
one thing here that is not undone — and even that only removes the board: the files stay in
their folders.

Boards are read only inside your workspace, and no model is trained on what you put on
them. The people who can arrange a production's boards are the members who can curate it;
if you cannot, the controls say so when you hover them.

## Putting a file on the stage

Click a still's or a clip's name in the list and the Viewport opens on it; the row of the file on
the stage is marked. The page address follows, so the link can be shared. Audio and other files
have no stage to go to, so their names are not buttons. A withdrawn file cannot be put on the
stage either, for the reason below.

## Taking a file out of circulation

**Withdraw** a file, with the **Withdraw** button on its row, and nothing new can be built on
it: it stops being offered as a reference, and CODA will not pick it up. It stays in the Files
tab, dimmed and marked *withdrawn*, with a **Restore** button where Withdraw was. That is
deliberate: you undo it from the same place you did it. The Viewport stops showing it, because
the Viewport shows the work on offer. Work already committed against the file stands;
withdrawing is about what happens next, not about rewriting what happened.

**Erase** is different and much harder. It removes the bytes, and it is refused while the
file is referenced, committed or delivered — if a client received a film, destroying its
sources destroys the record of how it was made. When it is refused, it says what refused it.
Erasing is an operator action with a reason, so there is no Erase button: ask support. The
file is then marked *erased* in the Files tab, cannot be restored, and the record of it stays
behind: what it was, when, and as part of what.

## Links expire

When the page shows you a file, it asks for a temporary link that stops working after fifteen
minutes. Copying that link out of the browser and sending it to someone will not work for them
later.

This protects you. It means a link that ends up in an old email, a screenshot or a forwarded
message is worthless by the time anyone finds it.

## What is not here yet

- **Download a selection as a zip.** You can download a whole folder; downloading only the files
  you ticked is not built yet.
- **Folders only some people can see.** Folders belong to the production and everyone on it sees
  the same tree.
- **Deleting a file.** Deletion is deliberately not something the application can do — see
  *Taking a file out of circulation* above, and the retention rules for why. It arrives as a
  reviewed action, not a button.
