# Superluminal vs Fox Renderfarm

> Fox Renderfarm showed 129 running nodes on Classroom. Superluminal still completed each tested scene sooner and delivered every scene to local disk first.

- Canonical HTML: https://superlumin.al/compare/superluminal-vs-fox-renderfarm
- Markdown endpoint: https://superlumin.al/compare/superluminal-vs-fox-renderfarm.md
- Structured page data: https://superlumin.al/compare/superluminal-vs-fox-renderfarm.json
- Published: 2026-08-04
- Last updated: 2026-08-07
- Author: Superluminal Engineering

## Quick answer

Fox Renderfarm GPU 3 completed all four scenes. Recorded data covers farm time, local output, exact charges, Raysync, and EEVEE setup.

## Data access

- [This page as structured JSON](https://superlumin.al/compare/superluminal-vs-fox-renderfarm.json)

- Every chart below includes a full-resolution PNG and its underlying values as a Markdown table.

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

## Related documentation

- [Troubleshoot the Blender add-on](https://superlumin.al/docs/blender-addon/troubleshooting): Diagnose connection, project, submission, dependency, render, and download problems without exposing credentials.

## Complete report

Superluminal reached local disk first and had a lower exact charge in all four scenes. Fox Renderfarm completed all four, but it required scene analysis and a second action to start the full job.

![Superluminal and Fox Renderfarm selected on the 2026 render farm score scatterplot](https://superlumin.al/seo/charts/superluminal-vs-fox-renderfarm-ranking-2026.png "Superluminal and Fox Renderfarm in the benchmark ranking")

*[Open the full-resolution PNG](https://superlumin.al/seo/charts/superluminal-vs-fox-renderfarm-ranking-2026.png).*

#### Underlying data: Superluminal and Fox Renderfarm in the benchmark ranking

Scores are frozen against the 2026 benchmark. 100 is the reference on both axes.

| Initial state | Rank | Render farm | Time Score | Price Score | Combined score | Coverage |
| --- | --- | --- | --- | --- | --- | --- |
| selected | 1 | Superluminal | 179.1 | 187.8 | 182.0 | all 4 scenes |
| muted | 2 | GarageFarm | 138.2 | 102.2 | 126.2 | all 4 scenes |
| muted | 3 | RenderJuice | 93.7 | 176.2 | 121.2 | all 4 scenes |
| muted | 4 | RebusFarm | 102.0 | 59.9 | 88.0 | all 4 scenes |
| muted | 5 | RenderStreet | 68.8 | 121.7 | 86.5 | all 4 scenes |
| selected | 6 | Fox Renderfarm | 67.5 | 115.3 | 83.5 | all 4 scenes |
| muted | 7 | iRender | 51.4 | 66.4 | 56.4 | all 4 scenes |
| muted | 8 | Render Network | 49.7 | 37.7 | 45.7 | 1 of 4 scenes with both metrics; no coverage penalty |
| muted | 9 | Blendergrid | 22.9 | 80.6 | 42.1 | 3 of 4 scenes with both metrics; no coverage penalty |

[Open the complete benchmark dataset](https://superlumin.al/seo/evidence/render-farm-benchmarks-2026-08.json)

Fox Renderfarm ranked sixth overall at 83.5. Its Time Score was 67.5, and its Price Score was 115.3. The [benchmark method](/compare/blender-render-farms) uses the render pipeline.

## Recorded render-pipeline times

| Scene | Fastest Superluminal render pipeline | Fox Renderfarm render pipeline | Fox Renderfarm charge |
|---|---:|---:|---:|
| ![](/seo/benchmarks/thumb-classroom.jpg) Classroom | 90.5 s | 292.8 s | $3.204 |
| ![](/seo/benchmarks/thumb-junkshop.jpg) Junk Shop | 64.5 s | 710.6 s | $2.456 |
| ![](/seo/benchmarks/thumb-monster.jpg) Monster Under the Bed | 59.9 s | 575.0 s | $1.795 |
| ![](/seo/benchmarks/thumb-fox.jpg) Fox (EEVEE) | 66.5 s, 10 nodes | 540.4 s | $2.443 |

Even the 10-node Superluminal run completed the Classroom render pipeline in 226.7 seconds, versus 292.8 seconds for Fox Renderfarm.

Every Fox Renderfarm job waits behind a mandatory analysis gate before rendering can start. On Junk Shop the gate turned hostile: 87.1 seconds of analysis ended in a failure with no stated cause, the failure status itself arrived late, and an immediate identical retry passed in 28.0 seconds ([Junk Shop record](/seo/evidence/runs/foxrenderfarm-gpu3-junkshop-2026-08-01.json)). Nothing about the project changed between the two attempts.

The Monster submission added a version incompatibility warning that the render then ignored. Node allocation was also outside our control: the Classroom job jumped to 129 visible nodes on its own, and no setting influenced the count.

Superluminal has no analysis gate. The add-on [checks the project](/dependencies) inside Blender before upload and names problems on screen, so the farm's first action is rendering. Capacity does not jump on its own either: you select 5, 10, or 30 nodes, and the job runs at the size you chose.

The desktop client uploaded at an effective 3.9 MB/s. Fox Renderfarm billed a prepaid balance and showed the exact charge for each job, which puts it ahead of the credit-based farms on billing clarity.

![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.*

![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.*

## Output download and EEVEE

Fox Renderfarm started a Raysync download after reporting provider completion. The last file reached local disk 12.9 to 36.4 seconds later. Delivery runs through that separate Raysync helper application on every job.

Superluminal needs no helper and no completion event. The add-on that submitted the job [downloads each finished frame](/live-previews) while later frames render, so delivery overlaps the render instead of following it.

Fox Renderfarm required the render device set to `None` before it accepted the Fox (EEVEE) scene. Superluminal rendered the submitted scene without that change.

## Sources

| # | Source | Type | Checked | URL |
| --- | --- | --- | --- | --- |
| 1 | Render farm benchmark dataset, July to August 2026 | First-party benchmark evidence | 2026-08-04 | https://superlumin.al/seo/evidence/render-farm-benchmarks-2026-08.json |