Docs
Blender uploads and render output files
Last updated July 30, 2026
Plain-language guidance for Blender project uploads, completed render ZIPs, frame files, private delivery links, receipts, proof, and temporary retention.
Supported Blender uploads
FARPY currently accepts Blender .blend project files for supported Cycles GPU rendering workflows. One still image counts as one frame, and animation frame ranges can contain from 1 to 10,000 requested frames. The current public upload limit is 100 MiB per uploaded project file.
What to include in a .blend file
The uploaded .blend file should contain the scene, render settings, cameras, frame range, and packed or otherwise available project assets required for the job. Missing textures, linked libraries, caches, fonts, simulations, or external files can cause output differences or render failure. Test a representative frame before submitting a large animation.
Completed render ZIP packages
A successfully completed job produces a downloadable ZIP package. The package contains the rendered output available for that job and supporting metadata used by FARPY delivery, receipt, and proof systems. The exact contents depend on the submitted workload and the output successfully produced.
Frame files and output folders
Blender animation output is packaged as individual rendered frame files, commonly PNG images under an output folder inside the ZIP. File names and output format depend on the supported job configuration. A still render normally produces one completed frame file.
Where to download completed output
Use the authenticated FARPY workspace or the private delivery link associated with the job. Public software installers belong on the Downloads page, but customer render output does not. A completed job may also expose related receipt and proof links for verification.
Receipts and proof
The receipt records job and payment-related facts for the completed work. Proof artifacts expose verification information for the render where available. A receipt or proof page does not replace the actual output ZIP; use the job download link to retrieve rendered files.
Private access and job tokens
Workspace, download, receipt, and proof access can depend on private job tokens or authenticated account ownership. Anyone who receives a usable private link may be able to access that job. Do not publish or forward private links unless you intend to grant that access.
Temporary file retention
FARPY retains uploaded project files and rendered outputs temporarily according to operational policies for rendering, delivery, support, storage management, abuse prevention, and maintenance. This page does not promise permanent storage or a fixed retention duration. Download important output promptly and keep your own local backup.
File safety and privacy
Upload only files you are authorized to process. Avoid placing unrelated secrets, credentials, personal records, or unnecessary private data inside Blender projects. Review linked assets before upload, and treat downloaded ZIP packages and private job links as sensitive project material.
File workflow
Prepare and inspect the .blend file, upload it through the workspace or public API, submit the supported render job, monitor status, and download the completed ZIP when available. Then keep the output, receipt, and any useful proof artifact in your own project records.