Explain the scene before you move it
Scans project files, linked libraries, missing textures and references, packed assets, sequences, UDIMs, render outputs, baked caches, and cleanup hints before it writes a zip.
Renderjuice Blender extensions
Blend Project Packer
If it renders on your computer, help it render somewhere else. This Blender project packer extension gathers external files, fixes fragile paths in a copy, and exports a project zip you can send to another artist, archive, or render farm.
Install from Blender with Preferences > Extensions > Install from Disk and select the downloaded zip.
Version 0.1.0 | Blender 4.2+ | 101 KB
- License
- GPL-3.0-or-later
- Blender
- 4.2+ extension
- Internet
- Runs locally offline
Blender side panel
Blend Project Packer
Local render handoff
Portable render project
Scan Copy Paths Zip
Analysis
18 dependencies
assets/sequences/
libraries/props.blend
caches/GeometryNodes/
renders/compositor/
blend-project-pack.json
Shareable zip ready
Open it on another computer, archive it, share it, or upload it wherever you choose.
1
Analyze
Builds a scene report for external paths, linked libraries, sequences, caches, output paths, missing files, and cleanup hints.
2
Copy + rewrite
Copies render-critical files into a scratch project and rewrites the packed .blend to use portable // paths.
3
Archive
Writes a self-contained zip with a manifest receipt, ready to inspect, share, archive, or send to a render farm.
Output
project-portable.zip
dependency manifest included
Keep render-critical files together
Copies textures, image sequences, UDIM tiles, Alembic/cache files, VDBs, fonts, sounds, movie clips, linked-library dependencies, and baked simulation cache folders.
Rewrite only the packed copy
Saves a scratch .blend, remaps absolute and escaping paths to //-relative locations, moves render outputs under //renders/, and leaves the original file untouched.
Current coverage
Built for the messy projects artists actually hand off.
The extension is generic: useful for render farms, studio handoff, freelance delivery, moving between machines, and keeping an archived project copy that still knows where its files are.
Collects
The files Blender needs to find again
Preserves the project folder shape where possible, then categorizes outside files into predictable zip folders.
- Images, movie clips, sounds, fonts, VDB volumes, Alembic/cache files
- Image sequences and UDIM tiles expanded into concrete package files
- Linked .blend files plus recursively scanned single-file dependencies
- Baked particle, cloth, soft-body, fluid, dynamic-paint, and Geometry Nodes cache folders
Repairs
Paths that usually break after handoff
The packed .blend is saved with portable paths, so another machine opens the extracted project without reaching back to the original workstation.
- Absolute file paths converted to project-relative paths
- //../ escape paths folded back inside the portable project
- Scene render and compositor File Output paths remapped under //renders/
- Copied linked libraries rewritten so their own dependencies stay portable
Reports
A useful receipt for artists and future tooling
Every zip includes a local manifest that documents what was found, copied, rewritten, hashed, or left as an action item.
- Missing files and unbaked simulations surfaced as warnings
- Packaged file sizes and SHA-256 hashes recorded for inspection
- Dependency graph, sequence groups, cache moves, and render-output moves
- Offline diagnostic manifest that can be consumed and analyzed by your automations
Render handoff checklist
The zip handles paths. You still keep control of the render setup.
Blend Project Packer is intentionally local and conservative: it packages what it can prove, reports what needs attention, and avoids inventing files Blender never baked.
Bake simulations first If Blender has no cache files on disk, the extension reports the problem instead of pretending to bake them.
Install render-time add-ons where needed If a scene depends on a custom add-on at render time, the target machine or farm still needs that add-on available.
Open the extracted project folder The generated zip is designed to behave like a normal project folder after extraction, with local paths and local output folders.
Support and feedback
A stable home for help, docs, and roadmap input.
This page is the public Renderjuice support surface for Blend Project Packer. The extension itself stays generic, free, and local; feedback routes here so artists and reviewers have one reliable place to go.
Get help Send a support note if packing fails, a path looks wrong, or you need help preparing a specific scene. Email support Share feedback Request dependency-graph views, upload caching, deeper linked-library handling, or other workflow improvements. Open feedback board Read project-packing docs Review the broader Renderjuice guidance for zip structure, external assets, caches, and add-on workflows. Open docs
FAQ
Common questions
Does Blend Project Packer send my files to Renderjuice? +
No. It works offline: it reads files already referenced by your .blend and writes a zip on your computer. Nothing is sent to Renderjuice or anywhere else.
Why does the extension ask for file access? +
File access is the core feature: the extension needs to read referenced scene assets and write a portable archive.
Where should bug reports and feature requests go? +
Use support@renderjuice.com for help with a specific scene. Use the public feedback board for roadmap requests and workflow ideas.
Can I use it without a render farm? +
Yes. The zip is useful for sharing a project with another artist, archiving a stable copy, moving between machines, or preparing for any render farm.
Does it guarantee identical renders everywhere? +
It is designed to make locally renderable projects portable by collecting visible dependencies and rewriting paths. Blender version, render-time add-ons, hardware differences, and unbaked simulations can still affect final output.