Arnold GPU vs Redshift in Maya 2026: Which Fits Your Shot on a Multi-GPU Machine
The choice usually turns on features, approved frames and scene size. Check these first:
- Arnold GPU: same scene as Arnold CPU; switch the render device
- Feature gaps: Noice, Diffusion SSS, deep EXR and trace sets are among the items not supported on GPU
- Noise: Arnold GPU is non-splitting and needs higher AA samples than CPU at the same look
- Redshift: out-of-core textures and geometry for scenes larger than VRAM
- Licensing: Arnold batch needs an Arnold license on each machine; Redshift needs a Maxon license
Maya ships with Arnold, and Arnold can render on the GPU. Redshift is a separate GPU renderer that many Maya studios use for speed on multi-GPU machines. The two are not interchangeable: they use different materials, they handle GPU memory differently, and they license batch rendering differently.
This guide compares Arnold GPU and Redshift for Maya 2026 using what Autodesk and Maxon document: which features Arnold GPU does not support, how each engine handles large scenes, how each uses several GPUs, what licensing a render machine needs, and how to test both on the frame that matters.
Checked against Autodesk’s Arnold GPU feature list, Arnold licensing and system requirements, and Maxon’s Redshift for Maya documentation, November 2026.
1. Arnold GPU or Redshift: how to decide
The first question is whether the look depends on something Arnold GPU does not support. Autodesk lists, among others: Noice denoising (the variance filter is not supported on GPU), mipmap bias, Diffusion SSS mode in Standard Surface, the deep EXR driver, trace sets for many shaders and shapes, and some volume and transmission AOVs. Autodesk also notes GPU renders are non-splitting, so they are noisier at the same settings and need higher AA samples (Autodesk: Arnold GPU features and limitations).
If none of those gaps apply and the frames must match Arnold renders already approved, Arnold GPU keeps the same scene and shaders. If the scene is heavy or will be split across many GPUs, Redshift’s memory model and GPU selection usually decide it. Either way, the final answer comes from rendering the heaviest frame on the GPUs you will use.
2. What each engine does with GPU memory and several GPUs
Maxon describes out-of-core texturing and out-of-core geometry as Redshift features (Maxon: Memory (Maya)); some data, such as volume grids and VDB files, is not handled out-of-core (Maxon: What is out-of-core rendering). For several GPUs, Redshift for Maya accepts -gpu with a list of device IDs on Render.exe, and Maxon notes that using GPU subsets helps when rendering several frames at once on one machine (Maxon: Command-line Rendering and GPU Selection):
Arnold GPU uses NVIDIA GPUs on Windows and Linux (Autodesk: Arnold system requirements). Autodesk’s notes for the Arnold 7.2.5 GPU overhaul give one example of multi-GPU scaling: adding a second GPU took a test scene with 9 AOVs from a 1.1x to a 1.7x speedup (Autodesk: Arnold GPU overhaul). That is Autodesk’s scene, not a general figure; test yours.
3. How to test both engines on your scene (step by step)
The settings below set up a fair test on the heaviest frame. For Arnold GPU setup in detail, see our guide to Maya Arnold GPU rendering in 2026.
Settings checklist (copy or follow line by line):
4. Arnold GPU and Redshift side by side
The table sums up the documented differences that matter on a render machine. Licensing matters as much as speed: Autodesk states that batch rendering needs an Arnold license, and every node on a render farm needs one (Autodesk: Arnold licensing).
Arnold GPU and Redshift side by side
What changes for a Maya scene, from the vendors’ documentation.
| Topic | Arnold GPU | Redshift |
|---|---|---|
| Same scene on CPU and GPU | Yes, switch the render device | GPU renderer; Redshift CPU also exists |
| Denoising | Noice not supported on GPU (variance filter) | Its own denoisers in the render settings |
| Known gaps | Diffusion SSS, deep EXR driver, trace sets, some shapes and AOVs | Check Maxon release notes per feature |
| Scenes larger than VRAM | Not covered in the feature list | Out-of-core textures and geometry; volumes stay in VRAM |
| Several frames at once | Device selection in render settings | -gpu {ids} per Render.exe instance |
| Batch license | Arnold license on every batch machine | Maxon Redshift license per machine |
For other engines that use several GPUs in Maya, see the best multi-GPU render engines for Maya 2026. For V-Ray, see V-Ray GPU for Maya on multi-GPU machines.
5. SaaS or IaaS render farm for Arnold GPU or Redshift?
Which farm type fits each engine
Both engines can run on either farm type; the difference is licensing and who controls the test.
| Situation | Usually a better fit | Why |
|---|---|---|
| Arnold batch with the farm’s licensing | SaaS | Check that the farm covers Arnold licenses per node |
| Arnold GPU with your own Autodesk license | IaaS | You sign in to your Arnold license on the render machine |
| Redshift with GPU subsets per frame range | IaaS | You run Render.exe with -gpu on the server |
| Still deciding between the two engines | IaaS | Render the same frame with both on the same GPUs |
Rule of thumb: decide the engine on your heaviest frame, then render where licensing and setup fit.
Testing Arnold GPU and Redshift on an iRender server
An iRender server is a full Windows machine with 32 GB RTX 5090 or 24 GB RTX 4090 GPUs:
- Upload the project to iRender Drive before you start a server; uploading is free and does not use rental time.
- Start a server, install your Maya version and the matching Redshift build once; they stay in your image. Sign in to your own Arnold license for batch tests. Setup details are in Redshift for Maya on a multi-GPU render server.
- Render the heaviest frame with each engine on the same GPUs and compare time, noise and memory.
- Render the full range with the engine you chose, then shut down. Multi-GPU servers bill per minute; 1-GPU servers have a one-hour minimum.
Arnold GPU vs Redshift test checklist
Tick each item before you commit to one engine.
Frequently asked questions
1. Is Arnold GPU the same as Arnold CPU?
It uses the same scene and shaders, and you switch the render device. Autodesk lists features that are not supported on GPU and notes GPU renders are non-splitting, so they need higher AA samples for the same noise level.
2. Which Arnold features do not work on GPU?
Autodesk lists, among others, Noice denoising, mipmap bias, Diffusion SSS mode, the deep EXR driver, trace sets for many shaders and shapes, and some volume and transmission AOVs.
3. Can Redshift render scenes larger than GPU memory?
Maxon describes out-of-core textures and geometry for that case. Some data, such as volume grids and VDB files, is not handled out-of-core and must fit in VRAM.
4. How do I choose GPUs for Redshift from the command line in Maya?
Use -gpu with a list of device IDs, for example Render.exe -r redshift -gpu {0,1} scene.ma. Device IDs are listed in Redshift’s preferences.xml.
5. Does Arnold GPU scale with more GPUs?
Autodesk gives one example from the Arnold 7.2.5 GPU overhaul: adding a second GPU raised a test scene’s speedup from 1.1x to 1.7x. Results depend on the scene, so test yours.
6. Do I need an Arnold license to batch render?
Yes. Autodesk states batch rendering needs an Arnold license, and every node on a render farm needs one; interactive rendering inside Maya does not.
7. Can I convert an Arnold scene to Redshift?
Not directly. Redshift uses its own materials, so the look has to be rebuilt and compared on test frames.
8. Can I test Arnold GPU and Redshift on iRender?
Yes. An iRender server is a full Windows machine where you install Maya and Redshift, sign in to your own Arnold license for batch rendering, and render the same frame with both engines on the same GPUs.
Render your Maya 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. Maya is not pre-installed: you install the Maya version your scene uses with your own Autodesk license, and it stays in your image. Prime accounts get Redshift licenses pre-activated 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 connect to it:
A full Maya and Redshift session we recorded on an 8x RTX 4090 server:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Maya render farm for Redshift page or download the iRender GPU app.
Sources: Autodesk: Arnold GPU supported features and limitations · Autodesk: Arnold GPU overhaul (7.2.5) · Autodesk: Arnold system requirements · Autodesk: Arnold licensing · Maxon: Memory (Redshift for Maya) · Maxon Support: What is out-of-core rendering · Maxon: Command-line Rendering and GPU Selection (Maya). Checked November 2026.



