A project is the unit of work in CloudStudio — it bundles your media, NLE project files, exports, and access list under a single folder structure on shared storage. This page covers how to organize a project so it stays sane through a long edit, and how features like folder templates and version stacking save you time.Documentation Index
Fetch the complete documentation index at: https://docs.cloudstud.io/llms.txt
Use this file to discover all available pages before exploring further.
What a project gives you
When a workspace admin creates a project, CloudStudio sets up:- A dedicated folder under your workspace’s storage (visible as a regular mounted volume on your workstation)
- A consistent folder template (Footage, Audio, Graphics, Exports, etc.)
- An access list — only invited users see the project
- A media database that powers thumbnails, search, comments, and review links
Folder templates
Workspaces can define folder templates so every new project starts with the same structure. A typical template:Importing media
You have two paths to get media into a project:- Upload via app.cloudstud.io — drag into the project’s upload zone. Works from anywhere; uses Transfer Agent for large jobs (see Transfers).
- Copy directly on the workstation — your project folder is a regular mounted volume. You can
cp, drag in Finder, or use any tool that reads/writes files. CloudStudio detects new files automatically and starts proxy generation.
01_Footage/ (or equivalent) folder and shows up in the web app with thumbnails within a few minutes.
Version stacking
When you upload a file that has the same name as an existing asset, CloudStudio stacks them as versions instead of overwriting:- The latest version is what your NLE sees by default
- Earlier versions remain accessible via the asset’s version dropdown in the web app
- You can promote an earlier version to “current” without re-uploading
Asset organization tips
CloudStudio works with whatever folder structure you give it, but a few habits pay off:- Don’t rename files mid-edit. Your NLE references files by name + path. Renaming on disk breaks the link in your NLE bins. If you need to rename, do it in the NLE first and let CloudStudio’s rename action propagate.
- Keep exports out of footage folders. Drop them in
05_Exports/Review/so review links stay easy to find and your bin stays clean. - One sequence per project file. If you have multiple cuts, save them as separate
.prproj/.drpfiles. Long projects bloat fast. - Archive on milestone, not on done. Move finished-act footage to a colder tier when an act locks, not when the whole show is done. Your workspace admin can demote folders between storage tiers.
Searching across a project
The web app indexes filenames, descriptions, and review comments. From the project page, the search bar searches everything you’ve uploaded — useful when you can’t remember which take a specific shot was in. You can also search by metadata: codec, resolution, duration, upload date, and uploader.Project access
Only invited workspace members can see a project. If a colleague needs access:- Ask your workspace admin to add them in Project settings → Members
- They’ll get an email; once they accept, the project appears in their CloudStudio menu
What’s next
- Transfers — moving media in and out efficiently
- Sharing & review — getting cuts in front of clients
- Troubleshooting — when something feels off