Home · Volume 3 · Chapter 04

📖 Chapter 04 — Render Workflows

Where the actual rendering happens. The choice that determines what hardware to invest in.

v0.1 · draft Vol 3 · Ch 04
~12 min

Learning Objectives

Introduction

Editing is interactive. You scrub the timeline, make cuts, add effects. You need every frame to be ready in milliseconds.

Rendering is the opposite. You press "Export" and the NLE chews through every frame, applying effects, encoding, writing a file. The same operations that feel snappy during editing can take 10x real-time during export.

Where that rendering happens — laptop, NAS, or cloud — is one of the most consequential decisions a creator makes. The conversation was explicit: render on the laptop, archive on the NAS. This chapter is about why, and the cases where you'd break the rule.

The default: render on the laptop

For most projects, render on the laptop. Why:

For a 10-minute 1080p video with modest effects, the laptop renders in 30-60 minutes. That's fine. You can do other things while it renders.

When the laptop isn't enough

There are projects where the laptop chokes:

For these cases, you have three options: optimize the laptop, render on the NAS, or use a cloud render service.

Option 1: Optimize the laptop

Before adding new infrastructure, see if you can make the laptop faster. Most render time is in two places: codec decoding/encoding and effects. Both can be accelerated.

Hardware acceleration

Proxy-based rendering

If you edited using proxies (Chapter 03), the NLE can re-link to the originals for the final render. The render then uses the high-quality source, even though the edit was done on proxies. This is the right default — the proxy-based editing is for interactivity; the render uses the real source.

Optimized media

DaVinci Resolve has "Optimized Media" — a middle-ground between proxy and original. Faster than the original, higher quality than a proxy. Use it for the final render pass if disk space allows.

Option 2: Render on the NAS

For a small render farm, the NAS can do it. The setup:

  1. Install a render-capable app on the NAS. DaVinci Resolve doesn't run on TrueNAS (it requires macOS, Windows, or Linux desktop), but you can run:
    • ffmpeg for command-line encoding
    • HandBrake in CLI mode
    • Natron or other compositing software on Linux
  2. The render workflow:
    • Export the timeline as an EDL (edit decision list) or XML from the NLE on the laptop
    • Use the EDL/XML to drive ffmpeg or a render script on the NAS
    • The NAS renders the final output directly to Media/Archive/<year>/<slug>/renders/
  3. The benefits:
    • The laptop is free for other work during the render
    • The NAS can run the render unattended (overnight, while you sleep)
    • Network-attached storage is the right place for the rendered output anyway

The honest tradeoff

The NAS typically has a weaker CPU and no GPU compared to the laptop. For a CPU-only render, the NAS is 2-3x slower than a modern laptop. For a GPU-accelerated render, the gap is even bigger.

So "render on the NAS" only makes sense if:

For TK's build, the recommendation was the laptop. The NAS CPU is decent for transcoding/conversion tasks but not for full NLE renders.

Option 3: Cloud rendering

For occasional heavy work, cloud render services are an option. The conversation mentioned this as a possibility; the practical considerations:

For a hobbyist creator, cloud rendering is rarely worth the operational complexity. For a professional who bills for time, it can be.

The render farm pattern (advanced)

For very heavy workloads (feature-length documentary, lots of VFX), you can use multiple machines. The pattern:

  1. Split the timeline into segments. Each machine renders one segment.
  2. Combine the segments into a final file. ffmpeg concat does this in seconds.
  3. The total time is the slowest single segment, not the sum of all.

For a 4-machine render farm, a 4-hour render becomes a 1-hour render. The setup is non-trivial (most NLEs don't have built-in distributed rendering for single timelines), but ffmpeg and command-line tools can do it.

For most home creators, this is over-engineering. Mention it for completeness.

Render output formats

The "what format" decision is separate from the "where to render" decision but happens at the same time. The conversation's recommendations:

Master (for archiving and re-editing)

Web (for YouTube and similar)

Social (for Instagram, TikTok, etc.)

Render-time mistakes to avoid

Engineering Note

The render is one moment in time, not an ongoing process. You render once, you have the file. The cost of being slow on the render is annoying; the cost of losing the file is catastrophic. So: render to a destination that's already backed up. Render to the NAS archive. Then you have one file in one place, and that place is safe.

Summary

Default: render on the laptop. The laptop has the GPU, the local files, and zero setup. If the laptop isn't enough, optimize first (hardware acceleration, optimized media, proxy re-link). If still not enough, render on the NAS for long unattended overnight jobs, or use a cloud render service for occasional heavy work. Render directly to the NAS archive so the output is already in a backed-up place. Use the right format for the destination: ProRes for master, H.264 for web, vertical H.264 for social.

Checklist

Looking Ahead

Chapter 05 is the 3-2-1 backup story for video. The archive on the NAS is one copy. The cloud backup or external drive is the second. The cold copy in a fireproof safe is the third. The chapter that protects the projects from the disasters that no amount of in-NAS protection can handle.

Previous← Ch 03 · Active Project Scratch Next📖 Ch 05 · Backing Up the Backups →

Ch 04 · v0.1 · drafted from the original ChatGPT conversation, July 2026