SVT-AV1 at -crf 35 -preset 8 matches x264 at CRF 23 on VMAF in a file 42% smaller. ReelSDK runs that encode for $0.02 per compute minute: an 11-second clip took about 11 seconds and under half a cent.
Encode AV1 with ffmpeg
ffmpeg has two AV1 encoders worth using: libsvtav1, with presets from 0 to 13, and libaom-av1, smaller still but about 9 times slower. ReelSDK's engine ships both, so either command runs unchanged.
GuidesUpdated
ffmpeg -i input.mp4 -c:v libsvtav1 -crf 35 -preset 8 -c:a copy av1.mp4CRF 35 is the SVT-AV1 default and preset 8 a middle speed. On a vertical 1080p video it matched x264 at CRF 23 on VMAF in a file 42% smaller, in about 11 seconds.
Variations
The other commands you will need
Trade speed for size with the preset
Presets run from 0 to 13; lower is slower and smaller. Preset 4 took three times as long for a file about a quarter smaller. Preset 12 took half the time and was smaller than preset 8 too, but softer.
presets ffmpeg -i input.mp4 -c:v libsvtav1 -crf 35 -preset 4 -c:a copy av1-p4.mp4 ffmpeg -i input.mp4 -c:v libsvtav1 -crf 35 -preset 12 -c:a copy av1-p12.mp4Encode with libaom
libaom defaults to
-cpu-used 1, which is very slow; 6 is a common compromise, and-row-mt 1lets it use more threads. At CRF 30 it made the smallest file and the best score, but took over a minute and a half.libaom ffmpeg -i input.mp4 -c:v libaom-av1 -crf 30 -cpu-used 6 -row-mt 1 \ -c:a copy aom.mp4
The flags
The flags in these commands
| Flag | What it does | Used here |
|---|---|---|
-c:v libsvtav1 | Encodes AV1 with SVT-AV1 | SVT-AV1 |
-crf 35 | Quality target from 0 to 63 in SVT-AV1, 35 by default; lower is better | SVT-AV1 |
-preset 8 | SVT-AV1 speed from 0 to 13; higher is faster and lower quality | SVT-AV1 |
-c:v libaom-av1 | Encodes AV1 with libaom, the reference encoder | libaom |
-crf 30 | Quality target from 1 to 63 in libaom | libaom |
-cpu-used 6 | libaom speed from 0 to 8, default 1; higher is faster | libaom |
-row-mt 1 | Lets libaom split rows across threads | libaom |
Sources: FFmpeg AV1 encoding guide, ffmpeg codecs: libsvtav1, checked November 2026.
AV1 next to x264 and x265
All of these encoded the same 1080x1920 clip, and libvmaf scored each against it. All four landed at a VMAF of about 97, so the file size tells them apart: next to x264 at CRF 23, x265 was about a third smaller, SVT-AV1 42% smaller and libaom under half the size.
At about the same score, AV1 from SVT-AV1 was smaller than HEVC too, and took half the time of x264. libaom squeezed further, at about 9 times the SVT-AV1 time.
SVT-AV1 or libaom
Use SVT-AV1 when encode time matters, which is most of the time. Pick the preset first, since it decides the speed, then move the CRF until the result looks right. Preset 12 suits quick previews: it ran in half the time of preset 8, but scored about 2 points lower.
Use libaom when every byte counts and the encode runs once, for example a video that will be served millions of times. Raise -cpu-used before you give up on it: the default of 1 is slower still than the 6 we used.
Containers and playback
AV1 goes in MP4, WebM or MKV; these commands write MP4. Older devices and some players can't decode AV1 at all, so keep an H.264 copy where you can't control the player. To make the H.264 copy smaller, see compress a video with ffmpeg.
Without installing ffmpeg
The same command as one API call
The engine has both encoders. This SVT-AV1 job finished in about 11 seconds and cost under half a cent at $0.02 per compute minute; the libaom command above took about 88 seconds and under 3 cents. Each job runs ffmpeg 8.1 on a fresh machine.
curl "https://api.reelsdk.com/v1/ffmpeg?wait=60" \
-H "Authorization: Bearer $REELSDK_KEY" \
--json '{
"inputs": {
"input.mp4": "https://api.reelsdk.com/f/lib/demo/clip.mp4"
},
"args": [
"-i", "input.mp4", "-c:v", "libsvtav1", "-crf", "35", "-preset", "8",
"-c:a", "copy", "av1.mp4"
],
"outputs": ["av1.mp4"]
}'FAQ
Questions, answered
Which AV1 encoder should I use in ffmpeg?
libsvtav1 for most jobs: preset 8 at CRF 35 encoded our 11-second clip in about as long as it plays. libaom-av1 made a smaller file with a higher score but took 9 times as long, even at -cpu-used 6.
What CRF should I use for AV1?
Start at the SVT-AV1 default, 35. On our clip it scored level with x264 at CRF 23 on VMAF, about 97, with a 42% smaller file. Lower it for more quality.
Why is libaom so slow?
Its default -cpu-used is 1, one of its slowest settings. Raise it to 6 and add -row-mt 1; even then it took about 9 times as long as SVT-AV1 preset 8 on our clip.
Can I encode AV1 with an API?
Yes. The engine has libsvtav1 and libaom-av1: send the args to POST https://api.reelsdk.com/v1/ffmpeg. Our SVT-AV1 job finished in about 11 seconds and the libaom one in about 88, at $0.02 per compute minute, billed per second.
- Encode H.265 (HEVC) with ffmpegEncode HEVC with libx265: CRF 28 against x264 CRF 23 on one clip, the hvc1 tag Apple players need, and 10-bit output.
- Encode VP9 WebM with ffmpegMake a VP9 WebM with libvpx-vp9 and Opus: constant quality with -crf, the -b:v 0 rule, -row-mt, -cpu-used and two passes, measured.
- Choose a CRF value in ffmpegWhat CRF does in libx264, the file size and VMAF score for CRF 18, 23, 28 and 33 on one clip, and how x265's scale differs.
- Compress a video with ffmpegShrink a video with ffmpeg: CRF 28 in x264 or x265, a smaller frame or a slower preset, with the size and quality each one gets you.
- Set the video bitrate with ffmpegSet an average bitrate with -b:v, cap it with -maxrate and -bufsize, or run two passes to land on a file size, with measured results.
- Video compressionCompress a video to a size budget in one ffmpeg call: a 129 MB 1080p clip fits a 5 MB target at 4.6 MB, for under 1 cent.
Sources, checked November 2026
Ready to build?
Ship video from your app today
Your first $0.50 is free, and one key covers every endpoint.
