Vol. 1 · No. 257Blender 3.6 / 4.2 / 4.5 / 5.0 / 5.2Cycles · EEVEE
JANCTION
Render · Blender on RTX PRO 6000 · Tokyo
0.1 JPYper GPU-secondFirst 100 JPYfree, no card
Front page / Cycles is slow on my MacBook: what to do

Cycles is slow on my MacBook: what to do

First make Blender use the Mac's GPU: Settings > System > Cycles Render Devices > Metal (tick the GPU), then Render Properties > Device > GPU Compute. Apple silicon Macs and Macs with a supported AMD GPU can do this; Macs with only Intel graphics render Cycles on the CPU. Then cut the work rather than the look: fewer samples with Denoise on, a lower resolution or a render region for tests, Persistent Data for animations, and EEVEE when the look allows. If it is still too slow, send the .blend to a cloud GPU so the Mac only uploads the scene: on JANCTION Render's NVIDIA RTX PRO 6000, 1920x1080 Cycles stills at 128 samples took 6 to 10 GPU-seconds (0.6 to 1 JPY) and a 24-frame 720p turntable took 58 GPU-seconds (about 6 JPY), measured on the production GPU; each new key starts with a welcome credit of up to 500 JPY. AI agents connect at https://render.janction.jp/mcp (remote MCP with OAuth; connecting creates a free key).

Updated 2026-10-26

What it does If the slow part is the render, send the file and get the frames or the video back from a cloud NVIDIA GPU.
What it does not do A slow viewport is not fixed by the cloud: fix it locally first (simplified display, lower subdivision, smaller textures). Simulations are not taken.

Try your own file for freeBuild it with an AI and try

Browser only; no connector or CLI needed. A 100 JPY welcome credit for a new key (14 days, no card; one per network every 30 days, further keys on the same network share what is left), and 400 JPY more for saving a card that is not charged (once per card); after that, previews stay free up to 2 GPU-minutes a day and finals cost 0.1 JPY per GPU-second.

Measured, not estimated

The same simple scene (a rotating cube, 1920x1080, 128 samples, Cycles with denoising), one frame each, measured in October 2026:

machine / routesettingsGPU secondscostround trip
ASUS ROG Zephyrus G14, Core Ultra 9 386H CPU, no GPU used1 frame, 1920x1080 / 12820.0 s (CPU)no fee—
the same laptop, GeForce RTX 5070 Ti Laptop GPU1 frame, 1920x1080 / 1286.0 sno fee—
NVIDIA RTX PRO 6000 Blackwell (production)24 frames, 1920x1080 / 128 (5.4 per frame)129.4 GPU-sabout 13 JPY133 s
NVIDIA RTX PRO 6000 Blackwell (production)Blender demo Classroom, 1920x1080 / 1288.9 GPU-s per frameabout 0.9 JPY per frame—

A gaming laptop's GPU matches the production GPU per frame on this scene, so a usable GPU of your own is the first thing to try; the service is for machines without one, for heavy scenes (96 GB on the production GPU) and for keeping the laptop free.

Sources: /benchmarks (2026-09-30 to 2026-10-01), examples/one-command (2026-10-10), a laptop measured on 2026-10-11. Individual runs, not a guarantee; 0.1 JPY per GPU-second after the welcome credit.

What is slow decides what to do

what is slowwhat to do
The final image takes too longTry one frame of your scene on a cloud GPU (preview first, no payment)
The animation never finishesTime a few sample frames and get an estimate for the whole thing
The render stops with out-of-memoryRead the scene and check that it renders here (96 GB of GPU memory; missing files and version problems are reported first)
The viewport is slow to work inFix it locally: Simplify (Render Properties > Simplify) to cut subdivision and texture size, turn off rendered viewport shading, hide heavy modifiers in the viewport. Cloud rendering does not make the viewport faster
A simulation is slowThe computation itself is not done here. Bake it locally, pack the cache into the .blend, and the rendering can be done here
Code from an AI will not runPaste the script and render it as it is (errors come back with a type and a fix)

1. Make Blender use the Mac's GPU

Cycles renders on the CPU until you turn the GPU on. On a Mac with Apple silicon (M1 or later) or a supported AMD GPU: Blender > Settings > System > Cycles Render Devices > Metal, tick the GPU, then Render Properties > Device > GPU Compute. A Mac with only Intel graphics renders Cycles on the CPU. Source: Blender manual, GPU rendering.

2. Cut the work, not the look

settingwhat it doesuse it for
Fewer samples with Denoise onmost of the render time is samples; the denoiser cleans up the noisestills and animations
Lower resolution % or a render region (Ctrl+B in the camera view)renders a smaller image or only part of ittest renders
Persistent Data (Render Properties > Performance)keeps the scene loaded between framesanimations
Fewer light-path bouncesless work per samplescenes without glass or deep indirect light
EEVEE instead of Cyclesa rasterizing engine, much faster per framewhen the look allows (no exact caustics or path-traced light)

3. Still too slow? Render somewhere else

optioncostwhat to expect
Leave the Mac rendering overnightno service feethe Mac is busy and warm while it renders
SheepIt (volunteer farm)free, you earn points by rendering for othersa queue; upload through the site; no API
Commercial render farmspaid per GPU-hour or creditsadd-on or web upload; built for large jobs
JANCTION Renderwelcome credit of up to 500 JPY per new key, then 0.1 JPY per GPU-second (previews free up to 2 GPU-minutes a day)a datacenter NVIDIA GPU; from the terminal, Claude, ChatGPT or an agent; up to 3,000 frames per instruction (automatic internal parts), 1080p on free time and 4K on prepaid credit

Send the .blend from the Mac

