Getting Started with Super Renders Farm [2026]

Your First Cloud Render: What to Expect

If you've never used a cloud render farm before, the process is probably simpler than you think. There's no remote desktop, no software installation on remote machines, no license management, and no server configuration. On a fully managed render farm, the workflow comes down to: prepare your scene, get it onto the farm, and download finished frames.

This guide walks through the entire process on Super Renders Farm. We offer two ways to submit render jobs — a submission plugin that works directly inside your 3D software (currently for 3ds Max and Maya), and a web-based workflow that works with any supported software. We'll cover both methods, plus software-specific tips.

If you're still unsure what a cloud render farm is or whether one makes sense for your project, read our explainer on cloud render farms first.

What You Don't Need to Do

Before we get into what you do need to do, it's worth being explicit about what's handled for you. On a fully managed farm, you don't need to:

Install any 3D software on the farm — we maintain current versions of 3ds Max, Cinema 4D, Maya, Blender, Houdini, After Effects, and NukeX on all render nodes. When you submit a job, our system matches your scene to the correct software version automatically.
Install or license render engines — V-Ray, Corona, Arnold, Redshift, Octane, and Cycles are all installed and licensed on our machines. You don't consume any of your own license seats when rendering on the farm.
Manage plugins — Forest Pack, RailClone, Phoenix FD, Tyflow, AXYZ Anima, and other common plugins are installed. If your scene uses a plugin we don't have, our support team can install it — usually within the same business day.
Remote desktop into anything — you never connect to a remote machine. Everything happens through our desktop app, submission plugin, and web dashboard.
Configure networking, storage, or job scheduling — the farm's infrastructure handles all of this. You submit a job, we figure out how to distribute it across machines.

This is the core difference between a fully managed farm and a DIY/IaaS approach. If you want direct control over remote machines, IaaS services exist for that. If you want to focus on your creative work and let the farm handle infrastructure, the managed model is what you're looking for.

Step 1: Create an Account and Download the Client App

Create an account on our website and head to the download page to grab the SuperRenders Client App. It's a lightweight Windows application that serves as your central hub for uploading files, submitting jobs, and downloading results.

Once installed, log in with your account credentials. Every new account comes with $25 in free trial credits — enough to test a real project, not just a demo scene.

Important: When you install the Client App, a submission plugin is automatically installed for 3ds Max and Maya. You may need to restart your 3D software for the plugin to appear. In 3ds Max, look for the "SuperRenders" menu in the menu bar — it contains "Re-Validate" (to check your scene for issues) and "Submit to SuperRenders" (to package and send your job to the farm).

Step 2: Prepare Your Scene

Scene preparation is the single biggest factor in whether your farm render succeeds on the first try. Most render failures aren't hardware or software issues — they're missing files.

General checklist (all software):

Save your project file. Seems obvious, but unsaved changes won't be included in the upload.
Check texture paths. Every texture, HDRI, IES file, and reference image must be accessible. If a path points to a file that doesn't exist (deleted, moved, or renamed), that texture will be missing in the render.
Use "Collect Assets" or equivalent. Most 3D software has a feature to gather all external files into one folder. In 3ds Max, it's "Archive" or the Asset Tracking dialog. In Cinema 4D, it's "Save Project with Assets." In Maya, use the File Path Editor to verify all references. In Blender, use "File → External Data → Pack Resources."
Check your render settings. Output resolution, frame range, file format, render engine version — set these before submitting, not after.
Test locally first. Render one frame on your machine to confirm the scene produces the expected output. If it breaks locally, it will break on the farm too.

Common pitfalls we see every week:

Issue	What Happens	Prevention
Missing textures	Renders complete but with pink/black patches	Run Asset Tracking / File Path Editor before submit
Wrong frame range	Farm renders frames 0-100 when you needed 200-500	Double-check in render settings AND in the submission form
Outdated plugin version	Scene fails to load on farm	Update plugins locally or contact support
GI cache not set to per-frame	First few frames look different from the rest	Set GI to per-frame mode for animations
Scene saved with local paths	Textures found on your machine but not on the farm	Use relative paths or "Collect Assets"

Step 3: Submit Your Job

We offer two submission methods. Choose the one that matches your software and preference:

Method A: Submission Plugin (3ds Max, Maya)

This is the most streamlined path if you're working in 3ds Max or Maya.

Open your scene in 3ds Max or Maya.
Click "Re-Validate" from the SuperRenders menu — this scans your scene for potential issues (missing textures, unsupported plugins, render setting conflicts) before you commit to an upload.
Review the validation results — the plugin flags anything that might cause problems on the farm. Fix any issues it identifies.
Click "Submit to SuperRenders" — the plugin packages your scene file, collects all dependent assets (textures, proxies, caches), remaps file paths for the farm environment, and uploads everything.
Render output downloads automatically — finished frames are downloaded to your computer through the Client App in the background. You can keep working while it runs.

The plugin handles asset collection, path remapping, and software version detection. For most 3ds Max and Maya projects, this is the simplest way to get your job onto the farm.

