Every project on UNI has its own storage allowance for its resources folder, and the size of that allowance is decided by membership. The allowance belongs to the project, not to you, and it is set by the most generous membership held by any of that project's owners and admins. It is not set by whoever uploads the file. A project where none of its admins hold a membership gets 1 GB.
| Membership held by an admin | Storage for the project |
|---|---|
| None | 1 GB |
| Weekly | 2 GB |
| Monthly | 5 GB |
| Semester | 8 GB |
| Annual | 10 GB |
| Studio | 25 GB |
| Institutional | 50 GB |
Only files in the resources folder are measured. Images, video and embeds placed on the project itself are not counted against this allowance.
The most generous admin sets it, which cuts both ways
Because the highest tier on the team wins, a member with no membership at all can be working in a 50 GB project, purely because a collaborator with an Institutional membership is an admin on it. That is intended. It also means the number can move without you doing anything:
- If an admin with a higher membership joins the project, the allowance rises for everyone on it.
- If that person leaves the project, loses their admin role, or their membership lapses, the allowance drops back to the next best tier on the team.
- Only owners and admins count. A manager or an ordinary team member with an Institutional membership does not raise the allowance.
Nothing is deleted when the allowance drops below what the project already stores. Files that are already there stay where they are, stay downloadable, and stay attached to any snapshot that references them. What you lose is the ability to add more, until the project is back under its limit.
Sending a file to the trash does not free space
This is the part worth knowing before you start deleting things. Trashing a file in the resources folder removes it from view, and it is designed to be reversible so that older snapshots of the project keep working. The stored bytes are kept, and the storage figure does not go down. The message you see when you run out of room mentions removing files: that half of it does not currently work, and clearing the folder will not get you back under the limit.
Uploading a new version of a file behaves the same way. The new version is added on top, the previous one is kept, and the project's usage is the total of all of them.
What to do when a project is full
- Raise the allowance. Any owner or admin on the project taking a higher membership lifts the limit for the whole project immediately.
- Put the large files on a different project. Each project carries its own separate allowance.
- Export smaller before you upload. Compressing a model or flattening a large PDF is the only thing you control that changes the number.
- Write to support if you need space cleared on an existing project. Because trashing does not do it, this is the one route to genuinely recovering room on a project you have already filled.
Two limits apply no matter which membership you hold
Any single file must be under 2 GB. Over that you get "File is larger than the 2 GB limit", whatever space is left in the project. Importing from Google Drive has a lower ceiling of 512 MB, so anything bigger has to be uploaded directly.
Programs and browser-runnable files are refused outright. That covers installers and executables (.exe, .msi, .app, .jar, .sh, .bat) and anything a browser would run as a document rather than show you (.html, .svg, .js, .xml). Put them in a .zip if you need to share them.
Who can open these files
Only your project team, and only while signed in. Resources is not a public download area, which surprises people who upload a drawing set expecting visitors to get it. Project Resources is a private folder for your team explains what it is for.