Cloud Blender rendering: files, quote, and receipt

The problem

People want the PC free without being unclear about what left the disk. Cloud Blender rendering means the scene, packed images, and caches needed to render are uploaded. A benchmark site that never receives your shot is not cloud rendering.

Cause

Cycles has to see the same data the local machine would see. If textures stay on a NAS path that only exists at home, the remote job cannot finish. If the file is packed, the upload is the job. That is why inspect exists: FARPY reads the .blend before a quote.

What FARPY does

• Upload the .blend (100 MiB public limit, Blender Cycles).
• Inspect, then a locked quote. Start only after you accept it.
• Download a ZIP of finished frames. No babysitting the workstation.
• Receipt with accepted quote, captured amount, and output SHA-256. The hash proves integrity, not that the image “looks right.”

BenchMork measures GPUs on frozen public scenes. It does not execute your file. See measurement versus execution and render without using the PC.

Practical checks before upload

• Pack resources. Relative paths that only work on one PC will fail remotely.
• Do not upload secrets you would not send to a render vendor.
• Plan duration with the time calculator. Price still comes from the live quote.
• Read privacy and terms.

Estimate local render time

Local total time = frames × time per frame. The calculator also shows a human-readable duration, an independent-machine illustration, and an optional target completion. It never multiplies frames by a public dollar rate. FARPY price comes from a live quote after upload.

Open the Blender render-time calculator

Need the actual render finished?

Upload the .blend. FARPY inspects it and returns a locked quote before start. The accepted price does not increase after you approve it.