Reference
Limits and retention
File sizes, frame counts, supported engines and formats, and how long everything is kept.
Hardware
Every render runs on a single NVIDIA RTX 5090 (32 GB VRAM). Cycles uses OPTIX, falling back to CUDA. Denoising is routed to the GPU (OIDN), including compositor denoise nodes. Persistent data is enabled so the scene stays in VRAM between frames.
Limits
| Limit | Value |
|---|---|
| Frames per job | 5000 |
| Resolution override | 1 to 500 percent of the file's resolution |
| Files per job | 5000 |
| Total size per job | 100 GB |
| Single file, browser upload | 5 GB |
| Single file, add-on upload | No practical limit, larger files are uploaded in parts |
| Credits needed to start | 1 |
Supported
- Engines: Cycles and EEVEE. Third-party engines are not installed and are flagged before you launch.
- Blender versions: the version your file was saved with is used to pick the render image. Files from 4.x and 5.x are the tested path.
- Output: PNG sequences, or native FFmpeg video when the file is set to it. Other image formats currently come back as PNG.
- Extras: custom add-ons, custom OCIO configs, compositor File Output nodes, multi-layer EXR through File Output.
Retention
| Thing | Kept for |
|---|---|
| Jobs, frames, video output, extra outputs, logs | 30 days |
| Cached upload files | 30 days since last use, reset on every reuse |
| Credits | No expiry |
Download what you want to keep30 days is a hard cleanup, not a soft archive. Pull your frames down when a render finishes.
Where your files live
Uploads go from your machine straight to cloud object storage and are pulled from there by the render machine. File bytes never pass through our web backend. The machine is destroyed when the job ends, along with everything on it.