# Video Presets

A **`video_preset`** is a group of profiles. The adaptive streaming output, generated by profiles, improves playback experience. Based on your subscription package, one preset can contain up to 6 profiles.

<img src="https://pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net/atlassian/warning_64.png" alt=":warning:" data-size="line"> A preset should only include profiles with the same segment duration and orientation. If preset includes profiles with different segment durations (2s and 10s), the lower segment duration will be used for every profile. Different orientation will lead to different display aspect ratio when switching the profile, causing bad playback experience.

## The Video Preset Object

### Attributes

> **`id`** *string*
>
> The unique identifier for the video preset.

> **`name`** *string*
>
> The name of the video preset.

> **`description`** *string*
>
> Describes the content of the video preset. Useful to describe the profiles in the preset and talk about use cases.

> **`is_default`** *string*
>
> Defines if this preset is the default preset for encoding live entities and video entities.

> **`profiles`** *object*
>
> List of profiles in video preset. Number of profiles is defined by user's Tier (Developer - 1, Team - 3, Business - 6).&#x20;

> **`created_at`** *string*
>
> The timestamp at which the `video_preset` is created. This value follows the [ISO 8601 standard](https://www.w3.org/TR/NOTE-datetime-970915).

> **`updated_at`** *string*

> The timestamp at which the most recent update to the `video_preset` occurred. This value follows the [ISO 8601 standard](https://www.w3.org/TR/NOTE-datetime-970915).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.uiza.io/2020-03-26-1/api-reference/video-presets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.