Frequently Asked Questions

After you calculate the price for your project, you can choose your deadline (in hours). We give you a range in which we can render your project and once you choose your deadline we make sure we use enough computers to get the render done in time.

We only support Cycles at the moment. We have plans for supporting Eevee, but since this is considered more of a "preview engine", it typically doesn't require a render farm to render Eevee projects so the priority on this is low.

After you upload your Blender project at the start page and click "calculate price", we run some benchmarks. Based on the complexity of the scene, resolution, samples, number of frames, we send you an exact price quote.

Yes, we automatically do a few test renders for you when you create a price quote for your project. These test renders are typically done at a lower resolution and lower Cycles samples to speed them up. If you want to render a specific frame or at higher resolution, you can duplicate your project, change the settings, and render it the usual way.

Yes we do. We have installed Add-ons like True Terrain, Toonkit, Animation Nodes. But not all Add-ons you use are required for us to install. If you're not sure about this, try to ask the Add-on creator if you need to do anything special to prepare your .blend file for a render farm. If you have a specific Add-on that needs to be enabled on our end for the render to work, reach out and we will help you out!

Yes, you can definitely use the compositor. We just run it like you've set it up. You can even use File Output nodes if you want to!

Yes you can. After creating a Project, you will notice an "Image" vs "Animation" toggle. Just choose "Image" and we will only render a single image. A project will automatically be set to "Image" if the start and end frame are set to the same number in your Blender file.

Yes, all .blend files you upload, whether they are in a .zip file, or uploaded as a folder, can be turned into render projects.

Yes, if you want to use particle systems or simulations make sure everything is baked. Smoke simulations for example use an external cache, this means it creates extra files outside your regular .blend file. To render these kinds of simulations, just put everything in a .zip file and upload it.

Yes, we will first always render the images as a PNG sequence, but after that, we encode them as a video in the format you have chosen (whatever is set in the .blend file, or what you chose after uploading).

You can upload an entire project folder, multiple files, or pack your project files into a .zip file and upload it like that. You could also use the packing feature in Blender and pack all your textures inside the .blend file. Note that the packing only works for single image textures. Movie textures or image sequences are not packed by Blender. If external files are missing, we usually show warnings about this on the Projects page.

The current limit is 5 TB (with a capital T) which should be plenty. But if you have trouble uploading, you can always share the file with us in a different way. Please contact us if you need help getting a large file uploaded.

Yes, you can set any file output type. Multilayer EXR is great if you want to work with all the different render layers and passes that Blender can export.

If you have dynamic particle systems or hair systems (moving particles or moving hair strands) you should bake them before submitting, otherwise the result can be very funky. If your particles or hairs are not moving at all, it doesn't matter and you can ignore these warnings.

Yes you can. We enable all automatic scripts and drivers so you don't have to worry that anything breaks.