Video Compression Basics
This section covers basic options for VP9 encoding, including frame size, basic bitrate control and quality.
If you're new to video compression you may wish to watch this video to learn more about the need for video compression, and how it works.
A Simple Encode
The following FFMpeg command converts an input file to VP9 video with Opus audio. This is the simplest possible encode which uses default settings.
ffmpeg -i tears_of_steel_1080p.webm -c:v libvpx-vp9 -c:a libopus output.webm
This FFMpeg encode uses the following command-line parameters:
||Specifies input file name|
||Tells FFMpeg to create VP9 video|
||Tells FFMpeg to create Opus audio|
||Specifies output file name|
FFMpeg infers the type of file to make from the output file name you use. In
this example, FFMpeg will output a WebM file because we asked for
Every video has a frame size (indicating the pixel width and height). The following FFMpeg command-line parameter can be used to control the output video frame size for VP9 encoding:
||Frame width and height|
For example, the following FFMpeg command will output a 640x480 VP9 WebM video.
ffmpeg -i tears_of_steel_1080p.webm -vf scale=640x480 \ -c:v libvpx-vp9 -c:a libopus output.webm
Smaller resolutions are lower quality, but larger resolutions require more bandwidth, more processing power to decode, and may not be supported on older devices. For VP9, 640x480 is considered a safe resolution for a broad range of mobile and web devices.
Bitrate (bit rate)
VP9 supports several different bitrate modes:
|Constant Quantizer (Q)||Allows you to specify a fixed quantizer value; bitrate will vary|
|Constrained Quality (CQ)||Allows you to set a maximum quality level. Quality may vary within bitrate parameters|
|Variable Bitrate (VBR)||Balances quality and bitrate over time within constraints on bitrate|
|Constant Bitrate (CBR)||Attempts to keep the bitrate fairly constant while quality varies|
CQ mode is recommended for file-based video (as opposed to live streaming). The following FFMpeg command-line parameters are used for CQ mode:
||Sets target bitrate (e.g. 500k)|
||Sets minimum and maximum bitrate.|
||Sets maximum quality level. Valid values are 0-63, lower numbers are higher quality.|
For example, the following FFMpeg command will create a medium-quality 640x480 video file using CQ mode, with an average bitrate of 750kbps and maximum quality constrained to 33.
ffmpeg -i tears_of_steel_1080p.webm -vf scale=640x480 \ -b:v 750k -crf 33 -c:v libvpx-vp9 -c:a libopus output.webm
Bitrate will vary depending upon the quality you wish to achieve, and the resolution of the video. A full set of recommendations for bitrates at various resolutions can be found here.
Quality and Speed Settings
Compressing video is a trade-off between the quality of the output, and the amount of time it takes to create it. Generally speaking, you can always get higher quality by allowing more time to encode, but the time required to get the highest possible quality may be impractical.
VP9 offers several settings to balance quality and speed:
Quality setting instructs the encoder on the approach it takes to compress video. Available modes are best, good, and realtime.
Threading settings allow the encoder to use multiple CPU threads to encode the video. These settings may slightly reduce quality, but can significantly improve encoding and decoding speed.
These two types of settings are controlled by several command-line parameters:
||Indicates the number of threads to use during encoding.|
||May be set to
||This parameter has different meanings depending upon whether quality is set to
||Tiling splits the video into rectangular regions, which allows multi-threading for encoding and decoding. The number of tiles is always a power of two.
The following FFMpeg command will create a 640x480 file with quality set to 'good' and speed set to 0 (high quality):
ffmpeg -i tears_of_steel_1080p.webm -vf scale=640x480 \ -b:v 750k -quality good -speed 0 -crf 33 -c:v libvpx-vp9 -c:a libopus \ output.webm
Your choices for quality and speed settings may vary depending upon resolution and available processing power. A full set of recommendations can be found in the next section.