Here's a video walkthrough showing both submission methods using a 3ds Max project:

Method B: Web Upload (All Software)

For Cinema 4D, Blender, Houdini, After Effects, NukeX — or if you prefer manual control over the upload — use the web-based workflow. This method works with any software we support.

Uploading your project:

You need to get your project files into SRF Spaces — your personal cloud storage on our farm. There are several ways to do this:

Via the Client App — open the app, go to the SRF Spaces tab, click Upload, and select your project files or folders. Enable the "Auto keep local path" checkbox to preserve your local directory structure on the farm — this is important for scenes that use absolute file paths.
Via the website — log in to the render dashboard, navigate to SRF Spaces, and drag-and-drop your project folder. If your scene uses absolute paths (e.g., D:\projects\mybuilding\), create the matching folder structure in SRF Spaces first, then upload your files into it.
Via Google Drive or Dropbox — connect your cloud storage account and transfer files directly.
Via SFTP — for large projects or automated pipelines, SFTP upload is available.

Analyzing and rendering:

Analyze your scene — in SRF Spaces, navigate to your project folder and select "Yes! Analyze it." Fill out the analysis form with your software and render engine details, then click Analyze Scene. The system checks your scene for issues — missing assets, plugin compatibility, render settings.
Review the analysis — go to the Scene Analysis tab in the Client App (or the Scene Analysis page on the web dashboard) to check progress. If the analysis flags errors (missing textures, path issues), the error log tells you exactly what needs fixing.
Start the render job — once analysis is complete, click "Start Render Job." Set your render parameters (frame range, resolution, priority) and confirm to begin rendering.
Download output — go to the Render Dashboard, wait for rendering to complete, and click "Download render output." You can also check job status and history from the Jobs History page on the web dashboard.

Which Method Should You Use?

	Submission Plugin (Method A)	Web Upload (Method B)
Software	3ds Max, Maya	All supported software
Ease of use	Simplest — submit from inside your 3D software	Requires uploading files first, then analyzing
Asset handling	Automatic collection and path remapping	Manual — use "Collect Assets" or match folder structure
Upload options	Through the plugin	Client App, website, Google Drive, Dropbox, SFTP
When to use	Standard 3ds Max / Maya projects	C4D, Blender, Houdini, AE, NukeX — or complex projects where you want manual control

Step 4: Monitor Progress

Once the job starts rendering, you can track it through:

The Client App — go to the Render Jobs tab to see job status and frame progress.
The web dashboard — log in from any browser to see the same information. Useful for checking progress from your phone or another machine.

Each frame shows its status: queued, rendering, completed, or failed. If individual frames fail, they're automatically retried. If a frame fails repeatedly, our system flags it for support review.

For jobs submitted via the submission plugin (Method A), render output downloads automatically to your computer through the Client App — you don't need to manually trigger the download.

Software-Specific Tips

3ds Max + V-Ray / Corona (Use Method A — Submission Plugin)

3ds Max is the most common software on our farm, and the submission plugin makes it straightforward:

Open your .max file and verify render settings (V-Ray or Corona version, output resolution, frame range, GI settings).
Run File → Archive or check Asset Tracking (Shift+T) to verify all textures are found.
For V-Ray: set Light Cache and Irradiance Map to per-frame mode for animations. For stills, you can use saved maps if pre-calculated.
For Corona: if using UHD Cache, set it to per-frame for animations.
Click Re-Validate from the SuperRenders menu to check for issues → fix anything flagged → click Submit to SuperRenders.

3ds Max-specific tip: If your scene uses Forest Pack or RailClone, the plugin handles asset collection for these plugins. However, if you're using custom library paths that differ from the default installation, let our support team know so we can configure the farm nodes to match your setup.

Maya + Arnold / V-Ray (Use Method A — Submission Plugin)

Use Maya's File Path Editor (Window → General Editors → File Path Editor) to audit all external references. Red entries = missing files.
Set your render engine (Arnold or V-Ray) and output settings in the Render Settings window.
For Arnold: check that .tx textures are generated if using auto-conversion. The farm can generate them, but pre-generating saves render time.
Click Re-Validate from the SuperRenders menu → review results → click Submit to SuperRenders.

Cinema 4D + Redshift (Use Method B — Web Upload)

In Cinema 4D, go to File → Save Project with Assets to bundle all textures and references into one folder. This is critical because C4D projects often reference external files scattered across your drive.
If using Redshift, verify your GPU render settings — the farm runs NVIDIA RTX 5090 GPUs with 32 GB VRAM, so most scenes render without VRAM issues.
Upload the project folder to SRF Spaces via the Client App (with "Auto keep local path" enabled) or the website.
Run Scene Analysis → review results → Start Render Job.

As an official Maxon partner, we maintain current Cinema 4D and Redshift builds on all nodes, including Redshift 2025.5.0 with full RTX 5090 (Blackwell) support. For a detailed guide on Redshift farm rendering, see our Redshift + Cinema 4D article.

Blender + Cycles (Use Method B — Web Upload)

