The best render farm doesn't need Google Ads, you've just found it!
Simpler. Faster... Better!
Easy to use render farm
- “Ohh God! I just love how smooth it works” - one good reason
- We found out that advertising in google and branch portals costs millions of $, that is why we do not do this and our service is much more affordable and reasonable than most well known competitors.
- It is cheaper then rendering in-house in longer term - trust us - we used our calculator to figure it out
- It is faster than rendering in-house - this is obvious. And your time is money.
- You have support from people whos rendering knowledge is deeper than ocean.
- We are not the biggest render farm in the world, but this is not a case, because here you do not have to share your cake with thousands of users at a time. Think about it.
- It is so simple to use
Register account and get 100 Render Points for free
100 Render Points is equal to 5 hours of rendering in Basic plan on a single render node.
Lowest priority rendering when you're not in a hurry. Best option to test the RenderBuzz capabilities
- 0.01 EUR/USD per GHzh
- 0.40 EUR/USD per node per hour
- Longest turnaround time
- In the queue behind the Standard and Premium
- No render limits
- Limited support
Prefered choice for everyday rendering. Render jobs with the Business plan start before Basic jobs
- up to 250% faster than Basic
- 0.015 EUR/USD per GHzh
- 0.60 EUR/USD per node per hour
- Medium turnaround time
- In the queue behind Premium
- Access to 3ds Max V-Ray DBR rendering with 5 spawners
- No render limits
- Full support
Best choice for tight deadlines. Render jobs with Premium plan always start as soon as possible.
- up to 250% faster than Basic
- 0.02 EUR/USD per GHzh
- 0.80 EUR/USD per node per hour
- Short turnaround time
- In the queue before others
- Access to 3ds Max V-Ray DBR rendering with 10 spawners
- No render limits
- Highest priority support
The calculator provides an estimated value. Remember that the precision of indications follows directly from your knowledge of your project. We advise you to buy a little more rendering points than the calculations suggest and run some test render before submitting your main job.
Despite all our efforts, these calculations are purely approximate and we are not responsible for the presented results, nor do we guarantee obtaining them in practice.
Estimated cost of your project
|Render time||Render points||Render cost|
Create RenderBuzz account
Register account and wait for activation email. Sign in and enter your company details so we know who we are working with.
Prepare and upload your project
Run your 3D software, open your 3D scene and do all rendering setup as you usually do. When you are ready just click “Render with RenderBuzz”. Type your email and password to RenderBuzz and upload the project.
Submit your order to rendering queue
Go to RenderBuzz web page and sign in to your account, go to “Projects” page. Your project should be there. Click on it and make an order. You can tack order progress on the “Orders” page.
Fast Tips & Tricks
- Remember that you will need to download your output after rendering. Use image compression like JPG or TIFF with Packbits option enabled.
- For 3ds Max users - Enable “compress on save” in your 3ds Max settings to upload scenes up to 3x faster.
- When render farm is very busy, you may avoid queue by choosing Business or Premium Plan.
- When using V-Ray, it is much better to save output through V-Ray Frame Buffer (go to V-Ray documentation for details) instead of standard 3ds Max output.
RenderBuzz is built to offer its users maximum compatibility without limiting their freedom. However there are some common tips which will help you achieve maximum satisfaction and performance when using our service.
- Noise level threshold for progressive renderers. When using V-Ray progressive (not bucket) mode, please choose the Noise Level Threshold instead of time limit as a criterion for each frame completion. Some frames render faster, some slower, this is normal. So more important is to achieve equal quality of all frames then forcing the renderer to render them in a fixed amount of time. The second reason is that every render farm has multiple nodes with different specification. Using noise threshold criterion guarantees you get 100% of nodes performance, your bill will be lower and overall rendertime - shorter. Using time limit criterion may lead to uneven frames quality and/or excessive costs of the rendering.
- Output size optimisation. Rendering is the part of the process. Then you need time to download the rendered frames. In our renderfarm you have the advantage that your frames are synchronised in real-time with a global hosting solution - Dropbox. Wherever you live, you have guaranteed best possible download through our partner global infrastructure - Dropbox. To speed up the whole process even more, please use TIFF with enabled LZW compression for your render output format (If you need lossless compression) or JPG format. Using uncompressed output formats may easily lead to excessive file sizes (hundreds of Gigabytes).
- Use our plugins for uploading. Whenever possible. Every supported software package has its dedicated plugin for automatic scene upload to RenderBuzz. This will help you avoid mistakes and increase your comfort. Manual upload is of course possible, and will give you more control in particular projects, but it is recommended for advanced users, who already have rendered a few projects with RenderBuzz.
To ensure the highest level of software timeliness and quality of service, we only support the most popular formats:
- 3ds Max 2010-2018 (Corona 1.7, V-Ray 3.6)
- Cinema 4D R19 (V-Ray for C4D 3.5, Corona a6.4, built-in renderer)
- Maya 2018 (Vray 3.6)
Any questions? - firstname.lastname@example.org
For MAX files we provide the following plugins:
- ATile 2.52
- Autodesk 3ds Max Populate High-Resolution Data
- BerconMaps 3.04
- BonesProProxy 4.73.00
- ColorCorrect 3.4.132
- CityTraffic 2.028
- FloorGenerator 2.10
- Forest Pack Pro 5.4
- GrowFX 1.9.9 SP3
- gwIvy 0.976b
- Itoo Glue
- Itoo Clone
- Laubwerk Plants 1.0.21
- MadCar 3.059
- Multitexture 2.01
- Multiscatter 1.055
- PhoenixFD 3.04
- Quad Chamfer 1.16
- RailClone 3.07
- Siger ComplexFresnel
- Siger Noise
- Siger Scratches
- Siger ThinFilm
RenderBuzz is a prepaid service. This means that you need to know the approximate cost to know how many rendering points to buy. In order to estimate it you can use our cost calculator available on the website. To estimate time and cost, you have to provide the number of frames to render, average render time of one frame and your CPU model.
If during rendering process you run out of rendering points, RenderBuzz will complete all frames that have already started. Even if you make a little mistake in your estimates, there is a very good chance that the entire project will be completed without hindrance.
RenderBuzz offers three basic tariffs: Basic, Standard and Premium.
Basic is limited to maximum 40 render nodes per user. It also has lowest priority and support limited to cases, when farm is working inproperly. Basic renderjobs may be interrupted by highier priority renderjobs.
Standard is up to 2.5X faster then Basic, It has unlimited render node count per user and full support. It is designed to work best for everyday rendering. For single-frame V-Ray renderjobs - it give access to 5 spawners.
Premium is up to 2.5X faster then Basic. It is for urgent renderjobs. Premium overtake all Basic and Standard renderjobs, giving you almost instant access to whole render farm power and full support. What is more, when your Premium renderjob started, no other renderjob is able to interrupt your rendering. For single-frame Vray renderjobs - it give access to 10 spawners.
RenderBuzz provides exactly the same formats and sizes of frames as those provided by the software you use for rendering, without any additional limitations. You can of course also render some additional render passes, such as VrayAlpha, VrayReflection, etc. In a word - what you set in your 3D application will appear on your Renderbuzz output folder after the rendering is finished.
Our advice is to keep in mind that all output frames have to be downloaded after rendering. It is a good practice to use compression for output files (like lossless TIFF with enabled LZW compression, or simple JPG format) which will significantly increase download performance. In cases when multi passes are saved without any compression, the output folder may achieve a size of hundreds of Gigabytes and take a long time to download.
Typically, scenes do not require any particular preparation. You work exactly like you do every day. Of course, the scene should be neatly prepared. Keep in mind that there should be no missing texture files, traces of badly used/installed plugins, and there are no plugins that are not compatible with RenderBuzz. Then all you have to do is to use our one-click RenderBuzz upload plugin (see Get started web section).
Some manual actions will be required only when some external cache files are used. For example files from IFL list, Phoenix cache files or particle flow external cache need to be uploaded manually via FTP. For details please find a dedicated FAQ thread.
Sending a project to RenderBuzz is a two-step process. The first step is to upload files to RenderBuzz. They can be stored on your account for up to 14 days. During this time, you can replace and upload more files as it was your own hard drive. At this stage, there are no fees. The second step is to add a scene already uploaded to RenderBuzz into the rendering queue. At this point, you can choose the tariff you would like to use and add the project to the queue. You can remove the task at any time from the queue. When the project is in the queue, access to the scene files is locked, and scene files cannot be modified.
After setting up a RenderBuzz user account, we offer you two ways of uploading the scene to your RenderBuzz account. You can use our dedicated plugin, which automatically archives 3D scenes on your computer and then send them to your indicated RenderBuzz user account. You can also upload scenes directly through FTP client. In order to do this, you have to sign in to your user panel in RenderBuzz where you will find necessary data to connect your RenderBuzz account with your FTP client. To upload files manually please follow general rules mentioned in a detailed PDF instruction (see "get started" section of our web service).
Payments can be made electronically, through a PayPal or PayU account including credit card. Money is automatically converted into the adequate number of rendering points which appear in your user panel. Please note that RenderBuzz is a pre-paid service. This means, among other things, that the service never uses a larger amount than have been previously paid to RenderBuzz
After uploading your 3D scene to the RenderBuzz, you have 14 days to make changes. You can freely manage your files (at your own risk) using FTP client. The access to files is blocked after the scene is added to the rendering queue. If you still want to make changes, remove the scene from the rendering queue, then you will be able to manage your files again.
FTP access data can be found in your user-profile after sign-in to Renderbuzz.
Progress and statistics can be monitored in the user panel, under "Orders" tab and through a mobile application.
For very detailed informations, please click "Order details" button in upper-right corrner of render-job bar.
Distributed rendering is a technique for distributing a single frame renderjob across many computers in a network - an outcome of this process is up to 10x faster, exceptional quality rendering.
DBR is available for 3ds Max, V-Ray and following plans: Business (5 active render nodes) or Premium (10 active render nodes). Both options will also use an additional master node to control the rendering. You don't have to prepare your scene in any particular way - the only thing you'll have to do is to determine the proper gamma input & output parameters of the scene in RenderBuzz user panel.
If you are using 3ds Max and want to render multiple cameras from the same scene, then use the Override scene's camera settings when submitting new order. Then specify the exact name of the camera you want to render.
For Maya or Cinema 4D projects, you will need to prepare separate scenes for each camera. Place additional scenes in the same project directory and then submit separate orders for each of the prepared scenes.
The best way to render flicker free animation is to use V-Ray Irradiance Maps with Animation (prepass) and Animation (rendering) modes. RenderBuzz can render your animation using this technique without much problem. Overall it works pretty much the same as you would render locally on your machine.
You will need to submitt two render jobs. First job to render prepass files (vrmaps). The second job to render final images (animation frames). Take this into consideration during project cost estimation.
First render job - generating prepass files:
1. Set your scene exactly the same as you would want to store prepass files locally. Remember to select animation prepass mode and set the local file path for vrmaps.
2. Upload your scene via plugin.
3. Submit first render job. The farm will automatically detect that you want to render vrmaps and will save them to the assets folder of your submitted project. This way you will be able to use vrmaps without the need of downloading them.
Second render job - animation frames:
1. Prepare your scene for final rendering. Remember to set animation rendering mode and use the vrmap file path with exactly the same filename as you've set in the first job. This is very important, because if you use different filename then the farm won't be able to locate already calculated vrmaps.
2. Use our plugin to prepare only the scene file - in the plugin use Tools > Advanced options. You need only the scene file because all the assets should already be on the farm.
3. Upload prepared scene file to the same project folder (using eg. FTP) that was used to render prepass files. We will be using vrmaps which now should be located in the assets folder.
4. Submit second render job.
If you are not sure how this works then we advise you start with a simple test scene and verify each step.