
Render Faster: GPUs, Farms and Cloud Rendering
TL;DR
Find what is slow first: settings, scene, or hardware. Fix the settings and scene with the app tips, use the GPU where the renderer supports it, and send locked frame batches to a farm. Use a cloud computer when you also need to work on the scene.
Updated
·
6 chapters
·
10 min read
Start here: read the first post →
See the chapters ↓
In this guide
What you’ll learn
6 chapters

01
Find the bottleneck: CPU, GPU, farm or cloud workstation
How to decide between more hardware, a render farm and a cloud computer before you touch any settings.
Jump to chapter ↓

02
Blender: settings, engines and speed
Cycles or Eevee, GPU compute, samples and noise threshold, and the tips that cut time first.
Jump to chapter ↓

03
Twinmotion, Lumion, Enscape and V-Ray
Render modes and settings for architectural visualization, plus the GPU choices behind them.
Jump to chapter ↓

04
CAD and BIM renders: Revit, AutoCAD, SketchUp, SolidWorks, Rhino
Draft first, trim lights and geometry, and use proxies, with the setting that matters in each app.
Jump to chapter ↓

05
Video and compositing: Resolve, Premiere, After Effects, Nuke
GPU acceleration, optimized media and cache, multi-frame rendering and fast storage.
Jump to chapter ↓

