# Render farm user interfaces, compared

> We recorded nine submission workflows and scored 72 interface features against the evidence. Superluminal confirmed all eight monitoring features.

- Canonical HTML: https://superlumin.al/compare/render-farm-interfaces
- Markdown endpoint: https://superlumin.al/compare/render-farm-interfaces.md
- Structured page data: https://superlumin.al/compare/render-farm-interfaces.json
- Published: 2026-08-05
- Last updated: 2026-08-07
- Author: Superluminal Engineering

## Quick answer

43 recordings and retained benchmark jobs show how 9 Blender render services submit, monitor, review, and deliver frames. The page includes 40 interface stills.

### Key benchmark facts

| Fact | Value | Context | Evidence |
| --- | --- | --- | --- |
| Recorded runs | 43 | 9 services and four standard Blender scenes. | https://superlumin.al/seo/evidence/render-farm-benchmark-run-events-2026-08.json |
| Published interface images | 40 | Thirty-six workflow stills and four current feature-audit stills. |  |
| Verified feature cells | 72 | Eight interface features checked for each of the nine services. | https://superlumin.al/seo/evidence/render-farm-interface-features-2026-08.json |
| Submission families | 4 | Blender add-on, desktop client, browser, and remote workstation. |  |
| Longest check before rendering | 55 min 59 s | Blendergrid checked the uploaded Classroom scene before pricing it. |  |

## Data access

