Rendering Basics: Render Engines, Resolution, and Output Formats

Blender Fundamentals

Chapter 9 · Rendering Basics: Render Engines, Resolution, and Output Formats

Every chapter so far built up a scene — shape, material, lighting, and now animation. This chapter covers the final step that turns all of it into an actual, finished image or video: rendering.

What Rendering Actually Does: Turning a Scene Into a Final Image

Rendering calculates the final, finished appearance of a scene — every material's own color and reflections, every light's own effect, every shadow — pixel by pixel, producing either a single still image or a full sequence of frames for an animation. This is a genuinely different process from the viewport's own Material Preview mode from Chapter 6, which only approximates that same appearance in real time for convenience while working.

Eevee: Fast, Real-Time-Style Rendering

Eevee is Blender's own fast render engine, using techniques closer to real-time video game rendering to produce results quickly, often in a small fraction of a second per frame. It approximates many lighting and material effects rather than simulating them with full physical accuracy, trading some realism for dramatically faster render times.

Cycles: Physically Accurate Ray-Traced Rendering

Cycles simulates light physically, tracing individual rays as they bounce, reflect, and refract through a scene the way real light actually behaves. This produces genuinely more physically accurate results — more convincing reflections, more realistic soft shadows, more accurate light bouncing between surfaces — at the direct cost of considerably longer render times per frame.

Choosing Between Eevee and Cycles

Eevee suits real-time preview work, fast iteration, and situations where render time genuinely matters more than absolute physical accuracy — a game asset preview, a quick animatic, a fast client preview. Cycles suits final, polished output where physical accuracy matters more than speed — a hero product shot, a detailed architectural visualization, a final animation frame meant for real theatrical or broadcast delivery.

Resolution and Output Settings

Resolution sets the pixel dimensions of the final rendered image or frame — higher resolution produces a sharper, more detailed result at the cost of longer render time and a larger file size, the same fundamental trade-off Raster Editing Fundamentals' own material on pixel resolution described for 2D images.

Output Formats: Still Images vs. Animation

A single still image renders once, to a format like PNG or JPEG. An animation renders every individual frame in sequence, either as a folder of individual image files (one per frame) or directly compiled into a single video file. Rendering to individual frame images first is generally the safer choice for a longer animation, since a crash partway through only loses whatever frames hadn't rendered yet, rather than the entire in-progress video file.

Aspect	Eevee	Cycles
Speed	Fast, often real-time	Considerably slower
Accuracy	Approximated lighting/reflections	Physically accurate, ray-traced
Best suited to	Previews, fast iteration, game-style assets	Final polished output, realistic renders

This is where the capstone actually finishes

Chapter 10's own capstone brings every prior chapter's own technique together and finally renders the result — the direct, concrete payoff of everything modeled, materialed, lit, and animated across this entire course.

Cycles' greater accuracy doesn't automatically make it the right choice

It's tempting to assume Cycles must simply be the "better" render engine since it's more physically accurate, and default to using it for everything regardless of the situation. For iterative work — checking how a scene looks after each small adjustment, previewing an animation's own timing — Eevee's dramatically faster render time is often the genuinely better choice, even though its results are less physically precise. Reaching for Cycles by default for every render, including quick checks that don't need that level of accuracy, wastes considerable time without adding real value to work still in progress.

Hands-On Exercises

Exercise 1

A designer needs to quickly check how a scene's lighting looks after each small adjustment, iterating many times over a short work session. Using this chapter's own material, explain which render engine fits this need and why.

📄 View solution

Exercise 2

A student uses Cycles by default for every single quick preview render while still adjusting basic object placement, and finds their workflow has become frustratingly slow. Using this chapter's own warning box, explain what's happening and what a better approach would look like.

📄 View solution

Exercise 3

Explain, using this chapter's own material, why rendering a long animation to a folder of individual frame images is generally safer than rendering directly to one single video file.

📄 View solution

Chapter 9 Quick Reference

Eevee renders fast using approximated lighting/reflections, suited to previews and iteration
Cycles renders slower but physically accurate, suited to final, polished output
Higher resolution produces a sharper result at the cost of longer render time and larger file size
Rendering to individual frame images is generally safer for long animations than one continuous video file
More accurate isn't automatically the better choice — match the render engine to what the work actually needs right now