Render accepts packaged Blender Cycles scenes for distributed GPU rendering

Saved file references control what remote GPUs can load

A Blender scene tells the renderer which geometry, materials and external files to load. An asset left on the original computer cannot satisfy that reference remotely. The submission package needs the data those references identify, including any linked scenes, image sequences and external simulation caches the render uses.

Relative paths describe locations from the directory containing the saved.blend file and remain useful when dependencies move with their folder relationships intact. Keep external files within an organized project directory and preserve those relationships inside the ZIP. Folder names help organize the package; the paths saved in Blender determine where it looks. Putting every asset in one folder does not automatically repair references pointing elsewhere. A linked.blend file may also reference other resources, so its dependencies need attention alongside the main scene.

Browser uploads and desktop updates have different prerequisites

The browser scene uploader accepts ZIP archives, while desktop submission and differential updates require API access approved for the account.

Browser ZIP submission

The scene uploader accepts an archive containing the Blender project and its external dependencies. Select Blender as the application when the upload interface requests it. Processing prepares the uploaded scene for job creation. An uploaded archive and an active rendering job are separate states, so upload completion alone does not mean frames have rendered.

Desktop uploads with API access

The Render Network Manager App accepts Blender project folders or ZIP archives. Use an up-to-date app with differential uploading enabled to reuse unchanged files. Upload and job-management features require approved API access and a personal access token connected to the app. Installing the download utility alone does not establish those permissions. Node requirements concern contributing GPU hardware; creator-side preparation concerns scene compatibility and complete project data.

Should textures be packed or kept outside the.blend file?

Packed textures improve portability, while separate asset files allow smaller updates when differential uploading is available.

Packing eligible resources

Pack Resources embeds eligible external data in the.blend file when you next save it. The packed indicator beside a resource path helps identify embedded content. Not every external file supports packing, so inspect sequences and cache locations separately. Pack Linked Libraries marks linked library files for packing on the next save. These controls collect eligible data without replacing the browser workflow’s ZIP requirement.

External files during differential updates

For differential uploads, the Manager App treats a packed.blend file as one upload unit. A modification inside that file requires uploading the changed file. Separate textures or caches allow unchanged files to remain reusable while changed files upload individually. This distinction matters when heavy assets remain identical across scene revisions. External storage brings that transfer benefit only when the chosen upload workflow supports differential updates.

View full-size image

Bake script-driven movement and save simulation caches

Animation depending on local scripts or unsaved caches needs preparation before upload. Saved keyframes and reusable simulation results remove those particular runtime dependencies.

Script-driven animation channels

Python scripts do not execute in the network’s Blender Cycles rendering environment. Animation channels driven by scripted expressions therefore need a supported saved representation. Bake Action can store evaluated object or bone motion as keyframes over a chosen range. The submitted animation must then evaluate from saved data without requiring the original script.

An add-on used locally to create saved scene data has a different role from one executing during rendering. Packaging the add-on itself does not make its scripts executable remotely. Inspect the resulting scene data and any remaining runtime dependencies.

View full-size image

Simulation results stored on disk

Baking stores calculated simulation results for reuse, with cache storage following the particular physics system. For systems using Disk Cache, saved results live outside the scene file, requiring the relevant cache directory and its reference. Cloth or hair dynamics need accessible cache data when the project relies on those bakes.

A bake covers its configured simulation range, which must supply the data the selected render frames require. Timeline playback in an existing session may use temporary memory caches. Those temporary results can remain outside the saved submission, leaving the remote render without the cache it needs. An edit affecting the simulation can invalidate its bake, requiring regenerated data before the submission copy is saved.

Match the saved scene to the supported Blender version

Job creation starts from the render settings saved in the Blender scene. Check the displayed frame range and render configuration before committing GPU work. The network must support the Blender version and features the project uses. A local installation may evaluate features absent from the selected network build.

View full-size image

VRAM capacity and GPU count control different constraints

Video memory, or VRAM, holds the data a GPU needs while rendering. Minimum Node VRAM controls memory eligibility during node selection, while Maximum Number of GPUs sets a per-node GPU limit. The available choices belong to the job configuration and can change as supported hardware changes. Leave memory headroom for rendering overhead instead of matching the requirement tightly to a single observed allocation.

Adding GPUs does not generally combine their memory into one pool. Some hardware arrangements support sharing, so this is not a universal limitation of Cycles. A node still needs suitable usable memory for the selected workload. Reducing unnecessary geometry and excessive texture resolution can lower memory pressure. Local rendering that spills into system memory does not establish equivalent behavior or performance on a remote node.

Sampling choices shape the paid GPU workload

Rendering time changes with scene complexity and Cycles sampling settings. Higher sample counts generally reduce noise at the cost of more work; adaptive sampling stops refining pixels meeting the selected noise threshold. Resolution also affects the workload. Choose settings suited to the required output and supported Blender build. Cost estimates depend on job configuration and rendering time. An OctaneBench-based estimate uses an Octane benchmark, so its score does not independently establish Cycles performance.

When can a Cycles job’s finished frames be downloaded?

With manual frame approval selected, the full final render can be downloaded once all frames are approved. Completion reports rendering status; approval records acceptance of the output. Frame previews and sequence playback allow inspection before that acceptance. A completed frame can still contain an incorrect asset or unwanted animation state, so inspect the image content as well as its status.

The download configuration can restrict the delivered frame range and selected outputs. Rendered outputs are deleted one week after job confirmation, so download the files you need before then. Browser transfers, individual file downloads and the Render Network Download Manager provide retrieval options. Direct delivery to connected cloud storage requires pre-approved frames. That setting changes the review timing: manual inspection no longer stands between completion and automatic delivery.

Compositor outputs need passes chosen before submission

The Cycles output controls provide PNG and EXR, including Multilayer EXR. Choose the format and available bit-depth settings for the intended compositing workflow. Multilayer EXR can hold multiple render passes in one file. Selecting the required outputs before submission avoids a finished job lacking data needed for later compositing.

Custom File Output nodes and separately downloadable View Layer passes give access to additional output data. Their contents follow the saved compositor setup and enabled passes. Download controls select data the job produced; they cannot reconstruct a pass the scene never rendered. Decide which passes the final composition needs while preparing the scene and job settings.

Frame naming can include scene, frame and layer elements, together with custom text. Choose names distinguishing the outputs while keeping frame order understandable. The main image and additional passes need a consistent frame range for assembly. If the composition later requires an omitted pass, the render configuration must produce that additional data before it can be downloaded.