06
Cinema 4D, Maya, 3ds Max, Houdini, ZBrush and Unreal
DCC-specific render tips and GPU picks.
Jump to chapter ↓
A slow render can come from three places: the settings, the scene, or the hardware. Most guides jump straight to hardware. This guide starts earlier. It helps you find the bottleneck, then routes you to Vagon's per-app render posts, and then compares your options when hardware really is the limit: a better GPU, a render farm or a cloud computer. It summarizes the posts and does not promise a speed-up, since results depend on your scene, renderer and hardware.
Find the bottleneck: CPU, GPU, farm or cloud workstation
CPU vs. GPU Rendering explains the underlying split. A CPU is a small team of strong workers. A GPU is thousands of tiny workers doing the same math at once, which suits path tracing, ray bounces and shader calculations. The catch with GPUs is VRAM: even a 24 GB card can run out when a scene has high-resolution assets, and renderer compatibility varies. The post then matches hardware to workflow, with sections for beginners, constant animators and simulation-heavy work.
Render Farm vs. Cloud Workstation is the most useful decision post here. A farm processes queued render jobs and nothing else. It fits a locked scene with many independent frames, predictable output settings, portable assets and baked caches. A Vagon cloud computer is a remote Windows workstation where you can still build assets, adjust lighting, scrub a timeline, fix broken links and render test frames. The post also lists what to verify for each route, including exact application and renderer versions, plug-ins, license rules, asset paths and color settings. Its suggested hybrid is practical: build and test on the cloud computer, then submit the approved batch to a compatible farm and bring the frames back for review.
If you do pick a farm for Blender, Top Renderfarm and Cloud Rendering Services for Blender Users lists several and explains how to choose.
Read next
Blender: settings, engines and speed
The most-read Blender post, The Best Render Settings for Blender, opens with an honest point: there is no single best setting. Its rule of thumb is to use Eevee when speed matters more than physical realism and Cycles when realism matters more. A good workflow is to block out and iterate in Eevee, then switch to Cycles for the final.
For Cycles, set Device to GPU Compute first, and make sure Preferences point to the right backend: OptiX on NVIDIA, HIP on AMD, oneAPI on Intel, Metal on Apple Silicon. Then use Max Samples with a Noise Threshold instead of raising samples blindly. The post suggests 64 to 150 samples for fast previews, 200 to 300 for clean drafts and 300 to 800 for final stills. It also covers denoising, trimming light paths and turning on Persistent Data for animation.
How to Render Faster in Blender 3D turns this into a numbered list of fifteen tips: choose the engine first, switch to GPU, turn on denoising earlier than you think, lower samples until the image breaks and then walk back, use adaptive sampling, cut light bounces, remove expensive features you do not see, simplify geometry, bake what need not be procedural, optimize textures, use render regions for tests, tune Eevee, and accept when hardware is the limit. For engines beyond the built-ins, see Best Blender Render Engines, and for Eevee specifically, Blender Eevee Essentials.
Read next
Twinmotion, Lumion, Enscape and V-Ray
The Twinmotion settings post, Best Render Settings in Twinmotion, is the most-read render post in the library. It starts with the three modes. Real-Time Rendering is quick for a client meeting. Lumen is more polished, with realistic lighting. Path Tracer is for ultimate realism on a final. It then goes through resolution and output, lighting, materials and post-processing, plus performance tips on LOD settings, asset management and viewport resolution scaling. Your Guide to Best Render Settings on Twinmotion adds Twinmotion Cloud, which lets stakeholders explore the project from a link without powerful hardware, and tips for realism such as contrast, deliberate imperfection and realistic camera settings.
GPU choice is the other lever. Best GPU for V-Ray says VRAM is first, because if the scene does not fit nothing else matters, and to ignore gaming benchmarks. Best GPU for Lumion calls Lumion one of the most GPU-intensive renderers, again with VRAM the biggest factor. The GPU guide for Enscape does the same for that tool. If you are choosing between engines, read Lumion vs. Twinmotion, Enscape vs. Lumion and Enscape vs. V-Ray. For whole-machine specs, read Best PC for architecture and BIM.
Read next
CAD and BIM renders: Revit, AutoCAD, SketchUp, SolidWorks, Rhino
CAD tools share a pattern: render a draft first, then trim. How to Render Faster in Revit tells you to start with "Draft", adjust DPI, pick the right quality and size, reduce file size, reduce the number of lights and exclude scene backgrounds. How to Render Faster in SketchUp puts scene cleanup first, then proxies, plugins and hardware, and adds a section for weak devices. How to Render Faster in AutoCAD walks through the rendering process, hardware, in-app settings and plugins. Best Render Settings for SolidWorks groups settings into quality and denoiser, resolution, lighting and camera, materials and geometry, and shadows and reflections, then gives presets for different scenarios. How to Render Faster on Rhinoceros covers Cycles settings, denoisers and scene optimization.
If you are unsure which renderer to use at all, Rendering Software for Architects compares options for AutoCAD, SketchUp and Revit users.
Read next
Video and compositing: Resolve, Premiere, After Effects, Nuke
For video, the bottleneck is usually the balance of parts. How to Reduce Rendering Times in Premiere Pro distinguishes rendering, previewing and exporting, then walks through CPU, GPU, RAM and storage. Its storage point is easy to miss: during export, Premiere reads source media, previews and cache while writing the file, and a slow drive leaves the CPU and GPU waiting. Its closing idea applies to all of them: speed is about balance, not one impressive spec. The older Premiere Pro post covers basics.
For Resolve, the complete optimization guide lists GPU acceleration, render settings, optimized media and render cache, fewer heavy effects, a clean timeline and system tweaks, and this second guide adds common and advanced tips. Tips for Faster Rendering in After Effects starts with Multi-Frame Rendering, which only helps if you set it up properly, since effects that do not support it hold things back. Then it covers Render Time Viz to find slow layers, smart caching, proxies, a simpler project structure, codecs and GPU acceleration. For Nuke, How to Speed Up Nuke Renders focuses on the node graph: clean it up, avoid heavy nodes, use precomps and proxy mode, and cache manually.
Read next
Cinema 4D, Maya, 3ds Max, Houdini, ZBrush and Unreal
The DCC posts follow the same logic: lower what you do not see, then use the GPU. Cinema 4D starts with render settings (quality, global illumination, reflection depth, adaptive sampling, shadow maps) and then scene settings such as polygon count, and Best GPUs for Cinema 4D compares NVIDIA and AMD. Maya opens with choosing the right renderer, then settings, scene complexity, hardware acceleration and render layers, with a companion GPU guide. 3ds Max suggests low-poly models, turning off displacement, lowering output resolution and a denoiser, with a GPU guide. Houdini covers fewer shadows, GPU rendering, volume step rate and more. ZBrush suggests optimizing the model, using Preview Render for iteration and tuning BPR for finals.
Unreal Engine is real-time, but the same thinking applies. How to Make Unreal Engine Render Faster starts by finding what is slow: draw calls, material complexity, geometry and Nanite use, overdraw and transparency, lighting and post-processing.
Read next
What to try for your situation
Situation | Try first | Then |
|---|---|---|
Blender Cycles render is slow | Device to GPU Compute; noise threshold; denoise | More GPU or cloud computer |
Need quick iterations in Blender | Eevee for drafts | Cycles for the final |
Scene does not fit in VRAM | Simplify textures and geometry | A card or cloud tier with more VRAM |
Twinmotion render for a client meeting | Real-Time Rendering | Lumen or Path Tracer for the final |
Large locked animation, many frames | Render farm | Hybrid with a cloud computer for setup |
You still need to edit the scene | Cloud workstation | Farm for the final batch |
Premiere or Resolve export is slow | Optimized media, fast storage, GPU acceleration | Faster drive or bigger machine |
After Effects comp is slow | Multi-Frame Rendering, Render Time Viz, proxies | Larger RAM or GPU |
Revit or SketchUp render is slow | Draft, fewer lights, clean scene | Stronger GPU or cloud machine |
Doing this on Vagon
The fastest render is often the one on a bigger machine, rented only for the hours it runs. A Vagon Cloud Computer is a Windows or Linux machine in your browser with your own renderer and plug-ins installed. Build the scene on a small performance, then switch in seconds to one with up to four GPUs for the render, with the same files and apps. Shut it down when the frames are out and billing stops (pricing).
Two honest limits. One cloud computer is not a render farm, so a big locked animation may finish sooner on a farm. And if you render all day, every day, owning a GPU may cost less. Bring your own renderer licenses and check that they allow use on a remote virtual machine.
FAQ
What is the fastest way to speed up a Blender render?
Vagon's tips start with the render engine and the device. Use Eevee when speed matters more than realism and Cycles when realism matters more. In Cycles, set the device to GPU Compute (OptiX on NVIDIA, HIP on AMD, oneAPI on Intel, Metal on Apple Silicon), and use a noise threshold with a max sample ceiling instead of simply raising samples.
Is a render farm better than a cloud computer?
They do different jobs. Vagon's comparison says a farm processes queued jobs, and suits locked scenes with many independent frames. A cloud computer gives you a workspace to build, preview and fix the scene. A hybrid works: set up and test on the cloud computer, then send the approved batch to a farm.
Should I render on the CPU or GPU?
Vagon's comparison describes a GPU as thousands of tiny workers that excel at path tracing, with the trade-off being VRAM, and says Blender Cycles usually benefits from a GPU. CPU rendering suits workloads that need more memory or scale. Check what your renderer supports.
Which Twinmotion render mode should I use?
The settings guide says Real-Time Rendering is quick for a client meeting, Lumen is more polished with realistic lighting, and Path Tracer is for ultimate realism in a final render.
How do I make Premiere Pro or Resolve export faster?
Vagon's Premiere guide says export depends on a balance of CPU, GPU, RAM and storage, and that slow drives leave the CPU and GPU idle. The Resolve guide recommends GPU acceleration, optimized media and render cache, fewer heavy effects and a clean timeline.
Can a cloud computer render an animation?
Yes, you can install your renderer and render on a more powerful machine, and the comparison post says it can handle a whole interactive project. One machine has limited capacity, so a very large locked animation with many independent frames can be faster on a farm.
Read next
All posts in this guide
All guides →
Keep going
Related guides
All guides →



Hardware
6 chapters
Best GPU for 3D, CAD and video work
Match the GPU to the app, and look at VRAM before speed. CAD and editing work depends on drivers, stability and the CPU as much as raw GPU power. GPU renderers, real-time engines and AI features run out of VRAM first. If your needs change by project, renting by the minute can beat buying.
Read →



Hardware
6 chapters
Best Computers and Laptops by Creative Role
Match the machine to the job. 3D modeling and Rhino want CPU clock speed, GPU rendering wants VRAM, motion design wants RAM, and digital art and design want a good screen. Buy for your usual work and rent a cloud computer for the heavy days.
Read →



Hardware
5 chapters
Best PC for Architecture and BIM Software
Modeling apps like Revit, AutoCAD and Rhino lean on a fast CPU, enough RAM and an SSD. Visualization tools like Twinmotion, Lumion and V-Ray lean on the GPU and its VRAM. Buy for the heaviest thing you do, or rent a cloud workstation for the occasional big job.
Read →
Software
Software in this guide
Browse software →
























