# GPU or CPU for video rendering: which one pays off, and when?

> A graphics card (GPU) renders video with far less processor work, as long as the engine keeps the frame on the card. On the same 1080p video, Kodecz on the GPU used 2.0 s of CPU; on the processor alone, 28.1 s. Without a GPU the CPU path still works, and on some videos another tool wins.

Pedro Henrique Lahr, Konecz, 2026-11-19. https://konecz.com/en/blog/gpu-ou-cpu-para-renderizar-video

For video made with code, the graphics card (GPU) pays off when the engine can keep the frame on the card until the end. We measured the same 1080p video on both paths of Kodecz, the Konecz engine: on the GPU, the processor worked 2.0 seconds; on the processor (CPU) alone, 28.1 seconds, about 14 times more. Without a graphics card the video still comes out the same; it just costs the machine more.

## What is the difference between GPU and CPU in a render?

The CPU is the processor, the part that does the general math in a computer. The GPU is the graphics card, built to handle images very fast and, on NVIDIA cards, with a video encoder built in (NVENC).

A render has three jobs: drawing the page, compressing the frame into video and, when there is a filmed presenter, opening that recorded video. On the GPU, all three can stay on the card. On the CPU, all three land on the processor.

## How much did each path use on the same video?

On 2 November 2026 we measured two synthetic videos on the same machine and the same day, three rounds each (the numbers are medians):

| Video | Path | CPU | Wait time | Memory |
|---|---|---|---|---|
| Presenter, 1080p, 150 frames | Kodecz on the GPU | 2.0 s | 2.7 s | 0.48 GB |
| | Kodecz CPU only | 28.1 s | 7.1 s | 1.60 GB |
| Audiogram, 1080 × 1080, 814 frames | Kodecz on the GPU | 7.0 s | 7.8 s | 0.55 GB |
| | Kodecz CPU only | 24.6 s | 9.3 s | 0.98 GB |

Wait time (the clock, from the command to the finished MP4) also drops on the GPU, but much less than CPU time. What changes most is how busy the processor stays.

## When is the CPU enough?

When there is no NVIDIA card, or when the server has processor time to spare. The Kodecz CPU path does not take a screenshot of each frame either: the browser paints the frame and hands the raw frame to the x264 encoder. The result is the same video.

The kind of video matters too. On the audiogram (cover, title, 48 sound bars, captions), Kodecz on the CPU alone used 24.6 s, against 59.9 s for HyperFrames without a GPU: 2.4 times less.

## Where does the CPU path lose?

On the video with a filmed presenter. Without a GPU, HyperFrames used 26.3 s of CPU against 28.1 s for Kodecz. The reason: Kodecz paints the embedded 1080p video in software, frame by frame, while HyperFrames extracts the video's frames with ffmpeg once and caches them. We say so in our own measurement report, because a one-sided number helps nobody choose.

## And on the GPU, against the other tools?

On the presenter video, same day:

- Kodecz on the GPU: 2.0 s of CPU and 2.7 s of wait.
- HyperFrames defaults: 22.0 s of CPU and 6.4 s. With its own GPU option: 14.8 s and 6.6 s.
- Remotion defaults: 37.7 s of CPU and 9.9 s.

The gap comes from where the frame travels. The other two take a screenshot per frame; Kodecz hands the card's texture straight to NVENC.

## What does the GPU not solve?

Three things:

1. **NVIDIA on Linux only.** Mac, Windows and AMD cards have no GPU path in Kodecz. There, it is the CPU.
2. **A busy card.** If NVENC has no free session or the card's memory is full, the render fails with a message and waits, instead of quietly falling back to the CPU. On the Konecz server the CPU belongs to the websites, so a silent fallback would be worse.
3. **Tiny variation.** Animated text drawn on the card can differ by up to 2 color levels between two renders. You cannot see it, but it is there.

## Frequently asked questions

**Is it worth buying a graphics card just for rendering video?**
It depends on volume and on what else runs on the machine. If other services compete for the processor, the card takes almost all the video work off it. If not, the CPU copes, just more slowly.

**Does quality change between GPU and CPU?**
Very little. In the comparison with HyperFrames, Kodecz on the GPU had a mean SSIM of 0.9976 and on the CPU 0.9972, on a scale where 1 means identical.

**Why does wait time drop less than CPU time?**
Because part of the time is starting the browser, preparing the page and assembling the file. That does not go away with a card.

**Will any NVIDIA card do?**
It needs NVENC and driver 570 or newer. The measurements were taken on an RTX 5090; other cards will give other numbers.

The full numbers are in the post about the [Kodecz render engine](/en/blog/kodecz-render). At Konecz, every client video goes through the GPU path; see the results in the [portfolio](/en/portfolio).
