Reference

Troubleshooting

The render finished but looks wrong, or never finished at all. Causes, in the order worth checking.

The image is wrong

Pink, purple or black surfaces: A texture is missing. In the browser flow, check Step 2 for rows still marked needed. In the add-on, press Scan and resolve the red rows. Packing resources in Blender avoids this class of problem entirely.
Colours or exposure look different: The scene uses a custom OCIO config that the machine does not have. Upload it in Step 3, or leave the add-on's OCIO checkbox ticked.
Text renders in the wrong font: The font file was not attached, so Blender fell back to its default. It appears as a Font dependency.
Geometry, shading or effects missing: An add-on that runs at render time is not installed. Look at the detected list in Step 3 for anything marked needed at render, and install it.
A simulation renders as its first frame, or not at all: The cache sequence was not attached. Volume and cache rows need every frame, not just the anchor. The add-on expands sequences by itself.
The render is empty: Usually the wrong scene or camera is active in the saved file. What the farm renders is the scene that is active when you save.

Out of memory: Check the VRAM graph on the live view: a climb to the card's limit followed by a stop is the signature. Reduce texture sizes, subdivision levels or resolution percentage, and re-render. 32 GB of VRAM is a lot but a heavy volume scene can still exceed it.
It stopped and my balance is zero: Billing ran out. Frames rendered so far are kept. Top up and press Relaunch, narrowing the frame range to the frames you still need.
Failed while starting: The machine failed to come up. Press Relaunch, the failed machine is excluded from the next pick. A failed start does not cost render credits.
Stuck in Preparing: Large downloads take a while and preparing is not billed. If it really does not move, destroy and relaunch; the files are already uploaded so relaunching is quick.
Rendering is slower than my own machine: Compare against a single-GPU run, not against a CPU + GPU render. Also check the live log for a CPU fallback line, which means the scene used a feature OPTIX could not take.

The file will not open in the browser: Close Blender first, and make sure the file is not mid-sync in Dropbox, OneDrive or Google Drive. Browsers refuse to read a file that another program has locked.
Some files failed to upload: Press Retry. Files that made it are not sent again.
The upload is very large: Leave Skip re-uploading unchanged files ticked. The first render pays the full cost; later ones only send what actually changed.

Still stuck: mail contact.blenderfarm@gmail.com with the job ID from the render page. The ID lets us read that job's logs directly.