How to Manage Your Video Library in Scoutzera

Navigating the video library

The home page — labeled "Videos" — is your full library: a paginated grid of every video you've uploaded to your account. Each card shows the thumbnail generated after processing, the display name, the file size, and a relative upload time ("2 days ago", "Jun 4"). The grid uses infinite scroll, loading more videos as you reach the bottom rather than splitting them across numbered pages. Scroll down far enough and you'll see everything, oldest to newest.

The library is private by default. Only you see it when you're logged in. Your editors see only what you explicitly share via a project share link — they can't browse your full library, and they have no way to discover videos you haven't included in a project. Think of the library as your working storage and the project share as the curated delivery.

Renaming a video

Click the three-dot menu on any video card and select Rename. An edit modal opens with the current display name pre-filled — just clear it and type the new name. Click Save and the card updates immediately. The new name is what your editor will see in the project video grid, so choose something meaningful. A solid naming convention makes a real difference at scale: "EP23 — Rough v2" tells you exactly what the file is; "export_final_FINAL(2).mp4" tells you nothing three weeks later.

Useful naming patterns: include the episode or video number, the version (Rough, v2, Final), and the client or campaign name if applicable. "Client-Acme — Product Launch Hero", "Social Short — Aug Campaign v3", "YT-EP47 — Rough v1" are all findable at a glance. Avoid dates as the primary identifier — "Jun6" doesn't tell you what the video is about, and once you have 30 videos from June, it's useless.

Deleting a video

Click the three-dot menu on a video card and select Delete. A confirmation modal appears with the video name and a clear warning: "This cannot be undone." Confirm to permanently delete the video and all its timestamped notes. The storage space is reclaimed immediately and reflected in your usage counter. There's no trash or recovery — once deleted, the file is gone.

If the video is attached to a project, detach it from the project first. The confirmation modal will surface a warning if the video is still attached so you're not left with a broken card in a project grid. A good time to delete videos: after a project is complete and the final delivered files are in your editor's hands. Keep the annotated rough cut until you've confirmed delivery, then clear it to free up storage.

Checking your storage usage

Navigate to Settings from the sidebar. The Storage card shows your total used versus your plan limit — for example, "4.2 GB / 50 GB" — along with the number of videos in your library. If you're approaching your limit, work through the library and delete old rough cuts that have already been delivered. The briefed version is in your editor's workflow; you don't need the source file sitting in Scoutzera indefinitely.

Storage is also checked automatically when you try to upload a new video. If you're at or over your limit, the upload modal will block the upload with a clear error message before you select a file — you won't get partway through a large upload only to have it fail. If you hit the limit unexpectedly, delete a few old videos and try again, or check your plan options from the Settings page.

Organizing without projects

If you're not using projects, your entire library lives in one flat grid. Consistent naming is the only organizational tool available in this view, so a prefix system pays dividends: "YT-" for YouTube cuts, "SH-" for short-form social, "CLT-Acme-" for a specific client. Because the grid is sorted by upload date with the most recent first, you'll naturally find recent work at the top — the prefix system helps when you need to find something from two months ago.

If you later decide to start using projects, you can attach any existing video to a project without re-uploading. The video stays in your library and also appears in the project grid — no duplication, no extra storage cost. Projects are the better organizational layer for anything you're sharing with an editor, but the flat library approach works fine for solo work or light workflows.