# Media Tags

## What Tags Are for

To work properly, the resolution algorithms need each uploaded media to be marked with special tags. For video and images, the tags are different. They help algorithms to identify what should be in the photo or video and analyze the content.

## Tags for Video Files

The following tag types should be specified in the system for video files.

* To identify the data type of the video:
  * `video_selfie`
* To identify the orientation of the video:
  * `orientation_portrait` – portrait orientation;
  * `orientation_landscape` – landscape orientation.
* To identify the action on the video:
  * `video_selfie_left` – head turn to the left;
  * `video_selfie_right` – head turn to the right;
  * `video_selfie_down` – head tilt downwards;
  * `video_selfie_high` – head raise up;
  * `video_selfie_smile` – smile;
  * `video_selfie_eyes` – blink;
  * `video_selfie_scan` – scanning;
  * `video_selfie_blank` – no action;
  * `video_selfie_oneshot` – a one-frame analysis.

<mark style="background-color:red;">On January 1, 2027, the One Shot gesture will become unavailable. Please plan your</mark> [<mark style="background-color:red;">migration</mark>](/oz-knowledge/guides/developer-guide/migration-guides/migration-from-one-shot-gesture.md)<mark style="background-color:red;">.</mark>

The tags listed allow the algorithms recognizing the files as suitable for the [Quality](/oz-knowledge/guides/developer-guide/api/oz-api/types-of-analyses-and-what-they-check.md#quality-liveness-best-shot) (Liveness) and [Biometry](/oz-knowledge/guides/developer-guide/api/oz-api/types-of-analyses-and-what-they-check.md#biometry) analyses.&#x20;

Important: in API 4.0.8 and below, to launch the Quality analysis for a photo, pack the image into a .zip archive, apply the `SHOTS_SET` type, and mark it with `video_*.` Otherwise, it will be ignored by algorithms.

Example of the correct tag set for a video file with the “blink” action:

```javascript
"video1": [
  "video_selfie",
  "video_selfie_eyes",
  "orientation_portrait"
]
```

## Tags for Photo Files

The following tag types should be specified in the system for photo files:

* A tag for selfies:
  * `photo_selfie` – to identify the image type as “selfie”.
* Tags for photos/scans of ID cards:
  * `photo_id` – to identify the image type as “ID”;
  * `photo_id_front` – for the photo of the ID front side;
  * `photo_id_back` – for the photo of the ID back side (ignored for any other analyses like [Quality](/oz-knowledge/guides/developer-guide/api/oz-api/types-of-analyses-and-what-they-check.md#quality-liveness-best-shot) or [Biometry](/oz-knowledge/guides/developer-guide/api/oz-api/types-of-analyses-and-what-they-check.md#biometry)).

Important: in API 4.0.8 and below, to launch the Quality analysis for a photo, pack the image into a .zip archive, apply the `SHOTS_SET` type, and mark it with `video_*.` Otherwise, it will be ignored by algorithms.

Example of the correct tag set for a “selfie” photo file:

```javascript
"photo1": [
  "photo_selfie"
]
```

Example of the correct tag set for a photo file with the face side of an ID card:

```javascript
"photo1": [
  "photo_id",
  "photo_id_front"
]
```

Example of the correct set of tags for a photo file of the back of an ID card:

```javascript
"photo1": [
  "photo_id",
  "photo_id_back"
]
```


---

# 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://doc.ozforensics.com/oz-knowledge/guides/developer-guide/api/oz-api/media-tags.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.