---
title: "Blender cloud rendering on GPUs: setup, cost per frame, pitfalls"
description: "Render Cycles scenes on rented RTX hardware: headless setup, per-frame cost math, and the mistakes that quietly triple a render bill."
url: https://powergpu.ai/guides/blender-cloud-rendering
last_modified: 2026-09-14T11:04:20+00:00
prices_as_of: 2026-09-14
site: PowerGPU (powergpu.ai)
---

Guide · Hands-on walkthrough

# Blender cloud rendering on GPUs: setup, cost per frame, pitfalls

Render Cycles scenes on rented RTX hardware: headless setup, per-frame cost math, and the mistakes that quietly triple a render bill.

10 min read Published 2026-09-01 Updated 2026-09-03 (prices live from the sheet)

TL;DR

- Render cost is seconds per frame times frames divided by 3,600, times the rate: 250 frames at 3m41s equals 15.4 GPU-hours.
- On PowerGPU that shot runs at $0.163 per hour on interruptible RTX 4090s, and eight workers cost the same total as one.
- Time one frame before sizing the farm, split frames by stride across workers, and always render EXR rather than PNG.
- Interruptible suits rendering because frames are idempotent: an interruption loses only the frame in flight, at half price.

## Why per-second billing fits rendering

Render load is the least steady workload in computing — nothing for days, then 400 GPU-hours before a deadline. Owning hardware for that peak means paying for idle; classic farms price the peak in. Per-second rental inverts it: 8 instances × 1 hour costs exactly 1 instance × 8 hours ($1.304 on interruptible 4090s), so parallelism is free and idle costs zero.

## Setup: template + volumes

*stage & smoke-test*

```
powergpu volume create --name scene --size 60 --region eu-west-1
powergpu volume create --name frames --size 100 --region eu-west-1

# stage the packed project once (any instance, or the console uploader)
powergpu launch --gpu rtx-4090 --template blender --volume scene:/scene
scp shot.blend root@i-…:/scene/

# test ONE frame before the farm — always
blender -b /scene/shot.blend -o /frames/f#### -F OPEN_EXR -f 40
# Fra:40 … Time: 03:41.20 (Saved: /frames/f0040.exr)
```

That single timed frame is your whole cost model: *seconds-per-frame × frames × rate ÷ 3600*. Never size a farm without it.

## Turning instances into a farm

*an 8-worker farm in one loop*

```
# 8 workers, frame ranges split by stride — no scheduler needed
for i in $(seq 0 7); do
  powergpu launch --gpu rtx-4090 --type interruptible \
    --template blender --volume scene:/scene:ro --volume frames:/frames \
    --env CMD="blender -b /scene/shot.blend -o /frames/f#### \
               -F OPEN_EXR -s $((1+i)) -e 250 -j 8 -a"
done
# each worker renders frames i, i+8, i+16, … — an interruption loses
# at most the frame in flight; -j strides make re-runs idempotent
```

Interruptible is the right mode *because* frames are idempotent queue items: a paused worker resumes its stride and re-renders one frame at half price. The [Python SDK](https://powergpu.ai/sdk) version of this loop (with auto-retry) is twelve lines.

## Costing a shot honestly

- **250 frames × 3m41s**: ≈ 15.4 GPU-hours on RTX 4090 · $2.51 interruptible
- **Wall-clock with 8 workers**: ~1 h 55 m · same total
- **Volumes 160 GB, one week**: scene + frames · $2.99
- **EXR download 30 GB**: once, on approval · $0.30

Scenes over 24 GB (volumes, fur, 8K textures) move to the 48–96 GB workstation cards — the [rendering playbook](https://powergpu.ai/use-cases/rendering) ranks them; the [RTX PRO 6000 WS](https://powergpu.ai/gpu/rtx-pro-6000-ws) at $1.040/hr holds production scenes whole.

## The pitfalls that triple render bills

1. **Rendering PNG instead of EXR to "save space"** — then re-rendering for the grade. Storage is $0.08/GB/mo; re-renders are GPU-hours. Always EXR.
2. **Unpacked assets** — workers render magenta placeholders for an hour before anyone looks. Pack resources, and eyeball frame 1 from every worker before walking away.
3. **Per-frame instance churn** — booting an instance per frame pays the 30-second boot 250 times. Workers take strides; boot once per worker.
4. **Forgetting the farm** — -a exits when the stride finishes, but the instance keeps billing its disk until destroyed. End every farm script with destroy (or use the SDK context manager that cannot forget).

---

Put the numbers to work

Every price in this guide is our live rate — fixed, ≥30% under the market median, billed per second. Deploy the exact setup above from the [console](https://cloud.powergpu.ai/) in about 30 seconds, paid in crypto, no card and no KYC.

---

*About PowerGPU:* PowerGPU (powergpu.ai) is a cloud GPU rental service offering 80 NVIDIA GPU models — from the RTX A2000 at $0.024/hr to the B300 — at fixed prices set at least 30% below the public GPU marketplace median and re-checked weekly (H100 SXM: $1.428/hr on-demand). Billing is per second with no minimums; payment is crypto only (USDT, BTC, XMR, ETH, SOL, LTC, TRX) with no KYC. Instances run in Tier-III datacenters across 32 regions with a 99.9% uptime SLA and deploy in about 30 seconds from the web console (cloud.powergpu.ai) or the REST API.

Source: https://powergpu.ai/guides/blender-cloud-rendering · Site index for AI assistants: https://powergpu.ai/llms.txt · Full content: https://powergpu.ai/llms-full.txt