Upload formats and size limits: what works on the farm
Before you upload a project to Super Renders Farm, it helps to know which transfer method fits your file size, why the farm needs your project unpacked, and what happens to your files once a job finishes.
Quick answer
| Method | Ideal for | Limits |
|---|---|---|
| Web upload | Small to mid-size projects, one-off submissions | No hard limit, but keep it under 300 GB for reliability |
| Client App | Large projects, hands-off uploads and downloads | No practical limit — resumable, parallel, plus auto-download for output |
Archives: upload your project unpacked
The farm does not extract archives (.zip, .rar, .7z, .tar, .tar.gz), so nothing inside an archive gets rendered. Upload your project folder unpacked, with the scene file and every referenced asset in place.
Here's the practical effect: the web uploader accepts an archive file, and for .zip, .rar and .7z it warns that the file won't be unpacked automatically. The job still can't see the scene inside it. If you received a project as an archive, extract it on your workstation first, then upload the extracted folder.
Every upload path takes a plain folder: drag it into the web uploader, or upload it from the Client App's Spaces tab.
Uploading large projects (300 GB and up)
Web upload has no hard size cap, but once a project passes roughly 300 GB, switch to the SuperRenders Client App. It is resumable, so a dropped connection doesn't mean starting the transfer over, and it uploads in parallel chunks, which cuts total time on large asset libraries.
How long your files stick around
Rendered output and project files stay available for download after the job finishes; there is no fixed automatic deletion period, and we delete a project when you ask us to. Finished renders come back through a direct web download or automatic download through the Client App if you've set that up.
In practice: download your output promptly, or set up Client App auto-download so it lands on your local drive without you having to remember. Keep your own backup of the original scene files; the farm is not an archive.
Cross-references
- Missing textures or assets in your farm render: causes and fixes — what to check before you upload if your scene depends on external assets
- Supported versions and plugins matrix — confirm your DCC, render engine, and plugin versions are covered
- Contact support — if you're not sure a file or format will work, we can confirm before you upload
FAQ
Q: Can I upload a .zip? A: You can upload one, but the farm does not extract archives (.zip, .rar, .7z, .tar, .tar.gz), so nothing inside it gets rendered. Extract it on your workstation and upload the folder unpacked.
Q: Can you deliver renders to my Google Drive or Dropbox? A: No. Finished renders come back through web download or Client App auto-download; move them to your cloud storage yourself if that's part of your workflow.
Q: Is there a file size limit if I use the Client App? A: No practical limit. Once a project passes roughly 300 GB, we recommend it specifically because it supports resumable, parallel transfers, which handle large uploads more reliably than a browser-based upload.