Skip to main content
While Blender promises backwards compatibility across all versions, through loads of testing we’ve discovered that isn’t necessarily true. It is a tough promise to keep after all. We have found that while Blender may open up and work with older files, the rendering results can be different. Sometimes it may be missing a texture, or you’ll see odd black streaks on your render. This is due to the fact that the rendering engine is constantly being updated and improved. Ultimately, these are tough to trace down, so Renderjuice tries to match the Blender version you’re using as closely as possible. We use a fairly extensive version matching system to match your Blender version. This is critical because Blender’s render outputs change between each new update as the developers improve the product for all of us.

​
Supported Versions

Renderjuice maintains an internal registry of supported Blender versions. In practice, we aim to support:
  • The latest stable Blender release
  • Current Blender LTS (Long Term Support) releases
  • Curated recent non-LTS Blender lines that we have built and enabled
When you submit a file, we match based on major.minor (for example, 4.5.x). For reliability and bug fixes, we typically run the latest patch release within that line (for example, 4.5.0 may be rendered with a newer 4.5.x patch).

​
How We Handle Blender Versioning

Since our initial launch, we’ve been working relentlessly on supporting as many versions of Blender out of the box possible to iron out any strange kinks. When you start a render, we’ll automatically match up the metadata of your Blender version to closely match. We may stop supporting legacy versions of Blender, especially if they’re out of LTS support. At time of writing, that means we don’t support Blender versions < 2.9 If you find any issues with other versions of Blender, please reach out! We’re happy to help.