# Use Fallback Urls with HLS and Dash

You can combine the last three best practices together to serve an H.265 HLS file, then a WebM Dash file, then a h.264 HLS, and even a fragmented MP4 for browsers that don’t support any of these (IE11 on Windows 7 or earlier).&#x20;

#### Current Elm Difficult = Very Hard

If your browser supports HLS natively, you can just do some fallback Urls, but if you have to use the HLS.js or Dash.js plugins, it means a whole bunch of complicated roundtrips through ports to figure out how to support these files.

A better strategy might be to test for HLS.js and Dash.js support and send that info through flags, but that means downloading HLS.Js and Dash.js from the servers before you need them, which isn't great.<br>


---

# 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://danabrams.gitbook.io/av-best-practices/use-fallback-urls-with-hls-and-dash.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.
