Manage jobs and download output

Expand Manage & Download below the submission controls. This compact view is for tracking a project's jobs and transferring full output. Use the web app when you need frame previews, detailed metrics, controls, or logs.

*Select a project job, open deep diagnostics in the browser, and transfer original output to a local folder.*

• Annotation 1: Job list with status and progress

• Annotation 2: Download path and job output

Refresh and select a job

• Live Job Updates periodically refreshes the selected project's jobs.
• The manual refresh action fetches immediately.
• Click a row to make it the active job for browser and download actions.
• Sort the table by its supported columns and use the column menu to show the details that matter for the current task.

Columns include job name, state, submission/start/finish times, frame range and progress, Blender version, and upload type. What you see depends on the selected columns and the available job data.

Open the full job page

With a job selected, choose the browser action to open its web detail page. That page provides:

• frame-state grid and selection
• image-sequence playback and render-layer selection
• job, scene, and machine details
• charts and resource measurements
• searchable, filterable, downloadable logs

The web page does not download full output. It directs you back to the add-on.

Download output

Select a job

Choose the intended row and verify its project, name, range, and state.

Choose a local path

Set Download Path to a folder with enough free space and write access.

Start the transfer

Click Download job output. An external terminal shows discovery, polling, and file-transfer progress.

Verify the sequence

Check filenames, expected frames, layers or output-node files, and a few full-resolution images before downstream work.

You can start before the whole job finishes. The downloader polls for newly completed frames and transfers them as they become available. When a file already exists locally, a later run verifies it and moves on, so resuming is fast. When a frame was re-rendered remotely, the downloader replaces the older local copy.

The download terminal

Like submission, downloading runs in its own terminal window. The terminal shows the transfer's progress.

*A download in auto mode. The header panel names the job and destination. The transcript below tracks each transfer.*

Reading it top to bottom:

• The Download panel confirms which job is transferring and into which folder, before any bytes move.
• Auto-download appears when the job is still rendering: the worker keeps polling and transfers frames as they finish. Closing the window is safe. Running the download again resumes where it stopped.
• While downloading lists single-key shortcuts that work the whole time:

• Resuming reports how many frames a previous run already delivered. The downloader verifies those instead of downloading them again.
• Each Downloading pass ends with a confirmed transfer size, then the worker waits for the next finished frames.

*The completion screen. O opens the destination folder, and Enter closes the window.*

Download promptly

The farm currently keeps render objects for seven days. Keep a verified local or production-storage copy of anything you need beyond that window.

Safe download habits

• Use a dedicated folder per job or deliberate version.
• Keep enough space for multilayer EXR and file-output-node variants, not only the main beauty sequence.
• Do not rename partial files while the downloader is active.
• After a network interruption, run the same download again. Do not start a manual transfer.
• If frames were re-rendered, run the downloader again so it can replace the changed files.

If expected files are missing

1. Open the job in the web app and confirm the frame is finished rather than queued, paused, blocked, or errored.
2. Check whether the output belongs to a different render layer, view layer, camera, or file-output node.
3. Wait a moment. A frame that just finished can take a little time to become downloadable, and the downloader polls again on its own.
4. Run the same download again so it picks up all completed frames.
5. Check local disk space, permissions, security software, and the terminal's final error.

• Job detail reference: Understand the web app's frame, preview, details, chart, and log panels.
• Output and retention: Distinguish previews from full output and plan a durable copy.
• Download troubleshooting: Collect the right diagnostics for interrupted or incomplete transfers.