# What is NVENC, and why encode video on the graphics card

> NVENC is the video encoder built into NVIDIA graphics cards: it compresses frames into H.264 or HEVC without using the processor. In a Remotion render, swapping x264 for NVENC cut CPU time by 32%. The price: files that are sometimes a bit larger, and a limit on how many encodes run at once.

Pedro Henrique Lahr, Konecz, 2026-11-20. https://konecz.com/en/blog/nvenc-codificar-video-na-placa

NVENC is a piece of hardware inside NVIDIA graphics cards that does one thing: compress frames into video (H.264, HEVC). Because it is a separate circuit, it works without occupying the processor. On a 15 second stretch rendered by Remotion, swapping the x264 encoder (which runs on the CPU) for NVENC cut the processor's work by 32%. That is why every Konecz video is encoded on the card.

## What does a video encoder do?

It turns a sequence of images into a small file. A raw 1080p frame takes about 8 MB; a 60 second video would have 1,800 of them. The encoder compares each frame with the previous ones, keeps only what changed and drops what the eye does not notice. The result is the few-megabyte MP4 that goes to Instagram.

That work is heavy. Done by x264, the most widely used encoder, it lands entirely on the processor.

## How much does NVENC save in practice?

We measured a production video with a presenter, exported by Remotion, on a 15 second stretch with two rounds per setting:

| Setting | CPU (mean) | Wait time |
|---|---|---|
| Remotion's direct MP4, x264 | 176.8 s | 33.7 s |
| Remotion's direct MP4, NVENC | 121.1 s | 29.9 s |

Swapping the encoder alone took 55.7 seconds off the processor. Wait time dropped less, because the rest of the render (starting the browser, drawing, opening the presenter video) stays the same.

In Kodecz, the Konecz engine, the gain is bigger because the frame is born on the card. The image the browser draws goes straight to NVENC, without passing through the processor's memory. On the 1080p presenter video, that came to 2.0 seconds of CPU in total.

## Is the file the same?

Nearly the same picture, but not necessarily the same size. Each encoder has its settings, and they change the file's weight:

- On the same 150-frame video, Kodecz on the card (NVENC) produced 1.00 MB; on the processor (x264, CRF 18, veryfast preset), 0.75 MB.
- HyperFrames, with its own GPU option, produced 2.69 MB, against 1.62 MB with its default x264 setting.

The similarity score between these videos (SSIM) stayed above 0.996 for every pair, on a scale where 1 means identical. So the picture is the same; NVENC just spends a few more bits to get there. For a one-minute Reel that is a small difference, and the platform compresses it again anyway.

## Does NVENC have limits?

It does, and they are worth knowing before you build a production line:

1. **Sessions at once.** The card opens a limited number of encodes at the same time. If there is no free session, the Kodecz render fails with exit code 3 and waits, instead of quietly falling back to the processor.
2. **Card memory.** If video memory is full (on the Konecz server the card is shared with other services), same behavior: a clear failure and another try.
3. **NVIDIA only.** AMD and Intel cards have their own encoders, which Kodecz does not use today.

## How does Konecz use NVENC day to day?

At three points on a video's path:

1. **In the final render.** H.264 High profile, 4:2:0, no B-frames, with the index at the start of the file so it plays right away in a browser.
2. **When preparing takes.** Filmed or generated clips are sped up along with the voice and re-encoded on the card (NVENC at constant quality 19). If the card cannot read the format, it falls back to x264 at CRF 18 with a warning.
3. **For repeated frames.** When a frame equals the previous one, the engine does not even call NVENC: it writes a mark of about 40 bytes into the video. On closing, it waits for the NVENC queue to drain and passes on any error from it.

## Frequently asked questions

**Is NVENC worse than x264?**
At the same picture quality, NVENC tends to produce a slightly bigger file. In exchange, it barely touches the processor. For social video, the trade is worth it.

**Can I use NVENC with Remotion?**
Yes. Remotion has NVENC output. In our test, switching on its `<Video>` with direct MP4 and NVENC cut 65% of the CPU on one stretch, with no new code.

**Is HEVC through NVENC worth it?**
The file is smaller (0.91 MB against 1.03 MB in one test), but HEVC does not play in every browser. At Konecz, only on request.

**Do I need an expensive card?**
You need an NVIDIA card with NVENC and driver 570 or newer. Our measurements come from an RTX 5090; other cards will give other numbers.

Want to see what this path produces? The [portfolio](/en/portfolio) has the videos Konecz has made, and the [remotion-gpu](/en/blog/remotion-gpu) post shows how to bring the same gain to a Remotion project.
