Animation and film: your Blender sequences on several GPUs,
while you animate
Short films, series, game cinematics: your Blender frames split across 1 to 8 GPUs in parallel, billed on the time used.
How the service works in general, tiers included, is described on the Blender render farm page.
Why choose TURNA for your projects?
The frames of a sequence split across 1 to 8 machines in parallel
Your file's output format kept, multilayer OpenEXR included
An MP4 preview of the sequence, produced separately from the archive
Render machine destroyed at the end of the render
Ready to speed up your renders?
€25 of free credit when you sign up, no credit card required.
See our pricingA sequence split frame by frame
Each frame of an animation renders independently of the others. TURNA sends your scene from the Blender add-on, then splits the frames of the chosen range across the machines of the tier: 1, 2, 4 or 8 render at the same time. The wait is divided accordingly, the total compute stays the same, and you do not have to cut the sequence up yourself.
If a machine stops along the way, the frames it had not finished go to another machine, never to the one that has just failed. If the render still fails, you are refunded.
What you get at the end of the render
The render follows the output format set in your file: PNG, JPEG, TIFF, OpenEXR, or multilayer OpenEXR if you keep the passes for compositing. A video output set to FFmpeg is rendered frame by frame as PNG, which splitting across several machines requires.
You download the archive of the frames, and an MP4 preview of the sequence is produced separately for a first review. The archive stays downloadable for at least 30 days.
Before sending a sequence
- Bake your simulations. Cloth, fluids and particles must be baked before sending: the add-on reminds you, and an unbaked simulation does not appear in the final image.
- Test a few consecutive frames. Flicker from per-frame denoising only shows in motion: render five or six consecutive frames and play them back before launching the whole shot.
- Animate the noise seed. The clock icon next to Seed, in Render Properties > Sampling > Advanced, changes the noise pattern on every frame. Without it, the residual noise stays frozen on screen while the camera moves.
- Check the range and the output. The guide how to render an animation in Blender covers the frame range, the folder and the format, through to assembling an MP4.
Worked example: a 30-second animation
720 frames at 2 minutes per frame, i.e. 30 seconds at 24 frames per second. This time per frame is that of an RTX 4090, the card TURNA falls back on. On your computer, with an RTX 3060, each frame takes about 8 minutes: count on 91 h 12 during which it can do nothing else. On TURNA, your computer stays free and, on Turbo, the shot is ready in 3 h 00.
Your computer
RTX 3060, tied up during the render
91 h 12
TURNA Standard
1 GPU · €69.60 excl. VAT
67 h 12 saved
24 h 00
TURNA Boost
2 GPUs in parallel · €94.80 excl. VAT
79 h 12 saved
12 h 00
TURNA Max
4 GPUs in parallel · €119.40 excl. VAT
85 h 12 saved
6 h 00
TURNA Turbo
8 GPUs in parallel · €149.70 excl. VAT
88 h 12 saved
3 h 00
The time on your card comes from the GPU scores of our render time calculator (in French), aligned with the Blender Open Data ranking (in French): 40 for an RTX 3060, 152 for an RTX 4090. An RTX 5090, served first, is faster than this table; the actual gap depends on the scene. Billed on the time actually used, with a 30-second minimum. For your own scene, the render time calculator starts from the time of one frame.
Frequently asked questions about animation rendering
Do I need to split the sequence into several uploads?
No. You send the scene once with its frame range, and TURNA splits those frames across the machines of the chosen tier.
Does the render keep my render passes?
Your file's output format is kept, multilayer OpenEXR included: set it in Output Properties before sending. Only a video output is converted into a sequence of PNG images.
What happens if a machine goes down during the sequence?
The frames it had not finished are relaunched on another machine, never on the one that has just failed. If the render still fails, you are refunded.
