---
metadata:
  - name: generator
    content: Diplodoc Platform v5.56.0
alternate:
  - https://yandex.com/dev/rtb/doc/en/ssp/ads-formats.md
  - https://yandex.com/dev/rtb/doc/ru/ssp/ads-formats.md
  - href: https://yandex.com/dev/rtb/doc/en/ssp/ads-formats.md
    type: text/markdown
    title: Markdown version
  - href: https://yandex.com/dev/rtb/doc/en/llms.txt
    type: text/markdown
    title: llms.txt
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com/dev/rtb/doc/en/llms.txt

# Main ad formats

SSP requests support three main ad formats: banners, native ads, and video ads. The format is passed in the `imp` object of a `BidRequest`. For auctions to run properly, each request should contain only one `imp` object.


#|
|| **Ad format** | **Description** | **Object** | **Supported standards** ||
|| [Banner (Display)](https://yandex.com/dev/rtb/doc/en/ssp/banner-ads.md) | Banner ads: Most popular ad format, which can include static images, GIFs, or interactive HTML5 creatives. | `imp.banner` | MRAID versions 2.0 and 3.0 ||
|| [Native](https://yandex.com/dev/rtb/doc/en/ssp/native-ads.md) | Native ads: Rather than asking for a pre-made banner, the SSP requests individual assets (such as images, text, and buttons). The app or site then uses these assets to render an ad that looks like organic content. | `imp.native` | OpenRTB Native Ads 1.2 ||
|| [Video/CTV](https://yandex.com/dev/rtb/doc/en/ssp/video-ads.md) | Video ads and Connected TV: Video formats built around the VAST standard (an XML script for playing video). | `imp.video` | Video ads are served according to VAST 3.0 by default. This ad format supports EndCard, including MRAID v2.0 and v3.0. ||
|#