> For the complete documentation index, see [llms.txt](https://knowlg.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowlg.sunbird.org/learn/product-and-developer-guide/player.md).

# Player

Players are embeddable tools which help in rendering the assets. For ex., a video player plays all video content. Below are the players provided by Sunbird Knowlg building block:

<table><thead><tr><th width="171.13336635502452">Content Format</th><th width="261">MIME Type</th><th width="150">Player</th><th>Player v2</th></tr></thead><tbody><tr><td>ECML</td><td>application/vnd.ekstep.ecml-archive</td><td><a href="/learn/product-and-developer-guide/player/v1/players/ecml-player-v1.md">Yes</a></td><td>No</td></tr><tr><td>HTML, H5P</td><td>application/vnd.ekstep.html-archive, application/vnd.ekstep.h5p-archive</td><td><a href="/learn/product-and-developer-guide/player/v1/players/html-h5p-player-v1.md">Yes</a></td><td>No</td></tr><tr><td>PDF</td><td>application/pdf</td><td><a href="/learn/product-and-developer-guide/player/v1/players/pdf-player-v1.md">Yes</a></td><td><a href="/learn/product-and-developer-guide/player/v2/pdf-player.md">Yes</a></td></tr><tr><td>Epub</td><td>application/epub</td><td><a href="/learn/product-and-developer-guide/player/v1/players/epub-player-v1.md">Yes</a></td><td><a href="/use/installation-guide/players/v2/epub-player.md">Yes</a></td></tr><tr><td>WEBM, MP4</td><td>video/Webm, video/mp4</td><td><a href="/learn/product-and-developer-guide/player/v1/players/video-player-v1.md">Yes</a></td><td><a href="/learn/product-and-developer-guide/player/v2/video-player.md">Yes</a></td></tr><tr><td>YOUTUBE</td><td>video/x-youtube, </td><td><a href="/learn/product-and-developer-guide/player/v1/players/video-player-v1.md#youtube">Yes</a></td><td>No</td></tr></tbody></table>

### MIME Type

MIME Types defines the what type of the content it is. According to the mimeType you can load the specific [content launcher](/learn/product-and-developer-guide/player/v1/architecture.md#content-launchers) and play the different types of contents

### Online

Players are capable to rendering the assets online in web browser, mobile app and desktop app using the streaming url

#### Streaming url

Streaming URL is a used to stream the asset online. This streaming Url can be present in content metadata. If the streaming Url is present in metadata, the assets can be play online.

Sample streaming URL

```
metadata: {
    "streamingUrl":"https://sunbirddevmedia-inct.streaming.media.azure.net/9e45c4d8-37bf-430f-a467-388b37075d25/webm1-copy-17.ism/manifest(format=m3u8-aapl-v3)"
}
```

### Offline

Assets can be rendered offline in the player. Only html/h5p player v1 won't support the offline play.&#x20;

Please refer developer doc for [offline telemetry sync](/learn/product-and-developer-guide/player/telemetry-events/offline-telemetry.md) support


---

# 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://knowlg.sunbird.org/learn/product-and-developer-guide/player.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.
