Blender
Fully supportedThe Blender render farm service that stays in your viewport
RenderSonic is a render farm service built for Blender: submit straight from the render menu. It reads your active scene, camera and output settings automatically, syncs linked textures and packed data to the cloud node, and delivers finished frames back into your local output folder.
Built for Blender
One-click plugin install
RenderSonic detects your Blender install and adds the submission panel automatically - no manual add-on installation.
Packed & linked data handled
External textures, linked libraries and packed files are all synced before the job starts, so nothing renders missing.
Cycles and Eevee, same workflow
Switch render engines in Blender as usual - RenderSonic submits either one with the same cost and time estimate flow.
Render hardware
Render Blender on CPU or GPU - your choice
You choose for every job whether it renders on CPU nodes or GPU nodes, so each scene runs on the hardware that suits it.
CPU nodes
Server and workstation-class processors for CPU renderers and for scenes too large to fit in GPU memory.
- AMD EPYC128 or 256 GB RAM
- AMD Ryzen128 GB RAM
- Intel Xeon128 GB RAM
GPU nodes
NVIDIA RTX cards for GPU-accelerated render engines. Your scene's geometry and textures need to fit in the card's video memory (VRAM).
- NVIDIA GeForce RTX 509032 GB VRAM
- NVIDIA GeForce RTX 409024 GB VRAM
- NVIDIA GeForce RTX 309024 GB VRAM
- NVIDIA RTX A400016 GB VRAM
Which should I choose?
- Choose GPU
- For GPU-accelerated engines, when speed matters most and the scene fits within the card's VRAM.
- Choose CPU
- When a scene's geometry and textures exceed GPU memory, or the render engine runs on CPU only.
FAQ
Blender questions
Can't find what you're looking for? Reach out and we'll get back to you.
Which Blender versions are supported?
Blender 3.x, 4.x and 5.x.
Which render engines does RenderSonic support for Blender?
Cycles, Eevee and V-Ray are supported.
Can I render Blender scenes on CPU or GPU?
Yes - you choose for each job. CPU nodes run AMD EPYC (128 or 256 GB RAM), AMD Ryzen (128 GB RAM) and Intel Xeon (128 GB RAM). GPU nodes run NVIDIA GeForce RTX 5090 (32 GB VRAM), NVIDIA GeForce RTX 4090 (24 GB VRAM), NVIDIA GeForce RTX 3090 (24 GB VRAM) and NVIDIA RTX A4000 (16 GB VRAM).
Does RenderSonic support Blender add-ons?
Yes - all Blender add-ons are supported, including Geo-Scatter, Botaniq, FLIP Fluids and Physical Starlight and Atmosphere. If you use one that isn't listed on this page, tell us and we'll add it. For physics and particle simulations, bake the cache before submitting so every render node produces identical frames.
Do I need to pack my .blend file before submitting?
No. RenderSonic reads your scene and syncs external textures, linked libraries and packed files to the render node before the job starts, so nothing renders missing. You submit from Blender's render menu exactly as you would render locally.
Should I render Cycles on CPU or GPU?
Choose GPU for most Cycles scenes: NVIDIA RTX cards render Cycles with OptiX or CUDA far faster than CPUs, as long as the scene fits in the card's VRAM (up to 32 GB on an RTX 5090). Choose CPU nodes for very heavy scenes whose geometry and textures exceed GPU memory.
Can I render Eevee animations on the farm?
Yes. Eevee stills and animations are supported alongside Cycles and V-Ray. Eevee is a GPU-based engine, so submit Eevee jobs to GPU nodes.
Are fluid, smoke and cloth simulations supported?
Yes. Bake the simulation cache locally (for example Mantaflow fluids, smoke, cloth or FLIP Fluids) and keep the cache files with your project. RenderSonic syncs them with the scene, so every frame renders from the same simulation.