RENDERPULSE
Remote render control

Your Blender renders,
in your pocket.

Watch progress, see a live preview, and Start / Stop / Queue your renders from your phone — from anywhere. No IP addresses, no port forwarding, no firewall rule. Just scan a code.

Tap “Get the app” → on the build page tap Install (allow “install unknown apps” when Android asks). Blender 4.2+ extension. iOS coming later.

Get started

Set it up in 3 steps (about 60 seconds)

01

Install the app

Tap “Get the app”, install the APK on your Android phone, and open RenderPulse.

02

Add it to Blender

Drag the extension zip onto Blender (or Preferences ▸ Get Extensions ▸ Install from Disk) and enable RenderPulse. A code appears.

03

Scan the code

In the app, tap Scan and point it at the QR in Blender — or type the 6-digit code. Done. You're connected.

Power users

Keep the add-on auto-updating

Add the remote repository

In Blender ▸ Get Extensions ▸ ▾ ▸ Add Remote Repository, paste the URL on the right. RenderPulse will then auto-update to new versions for you.

https://renderpulse.pages.dev/repo/index.json
Questions

FAQ

Do I need home Wi-Fi?

No. Once paired, RenderPulse works over cellular or any Wi-Fi, anywhere. The only requirement is that your render PC has power and internet.

Do I need port forwarding, Tailscale, or a firewall rule?

No. The Blender extension only makes outbound connections, so there's nothing to open. (Those steps only apply to an optional advanced LAN-only mode that most people never use.)

My phone says the PC is offline.

Check that Blender is open, the RenderPulse extension is enabled, and the PC is awake and online. It reconnects automatically within a few seconds.

How do I install the app?

Tap “Get the app · Android”. On the build page that opens, tap Install / Download. The first time, Android asks you to allow “install unknown apps” for your browser — approve it, then tap Install. (This is normal for apps not from the Play Store.)

Is it private?

Yes. When you pair by scanning the QR code, the connection is end-to-end encrypted (ChaCha20-Poly1305): the relay only ever passes along ciphertext and can’t read your renders, previews, or commands. Pairing codes expire and every device gets its own token.