Blender animation render: PNG sequences vs MP4 codecs

Six hours of rendering and an MP4 that will not open: it was almost never the engine. It was the Output panel, the one nobody reads until it is too late. To render an animation in Blender is to configure that panel before the first frame ever starts.

Render an Animation in Blender: the Output Panel Decides Whether It Exists

The Output panel answers three questions you pay for during hours: where the result goes, in what format, and which frames are included. Get one wrong and the render finishes with no error at all and is still useless.

The confusion that eats nights is F12 against Ctrl + F12: the first renders a still and saves it nowhere, the second writes every frame to the configured path. That is why so many people "lose" a render that was never saved. Automatic saving can be switched off in the panel header, and then the video editor, compositing and playblasts demand an active output method or they fail.

The Output Panel, Field by Field (Blender 5.2)

File Path, Relative Paths and Frame Padding

Blender appends the frame number with four zeros: image0001.png. That padding is what lets a player sort the sequence, and you change it with hash marks: image_##_test.png produces image_01_test.png. The // prefix means "the folder of the .blend file" and saves projects that move between drives.

File Extensions and Cache Result

Without the extensions checkbox the files come out with no suffix and you end up renaming hundreds of frames. Cache Result stores layers and passes as a multi-layer OpenEXR inside the cache folder, reusable by the compositor after closing Blender: the difference between rendering again and compositing again.

Media Type: Image, Multi-Layer EXR or Video

Three options: Image (one file per frame), Multi-Layer EXR (everything in one OpenEXR) and Video (each frame encoded into a container). This is where old tutorials fail: video is no longer chosen as "File Format: FFmpeg Video" in Format, but in Output, under Media Type, with its options in Encoding. Format only governs resolution, percentage, aspect, region and frame rate.

Color Management on Save

Follow Scene uses what the scene defines; Override uses its own values and ignores the scene. Display formats such as PNG get the view and display transform; intermediate formats such as OpenEXR use the default output space, which is linear. With AgX or ACES this decides what gets baked in; I covered it in color management in Blender.

Frame Range: Start, End, Step and Time Stretching

Start and End hold the most expensive mistake: leaving the default range and rendering twice the real duration. The calculation that prevents it is one division, frames divided by frame rate gives seconds. One minute at 24 fps is 1,440 frames, not 250.

Step and Time Stretching

Step skips frames: at 4 or 8 you review the movement of a long shot in minutes, then go back to 1 for the final pass. Time Stretching remaps duration (old 2, new 1 plays everything at double speed) and does not affect Start and End, so you have to check by hand that the shot is neither cut short nor padded with extra frames.

Format: Resolution, Percentage, Region and Frame Rate

Percentage is perfect for tests but it stays put: it is the origin of the "final render at half resolution" that surfaces when the client opens it on a large monitor. Render region with crop does the same to the framing, and pixel aspect exists for old televisions only: set wrong, it distorts the whole shot.

Frame Rate and Base

Beyond the presets there is a custom mode with FPS and Base, the denominator of the fraction: that is where NTSC's 29.97 lives, which is really 30,000 divided by 1.001. Choosing 24, 25 or 29.97 depends on where the shot is shown and what it is cut against.

Image Sequence or Direct Video: The Decision Nobody Explains

The manual allows direct video for segments with under an hour of total render time, stable power and a free machine. Outside that, the sequence wins, and the reason hurts: if something fails halfway through a direct render the file can end up unreadable and you go back to frame one; with a sequence you resume at the frame that failed and encoding tests take seconds. The full walkthrough is in the image sequence rendering tutorial.

Overwrite and Placeholders

Overwrite off is the resume mechanism: finished frames stay and Blender moves on to the missing ones. Placeholders create empty files that reserve the frame name so another machine does not take it; with a shared network folder, Overwrite off and Placeholders on you have a render farm in two checkboxes. What actually scales is the cloud render farm.

The quality rule goes with the format rule: lossless PNG for the sequence, lossy compression only for delivery, and never re-process an already compressed file. Frame-to-frame noise is covered in the post about the denoiser in Maya and Blender.

Encoding: Container, Codec and Quality

A video file is a container plus a video codec plus an optional audio codec. H.264 is the safe bet for delivery, H.265 compresses better and supports HDR, AV1 and VP9 are the WebM options and ProRes is the intermediate standard. Not every pair is valid: that is where most "Blender cannot encode" reports come from.

CRF: Which Number to Touch and What 0 Means

It works opposite to intuition: the lower the number, the better the quality and the bigger the file. Ranges depend on the codec (0 to 51 for H.264, H.265 and AV1; 0 to 63 for VP9; 1 to 31 for MPEG-4), values outside get clamped and 0 means lossless. There is no universal number: you pick it by looking at the material and weighing the file.

Color Depth, ProRes and the 2 GiB Split

Depth runs from 8 to 12 bits depending on the codec. For HDR the manual asks for Rec.2100 PQ or HLG, H.265 or AV1 and 10 or 12 bits, with diffuse white at 100 nits; the most compatible setup is 10-bit PQ. Autosplit breaks the video once it passes 2 GiB, and H.264 requires dimensions divisible by 2: an odd resolution is a failure waiting to happen.

Audio

Audio encoding sets codec, channels, sample rate, bitrate and volume, and Render Audio exists separately in the Render menu with its own path. If the MP4 comes out silent it is almost never the codec: there was no audio to put inside the container.

From PNG to MP4: Assembling the Sequence in the Video Sequencer

Add the sequence as an image strip, check that the last item in the list matches the last frame of the render, choose container and codec, set the CRF and render. Before delivering, play the file in a player that is not Blender. A detail that saves an afternoon: the video editor does not read multi-layer EXR, so you have to go through an image input node in the compositor. The full workflow is in the post about the video sequence editor.

The Seven Classic Failures and Their Fix

• Nothing was saved. You pressed F12. Fix: Ctrl + F12 or save from the image editor.
• One frame, or 250 frames of a 120-frame animation. Start and End set wrong or Time Stretching touched. Fix: check range and duration.
• Frames at half resolution or cropped. Percentage at 50 % or region active with crop. Fix: 100 % and region disabled.
• Files with no extension the player will not open. Extensions disabled. Fix: enable them before rendering.
• A tiny MP4 that looks terrible. A lossy file re-encoded twice. Fix: start from PNG or EXR and compress once.
• Render killed at hour three. You were rendering straight to video. Fix: sequence plus Overwrite off to resume.
• Encoding fails or green streaks. Invalid container-codec pair or odd dimensions. Fix: MP4 with H.264 and even dimensions; H.265 or AV1 at 10 bits if HDR.

Conclusion

The Output panel is not paperwork: it is the contract between your scene and the file you deliver. If you come from Maya the workflow is the same under different names and it is laid out in rendering an image sequence in Maya; if every frame simply takes too long, that is solved earlier, in Cycles render optimization.

Three videos complete the route: Blender Guru's render routine, the image sequence tutorial and ten ways to render faster.