If a project works locally but fails, renders incorrectly, or behaves differently on Renderjuice, the cause is usually not Blender itself. It is usually one of a few setup issues that only become obvious once the file leaves your machine.
Check these first
- Are all external files actually inside the project zip or packed into the
.blend?
- Are your file paths relative instead of pointing to your local disk?
- Did you upload required add-ons separately before rendering?
- Did you bake any simulation or cache-based systems and include those caches?
- If your zip contains multiple
.blend files, did you select the correct one in Renderjuice?
Missing files and assets
Missing references are one of the most common reasons for:
- incorrect output
- missing textures or elements
- slower or unstable renders
What to check:
- Pack textures, fonts, images, and sounds when possible.
- Zip external assets that cannot be packed.
- Make linked paths relative.
Related guide:
Missing caches or unbaked simulation data
If a simulation works locally but not on Renderjuice, the cache is often missing, not baked, or not included in the project you uploaded.
This commonly affects:
- fluid simulations
- simulation nodes
- rigid body workflows
- other cache-based systems
What to check:
- Bake the simulation locally.
- Save the
.blend after baking.
- Include the cache folder in the upload if it is external.
- Keep the cache path relative.
Related guides:
Missing add-ons or extensions
If the scene depends on a custom add-on or extension, the render may not match local output unless that add-on is uploaded and validated in Renderjuice first.
What to check:
- Upload the add-on from your local Blender add-ons or extensions directory.
- Do not upload the original installer archive from the add-on website unless it is the exact installed folder.
- Keep the add-on folder name unchanged when you zip it.
- Wait for the add-on to validate before selecting it in a render job.
Related guide:
Zip and project structure mistakes
Even when you upload a .zip, the structure can still be wrong.
Common mistakes:
- zipping the wrong parent folder
- leaving dependencies outside the archive
- including multiple
.blend files and choosing the wrong one
- mixing backup or test scenes into the same archive
Related guide:
Relative vs absolute paths
Absolute paths like C:\..., D:\..., or local macOS/Linux paths will often break once the file leaves your machine.
Relative paths are much safer because they keep references working after the project is extracted on a render node.
Related guide:
When it may be okay to continue anyway
Sometimes Renderjuice will warn you about missing files or caches that are not actually used by the exact scene, shot, or frame range you plan to render.
That means:
- some warnings are safe to ignore
- but important missing dependencies can still affect output, speed, or stability
If you are unsure, fix the issue before rerendering.
If you are under time pressure, work through the checklist above first. It covers the most common causes before you spend more render time.
