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 |
| The .blend itself, browser upload | 200 MB. Bigger scenes go through the add-on |
| Any other 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 |
Browser uploads need one purchase firstUploading a
.blend from the dashboard unlocks after your first credit purchase, on any pack. It is an anti-abuse measure and not a paywall on the product: your free credits are untouched and you can spend every one of them through the free Blender add-on, which has no such requirement and does considerably more than the browser can.Why the browser caps the .blend at 200 MBThe 200 MB cap applies to the
.blend file only, and only in the browser. Your textures, caches and linked libraries are not counted against it. If your scene file is bigger than that, the free Blender add-on handles it: it packs the scene, works out which add-ons the render actually needs, uploads in parts, and skips anything we already hold from a previous render. There is no size limit on that path.Supported
- Engines: Cycles and EEVEE. Third-party engines are not installed and are flagged before you launch.
- Blender versions: 4.4, 4.5, 5.0, 5.1, 5.2. The version your file was saved with picks the render image, and within a version you get the newest patch release. A file saved with anything else is refused before it uploads rather than rendered on a version it was not made for.
- Output: PNG, JPEG, WebP, BMP, TIFF, OpenEXR, OpenEXR Multilayer, or FFmpeg video. Pick per scene at upload or in Quick edit.
- 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.