In Blender, go to File → External Data → Report Missing Files to check for broken references.
Consider using File → External Data → Pack Resources to embed textures into the .blend file. This is the most reliable way to ensure nothing is missing on the farm.
Set your render engine to Cycles, configure output settings (resolution, frame range, file format).
Upload to SRF Spaces and follow the analyze → render → download workflow.

Blender scenes are typically the simplest to submit because Blender's packing system handles most dependency issues.

Understanding Priority Levels and Cost

When you submit a job, you choose a priority level that determines how many machines are allocated to your job:

Low priority — fewer machines, cheaper per unit, longer total time. Good for overnight or weekend jobs where you're not in a rush.
Medium priority — balanced allocation. The default for most jobs.
High priority — maximum machines, quickest turnaround, higher cost per unit. For deadline-critical jobs.

The total cost is: render time per frame × number of frames × unit rate for your priority level. The submission form shows an estimate before you start, and the cost tracker on the dashboard updates in real time during rendering.

Our CPU rate starts at $0.004/GHz-hour and GPU at $0.003/OBh. Credits never expire and there are no subscriptions or contracts — you only pay for what you render. For projects over $200, volume discounts up to 40% apply.

When Something Goes Wrong

Render issues on a farm fall into a few common categories, and most are fixable quickly:

Missing textures or assets — the most common issue. The submission plugin catches most missing files for 3ds Max and Maya. For web uploads, the Scene Analysis step flags missing assets in its error log. Our support team can help identify what's missing and get you back on track.

Plugin version mismatch — your scene was created with Forest Pack 8.1.2 but the farm has 8.1.1. Even minor version differences can cause issues. Let support know your exact plugin versions, and we can update the farm to match.

Memory errors — the scene exceeds available RAM (CPU) or VRAM (GPU). For CPU rendering, our machines have 96–256 GB RAM, which handles the vast majority of scenes. For GPU, the RTX 5090's 32 GB VRAM covers most production workloads. If your scene is genuinely that heavy, support can route it to high-memory machines.

Unexpected output — the render completes but looks different from your local output. Common causes: different gamma settings, color management differences, or GI cache inconsistencies. Submit a local reference frame so support can compare.

In all cases, reach out through the in-app chat or support tickets. We've been operating since 2010 and have processed hundreds of thousands of render jobs — most issues we've seen before and can resolve quickly.

FAQ

Q: Do I need to install any software on the render farm? A: No. On Super Renders Farm, all 3D software (3ds Max, Cinema 4D, Maya, Blender, Houdini), render engines (V-Ray, Corona, Arnold, Redshift, Octane, Cycles), and common plugins are pre-installed and licensed. You submit your scene through our submission plugin or web dashboard, and the farm matches it to the correct software version automatically.

Q: What is the easiest render farm to use for 3ds Max? A: A fully managed render farm with a submission plugin is the simplest option for 3ds Max users. On our farm, the plugin installs automatically with the Client App — click "Re-Validate" in the SuperRenders menu to check your scene, then "Submit to SuperRenders" to send it. The plugin handles V-Ray/Corona detection, texture collection, and asset packaging. Render output downloads back to your machine automatically.

Q: How do I upload my scene to a cloud render farm? A: On Super Renders Farm, there are two ways. For 3ds Max and Maya, the submission plugin packages and uploads your scene directly from inside your 3D software. For other software (Cinema 4D, Blender, Houdini, etc.), upload your project to SRF Spaces via the Client App, website, Google Drive, Dropbox, or SFTP — then use the web dashboard to analyze and render.

Q: What if my scene uses plugins like Forest Pack or RailClone? A: We maintain current versions of Forest Pack, RailClone, Phoenix FD, Tyflow, and other common 3ds Max plugins on all render nodes. The submission plugin collects plugin-dependent assets (proxy files, custom libraries) during submission. If you're using a plugin version we don't have yet, our support team can typically install it within the same business day.

Q: How much does a first render job cost? A: Every new account gets $25 in free credits — enough for a real production test, not just a demo. A typical archviz still frame (3ds Max + V-Ray, 4K resolution, 5-minute render time) costs roughly $0.10–$0.50 depending on priority. A 300-frame animation at the same complexity runs $30–$150. The submission form shows a cost estimate before you start.

Q: Can I keep working while the farm renders my job? A: Yes. Whether you submitted via the plugin or web upload, rendering happens entirely on our infrastructure. Your workstation is free to continue working in your 3D software, open other projects, or even shut down — you can monitor the job from any browser via the web dashboard.

Q: What happens if my render fails? A: Failed frames are automatically retried on different machines. If a frame fails repeatedly, our system flags it and our support team investigates. Common causes (missing textures, plugin mismatches, memory limits) can usually be resolved within minutes. For web uploads, the Scene Analysis step catches most issues before rendering even starts. You're not charged for failed frames.

Q: How long does it take for a new plugin to be installed on the farm? A: For common plugins with a stable release, installation typically happens within the same business day. For niche or beta plugins, it may take longer depending on licensing requirements and testing. Contact support before submitting if you're unsure about plugin availability.