Redshift Hardware Requirements in 2026: GPU, VRAM, CPU, RAM and Storage
What Redshift needs from each part of a workstation, and where to spend the budget:
- Official floor: Maxon lists an NVIDIA GPU with CUDA compute capability 5.0 and 8 GB of VRAM, 16 GB of RAM and a 64-bit CPU with AVX2 as the minimum on Windows; it recommends RTX GPUs with 12 GB of VRAM or more and 32 GB of RAM.
- GPU first: Redshift renders entirely on the GPU, so the cards set the render time and their VRAM sets how much of a scene fits before Redshift has to page data out of core.
- CPU second: the CPU does not render, but a fast one keeps Cinema 4D, Maya or Houdini responsive, and the platform decides how many GPUs you can fit.
- On iRender: 1x to 8x RTX 4090 (24 GB) or RTX 5090 (32 GB) servers on Threadripper PRO, with Cinema 4D and Redshift pre-installed, so you can test your scene on the hardware before you buy it.
Redshift is a GPU renderer, so the usual workstation advice does not fully apply: a 64-core CPU will not make a frame render faster, while a second GPU often will. This guide goes through Maxon’s official requirements, then each part of a Redshift machine in order of importance, with our own measured runs where we have them and three example configurations at the end.
1. Maxon’s official Redshift requirements
These are the figures Maxon publishes for Windows and Linux. Treat the minimum as “it will start”, not as a production target:
| Component | Minimum | Recommended |
|---|---|---|
| GPU | NVIDIA GPU with CUDA compute capability 5.0 or higher and 8 GB VRAM; or AMD RDNA 2 or later with 8 GB VRAM (Windows) | Multiple NVIDIA GPUs with compute capability 7.0 or higher, 12 GB of VRAM or more and RTX technology; or multiple AMD “Navi” GPUs with 12 GB or more |
| CPU | 64-bit processor with AVX2 support | Core i7 or Xeon equivalent or better, 3.0 GHz+ |
| RAM | 16 GB | 32 GB or more |
| RT features | RedshiftRT needs an NVIDIA RTX GPU on Windows 10 and 11 | — |
Source: Maxon: Redshift requirements. Maxon’s support article on system requirements also lists NVIDIA driver 570 or later as the minimum for current versions (Maxon support).
2. GPU: speed and VRAM decide everything
Puget Systems puts it plainly: Redshift is a fully GPU-based renderer, so the video cards decide how long renders take, not the CPU. Two properties of a card matter: its raw speed and the amount of memory on it. When a scene does not fit in VRAM, Redshift can still render it by moving data out of core to system memory, but Puget notes this comes with a reduction in speed, so the advice is to buy cards with enough memory on board (Puget Systems: Hardware Recommendations for Redshift).
The two cards most Redshift users compare today:
| Spec | RTX 4090 | RTX 5090 |
|---|---|---|
| VRAM | 24 GB GDDR6X | 32 GB GDDR7 |
| Memory bandwidth | 1,008 GB/s | 1,792 GB/s |
| CUDA cores | 16,384 | 21,760 |
| Board power | 450 W | 575 W |
NVIDIA specifications.
Redshift can use several GPUs at once and spreads the render blocks of each frame across them, so a second, third or fourth card shortens render time. It does not add memory: each card has to hold the scene in its own VRAM, so the size limit is set by the smallest card in the machine.
What multi-GPU servers achieve on real jobs, from Redshift runs we recorded on video (different scenes, so compare each row on its own):
| Test scene | Server | Frames | Render time | Cost at list price |
|---|---|---|---|---|
| Cinema 4D animation, 1080p | 5i · 4x RTX 5090 | 150 | 1h 42m · 40.84 s/frame | ~$64.66 |
| Fluid and particle animation, 1080p | 9S · 8x RTX 4090 | 360 | 1h 18m 13s (1h 21m billed) | $70.20 |
| Cinema 4D animation, 1080p, 30 fps | 4S · 2x RTX 4090 | 300 | ~2h 50m · 33.95 s/frame | ~$42.44 |
| Cloth simulation, 1080p | 3i · 1x RTX 5090 | 301 | 1h 46m 30s · 21.3 s/frame | — |
Source: iRender multi-GPU render benchmarks, each row with its video.
Put together, each part of the machine limits a different thing:
The GPU rows decide most of the render time, which is why this guide spends the most space on them. CPU, RAM and storage matter when they hold the GPUs back, for example a long scene export in the 3D app or slow texture loading. The next sections cover each of them.
3. CPU: clock speed for the 3D app, platform for the GPUs
The CPU does not take part in Redshift’s rendering. It does run your 3D app, and it hands the scene to Redshift at the start of every frame, so a CPU with a high clock speed keeps modeling, animation and scene extraction fast. Puget’s advice is to choose a high-clock CPU without worrying about core count and to put the budget into GPUs instead; its single- and dual-GPU Redshift workstation uses an AMD Ryzen 7 9700X (Puget Systems: Hardware Recommendations for Redshift).
The CPU platform matters once you add GPUs, because it decides how many cards the board can feed. Desktop platforms have a limited number of PCIe lanes, so a board with several cards splits them. Workstation platforms such as AMD Threadripper PRO have many more: Puget’s multi-GPU Redshift workstation uses a Threadripper PRO 9965WX, and the Threadripper PRO 3955WX and 5975WX in iRender servers each provide 128 PCIe 4.0 lanes.
4. RAM and storage
RAM. Maxon’s minimum is 16 GB and its recommendation 32 GB or more (Maxon: Redshift requirements). System RAM also holds the data Redshift pages out of core when a scene does not fit in VRAM, and your 3D app, caches and textures need room too, so heavy scenes and simulations benefit from more.
Storage. Keep the project, textures and simulation caches on a local NVMe SSD. Redshift reads textures and caches during every frame, and a slow or network drive adds wait time that no GPU can hide. Pre-converting textures with the Redshift Texture Processor also saves conversion time at render (Maxon: Redshift Log Files).
5. Three example Redshift configurations
Our suggestions, built from Maxon’s requirements and Puget’s recommendations above. Prices change quickly, so the table lists parts rather than prices:
| Part | Look development, 1 GPU | Production, 2 GPUs | Studio, 4 GPUs or more |
|---|---|---|---|
| GPU | RTX 5080 (16 GB) or RTX 5090 (32 GB) | 2x RTX 5090 (32 GB each) | 4x RTX 5090, or a rendering server |
| CPU | High-clock desktop CPU such as Ryzen 7 9700X | High-clock desktop or Threadripper PRO | Threadripper PRO (many PCIe lanes) |
| RAM | 64 GB | 128 GB | 128–256 GB |
| Storage | 1–2 TB NVMe SSD | 2 TB NVMe SSD + project drive | NVMe SSDs + shared storage |
Our suggestion based on the sources in this article, not a benchmark result.
Four RTX 5090 cards draw about 2.3 kW at their rated board power (4 × 575 W, our calculation), before the CPU and the rest of the system, so a 4-GPU machine also needs the power, cooling and space to match. That is where many studios rent multi-GPU servers for the heavy jobs instead.
SaaS or IaaS render farm when you are sizing Redshift hardware?
A Redshift scene renders the same on any farm that runs the same 3D app and Redshift versions; the settings come from your file. The difference is what you can do around the render. On a SaaS render farm you upload the scene, the farm picks the hardware and returns frames. On an IaaS render farm such as iRender you rent a specific GPU server, open the scene yourself and measure memory use and render time on that hardware.
| Your situation | SaaS render farm | IaaS render farm (iRender) |
|---|---|---|
| The scene is finished and fits your GPU; you need frames | A good fit: upload, submit and download frames, with no machine to manage | Works too, but you start the server and run your 3D app yourself |
| You have a deadline and need to know when rendering starts and ends | Jobs join the farm’s queue, so the start time depends on how busy the farm is; many farms sell higher-priority plans to start sooner | The server runs only your job from the moment it boots, so you control when rendering starts and can time the whole job |
| You are choosing between a 24 GB and a 32 GB card | You see render times on the farm’s hardware, not on a card you choose | Rent a 1-GPU RTX 4090 or RTX 5090 server and time your own frame on each |
| You are deciding whether 2 or 4 GPUs are worth it | You see the total job time, not the effect of more cards | Render the same frame on a 2x and a 4x server and compare the times |
| The scene may not fit in VRAM | The log tells you after the job | Open the scene and read the memory figures in the Redshift log before committing |
| A deadline with many frames | The farm spreads frames across its machines | Rent a 4x or 8x server, or several servers with split frame ranges |
A comparison of how the two farm models work for this task, not a speed test.
A simple rule: if the scene is ready and you only need frames, a SaaS farm is the shorter path. If you are still deciding what hardware to buy, you need a machine you can open and measure, which is what an IaaS server gives you.
A hardware test workflow on an iRender server
- Upload first. Put the scene and textures in iRender Drive before you start a server; transfer and storage are free and no rental time runs while you upload.
- Pick the hardware to test. RTX 4090 servers (3S, 4S, 5S, 9S) have 24 GB per GPU; RTX 5090 servers (3i, 4i, 5i, 9i) have 32 GB. 1-GPU servers have a one-hour minimum; multi-GPU servers bill per minute.
- Open the scene. Cinema 4D and Redshift are pre-installed; install your plugins.
- Measure. Render the heaviest frame at final settings and note the rendering time and memory figures from the Redshift log.
- Compare. Repeat on a server with more GPUs or more VRAM, then decide what to buy, or render the job on the server that fits.
Frequently asked questions
1. What are the minimum requirements for Redshift?
On Windows, Maxon lists an NVIDIA GPU with CUDA compute capability 5.0 or higher and 8 GB of VRAM (or AMD RDNA 2 with 8 GB), a 64-bit CPU with AVX2 support and 16 GB of RAM.
2. How much VRAM do I need for Redshift?
Maxon recommends 12 GB or more. Heavier production scenes benefit from 24 GB or 32 GB, because a scene that fits in VRAM avoids slower out-of-core rendering.
3. Does the CPU matter for Redshift?
Not for render speed, because Redshift renders on the GPU. A high-clock CPU keeps your 3D app and scene extraction fast, and a workstation platform such as Threadripper PRO lets you fit more GPUs.
4. Do multiple GPUs speed up Redshift?
Yes. Redshift spreads the render blocks across all the GPUs, so more cards shorten render time. They do not add VRAM; each card needs the scene in its own memory.
5. Is the RTX 5090 better than the RTX 4090 for Redshift?
It has 32 GB of VRAM against 24 GB and more memory bandwidth, so more scenes stay in VRAM. Test your own scene on both to see the speed difference for your work.
6. How much RAM does Redshift need?
Maxon’s minimum is 16 GB and its recommendation 32 GB or more. Heavy scenes, caches and out-of-core data use more.
Render your Cinema 4D and Redshift projects on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. Your server image is saved between sessions, so your plugins and settings stay installed. Cinema 4D and Redshift are pre-installed on every server.
Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This quick start shows how to start a server and render Cinema 4D and Redshift on it:
Two Redshift runs we recorded on our servers: 150 frames at 1080p on 4x RTX 5090 at 40.84 seconds per frame (about 1h 42m), and a 301-frame cloth simulation at 1080p on 1x RTX 5090 at 21.3 seconds per frame:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Cinema 4D and Redshift render farm page or download the iRender GPU app.




