Blender Render Server — from €5.49/mo
Run Cycles on a multi-core server while your own computer stays free — a 5-hour test period, so you risk nothing
Start rendering now
A Blender render server is a virtual server for background CPU rendering in Cycles: the scene computes on the server while your working computer stays free. Cycles renders natively on the processor, so this kind of node needs no graphics card — speed is set by the core count and the memory available for the scene. For regular rendering people take 16 vCPU and 24 GB RAM (Power 3, €27.99/mo); for heavy high-resolution frames — 40 vCPU and 64 GB (Max 3, €84.99/mo); the range starts at €5.49/mo. Eevee is a real-time engine and requires a GPU — for it you need a configuration with a graphics card. A 5-hour test period before payment is available — run your own .blend and compare frame times. The other plans are on the VPS hosting page.
Plans
VPS for Blender rendering
Frame time in Cycles drops almost linearly with the core count, so rendering calls for the higher plans: Power 3 — 16 vCPU and 24 GB for €27.99/mo, Max 3 — 40 vCPU and 64 GB for €84.99/mo. The range starts at €5.49/mo, with a 5-hour test period before payment.
Compare all plansStandard 1
| 4 vCPU · AMD EPYC |
| 4 GB RAM |
| 50 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Standard 2
| 4 vCPU · AMD EPYC |
| 6 GB RAM |
| 60 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Strong vCPU for Cycles
Ray tracing in Cycles parallelises across cores: 16 vCPU compute a frame roughly four times faster than 4.
Plenty of RAM and NVMe
Heavy scenes with high-poly models and textures fit in memory, and the NVMe drive writes the output fast.
Background rendering over the network
Launch renders with the blender -b command and collect finished frames without tying up your own computer.
How to launch a render
Choose a plan and an image
Size the configuration to your scenes — from Power 3 (16 vCPU, 24 GB) to Max 3 (40 vCPU, 64 GB) — and pick an OS image, usually Linux.
Install the OS and Blender yourself
Through the KVM console you deploy the OS yourself, install the Blender version you need and upload your .blend files and textures.
Render and collect the frames
Connect over SSH or RDP, run the render in the background and download the finished images and animation.
Batch rendering and animation with no queues
Compute long animations frame by frame on a separate server: your working computer stays free while the render runs around the clock.
Full root access lets you install the Blender version, add-ons and automation utilities your visualisation pipeline needs. For rendering in other packages there is a 3D rendering server, and CAD scenes are prepared on a VPS with 3ds Max.
Ask a questionFrequently asked questions
Didn't find your answer?
Write to us via the contact page.
Yes, Cycles renders natively on the processor — the normal mode for render nodes. Speed is set by the core count, which is why rendering calls for the higher plans.
For regular CPU rendering take at least 16 vCPU and 24 GB — Power 3 at €27.99/mo. Heavy high-resolution scenes compute on Max 3: 40 vCPU and 64 GB at €84.99/mo.
The whole scene loads into memory, so RAM should be roughly double the size of the .blend with textures. A 10 GB project renders comfortably on 24 GB (Power 3).
Not on these plans: Eevee is a real-time engine and requires a graphics card. It needs a GPU configuration, while our VPS are built for CPU rendering in Cycles.
You do: pick the image yourself and install the OS through the KVM console, then the Blender version and add-ons you need. Hardware-level access lets you reinstall the system any time.
From the command line with blender -b: the scene computes in the background and you can disconnect from the server. Collect the output over SSH or from a shared folder.
Over SSH with scp or rsync, or by mounting the render folder as a network drive. Frames sit on the server's NVMe — 240 GB (Power 3) holds a long EXR sequence.
Yes. Over SSH and Blender's command line you can set up batch rendering, scripts and queues — the server computes frames without your involvement.