Uploading in the browser
Step 1: Scene
Engine, frame range, resolution and output format, read out of your .blend, plus what you can override before launching.
Everything on this step is read out of your .blend in your own browser. The frame range, resolution and output format are editable here; the rest is shown so you can confirm the file is set up the way you think it is.
Files with more than one scene
A .blend can hold several completely independent scenes. When yours does, this step says Multi-scene file detected and lists them all with a tick box each.
- Only the scene your file opens on starts ticked. Nothing else renders unless you ask for it, so a multi-scene file never quietly costs you three renders.
- Every scene keeps its own frame range, resolution and output format. You can render one at 100% as EXR and another at 50% as JPEG in the same job.
- Selected scenes render one after another on the same GPU, in the order they are listed.
- The frame limit applies to the total across selected scenes, not to each one.
Unticking a scene also saves you the uploadWe work out which files each scene uses, so step 2 only asks for the ones your selected scenes actually need. On a file where each scene is a different project, that can be four textures to find instead of thirty. Anything we cannot attribute is always included, so nothing goes missing.
Fields
- Render engine
- Cycles and EEVEE are the supported engines. A third-party engine (Octane, V-Ray, LuxCore and similar) is flagged with a warning badge: the render machine only has stock Blender, so those scenes will not render as they do locally.
- Frame rangeeditable
- Defaults to the range saved in the file, marked from file. Type your own values to override it and the badge flips to custom; reset puts the file's range back. This is the single biggest cost control you have, a 1 frame test costs 1 credit.
- Total frames
- Derived from the range you set. This is also what the launch button counts.
- Frame step
- Read from the file and used as-is. A step of 2 renders every second frame. Not editable here, change it in Blender if you need to.
- FPS
- The scene's effective frame rate, used to show the duration of the range. It does not affect an image sequence, only the length of a video output.
- Duration
- How long the chosen range plays back at the scene's FPS. Not render time.
- Resolution
- Shows the final pixel size after the resolution percentage is applied, with the base size in brackets when the percentage is not 100. The render machine uses exactly this. To change it before the first launch, change it in Blender; afterwards you can override the percentage with Quick edit.
- Output
- The output format saved in the file, and whether that counts as an image or a video. See below for what the farm actually writes.
What output format you get back
| Format | What you get back |
|---|---|
| PNG, JPEG, WebP, BMP | One file per frame, previewable in the browser as it renders |
| TIFF | One file per frame. Thumbnails work, but browsers cannot show a TIFF full size, so the lightbox offers a download instead |
| OpenEXR, OpenEXR Multilayer | One file per frame, full float data for compositing. No previews or thumbnails, download only |
| FFmpeg video | One movie, with the codec and container configured in your file. If the file has no video settings we use MP4 / H.264. No live frame previews, Blender writes the file at the end |
The picker defaults to whatever your .blend is set to, so leaving it alone renders exactly what Blender would. Changing it does not touch your file.
Want a video but also want live previewsPick an image format, watch it come in frame by frame, and assemble the video locally. You can also switch an already-uploaded job between any of the formats from Quick edit without re-uploading anything.
Compositor
If the scene has compositor nodes enabled, a second card appears summarising them. It matters for one reason: File Output nodes write extra files, and their paths point at your machine, which does not exist on the render pod.
- Each File Output node is listed with its original path, and whether that path is relative (
//...) or absolute. - Every node is automatically repointed to its own folder on the render machine, shown as the Remapped on the render pod line. You do not have to change anything in your scene.
- Everything those nodes write is collected after the render and appears in Extra outputs on the live view, downloadable as one zip.
Multi-layer EXR and passesExtra passes written through File Output nodes come back in the extra outputs zip in their own format, whatever the main sequence is set to.