> For the complete documentation index, see [llms.txt](https://knowledgebase.fabricdata.com/origin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.fabricdata.com/origin/video-players.md).

# Video Players

## Mobile Native <a href="#id-9nhqj" id="id-9nhqj"></a>

Fabric Origin recommends Adaptive Streaming using the native player on mobile platforms when possible. This provides the fastest startups and overall best user experience especially on mobile devices that could have frequent bandwidth changes over a short period of time. [Read more about Adaptive Streaming Here](https://en.wikipedia.org/wiki/Adaptive_bitrate_streaming)[.](https://en.wikipedia.org/wiki/Adaptive_bitrate_streaming)

## Mobile and Desktop Web Browsers <a href="#phvc7" id="phvc7"></a>

Virtually all modern web browsers now support Adaptive Streaming natively or with some javascript support using W3C's [Media Source Extensions](https://en.wikipedia.org/wiki/Media_Source_Extensions)[.](https://developer.iva-api.com/docs/v2/players#)

Media Source Extensions can be used with Dash and HLS Adaptive streaming and many HTML5 Players support both options. IVA Recommends using HLS Adaptive Streaming to support both mobile and desktop web browsers with the same code base. The current browser compatibility for Media Source Extensions [here](http://caniuse.com/#search=MediaSource) shows that virtually all modern browsers support Media Source Extensions with the exception of IOS Safari which supports HLS natively. Hence, one video format (HLS) can be played everywhere.

There are some limitations on older devices with HLS playback. In our tests, limiting the bitrate and size of the adaptive streams to no more than 2.5 Mbps video and audio streams enables older devices with Media Source Extensions to have a quality user experience with the benefits of adaptable bitrates.

`curl -X GET --header 'Accept: application/json' 'https://ee.iva-api.com/Videos/GetVideo/1234?MaxRate=adap_2500000&Format=hls&Expires=2018-1-1'`

**VideoJS Player - HLS Video**

<figure><img src="https://content.internetvideoarchive.com/content/hdphotos/10734/010734/010734_1280x720_305735_154.jpg" alt=""><figcaption></figcaption></figure>

```
<video id="example-video" 
 class="video-js vjs-default-skin vjs-16-9 vjs-big-play-centered" 
 controls 
 preload="auto" 
 poster="https://content.internetvideoarchive.com/content/hdphotos/10789/010789/010789_640x360_214986_40755.jpg" 
 playsinline> 
 <source src="https://video.internetvideoarchive.net/video.mp4?cmd=6&fmt=11&cust...." type="video/mp4"> 
</video> 
<track kind='captions' src='https://ee.iva-api.com/Rev/5/Attachments/WebVTT/content?subscription-Key=.....' srclang='en' lable='English' default /> 
<link href="css/video-js.css" rel="stylesheet" /> 
<script src="js/video.js"></script> 
<script src="js/videojs-contrib-hls.js"></script> 
<script> 
 var player = videojs('example-video'); 
</script>
```

&#x20;\
&#x20;<br>


---

# 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 dynamically by asking a question.

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

```
GET https://knowledgebase.fabricdata.com/origin/video-players.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.