Render Blender without using your PC
A local render owns the machine: fans, VRAM, and the Blender process that refuses to quit cleanly. If you need the PC for other work, or you cannot leave it on overnight, the .blend has to leave the box.
What “using your PC” actually costs
Cycles on a laptop turns the chassis into a heater and the battery into a countdown. On a workstation it often means you stop sculpting, editing, or running a second DCC until the queue drains.
Crashes while rendering are a local-ownership problem: driver resets, VRAM exhaustion, a sleep policy, or a Windows update. You do not need a separate article to know that an eight-hour local job is one freeze away from starting over. Offloading does not make Cycles immune to bad files. It does stop that job from holding this keyboard.
What has to be true of the file
FARPY renders Blender 4.1.1, Cycles GPU, from a .blend you upload. Pack what the scene needs. External textures that are not packed will fail preflight. Maximum upload is 100 MiB. Frame requests are 1–10,000.
If the file is larger than 100 MiB, this path will not take it. Shrink, pack carefully, or split linked libraries before you look for a farm that pretends size is free.
The PC stays yours after upload
You still have the original file. FARPY runs the quoted range and, when the job completes, you download a ZIP plus a receipt and proof record. You can keep working locally on a copy. Do not overwrite the uploaded version until you know you packed the right one.
Rendering is from 1¢ per completed frame. You see the exact fixed quote before work starts. Nothing in that quote requires you to leave Blender open on this machine.
Upload, then walk away
Sign in, drop the .blend on the homepage, confirm the frame range, read the quote, start. Docs describe the same flow for the API if a person should not babysit the browser. Status and Your renders are for jobs already in flight, not for keeping Cycles on this GPU.
What FARPY accepts
- Blender 4.1.1
- Cycles GPU
- .blend files, 100 MiB maximum
- 1–10,000 frames
- Rendering from 1¢ per completed frame
- Exact fixed quote before work starts
Upload a .blend
See the exact fixed quote for your frame range before anything is reserved. Rendering from 1¢ per completed frame.
Questions for this problem
Can I keep using Blender on this PC after I upload?
Yes. Upload is a copy of the packed .blend. Close the local render queue. Keep working on your file. The remote job does not need this GPU.
What if my scene is over 100 MiB?
This public path will not accept it. Pack and strip unused data, or split the shot, until the upload is at or under 100 MiB.