- [This page as structured JSON](https://superlumin.al/compare/render-farm-interfaces.json)

- [Recorded runs](https://superlumin.al/seo/evidence/render-farm-benchmark-run-events-2026-08.json): 9 services and four standard Blender scenes.

- [Verified feature cells](https://superlumin.al/seo/evidence/render-farm-interface-features-2026-08.json): Eight interface features checked for each of the nine services.

- Every screenshot below is embedded with its alt text, caption, and full-resolution URL.

## Related documentation

- [Read the submission terminal](https://superlumin.al/docs/blender-addon/submission-terminal): Understand the terminal window that opens on submit: tracing, packing, uploading, the success screen, and how to share its diagnostics.

## Complete report

We checked 43 recordings, the retained benchmark jobs, current desktop clients, and provider documentation. A feature gets **Yes** when the interface or current documentation confirms it.

**No** means we did not find the feature in the screens and sources checked.

## Interface feature ranking

Sorted by **Yes** results, then **Partial** results. iRender is unranked because it rents a workstation instead of managing render jobs.

| Ranked service | EXR layers | Frame timing | Render stages | Logs | Capacity shown | Machine details | Frame view | Playback while rendering |
|---|---|---|---|---|---|---|---|---|
| 1 Superluminal | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 2 GarageFarm | No | Yes | Partial: worker-group stages | Yes | Yes | Yes | Yes | No |
| 2 RebusFarm | Yes | Yes | No | Partial: supported renderers | Yes | No | Yes | Yes |
| 4 Fox Renderfarm | No | Yes | No | Yes | Yes | Yes | Yes | No |
| 5 RenderStreet | No | Yes | No | No | Yes | Partial: device class and count | Yes | Yes |
| 6 Render Network | Partial: downloadable passes | No | No | No | Partial: active frames only | Yes | Yes | Yes |
| 7 RenderJuice | Partial: separate browser viewer | No | No | Yes | No | No | Yes | No |
| 8 Blendergrid | No | No | No | No | No | No | Yes | No |
| Unranked iRender | Not applicable | Not applicable | Not applicable | Not applicable | Yes | Yes | Not applicable | Not applicable |

The [evidence for all 72 cells](/seo/evidence/render-farm-interface-features-2026-08.json) records the screen or source behind each answer.

## Superluminal

![Superluminal submission terminal confirming the queued job after packaging and upload](https://superlumin.al/seo/interfaces/superluminal-submission-terminal.png)

*Submission ends in the add-on's terminal: the job is packaged, uploaded, and queued before any browser opens.*

![Superluminal Classroom job starting active rendering on 30 nodes](https://superlumin.al/seo/interfaces/superluminal-live-progress-classroom.webp)

*Active rendering started after the upload and queue phases in the same recording.*

![Superluminal Classroom job after all 145 frames completed](https://superlumin.al/seo/interfaces/superluminal-completed-classroom.webp)

*Provider completion showed all 145 Classroom frames finished.*

![Superluminal Classroom job after all 145 frames reached local disk](https://superlumin.al/seo/interfaces/superluminal-downloaded-classroom.webp)

*The final boundary confirms the complete local frame set 106.7 seconds after upload began.*

The whole submission starts in Blender:

1. Choose the project, Blender version, node count, output, and required add-ons.
2. Select **Submit**. The add-on checks external files, packages the project, and uploads it.
3. You do not need a second start action. The job queues and starts rendering.
4. The job view shows finished, active, and queued frames. With live download enabled, completed files also start moving to local disk.

The August 6 Classroom recording showed 30 selected nodes and all 145 frames at completion. Its four published stills mark upload, active render, provider completion, and local completion.

The [job submission guide](/docs/blender-addon/job-submission) covers the Blender controls. The [job details guide](/docs/web-ui/job-details) explains the frame viewer, timing chart, machine data, and logs. See the [Superluminal interface guide](/interface) for the full workflow.

## Blendergrid

![Blendergrid Classroom upload entering its active state](https://superlumin.al/seo/interfaces/blendergrid-uploading-classroom.webp)

*Upload started at 01:22:34.033 CEST in the authoritative Classroom recording.*

![Blendergrid Classroom two-hour quote showing 11.73 dollars](https://superlumin.al/seo/interfaces/blendergrid-price-benchmarking-classroom.webp)

*The selected two-hour Classroom quote showed $11.73. The recording does not show a final debit or invoice.*

![Blendergrid Classroom run showing its first completed frame batch](https://superlumin.al/seo/interfaces/blendergrid-rendering-classroom.webp)

*The first completed-frame signal appeared 569.0 seconds after upload began.*

![Blendergrid Classroom job after mandatory finalization](https://superlumin.al/seo/interfaces/blendergrid-completed-classroom.webp)

*Blendergrid exposed Downloads after all 145 frame tiles and 102.8 seconds of finalization.*

![Chrome showing the Blendergrid Classroom ZIP download as done](https://superlumin.al/seo/interfaces/blendergrid-download-complete-classroom.webp)

*Chrome first showed the Classroom ZIP as Done at 02:49:28.233 CEST.*

Each recorded Blendergrid job required four stages:

1. Upload the project in the browser.
2. Wait for the scene check.
3. Confirm the scene settings and wait for price calculation.
4. Choose a deadline quote and start the render.

Classroom reached render submission 373.0 seconds after upload began. Junk Shop took 617.8 seconds, and Monster took 206.3 seconds.

The job page showed one status tile per frame. The authoritative recordings did not open a rendered-frame preview.

All three runs exposed a ZIP after finalization. The [Blendergrid comparison](/compare/superluminal-vs-blendergrid) has each phase and displayed quote.

## Fox Renderfarm

![Fox Renderfarm Raysync client uploading Classroom](https://superlumin.al/seo/interfaces/fox-renderfarm-raysync-upload-classroom.webp)

*Raysync handles the recorded project upload.*

![Fox Renderfarm Classroom job with running node count](https://superlumin.al/seo/interfaces/fox-renderfarm-running-nodes-classroom.webp)

*The job page shows the running node count.*

![Completed Fox Renderfarm Classroom job](https://superlumin.al/seo/interfaces/fox-renderfarm-completed-classroom.webp)

*The browser job reaches its completed state.*

![Fox Renderfarm Classroom output delivered through Raysync](https://superlumin.al/seo/interfaces/fox-renderfarm-downloaded-classroom.webp)

*Raysync also handles the recorded output delivery.*

![Fox Renderfarm completed Classroom task with a per-frame render-time graph](https://superlumin.al/seo/interfaces/fox-renderfarm-frame-time-graph-2026.webp)

*The completed task plots render time for each frame and shows the selected frame preview.*

Fox Renderfarm split submission between a desktop client and the browser:

1. Upload the project with Raysync.
2. In the browser, choose the scene, hardware, and render device.
3. Run the required scene analysis.
4. Review the result and select **Render full job**.

After the job started, the page showed progress, cost, and running nodes. Classroom peaked at 129 visible nodes. Raysync handled the output download.

A completed task also showed a per-frame time graph and timestamped Blender logs. Task details listed RAM, GPU model, GPU memory, and GPU count. The [Fox Renderfarm comparison](/compare/superluminal-vs-fox-renderfarm) has the scene results.

## GarageFarm

![GarageFarm WebManager job settings for Classroom](https://superlumin.al/seo/interfaces/garagefarm-job-settings.webp)

*The operator configures and starts the uploaded job in WebManager.*

![GarageFarm job page showing active nodes](https://superlumin.al/seo/interfaces/garagefarm-active-nodes.webp)

*WebManager shows active nodes while work runs.*

![Completed GarageFarm Classroom job with cost](https://superlumin.al/seo/interfaces/garagefarm-completed-classroom.webp)

*The completed page reports progress and dollar spend.*

![GarageFarm renderBeamer delivering completed output](https://superlumin.al/seo/interfaces/garagefarm-renderbeamer-delivery.webp)

*renderBeamer continues retrieving originals after provider completion.*

![GarageFarm completed benchmark jobs with average time per frame for each worker group](https://superlumin.al/seo/interfaces/garagefarm-completed-frame-timings-2026.webp)

*Done Frames reports average frame time, worker time, node type, and cost for each group.*

![GarageFarm process results separating pre-render time from render duration for a five-frame worker group](https://superlumin.al/seo/interfaces/garagefarm-pre-render-and-render-times-2026.webp)

*Process Results separates seven seconds of pre-render work from two minutes and 33 seconds of rendering.*

GarageFarm used three connected interfaces:

1. Send the Blender scene to renderBeamer.
2. Let renderBeamer check, compress, and upload the project.
3. Open WebManager, review the settings, choose the priority and node groups, then select **Submit**.

WebManager showed the active node count and per-worker load. Completed worker groups added average frame time, logs, and separate pre-render and render times. The stage values cover five-frame groups.

renderBeamer downloaded finished files in the background. For Classroom, the last file reached local disk 301.3 seconds after GarageFarm reported completion. The [GarageFarm comparison](/compare/superluminal-vs-garagefarm) has all four scene results.

## RebusFarm

![RebusFarm ControlCenter with the Classroom project ready to render](https://superlumin.al/seo/interfaces/rebusfarm-upload-ready.webp)

*After upload, ControlCenter lists Classroom as Ready to Render and requires a separate Render action.*

![RebusFarm Classroom job showing active nodes](https://superlumin.al/seo/interfaces/rebusfarm-active-nodes-classroom.webp)

*ControlCenter shows active capacity and progress.*

![RebusFarm ControlCenter list with three completed benchmark jobs](https://superlumin.al/seo/interfaces/rebusfarm-completed-costs.webp)

*The job list shows Classroom at 145 of 145 frames and 9.74 RenderPoints.*

![RebusFarm Classroom at 145 of 145 frames at the verified local-completion boundary](https://superlumin.al/seo/interfaces/rebusfarm-classroom-local-completion-boundary.webp)

*At the logged local-completion boundary, ControlCenter showed 145 of 145 frames and 100 percent.*

RebusFarm also moved between local and web tools:

1. Send the scene from Blender to RebusDrop.
2. Let RebusDrop validate, package, and upload it.
3. Open ControlCenter in the browser.
4. Find the job marked **Ready to Render**, choose the tier, and select **Render**.

ControlCenter then showed the preview, progress, charge, and active node count. Current documentation also shows per-frame time, render elements, AOV review, and logs for supported renderers.

RebusDrop downloaded files in the background. The [RebusFarm comparison](/compare/superluminal-vs-rebusfarm) explains the tested tiers and the incomplete Fox (EEVEE) download.

## RenderJuice

![RenderJuice validated Classroom configuration](https://superlumin.al/seo/interfaces/renderjuice-validated-configuration.webp)

*The browser validates the uploaded job before rendering.*

![RenderJuice Classroom job rendering at 99.3 percent](https://superlumin.al/seo/interfaces/renderjuice-classroom-active-progress.webp)

*The active Classroom view shows 99.3 percent progress and 64 GPU minutes used.*

![Completed RenderJuice Junk Shop job with render settings and GPU minutes](https://superlumin.al/seo/interfaces/renderjuice-completed-junk-shop.webp)

*The completed view shows the job settings and 40 GPU minutes used.*

![RenderJuice Fox EEVEE output page with ZIP download controls](https://superlumin.al/seo/interfaces/renderjuice-completed-fox-eevee.webp)

*The output page offers a browser ZIP and a Fast Download archive.*

RenderJuice required a packer and the browser:

1. Pack the project with the desktop app.
2. Upload the package in the browser and wait for validation.
3. Confirm the frame range, engine, render settings, and priority.
4. Select **Start Render**.

Overview showed progress and GPU minutes. Monitor exposed job output, warnings, and errors. Review opened a contact sheet and frame gallery after completion.

No inspected job tab, Stats page, or Performance page showed a per-frame timing graph. The [RenderJuice comparison](/compare/superluminal-vs-renderjuice) explains the subscription cost.

## RenderStreet

![RenderStreet Classroom settings immediately before Launch job](https://superlumin.al/seo/interfaces/renderstreet-job-launch-classroom.webp)

*After upload and analysis, the operator confirms the On Demand GPU settings and launches the job.*

![RenderStreet Classroom job allocating servers during processing](https://superlumin.al/seo/interfaces/renderstreet-processing-classroom.webp)

*The processing view reports elapsed time, completed frames, billed device time, and price so far.*

![RenderStreet Classroom sequence playback available while rendering](https://superlumin.al/seo/interfaces/renderstreet-live-playback-classroom.webp)

*RenderStreet builds a sequence preview while the job is still processing.*

![Finished RenderStreet Classroom job with exact price and per-frame timing](https://superlumin.al/seo/interfaces/renderstreet-finished-classroom.webp)

*Finished exposes the exact $4.37 price, billed device time, frame timing, and download controls.*

RenderStreet kept submission and monitoring in the browser:

1. Upload the `.blend` file and wait for scene analysis.
2. Check the Blender version, frame range, output format, and render device.
3. Choose the On Demand plan and select **Launch job**.
4. Watch the job state, active-machine count, sequence preview, price, elapsed time, and billed device time.

The live Classroom job created a playable sequence preview before the render finished. The completed job exposed each frame's duration, size, and individual download action.

The persistent header showed live active-machine counts. The observed peaks were 16 for Classroom, 22 for Junk Shop, 9 for Monster, and 2 for Fox (EEVEE).

The [RenderStreet comparison](/compare/superluminal-vs-renderstreet) has the scene results and both plans. The comparison clock starts when the operator selects **Launch job**. It stops when **Finished** and the download controls first appear. Upload, form handling, retrieval navigation, destination handling, and archive transfer remain separate measurements.

The supplemental One recording used the same form with `RenderStreet One` and
`CPU` selected. The job page did not expose the assigned CPU or server count.
It showed 3:19:46 elapsed and 9:29:13 total rendered time at completion.

## Render Network

![Render Network submission settings for Tier 2, RNDR Credits, and manual frame review](https://superlumin.al/seo/interfaces/render-network-manual-review.webp)

*Before submission, the operator selects Tier 2 Priority, RNDR Credits, and manual frame review.*

![Render Network job during early progress](https://superlumin.al/seo/interfaces/render-network-early-progress.webp)

*The job page starts at 0 percent and reports RNDR Credits used.*

![Render Network Classroom job near completion](https://superlumin.al/seo/interfaces/render-network-progress.webp)

*The Classroom job reached 90 percent before a long final stretch.*

![Render Network Downloader Manager retrieving Classroom frames](https://superlumin.al/seo/interfaces/render-network-download-manager.webp)

*The separate Downloader Manager retrieves the complete frame set.*

The recorded job began with a package prepared outside the service:

1. Prepare the Blender package.
2. Upload it in the browser.
3. Choose Tier 2 Priority, RNDR Credits, and manual frame review.
4. Create the job.

The job view showed a frame grid, review controls, overall progress, and up to 100 frames in progress. The completed Classroom job opened individual previews and a sequence player.

The settings listed requested VRAM and render passes. They did not list assigned hardware. The browser opened one download prompt per file, so we switched to Downloader Manager. The [Render Network comparison](/compare/superluminal-vs-render-network) covers the two Junk Shop attempts that returned no output.

## iRender

![iRender remote workstation hardware configuration](https://superlumin.al/seo/interfaces/irender-machine-configuration.webp)

*The operator chooses a remote workstation instead of a queued job.*

![iRender remote machine start dialog](https://superlumin.al/seo/interfaces/irender-machine-start-dialog.webp)

*The rented Windows machine must boot before Blender opens.*

![Blender rendering Classroom through iRender remote desktop](https://superlumin.al/seo/interfaces/irender-remote-desktop-render-start.webp)

*The operator starts Blender and the render through remote desktop.*

![iRender Drive synchronizing the 145-file Classroom output folder](https://superlumin.al/seo/interfaces/irender-drive-classroom-synchronizing.webp)

*After remote rendering, iRender Drive shows the Classroom output synchronization in progress.*

iRender rented a remote Windows workstation instead of running a managed farm job:

1. Choose GPU Server 5S with four RTX 4090 GPUs and start the machine.
2. Wait for the connection, then open the remote desktop.
3. Move the project to the workstation and open it in Blender.
4. Start the render in Blender and use iRender Drive to synchronize the output.

For Classroom, the remote desktop became usable 13 minutes 11 seconds after the paid machine started. The dashboard lists each retained machine's package, CPU, GPU count, Blender version, and hourly price.

The user had to manage Blender, storage, rendering, and file transfer. The [iRender comparison](/compare/superluminal-vs-irender) reports the full paid window.

## Sources

| # | Source | Type | Checked | URL |
| --- | --- | --- | --- | --- |
| 1 | Render farm benchmark dataset, July to August 2026 | First-party benchmark evidence | 2026-08-05 | https://superlumin.al/seo/evidence/render-farm-benchmarks-2026-08.json |
| 2 | Render farm benchmark run events | First-party timing and interface evidence | 2026-08-05 | https://superlumin.al/seo/evidence/render-farm-benchmark-run-events-2026-08.json |
| 3 | Render farm interface feature evidence | Cell-level recording, authenticated interface, and provider documentation evidence | 2026-08-05 | https://superlumin.al/seo/evidence/render-farm-interface-features-2026-08.json |