Blender add-on

Send a .blend from Blender to FARPY.

The FARPY add-on packages a saved Blender scene and sends it to your workspace. FARPY renders Cycles on GPU with Blender 4.1.1, then returns a ZIP and a receipt. Pricing, Google sign-in, and download stay in the browser — the add-on does not store a password.

  • What it doesStarts a FARPY job from Blender with a saved .blend.
  • Who it is forBlender artists sending Cycles GPU stills or frame ranges.
  • How it connectsInstall in Blender, send the file, then quote, pay, and download in the workspace.
Download add-on ZIPOpen Workspace

Tested with Blender 4.1.1 on Windows · install the ZIP directly (do not unzip) · 100 MiB upload · 1–10,000 frames · from $0.01 per completed frame

  1. Download
  2. Install
  3. Send
  4. Track
  5. Receive

Install

  1. Download Farpy-Blender-Addon-unified.zip. Keep it zipped.
  2. In Blender, open Edit → Preferences → Add-ons → Install.
  3. Select the downloaded ZIP, then enable Farpy Render Delivery.
  4. Open the Farpy panel in the 3D View sidebar and send a small test scene first.

Updating? Remove or disable the older Farpy add-on first, restart Blender, then install this ZIP.

How it works

  1. Save your .blend with the intended camera, Cycles settings, and frame range.
  2. Send the package from the FARPY add-on in Blender.
  3. Sign in with Google in the workspace to see the quote, pay, and track the job. Email sign-in is coming soon.
  4. Download the result ZIP and delivery receipt when the job completes.

Package support

  • FARPY production rendering is Blender 4.1.1, Cycles GPU, .blend in, ZIP out.
  • The add-on was tested with Blender 4.1.1 on Windows; other Blender 4.x releases may work but are not yet fully audited.
  • Blender .blend stills and frame ranges are supported. Upload up to 100 MiB. Requests may include 1–10,000 frames.
  • Pricing is from $0.01 per completed frame. Quote, payment, tracking, downloads, and receipts continue in the browser workspace.
  • Sign in with Google in the workspace. The add-on does not store a browser password.
  • Your workspace tracks the job from send to completed package delivery.
  • Delivery receipts verify completed packages.

Need help?

Start with a small saved scene that has an active camera. If installation or sending fails, include your Blender version, operating system, and package ID when you contact support. Do not share private workspace links.

Prepare a Blender project before sending

Save the .blend file before creating a package. Confirm that the intended camera, render engine, frame range, output settings, and scene state are correct.

Missing textures, linked libraries, caches, fonts, simulations, or other external assets can cause a project to render differently or fail. Pack required assets where appropriate and test one representative frame before sending a large range.

Authentication and browser handoff

Pricing, payment, wallet balance, tracking, downloads, and receipts continue in the browser workspace. Sign in with Google. Email sign-in is coming soon. The add-on does not store your browser password.

Treat workspace, delivery, receipt, and proof links as private job access. Do not publish or forward them unless you intend to grant access to the associated job.

Track package delivery

The workspace follows the package from submission through FARPY rendering and completed package delivery. Use the job-specific workspace state rather than assuming that a successful upload means rendering has completed.

When output is available, download the completed package and retain your own local copy. FARPY is not permanent archival storage.

Receipts and verification

Delivery receipts verify completed packages and can include job, renderer, frame, cost, and SHA-256 information. A receipt does not replace the rendered output ZIP.

Use the receipt guide, files guide, and proof index for related verification guidance.

Compatibility limits

This add-on is tested with Blender 4.1.1 on Windows. FARPY renders that scene with Blender 4.1.1 Cycles GPU. Other Blender 4.x releases may work but are not yet fully audited. That wording is not a general compatibility guarantee.

Start with a small saved scene. A successful installation does not prove that every Blender scene, dependency, feature, or external asset is supported.

Verify the add-on ZIP

Verify the downloaded ZIP before installation. On Windows PowerShell, run Get-FileHash .\Farpy-Blender-Addon-unified.zip -Algorithm SHA256 and compare the complete result with the value below.

8D5CA2D53C2C71736BF9D7205D61D07D49AF40C2BB8E6EA97B697ABC6FC6260B

A mismatch means the file is not byte-identical to the published add-on artifact and should not be installed.

Add-on questions

Should I unzip the add-on before installing it?

No. Install the published ZIP directly in Blender.

Which Blender version was tested?

Blender 4.1.1 on Windows was tested. FARPY renders with Blender 4.1.1 Cycles GPU.

Does the add-on store my browser password?

No. Sign in with Google in the workspace. The add-on does not store a browser password.

Where do pricing and payment happen?

Pricing, payment, tracking, downloads, and receipts continue in the browser workspace.

What should I send when asking for help?

Include the Blender version, operating system, and package ID, but do not share private workspace links.

Related add-on resources

Open the workspace, review public downloads, check pricing, read the files guide, or contact support.