Render a Blender animation online and get an MP4 back

Send the scene (a .blend, a bpy script or a 3D file) with a frame range and you get the frames rendered on an NVIDIA RTX PRO 6000 and joined into a video: janction-render render scene.blend --frames 1-96 --size 1280x720 --samples 64 --wait, or render_final(frame_start=1, frame_end=96, output='mp4') from an agent. Measured: about 2.4 GPU seconds per 720p frame at 64 samples on Cycles for a simple scene (24 frames = 59 s); EEVEE costs about two-thirds of Cycles per frame for a few dozen frames or more (same scene, 720p, 120 frames: 142 vs 223 GPU-seconds, 2026-11-06). A final goes up to 3,000 frames per instruction (automatically split internally under one job id), 1080p on free time and 4K on prepaid credit; outputs are mp4 (H.264), webm (VP9), prores (422 HQ), gif, webp or png / exr frames. Preview 4 frames first to check camera and motion. AI agents connect at https://render.janction.jp/mcp (remote MCP with OAuth; connecting creates a free key).

Updated 2026-11-12

What it does Render a Blender animation and get it back as an MP4 (up to 3,000 frames per instruction, rendered as automatic internal parts; 1080p on free time, 4K on prepaid credit).
What it does not do No simulation baking (bake and pack locally first). The viewport does not get faster.

Try your animationBuild 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.

Commands

janction-render preview scene.blend --frames 1-96               # 4 frames spread over the range, one sheet
janction-render render scene.blend --frames 1-96 --size 1280x720 --samples 64 --wait            # output.mp4
janction-render render scene.blend --frames 1-96 --engine eevee --output webm --wait            # cheaper per frame
janction-render render scene.blend --frames 1-96 --output prores --wait                         # for editing
janction-render render model.glb --frames 1-48 --orbit --environment studio --wait              # turntable of a model

From an agent the same is render_preview(frames='1-96') then render_final(frame_start=1, frame_end=96, width=1280, height=720, samples=64, output='mp4'); render_estimate first tells you the time and whether it fits the free GPU time left (the welcome credit while it lasts, then up to 2 preview GPU-minutes a day).

How long it takes

These are individual observations of simple scenes (2026-09-30 to 10-01 UTC, NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition, 96 GB). The 4-GPU-second example used a rotating cube, four 640x360 tiles and 16 samples. GPU time includes Blender startup and scene loading; it is distinct from completion time including queue and transfers. See conditions, round trips and reproduction files. These are not speed guarantees.

render_estimate gives the number before rendering; once a scene has been rendered once, the estimate uses that scene's own measurement.

Frames are split into chunks and rendered in order; while a job runs, render_status shows frames done and the ETA. The benchmarks page has the per-frame table for several resolutions and sample counts.

Cycles or EEVEE

Cycles (default) is the path tracer: accurate light, slower. engine='eevee' is Blender's real-time rasterizer: about two-thirds of the Cycles cost per frame (same scene, 720p, 120 frames: 142 vs 223 GPU-seconds, 2026-11-06), but every job pays about 7 seconds of shader compilation, so it only pays off for a few dozen frames or more; previews stay on Cycles. HDRI presets work on both.

Outputs

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.

Connect

FAQ

Related

• Blender MCP server for rendering
• How to render Blender without a GPU
• Render a .blend file online on a GPU (free tier): upload, preview, final
• FAQ
• How much does cloud rendering a Blender video cost? Measured GPU seconds and prices

Overview · All guides · llms.txt