> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-ads-demand/ad-formats/html-ads.md).

# HTML Ads

DT Exchange HTML Ads include all display ads, such as banners, MRECs, and interstitial ads. The following sections outline the specifications for different HTML ad categories.

## Small Square Ads

| DIMENSIONS                              | CREATIVE FILE TYPE | MIME TYPES | MARKUP NOTES                                           |
| --------------------------------------- | ------------------ | ---------- | ------------------------------------------------------ |
| 300x250, 300x50[^1], 320x50, 320x10[^1] | PNG                | HTML       | Snippets of JS or HTML code only (not full documents). |

## Horizontal and Banner Ads

| DIMENSIONS                  | CREATIVE FILE TYPE | MIME TYPES | MARKUP NOTES                                                                    |
| --------------------------- | ------------------ | ---------- | ------------------------------------------------------------------------------- |
| 468x60[^1], 728x90, 480x320 | JPG/JPEG           | HTML5      | <p>Ad markup should be <code>CGI escaped</code>.<br>It should not be a URL.</p> |

## Tracking Click Events on Image Ads

The click tracking URL fires the JS click event when the user taps on the ad container (`webView`).

[^1]: This size can be passed in an array of multiple ad sizes via `banner-format` in the bid request. To view a sample bid request, see [Sample Bid Requests](https://docs.digitalturbine.com/dt-ads-demand/dt-exchange-openrtb-2.5-specs/sample-bid-requests.md). To enable these sizes for your bidder, contact your demand account manager.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digitalturbine.com/dt-ads-demand/ad-formats/html-ads.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
