Upload formats, size limits, and cloud storage: 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, which archive formats we can actually open, and what happens to your files once a job finishes. This page covers all three, plus the retention windows that decide how long you have to grab your files.
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 |
| SFTP | Large projects, scripted or repeated transfers | No practical limit — resumable, supports parallel transfers |
| Client App | Large projects, hands-off uploads and downloads | No practical limit — resumable, parallel, plus auto-download for output |
| Google Drive import | Pulling project files already stored in Drive | Import only — we can't push renders back to Drive |
| Dropbox import | Pulling project files already stored in Dropbox | Import only — we can't push renders back to Dropbox |
Archive formats: what we can open
We support three archive formats: tar, tar.gz, and 7z. .zip is not supported. This is a long-standing limit on our side, and it catches a fair number of people who assume every archive format is interchangeable.
Here's the practical effect: we can only unpack the formats listed above — .zip isn't one of them, so a .zip upload won't process. Repacking before you upload avoids finding that out after the fact.
On macOS or Linux, one command handles it:
tar -czf project.tar.gz project/That compresses the project folder into project.tar.gz, ready to upload as-is.
On Windows, the simplest route is the free 7-Zip GUI: right-click your project folder, choose 7-Zip > Add to archive, set Archive format to tar (or 7z if you'd rather use 7z directly), then click OK. If you'd rather skip the GUI, Windows 10 and later ship with a built-in tar command, so the same one-liner above works from a terminal too.
None of this is mandatory, either — SFTP and the Client App both accept a plain, unarchived folder if repacking is more hassle than it's worth for a given project.
Uploading large projects (300 GB and up)
Web upload has no hard size cap, but once a project passes roughly 300 GB, switch to SFTP or the SuperRenders Client App. Both are resumable, so a dropped connection doesn't mean starting the transfer over, and both support parallel transfers, which cuts total time on large asset libraries.
Either works well at this size. SFTP tends to suit scripted or pipeline-driven transfers; the Client App tends to suit artists uploading manually from a desktop, since it also queues your render job automatically once the transfer finishes.
Cloud storage: what "import" actually means
If your project files already live in Google Drive or Dropbox, we can pull them directly — point us at the folder and we'll import the files as part of your upload.
That's the extent of the integration, though: it's import only, in one direction. We do not push finished renders back to Google Drive or Dropbox. There's no bidirectional sync today, so once your job completes, output comes back through one of three channels: a direct web download, an SFTP pull, or automatic download through the Client App if you've set that up. If your workflow assumes renders will land back in your Drive folder on their own, plan on one of those three instead.
How long your files stick around
Rendered output stays available for 45 days after the job finishes, then it's deleted automatically — that doesn't change based on your plan or credit balance. Project scenes and input files clear out sooner: 14 days after job completion.
In practice: download your output within 45 days, or set up Client App auto-download so it lands on your local drive without you having to remember. If you need your original scene files back — for a re-render, an archive copy, or a handoff to another artist — grab them inside the 14-day window. After that, you'd need to re-upload from your own backup.
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: No — .zip archives aren't supported. Repack your project as .tar.gz or .7z before uploading, or skip archiving altogether and upload the folder as-is through SFTP or the Client App.
Q: Can you deliver renders back to my Google Drive? A: No. On SuperRenders, Google Drive and Dropbox integration is import-only — we can pull your project files from either, but we don't push finished renders back. Download your output via the web, SFTP, or Client App auto-download instead.
Q: Is there a file size limit if I use SFTP or the Client App? A: No practical limit for either. Once a project passes roughly 300 GB, we recommend both specifically because they support resumable, parallel transfers, which handle large uploads more reliably than a browser-based upload.