Looks like you are using an ad blocker.
Would you mind turning it off on Sheep It?
We need every cent we can get to keep the site online.

Frequently asked questions

You have questions? We have answers.



A render farm is a group of computers connected together to complete a large task. In the case of 3D rendering, most of the time a render farm will distribute frames of an animation to multiple computers. Instead of having a single computer work for 100 days, you can have 100 computers work for 1 day.
When the owner of a project adds his scene to jobs to queue, the service splits the animation into single frames to render, sends each frame to a connected computer and aims to optimize its choice based on the available memory, as well as the CPU/GPU power.
The difference is in the word distributed, which means that the service doesn't own machines that render but instead relies on people to share their computers. It means there is virtually no limit on the amount of power the render farm can have.
Yes, it is! We don't have any hidden tax like paying to get the final result, everything will be free. We only rely on donation and ads to pay for the domain, server and development. You can donate on this page. We accept PayPal, bitcoin and dogecoin.
It was a suggestion by one of our members when the project was in Beta. We liked the "tone" of this name and found a beautiful explanation : "To sheep it is to follow everyone else when you don't know where you're going or what is happening. Derived from the term 'sheep', used to describe one who does what others do in an effort to fit in."
You can add as many you want BUT you can only have 2 rendering at the same time. This limit is set to avoid having a person flooding the render farm with too many projects.
If the render farm is indeed flooded this limit will be temporarily lowered to 1 (It does happen, but no more than a few times a year).
Yes! You will render your project first.
If you don't want to prioritize rendering your own project (for example because you have less powerful machine) you can change this behavior on your account page under the 'Option' tab.
Points are used to order the list of projects. The more points you have the higher priority your project will have.
You will earn points by sharing your computer to help rendering. But you will lose some when someone renders one of your frames.
The calculation of points is only based on render time. How points are calculated:
* remove 3.5 * render time (in minutes) when ordering a frame.
* add 10 * render time (in minutes) when rendering a frame.
* If the owner of a project renders a frame, no penality is made and it gets 30% of the adding points (The 30% penality is to avoid "farming".).

The render time is not the actual duration on your machine, because that would advantage slow machines. Instead it's scaled to a 'reference machine', which is currently an Intel Core i5-2500K @ 3.30GHz x4. You can see the list of machine performance on the machines page.This list is generated by rendering the same project on each machine when the computer's specs are new.
For example, with a project of 100 frames at 15min/frame (on the reference machine), the owner will lose 15,000 points.
No matter the frame is render on, they will earn the same amount of points.
Explanation with 200% machine: 100 * 2.0 * 7.5 * 10 = 15,000 and 25% machine: 100 * 0.33 * 45 * 10 = 15,000

This system is made to be fair, previously it was with weight on each frame and the other on duration, but it was actually unfair because it was based on the number of frames rendered and not on time spent.
No, points are not transferable.
You have two ways to view teams.
Either you can create a bit of competition by being part of a team and competing to generate the most points.
Or you want to help a specific group of people, for example, you are working on a collaborative project and you want to render this project first. You can do so by checking 'Render my team's projects first' on your profile's options.
It does not matter because the size will be overwritten.
The split of frames depends of the render engine.
With Blender Internal, the split is achieved with the border feature, each frame is split with a chessboard motif. It's simple and effichiant but it does not support compositing.
With Cycles, the split creates "layers", each frame is rendered with samples lower to 1/n and a different seed. Them recomposed with 100%, 50%, 33%, 100/n % opacity to generate the final image. This method has the main advantage to support the compositing but it does not support variation of sample amount throught lpo.
In theory, yes, BUT we don't recommend to using fluids, because you need to have bake files, which are very big. You are limited to 500MB per project, which is usually not enough to include fluid bake files.
Yes, you can! Each time the Blender Foundation releases a new version we add it to the renderfarm. But we only add stable versions.
On project creation, the version will be auto-detected but you can override it.


Another question?

If you didn't find the answer to your question, please contact us through the box at the bottom of the page, we will answer you shortly


You are running Windows, NOTHING! You can use the standalone client which will do everything for you.
You are running Linux or OSX you only need to have Java installed. In every case, no need to have Blender, it will be downloaded for you. If you are not sure if your system is supported, go to the Blender binary listing to check if we added it to the render farm
Go on the get started page. You can either use the Java applet or standalone client for windows or a .jar file.
We are providing Blender which is an official Blender Foundation release, we are not modifying in any way the Blender binary.
We do embed a python script, for single frame rendering and to set up the compute method but we do not allow the owner of a project to use his own script.
Yes, you can. The more machines are connected the better!
You can use the Java application in a command line, by downloading the jar file and typing this command:
java -jar sheepit-client-5.413.2825.jar
You can specify if you want to use a GPU when you render projects. Look at the usage for more details (java -jar sheepit-client-5.413.2825.jar --help).
In theory yes BUT we disabled it due to the size of the output file, a 1920x1080 frame can take more than 40MB, it will be very difficult for the renderer to upload it. For the owner, it will be even worse; a 400 frames animation could be 16GB to download.


At the moment only one GPU is supported per session. But if you really want to use multiple GPUs you can launch more than one session (by using different web browser profiles or by using multiple command line clients).
The client source code is GPL and you can help it. The client's project is being hosted on Github at https://github.com/laurent-clouet/sheepit-client. Pull requests are more than welcome!


You can request a feature or vote for the next feature to be added to the render farm by going to the request feature page.
If you think you can code it yourself, you can also do a pull request on the Github client project.