There is no single normal number for per-frame render time, because it is driven almost entirely by what is in the frame. A flat motion graphics
There is no single normal number for per-frame render time, because it is driven almost entirely by what is in the frame. A flat motion graphics loop might render in 20 to 60 seconds a frame, a lit interior with global illumination in 5 to 15 minutes, and a character shot with hair, subsurface skin, or volumetrics can legitimately take 20 to 45 minutes or more. So 25 minutes can be completely reasonable for a heavy shot, or a sign of serious waste on a simple one. To tell which, compare your frame to its scene type below, then check whether the time is coming from the scene itself or from settings you can dial back.
I get asked this more than almost anything else, usually by someone who just watched a frame crawl and started to panic about whether their setup is broken. The answer I give them is that the question is incomplete. Twenty-five minutes for what kind of frame? A bare mograph loop and a fog-filled character close-up are not in the same universe, and comparing one to the other tells you nothing.
So instead of a yes or no, let me give you something you can actually measure yourself against.
Rough per-frame times by scene type
These are ballpark ranges I see on a single modern GPU at roughly 1080p, using a current engine like Redshift, Octane, or Cycles with sensible settings. They are wide on purpose, because the same scene type swings a lot depending on lighting and materials.
| Scene type | Typical per-frame (1080p, 1 modern GPU) | Main time drivers |
|---|---|---|
| Flat motion graphics / logo loop | ~20 to 60 seconds | Simple shading, little GI, low samples needed |
| Stylized character, simple lighting | ~1 to 4 minutes | Character shading, some GI, moderate samples |
| Product shot with reflections | ~3 to 8 minutes | Reflections, depth of field, clean samples |
| Lit interior with global illumination | ~5 to 15 minutes | GI bounces, many light sources, glossy surfaces |
| Character with hair, subsurface, or fur | ~15 to 40 minutes | Hair primitives, SSS, dense sampling to stay clean |
| Volumetrics, fog, heavy effects | ~20 minutes to over an hour | Volume sampling, the most expensive thing you can render |
Find the row that matches your shot. If you are rendering a fog-heavy character close-up and seeing 25 minutes, you are right where you should be, and the answer to your panic is that nothing is wrong. If you are rendering a flat logo loop and seeing 25 minutes, something is badly off and it is worth an afternoon to chase down.
If your number is too high for the scene type
When a frame is taking far longer than its row suggests, the cause is almost always settings rather than the scene being inherently heavy. The usual culprits are samples set far higher than the shot needs, motion blur running full steps on objects the eye never settles on, a global illumination bounce count nobody revisited, and 8K textures on things that fill a sliver of the frame. Read your render log to see which stage is eating the time, drop that one thing, and re-test on your busiest frame.
There is a separate guide in this series that walks through the nine bottlenecks I run into most, if you want the full checklist. The short version is that you can usually pull a bloated frame down to where its scene type says it should be without touching hardware at all.
When the frame is genuinely heavy and the sequence is long
Some frames are heavy because the shot demands it, and that is fine for one image. The problem is multiplication. A legitimate 25-minute frame across a 500-frame sequence is over 200 hours on a single card. At that point the scene being correct does not save your deadline, and you need more machines working at once.
This is where a render farm makes sense, and the right one depends on what your project needs. As an independent site, here is the short version. GarageFarm is the easiest to start with if you just want to submit and walk away, though a custom plugin can trip it up. Fox Renderfarm usually comes in cheapest for a long batch of frames like this. RebusFarm adds a useful scene checker that catches setup problems before they cost you render time. SheepIt is free if you are on Blender and not racing a deadline, since you wait in a community queue.
When I render a heavy sequence myself I reach for iRender, because I want the machine to match my scene exactly. It runs an IaaS model, so I rent a full server with up to 8x RTX 4090 and 256GB of RAM and install my own engine version and plugins. A volumetric character shot tends to use a specific setup, and “your renders, your rules” is the part of their pitch that actually matters to me, since the server runs whatever my workstation runs rather than forcing me onto a template.
It is worth knowing what you take on with that control. You set the machine up the first time, around half an hour in my experience, and the billing runs from server boot until you shut it down, so a forgotten idle server keeps charging. Turning it off the moment the last frame writes is part of the routine for me.
On cost: iRender returns roughly 10% to 20% of spend through Credit Back (10% standard, 12% weekday Happy Hours, 20% weekend Golden Hours, GMT+7), and new accounts get a 100% first-deposit bonus. For a long, heavy sequence, lining the render up for the weekend and stacking the first-deposit bonus can take the effective rate down a fair way. (Check current rates before relying on them.)
FAQ
Is 25 minutes per frame normal for animation?
It can be, depending on the scene. A flat motion graphics loop should render in under a minute, while a character with hair, subsurface skin, or volumetric fog can legitimately take 20 to 45 minutes a frame. Match your shot to its scene type. If a simple frame takes 25 minutes, something is wasteful; if a heavy effects frame does, it is likely normal.
How long should one frame take to render?
There is no universal figure, since per-frame time is set by scene complexity. As a rough guide on one modern GPU at 1080p, expect 20 to 60 seconds for flat motion graphics, 5 to 15 minutes for a lit interior with global illumination, and 20 to 40 minutes or more for heavy character or volumetric shots. Rendering at 4K usually multiplies these by about 3 to 4.5 times.
How do I make a slow frame render faster?
If the frame is slower than its scene type suggests, the cause is usually settings, not the scene. Lower oversized samples and add a denoiser, right-size textures, and trim motion blur and global illumination bounces where they do not matter. Read the render log to find the slowest stage and fix that one first, then re-test on your busiest frame.
Your renders, your rules
When a frame is heavy for good reason and the sequence is long, I split it across a full GPU server I control instead of waiting days on one card. New accounts get a 100% first-deposit bonus, and weekend renders earn up to 20% back. See iRender GPU servers and pricing → iRender RTX 4090 servers.
See more: Why Does My Animation Render So Slowly? 9 Bottlenecks I Found in My Own Scenes
Image source: Blender Studio
COMMENTS