PocketShell
Blender on an Android phone: what renders, how fast, and the limits
You can run the real desktop Blender on an Android phone and render with EEVEE on the phone's GPU. Below is what that is good for, a full 10-second animation made and rendered on a Galaxy Z Flip 3, the measured times, and what does not work.
What you can actually do
- Render EEVEE stills and animations on the phone's GPU, in the background, while the phone sits on a desk.
- Script scenes in Python and run Blender headless (
blender -b). This is where a phone shines: you, or an AI coding agent, write the script in a terminal, and Blender builds and renders the scene. - Open the full Blender interface on a Linux desktop, on the phone screen or a tablet, for inspecting and small edits. It is a desktop program on a small touch screen: usable on a tablet with a mouse or keyboard, cramped on a phone.
- Fix and convert files on the go: open a .blend someone sent you, check it, re-export it.
A real example: a 10-second cinematic made on a phone
The scene (a night highway, a green tornado, lightning and a logo reveal) was built entirely by AI coding agents running in the PocketShell terminal on a Galaxy Z Flip 3. OpenCode with DeepSeek V4.1 Flash made a first version; it set up the scene, but the tornado looked like a paper streamer and the whole frame was a flat green. Claude Code (Claude Opus 5.5) then rebuilt it as about 20 Python scripts, around 3,700 lines, that Blender runs headless, so the whole scene can be rebuilt from scratch.
| What | Value |
|---|---|
| Output | 240 frames, 1280×720, 24 fps (10 s), EEVEE, 24 samples |
| Software | Blender 4.3.2 (Debian 13 package) on its OpenGL back end; Mesa 26.1.6 Zink on the Turnip Vulkan driver |
| Device | Galaxy Z Flip 3, Adreno 660 |
| Time per frame | median 14.4 s (fastest 11.3 s) with the screen on |
| Whole render | 84 min, of which about 25 min were frames slowed down while the screen was off (see below); about an hour with the screen on |
Two things made it fit on a phone. The storm sky was a heavy 3D volume, so it is rendered once as still layers and every frame then renders a much lighter scene. And frames are rendered in batches of 20 with a fresh Blender each time, so memory never builds up.
Measured: EEVEE on the GPU
| Test | Device | Time |
|---|---|---|
| Default scene plus a level-5 subdivided monkey, 1280×720, 16 samples, offscreen | Tab S7 (Adreno 650) | 12.0–12.6 s |
| Default scene, 1280×720, 16 samples, including first-run shader compile (earlier Alpine-based build, Blender 5.1.2) | Flip 3 (Adreno 660) | 10.7 s |
| Green Tornado frame, 1280×720, 24 samples (median of 240) | Flip 3 (Adreno 660) | 14.4 s |
Limits, plainly
- Cycles does not use the phone GPU. Cycles supports CUDA, OptiX, HIP, oneAPI and Metal; none exist on a phone. Cycles runs on the CPU and is slow. Use EEVEE.
- Blender's Vulkan back end does not work here. EEVEE with shadows on Blender's Vulkan back end hangs: one GPU job runs longer than the roughly two seconds Android's GPU driver allows, the driver resets the GPU context and Blender waits forever. The default OpenGL back end works.
- Keep the screen on while rendering. With the display off, Android slows the phone down: in the run above, 23 frames took 30 seconds to over 4 minutes each, instead of about 14 s.
- Memory is tight. Phones share memory between CPU and GPU. Very heavy volumes can push Android to kill the app; the example above stops a batch when free memory drops to about 550 MB and resumes later.
- Heavy interactive viewport work (sculpting a dense mesh, big scenes in Material Preview) was not measured. Every frame of a desktop window is copied through the CPU to the screen, which costs a few milliseconds per frame.
- Adreno only. The GPU path in PocketShell works on Qualcomm Adreno GPUs only. On other GPUs (Mali on many Exynos, MediaTek and Google Tensor phones) the same programs run on the CPU, which is much slower for graphics. That is being worked on; it does not work today.
- Battery use and heat during long renders were not measured.
How to try it
- Install Blender in the PocketShell terminal:
apt install blender. - Start the Linux desktop once. That installs and checks the GPU drivers; the desktop's Info sheet then says "Graphics: On the GPU" with your Adreno model.
- Open Blender from the desktop, or render from the terminal on the GPU:
. /tmp/ps-desktop/gpu.env; blender -b scene.blend -E BLENDER_EEVEE_NEXT -a - Keep the screen on for long renders, and render long animations in batches of frames.
Questions
Can I run Blender on Android?
Yes, the full desktop Blender (not a viewer) runs inside a Debian Linux system on Android with PocketShell. EEVEE renders on Qualcomm Adreno GPUs; other GPUs fall back to the CPU.
How fast is Blender on a phone?
On a Galaxy Z Flip 3 (Adreno 660), a 1280×720 EEVEE frame of a heavy storm scene took a median 14.4 seconds; a simple scene renders in about 10–12 seconds on a Flip 3 or Galaxy Tab S7. A desktop GPU is many times faster.
Does Cycles work on the phone GPU?
No. Cycles supports CUDA, OptiX, HIP, oneAPI and Metal only, so on a phone it runs on the CPU. Use EEVEE.
Why do my phone renders slow down?
Check that the screen stays on. With the display off, Android throttles the phone, and frames that took about 14 seconds took 30 seconds to over 4 minutes.
Written by Muhammad Taha Raees, the developer of PocketShell. Measurements are single runs on the devices named, unless the text says otherwise. Last checked: 2026-11-04.