Where your files live, when a broadcast is kept as a recording and when it is not, what happens as storage fills, and exactly what deleting removes.
Everything you uploaded and everything that was recorded lives in one place: Media storage. From there you open a file in the editor, cut clips from it, publish it or download it.
The screen lists all your files, separating those you uploaded from recordings the system made. A meter at the top shows how much of your plan's storage is in use.
You can upload video, audio and images. The ceiling for a single file is six gigabytes — not out of meanness, but because files heavier than that upload slowly and play back poorly.
This is the part that surprises people most, and it is worth understanding before your next broadcast:
The infrastructure records every live broadcast temporarily, because without that there is no live preview while you are on air. But the recording is only kept if you pressed Record. If you did not, the video is removed roughly two hours after the broadcast ends.
The reasoning is simple: it is not right to charge your storage for video you never asked for.
So the past-broadcasts list shows two kinds of card:
A recording you kept stays until you delete it. No timer removes it.
A recording is sent to the server in pieces as it goes, so a browser crash does not erase what was already captured. Next time you come in, the system finishes the job on its own: a recording with real content is restored in the background, and an empty or very old one is discarded. There is no dialog asking you to decide based on a count of chunks and megabytes.
Recordings are given a running name in the style of Recording 4. If you deleted recordings along the way the numbering skips — it counts what there has been rather than renaming existing files.
A live broadcast's recording is downloaded from its card in the broadcasts list. Everything else — uploads, studio recordings, clips and exports — opens and downloads directly from Storage.
Deleting here really deletes: the file goes, the copy in cloud storage goes, and the recording pieces stored along the way go with them.
Two protections come first:
Every plan includes an amount of storage. At around 85 per cent you are warned — not to nag, but because storage filling up mid-recording cuts the recording short.
When the quota is full, a new upload is refused with a message saying how much of how much is used, and offering to delete old files or move up a plan. Broadcasting and recording keep working; only uploads are blocked.
A file in your library is protected. The server's automatic clean-up of temporary files explicitly skips any file a library entry points at, and if it cannot confirm that, it deletes nothing at all. It was written that way after a blanket sweep once caught users' source files.
Not if you did not press Record. The temporary video is removed roughly two hours after the broadcast ends. For the next one, press Record at the start.
Until you delete it. There is no automatic time-based deletion for a recording you asked to keep.
The number reflects how many recordings there have been, not how many exist now. Deleting leaves a gap rather than renaming files you already have.
New uploads are blocked with a message showing how much of your quota is used. Deleting old files or moving up a plan resolves it. Broadcasting and recording are not stopped.