How Much Does Cloud Rendering Cost Per Frame? A Realistic Breakdown
Overview
What Does Cloud Rendering Actually Cost Per Frame?
The most common question we hear from studios evaluating a cloud render farm for the first time is some variation of: "How much per frame?" It sounds like it should have a simple answer. It doesn't.
Per-frame cost depends on scene complexity, render engine, resolution, sampling quality, and the farm's pricing model. A simple archviz interior at 3K resolution might cost $0.08 per frame on CPU. A dense VFX shot with volumetrics and subsurface scattering at 4K might cost $2.50. Same farm, same pricing structure — wildly different per-frame costs.
We've rendered millions of frames across every major engine since 2010. This guide breaks down what drives per-frame cost, gives you real ranges for common project types, and explains how different pricing models affect what you actually pay.
The Three Pricing Models for Cloud Render Farms
Before talking about per-frame cost, you need to understand how farms charge — because the pricing model determines whether "cost per frame" is even a meaningful metric for your comparison.
Per-Unit Pricing (Compute Time)
This is what we use at Super Renders Farm and what most established farms use. You pay for the compute time your job consumes, measured in units like:
- GHz-hour (CPU rendering) — one CPU core running at 1 GHz for one hour. A 44-core machine running at 2.2 GHz for one hour consumes 96.8 GHz-hours.
- OctaneBench-hour (OBh) (GPU rendering) — one unit of GPU compute based on OctaneBench scoring. An RTX 5090 scores roughly 1,100 OB, so one hour of RTX 5090 time is ~1,100 OBh.
We charge $0.004/GHz-hour for CPU and $0.003/OBh for GPU. The per-frame cost is a direct function of how long each frame takes to render on the farm's hardware.
This model is transparent: you see exactly how much compute your job consumed. The trade-off is that per-frame cost isn't fixed — it depends on your scene.
Subscription Plans
Some farms offer monthly plans with a set number of render hours or credits included. This can flatten your per-frame cost if you render consistently. If your studio outputs 4-6 animations per month with predictable complexity, a subscription can provide cost certainty.
The risk: unused credits. If you have a slow month, the subscription cost is sunk. Most subscription plans also have overage rates that are higher than the base per-unit rate.
Pay-Per-Frame (Fixed Pricing)
A few farms offer fixed per-frame pricing — you pay a set rate regardless of how long the frame takes to render. This is the simplest model to budget for: 1,000 frames × $0.15/frame = $150.
The hidden trade-off: the farm sets the per-frame price high enough to cover their worst-case scenario. If your scenes are simple, you're overpaying relative to per-unit pricing. If your scenes are complex, the farm might throttle quality settings to keep their costs in line. Ask what happens when a frame exceeds the expected render time.
Real Cost-Per-Frame Ranges by Project Type
These numbers come from our farm's actual job data. They assume per-unit pricing at current rates ($0.004/GHz-hr CPU, $0.003/OBh GPU), standard priority, and production-quality settings (not draft).
If you want the CPU and GPU scenario tables with worked per-frame math, check our companion article for the 2026 breakdown with current rates.
Archviz — Still Images
| Scene Type | Engine | Resolution | Avg Frame Time | Est. Cost/Frame |
|---|---|---|---|---|
| Interior (moderate) | V-Ray CPU | 4K (3840×2160) | 8-15 min | $0.12 – $0.25 |
| Interior (heavy — glass, caustics) | V-Ray CPU | 4K | 20-40 min | $0.30 – $0.65 |
| Interior (moderate) | Corona | 4K | 10-20 min | $0.15 – $0.30 |
| Exterior (landscape, vegetation) | V-Ray CPU | 4K | 5-12 min | $0.08 – $0.20 |
| Interior | Redshift GPU | 4K | 2-6 min | $0.06 – $0.18 |
Archviz stills are typically the most cost-effective renders on a farm. Most archviz studios spend $5–$50 per scene for a set of camera angles, depending on complexity and resolution.
Archviz — Animation (Walkthrough / Flythrough)
| Scene Type | Engine | Resolution | Frames | Avg Frame Time | Total Est. Cost |
|---|---|---|---|---|---|
| Interior walkthrough | V-Ray CPU | 1080p | 900 (30s × 30fps) | 3-8 min | $40 – $120 |
| Interior walkthrough | Corona | 1080p | 900 | 4-10 min | $55 – $150 |
| Exterior flythrough | V-Ray CPU | 1080p | 1,500 (50s) | 2-5 min | $45 – $125 |
| Interior walkthrough | Redshift GPU | 1080p | 900 | 1-3 min | $18 – $55 |
Animation is where farms provide the most dramatic time savings. A 900-frame walkthrough that takes your workstation 3-5 days finishes in 2-4 hours on a farm. The cost — $40 to $150 — is typically a fraction of one day's artist salary.
VFX & Motion Design
| Scene Type | Engine | Resolution | Frames | Avg Frame Time | Total Est. Cost |
|---|---|---|---|---|---|
| Motion design loop | Redshift GPU | 1080p | 300 (10s) | 1-4 min | $6 – $25 |
| Product turntable | V-Ray GPU | 2K | 360 | 2-5 min | $15 – $40 |
| VFX composite (heavy) | Arnold CPU | 2K | 200 | 15-45 min | $45 – $150 |
| Particle simulation | Houdini + Karma | 1080p | 500 | 8-20 min | $60 – $165 |
VFX scenes vary enormously. Simple motion design loops are cheap. Heavy simulation-based shots with volumes, particles, and multiple render passes can be expensive per frame but still far cheaper than rendering locally when you factor in time.
Feature Animation / Long-Form
| Scene Type | Engine | Resolution | Frames | Avg Frame Time | Total Est. Cost |
|---|---|---|---|---|---|
| Character animation (moderate) | Arnold CPU | 2K | 2,400 (80s) | 10-25 min | $360 – $1,000 |
| Full episode (15 min) | V-Ray CPU | 1080p | 27,000 | 3-8 min | $1,200 – $3,500 |
Long-form projects are the high end. Studios producing episodic content or feature-length animation typically negotiate volume pricing or use subscription plans.
What Drives Per-Frame Cost Up (and Down)
Understanding these factors helps you estimate costs before submitting — and optimize scenes to reduce them.
Factors That Increase Cost
Materials complexity. Multi-layer materials (car paint with clearcoat, SSS skin, caustic glass) require more ray bounces. A scene with simple diffuse materials might render 5× faster than the same geometry with physically accurate glass and SSS.
Light bounces and GI quality. Higher global illumination quality (more light bounces, higher sampling) means more computation per pixel. Production GI is often 3-5× more expensive than "good enough" preview quality.
Resolution. Linear scaling: 4K has 4× the pixels of 1080p, so it costs roughly 4× as much per frame, all else equal.
Texture resolution. 8K textures consume more memory and more disk I/O. The render time increase is modest (5-15%), but VRAM limits can force CPU fallback on GPU engines, which changes the cost profile dramatically.
Dense vegetation and particles. Forest Pack scenes with millions of scattered instances, or particle simulations with high counts, increase both memory usage and render time.
For concrete ranges on how these dense scatter scenes distribute across CPU and GPU paths, what VRAM peaks to expect, and where median vs p95 per-frame times land in 2026, our 2026 operational data on Forest Pack workloads aggregates anonymized fleet data from 2025–2026.
Factors That Decrease Cost
GPU rendering for compatible scenes. Redshift and V-Ray GPU are typically 3-8× faster per dollar than their CPU counterparts for scenes that fit in VRAM. An RTX 5090 with 32 GB VRAM handles the vast majority of production archviz scenes.
Render engine optimization. V-Ray 6/7 and Corona 12 are significantly faster than versions from 2-3 years ago. Using current versions on the farm means lower per-frame cost even for the same scene.
Adaptive sampling. Modern render engines adjust sampling per-pixel — spending more samples on complex areas and fewer on simple ones. Enabling adaptive sampling (on by default in most current engines) can reduce render time 20-40% with no visible quality loss.
Lower resolution for animation. Archviz animations rarely need 4K. 1080p or 2K is standard for video delivery, and the cost reduction is proportional.
Subscription vs. Pay-Per-Frame: Which Saves More?
This depends on your render volume and predictability.
Subscription works if:
- You render every month without fail
- Your monthly render volume is consistent (±20%)
- The subscription rate is meaningfully lower than per-unit pricing
- You have the discipline to use all included credits before expiration
Per-unit (pay-as-you-go) works if:
- Your render volume is unpredictable (project-based, not continuous)
- You have months with zero rendering
- You want to avoid sunk costs
- You prefer paying only for what you use
Pay-per-frame works if:
- You need guaranteed per-frame budgets for client billing
- Your scenes are complex enough that you'd overpay on per-unit pricing
- You value simplicity over optimization
At Super Renders Farm, we use per-unit pricing with no subscription and no contracts. Credits never expire. For studios with irregular render schedules — which describes most archviz studios — this avoids the wasted-credit problem that subscriptions create.
For a broader comparison of pricing models across major farms, see our render farm pricing guide.
For a structured side-by-side of all six pricing structures — including subscriptions, credits, hybrid plans, and IaaS rental — explore our full pricing comparison across models.
How to Estimate Your Cost Before Submitting
Here's a practical method that works regardless of which farm you use:
Step 1: Render one frame locally and note the time. Use the same settings you'd use for final output.
Step 2: Convert to farm time. Farm machines are typically faster than workstations. As a rough rule: farm CPU render time ≈ local time ÷ 2 to 4 (depends on your local hardware vs. farm hardware). For GPU: farm RTX 5090 vs. your local GPU — check benchmarks for your specific engine.
Step 3: Multiply by the farm's rate. If a frame takes 5 minutes on the farm at standard priority, and the rate is $0.004/GHz-hr on a 96.8 GHz machine: cost = (5/60) × 96.8 × $0.004 = $0.032 per frame.
Step 4: Multiply by frame count. 1,000 frames × $0.032 = $32 total.
Most farms also have a cost calculator on their pricing page, and many will provide an estimate if you submit a test frame.
The Total Cost Equation (Not Just Per-Frame)
Per-frame cost is the metric everyone asks about, but it's not the only cost that matters. The real equation is:
Total cost = (per-frame cost × frames) + upload/download time cost + artist supervision time + re-render cost for failed frames
On a fully managed farm, the last two factors are minimized: support teams handle failures, and the upload/download process is automated. On a DIY setup, failed frames and debugging time add up — we've seen studios where 10-15% of frames need re-rendering due to configuration issues, which adds that percentage to the effective cost.
For a concrete comparison between a DIY-style IaaS GPU rental service and a fully managed farm, our iRender vs Super Renders Farm comparison breaks down how the re-render policy, operator validation, and idle-time billing differ in practice.
When comparing farms, don't just compare the per-frame or per-unit rate. Ask: what happens when a frame fails? What's the re-render policy? How much of your own time will you spend managing the process?
For a concrete side-by-side on one of the common head-to-head decisions — Fox Renderfarm vs. Super Renders Farm — our comparison guide covers the pricing structure, GPU hardware, and workflow model differences.
For a European archviz-focused head-to-head, our Ranch Computing vs Super Renders Farm comparison covers priority-tiered euro pricing, TPN Gold Shield accreditation, and the self-serve-plugin versus fully-managed workflow split.
For a deeper look at the managed vs. DIY cost comparison, see our managed vs. DIY guide. And if you're evaluating whether a cloud render farm makes sense for your studio at all, our introductory guide covers the fundamentals.
FAQ
Q: How much does cloud rendering cost per frame on average? A: There is no single average — cost per frame depends on scene complexity, render engine, and resolution. For archviz at 1080p, typical costs range from $0.03 to $0.25 per frame. Heavy VFX shots can reach $1–$3 per frame. Most farms charge per compute time rather than per frame, so the actual cost scales with your scene's render time.
Q: Is GPU rendering cheaper per frame than CPU rendering? A: For scenes that fit in GPU VRAM, yes — GPU rendering (Redshift, Octane, V-Ray GPU) is typically 3-8× faster per dollar than CPU rendering. An RTX 5090 with 32 GB VRAM handles most production archviz and motion design scenes. Scenes that exceed VRAM fall back to CPU or out-of-core mode, which eliminates the cost advantage.
Q: What's the difference between pay-per-frame and pay-per-compute-time pricing? A: Pay-per-frame charges a fixed rate regardless of render time — simple to budget but you may overpay for simple scenes. Pay-per-compute-time (GHz-hour or OBh) charges for actual compute used — more transparent and efficient, but per-frame cost varies with scene complexity. Most professional farms use compute-time pricing.
Q: How much does a typical archviz animation cost to render on a farm? A: A 30-second walkthrough at 1080p (900 frames) typically costs $40–$150 on a cloud render farm using V-Ray or Corona CPU. GPU rendering with Redshift can bring that to $18–$55 for the same animation. The exact cost depends on scene complexity, material quality, and GI settings.
Q: Is a render farm subscription worth it compared to pay-as-you-go? A: Subscriptions save money if you render every month with consistent volume. For studios with irregular schedules — project-based work with gaps between renders — pay-as-you-go avoids wasted credits. At Super Renders Farm, we use per-unit pricing with no subscription and credits that never expire, which suits studios with variable render loads.
Q: How can I reduce my per-frame cost on a cloud render farm? A: Enable adaptive sampling in your render engine (most have it on by default). Use GPU rendering when your scene fits in VRAM. Reduce resolution for animation (1080p is standard for video delivery). Optimize materials — simplify glass and SSS where full physical accuracy isn't visible. Render a test frame first to estimate total cost before submitting the full job.
Q: What happens if frames fail during rendering — do I pay for them? A: On fully managed farms like Super Renders Farm, failed frames are typically re-rendered at no additional charge. The farm's support team investigates failures (missing textures, plugin conflicts, VRAM overflows) and resolves them. On DIY or IaaS setups, troubleshooting and re-rendering is your responsibility, which adds to the effective per-frame cost.
Q: How do I compare render farm pricing across different providers? A: Compare total cost, not just the rate. Calculate: (rate × estimated compute time × frames) + any upload/download fees + any minimum charges. Then factor in re-render policies and support quality. A farm with a slightly higher rate but zero re-render charges and expert support often costs less overall than the lowest per-unit option. Our pricing guide has a detailed comparison framework.
For a provider-by-provider price breakdown across eight cloud render farms in 2026 — including which one wins for archviz, animation, VFX, and Blender freelancers — see our cheapest render farm comparison.
About Thierry Marc
3D Rendering Expert with over 10 years of experience in the industry. Specialized in Maya, Arnold, and high-end technical workflows for film and advertising.
