<commit_before>---
title: Efficient Formats
description: |
  Improve the visual quality of your streams by encoding videos using more
  efficient formats while targeting different platforms.
date: April 2nd, 2021
length: '1:04'
video-sources:
  - src: https://storage.googleapis.com/kino-assets/efficient-formats/manifest.mpd
    type: application/dash+xml
  - src: https://storage.googleapis.com/kino-assets/efficient-formats/master.m3u8
    type: application/x-mpegURL
video-subtitles:
  - default: true
    kind: captions
    label: English
    src: https://storage.googleapis.com/kino-assets/efficient-formats/cap-en.vtt
    srclang: en
  - default: false
    kind: captions
    label: Česky
    src: https://storage.googleapis.com/kino-assets/efficient-formats/cap-cz.vtt
    srclang: cz
thumbnail: https://storage.googleapis.com/kino-assets/efficient-formats/thumbnail.png
---

## Introduction

Now that you've learned which format to use to encode once for both DASH
and HLS, let's talk about use cases that call for a different approach.

## Better compression

Sometimes you have the time and disk space to encode your media in multiple
formats. We previously learned about encoding [multiple sources] which can
lead to greatly reduced files sizes compared to the standard `H.264` codec,
with our example source video being reduced to around 50% of its original
file size.

Consider a video on demand platform like YouTube. The main bottleneck for
YouTube is... you, or rather the **available bandwidth** between YouTube
servers and your device. YouTube rescales your video and aims to stay under
certain bitrate thresholds for every resolution. It also uses `VP9` as an
efficient coding format of choice along with `H.264`.

This helps YouTube to deliver **smaller video chunks** to clients that
support the more efficient coding formats.

## Targeting different clients

Browsers sometimes support **different coding formats**. If you want to
distribute your stream in an efficient coding format, you're left with two
options:

1. Progressive enhancement.
2. Encoding in multiple formats.

YouTube chose the free `VP9` codec to **progressively enhance** the
experience in clients that implement it. The 4k resolution videos were only
available in`VP9`. Safari previously did not support the `VP9` codec, which 
led to Safari users being unable to play 4k videos on YouTube but still able
to play 1080p.

Another options would be to encode your media in several efficient coding
formats. Safari supports `H.265`, which means that encoding for `VP9` *and*<commit_msg>Fix missing space<commit_after>---
title: Efficient Formats
description: |
  Improve the visual quality of your streams by encoding videos using more
  efficient formats while targeting different platforms.
date: April 2nd, 2021
length: '1:04'
video-sources:
  - src: https://storage.googleapis.com/kino-assets/efficient-formats/manifest.mpd
    type: application/dash+xml
  - src: https://storage.googleapis.com/kino-assets/efficient-formats/master.m3u8
    type: application/x-mpegURL
video-subtitles:
  - default: true
    kind: captions
    label: English
    src: https://storage.googleapis.com/kino-assets/efficient-formats/cap-en.vtt
    srclang: en
  - default: false
    kind: captions
    label: Česky
    src: https://storage.googleapis.com/kino-assets/efficient-formats/cap-cz.vtt
    srclang: cz
thumbnail: https://storage.googleapis.com/kino-assets/efficient-formats/thumbnail.png
---

## Introduction

Now that you've learned which format to use to encode once for both DASH
and HLS, let's talk about use cases that call for a different approach.

## Better compression

Sometimes you have the time and disk space to encode your media in multiple
formats. We previously learned about encoding [multiple sources] which can
lead to greatly reduced files sizes compared to the standard `H.264` codec,
with our example source video being reduced to around 50% of its original
file size.

Consider a video on demand platform like YouTube. The main bottleneck for
YouTube is... you, or rather the **available bandwidth** between YouTube
servers and your device. YouTube rescales your video and aims to stay under
certain bitrate thresholds for every resolution. It also uses `VP9` as an
efficient coding format of choice along with `H.264`.

This helps YouTube to deliver **smaller video chunks** to clients that
support the more efficient coding formats.

## Targeting different clients

Browsers sometimes support **different coding formats**. If you want to
distribute your stream in an efficient coding format, you're left with two
options:

1. Progressive enhancement.
2. Encoding in multiple formats.

YouTube chose the free `VP9` codec to **progressively enhance** the
experience in clients that implement it. The 4k resolution videos were only
available in `VP9`. Safari previously did not support the `VP9` codec, which
led to Safari users being unable to play 4k videos on YouTube but still able
to play 1080p.

Another options would be to encode your media in several efficient coding
formats. Safari supports `H.265`, which means that encoding for `VP9` *and*
{'fraction_non_alphanumeric': 0.06943366951124903, 'fraction_numerical': 0.013188518231186967, 'mean_word_length': 4.300102774922919, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 10, 'lorem ipsum': 0, 'www.': 0, 'xml': 2}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5095863', 'n_tokens_mistral': 1446, 'n_tokens_neox': 1347, 'n_words': 646}