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. Only the frame range is editable here; the rest is shown so you can confirm the file is set up the way you think it is.
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
| Your file is set to | What the farm renders |
|---|---|
| PNG | PNG sequence, one file per frame |
| Any other image format (JPEG, EXR, TIFF, ...) | PNG sequence. Other image formats are not enabled yet, so the row is badged rendered as PNG |
| FFmpeg video | Your video, rendered natively with the codec and container configured in the file. There are no live frame previews for video, Blender writes one file at the end |
Want a video but also want live previewsRender as a PNG sequence, watch it come in frame by frame, and assemble the video locally. You can also flip an already-uploaded video job to PNG (and back) 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 even though the main sequence is PNG. That is the way to get EXR passes out today.