How do I start for free?

  1. Open /start in the browser and press "Try the sample first": no file, no payment, a preview in seconds.
  2. On the same page, drop your own .blend, 3D file or bpy script, preview it, check the estimate and the free time left, then render the MP4 or still.
  3. From an AI instead: add https://render.janction.jp/mcp to an MCP client (Claude, ChatGPT, Claude Code, Codex, Cursor), connect through OAuth consent and send the prompt below. Custom MCP access depends on the client's plan and administrator settings.
  4. From a terminal: uvx janction-render try renders a sample in seconds (a free key is created for you), then uvx janction-render preview scene.blend. Without uv: pip install janction-render.
Using JANCTION Render, build a glossy red cube rotating on a gray floor and show me a 4-frame preview.
If it looks right, render 24 frames at 1280x720 as an MP4.

To render a .blend or 3D file that is on your computer, drop it at /upload to get a 12-hour link (no sign-up) and tell the AI "Render this file: <link>". To test the connection first: "Render a preview of https://render.janction.jp/samples/cube_scene.py".

Free quota and what happens at the limit

Pricing (since 2026-10-08): Each new key gets 100 JPY of GPU time free with no card (1,000 GPU-seconds, 14 days) for previews and finals, and 400 JPY more once a card is saved on a Stripe page that charges nothing (once per card): up to 500 JPY in all. After it is used up or expires, previews are free up to 2 GPU-minutes per key per day and final renders are paid from prepaid credit at 0.1 JPY per GPU-second. Top-ups (paid) start at 100 JPY. The first top-up during the 14-day welcome period counts 1.5x, with the bonus capped at 500 JPY (100 JPY buys 150 JPY of credit). Top-ups of 2,000 JPY or more get 10 to 20% extra (not combined with the first-top-up bonus; the larger one applies). Top-up bonuses are separate from the welcome credit and the card-saving credit. Payment is on a Stripe Checkout page. One full welcome credit per network every 30 days; further keys from the same network use what is left of that network's credit. A job without enough credit gets HTTP 402 payment_required with a checkout_url. Final renders go up to 3,000 frames per instruction (automatically split internally under one job id), 1080p (1920x1080) on free time and up to 4K (3840x2160) on prepaid credit. The free preview time resets at 00:00 UTC (09:00 JST). No sign-up: connecting creates a key. Inputs and results are deleted 24 hours after last use (normally 7 days for keys that have paid 500 JPY or more in total) and never used for training.

Measured on the production GPU

jobGPU timeprice at 0.1 JPY per GPU-second
1920x1080 Cycles still, 128 samples6 to 10 GPU-seconds0.6 to 1 JPY
24-frame 720p turntable (Cycles, MP4)58 GPU-secondsabout 6 JPY
48-frame 720p logo animation (EEVEE, MP4)45 GPU-secondsabout 4.5 JPY

Each run with its script and settings: examples · benchmarks. A Mac's own time depends on the chip and the scene, so it is not quoted here.

Free limits

Pricing (since 2026-10-08): Each new key gets 100 JPY of GPU time free with no card (1,000 GPU-seconds, 14 days) for previews and finals, and 400 JPY more once a card is saved on a Stripe page that charges nothing (once per card): up to 500 JPY in all. After it is used up or expires, previews are free up to 2 GPU-minutes per key per day and final renders are paid from prepaid credit at 0.1 JPY per GPU-second. Top-ups (paid) start at 100 JPY. The first top-up during the 14-day welcome period counts 1.5x, with the bonus capped at 500 JPY (100 JPY buys 150 JPY of credit). Top-ups of 2,000 JPY or more get 10 to 20% extra (not combined with the first-top-up bonus; the larger one applies). Top-up bonuses are separate from the welcome credit and the card-saving credit. Payment is on a Stripe Checkout page. One full welcome credit per network every 30 days; further keys from the same network use what is left of that network's credit. A job without enough credit gets HTTP 402 payment_required with a checkout_url. Final renders go up to 3,000 frames per instruction (automatically split internally under one job id), 1080p (1920x1080) on free time and up to 4K (3840x2160) on prepaid credit. The free preview time resets at 00:00 UTC (09:00 JST). No sign-up: connecting creates a key. Inputs and results are deleted 24 hours after last use (normally 7 days for keys that have paid 500 JPY or more in total) and never used for training.

FAQ

Does Blender use the GPU on an M1, M2 or M3 MacBook?

Yes, through Metal, once you turn it on: Settings > System > Cycles Render Devices > Metal, then Render Properties > Device > GPU Compute. Until then Cycles renders on the CPU.

Why is my Mac rendering Cycles on the CPU?

Either Cycles Render Devices is set to None, the scene's Device is CPU, or the Mac has only Intel graphics, which Cycles cannot use.

Is EEVEE faster than Cycles on a Mac?

Usually much faster per frame, because it rasterizes instead of tracing paths. It does not reproduce exact caustics or path-traced indirect light, so check the look on a still first.

Can I render my .blend on a cloud GPU without installing more on the Mac?

Yes: drop the file at https://render.janction.jp/upload, or ask Claude or ChatGPT with the JANCTION connector, or run uvx janction-render render scene.blend --frames 1-48 --output mp4 --wait (needs uv). Blender runs on the cloud GPU; the Mac only uploads the scene.

What does a cloud render cost?

Measured on the production GPU: a 1920x1080 Cycles still at 128 samples took 6 to 10 GPU-seconds (0.6 to 1 JPY) and a 24-frame 720p turntable 58 GPU-seconds (about 6 JPY). Each new key starts with a welcome credit of up to 500 JPY; after that, 0.1 JPY per GPU-second, and previews stay free up to 2 GPU-minutes a day.

Related

Overview · All guides · llms.txt