---
updatedAt: 2026-11-13T17:33:53.000Z
agentTools:
  projectIndex: https://docs.wistia.com/llms.txt
---

# Asset URLs

Working with direct file URLs for Wistia-hosted content

Sometimes a particular implementation calls for the use of a file URL, what we call a *Direct Asset URL* in Wistia. This is the raw video or image file ending in the relevant file extension like `.mp4` or `.png`. Below are some techniques for obtaining these asset URLs with a few tips & tricks for using them.

<Callout icon="📝" theme="default">
  ### Note

  The Wistia APIs were specifically built for videos in folders. We do not formally support using our APIs for audio files in folders, or audio or video episodes in Channels at this time. For the most reliable experience, we recommend continuing to use these for videos in folders.
</Callout>

<br />

An 'asset' refers to the any of the video or image files attached to media. Video files for streaming, thumbnail images, and storyboard images are all considered 'assets'.

## Common questions

Quick answers to the questions we hear most about Direct Asset URLs. Each links to the full detail below.

* **How do I get a Direct Asset URL for my video?** Request the [Media Show](https://docs.wistia.com/reference/get_medias-media-hashed-id-json) method in the Data API and read the `assets` array, or use the [`videolinkfor` tool](https://wistia.com/tools/video_link_for) for a quick 1280 × 720 `.mp4` link. See [Getting an Asset URL](#getting-an-asset-url).
* **The URL ends in&#x20;**`.bin`**&#x20;— how do I make it end in&#x20;**`.mp4`**&#x20;(or another extension)?** Drop the `.bin`, add a slash, and append any filename and extension you want (for example `.../my-file.mp4`). You still get the same underlying file. See [Asset URL File Extensions](#asset-url-file-extensions).
* **How do I get an HLS (**`.m3u8`**) URL?** Start from an `.mp4` asset URL and change the extension to `.m3u8`. See [Getting HLS assets](#getting-hls-assets).
* **How do I make an asset URL download instead of play in the browser?** Append `?disposition=attachment` to the URL. See [Enabling Downloads from Asset URLs](#enabling-downloads-from-asset-urls).
* **My bandwidth is high but my play count is low — why?** Traffic to asset URLs uses [bandwidth](https://wistia.com/support/account-and-billing/bandwidth) but records no plays or engagement, so it shows up as bandwidth your media stats can't explain. See [Bandwidth and Analytics Tradeoffs](#bandwidth-and-analytics-tradeoffs).
* **Should I use Direct Asset URLs at all?** Usually not. To keep analytics, embed the Wistia player; to pull stats programmatically, use the [Stats API](https://docs.wistia.com/reference/getting-started-with-the-stats-api). See [Safer alternatives](#safer-alternatives).

## Bandwidth and Analytics Tradeoffs

A Direct Asset URL serves the raw file outside the Wistia player, so it behaves very differently from a normal embed for both billing and analytics. Understand these tradeoffs before you build a workflow around asset URLs.

Requests to an asset URL never reach the Wistia player, so they produce no plays, no engagement graphs, and no viewer data. That activity is invisible in your media stats. It still consumes bandwidth, and that bandwidth counts toward your account's [bandwidth](https://wistia.com/support/account-and-billing/bandwidth) usage just like a normal play. Using asset URLs can raise usage significantly and incur additional costs.

Because bandwidth is counted but plays are not, direct asset distribution shows up as bandwidth with no player analytics to explain it. This is a common reason a Wistia account's bandwidth doesn't line up with its play counts.

### Signs direct asset URLs are driving your bandwidth

If your bandwidth usage looks high relative to the plays reported in your media stats, direct asset distribution is a likely cause. Check for these signals:

* Bandwidth in the [billing dashboard](https://wistia.com/support/account-and-billing/bandwidth) is higher than your play volume would suggest.
* A media's file URL (an `embed-ssl.wistia.com/deliveries/...` link) has been pasted into a website, email, RSS feed, podcast host, or app.
* Downloads are enabled on an asset URL with `?disposition=attachment`.
* A large `OriginalFile` asset is being linked instead of a streaming-optimized asset.

Confirming which asset is responsible usually requires a CDN-log investigation by Support, so it's fastest to first rule out the causes above.

### Safer alternatives

* To keep analytics, use a standard Wistia embed instead of a raw file URL. That's the only way to record plays and engagement.
* To pull stats programmatically, use the [Stats API](https://docs.wistia.com/reference/getting-started-with-the-stats-api) rather than asset URLs. It returns play and engagement data without touching the file.
* If you must distribute the file, prefer a streaming-optimized asset over the `OriginalFile` to limit bandwidth per request, and only enable downloads where you accept the untracked bandwidth cost.
* Because direct asset traffic won't appear in media stats, monitor the [bandwidth dashboard](https://wistia.com/support/account-and-billing/bandwidth) directly to catch a spike early.

<Callout icon="📘" theme="info">
  ### Alert

  We generally do not recommend using Asset URLs, as accessing a Wistia-hosted video file _outside_ of the video player means you won't get any video stats, analytics, customizations, [HLS playback delivery](https://wistia.com/support/uploading/export-settings#adaptive-streaming), or other features specific to the Wistia player. This activity _does_ count towards your account's [bandwidth](https://wistia.com/support/account-and-billing/bandwidth) usage however. If you do start using Asset URLs, be aware that bandwidth usage may increase significantly, which can incur additional usage costs for your account.
</Callout>

## Getting an Asset URL

Asset URLs are obtained through the [Wistia Data API](https://docs.wistia.com/docs/wistia-data-api), specifically the [`Media Show` method](https://docs.wistia.com/reference/get_medias-media-hashed-id-json). This request requires [an API token](https://docs.wistia.com/docs/making-api-requests#getting-started) which can be obtained by or from the Account Owner.

The response to a `medias:show` request includes an array of `assets`, with their direct URLs and information on each asset's size and type. The `OriginalFile` asset is the source media that was uploaded to Wistia, and all other assets are the streaming-optimized files delivered by the Wistia player during playback.

<Callout icon="📝" theme="default">
  ### Note

  The `OriginalFile` is used as a blueprint for encoding a set of streaming assets, and is never used for video streaming/playback in the Wistia player. Originals are typically much larger in size compared to our streaming-optimized assets, which means higher bandwidth usage when viewed or downloaded. Unless you're looking for a backup of your original, we generally recommend against using the `OriginalFile` for embedding or downloading, as doing so can lead to high usage costs.
</Callout>

Alternatively, you can use <Anchor target="_blank" href="https://wistia.com/tools/video_link_for">this handy 'videolinkfor' tool</Anchor>. This makes it a little easier to get an asset URL without directly using our API, and it will give you a link for the 1280 x 720p asset URL, in `.mp4` format.

## Asset URL File Extensions

Asset URLs in Wistia take this form:

```
https://embed-ssl.wistia.com/deliveries/856970d9a4bcb9aab381a0bd9ab714f19d72c62f.bin
```

The `.bin` extension at the URL is for *binary*. Certain clients won't accept URLs with an unfamiliar extension like this one. In this case, you can drop the `.bin`, add a slash, and append whatever filename and extension you like -– you'll still get the underlying video asset.

So, say the URL above is an mp4 file and we need the URL to end in the proper file extension. Here's how we would change it:

```
https://embed-ssl.wistia.com/deliveries/856970d9a4bcb9aab381a0bd9ab714f19d72c62f/my-file.mp4
```

## Getting HLS assets

Wistia uses HLS playback by default - if you would like to retrieve HLS assets for your videos in m3u8 format, you’ll first want to grab an mp4 asset URL from your video using the Data API technique mentioned above. All m3u8 files in Wistia are generated dynamically from the mp4 files for that same media.

With an mp4 asset URL for your media, you can change the extension from `.bin`  to `.m3u8`, which will return an HLS manifest file for that particular mp4.

<Callout icon="📝" theme="default">
  ### Note

  The contents of the .m3u8 playlist does not include captions data. If you use the "main" .m3u8 playlist, the information will include captions data.

  That format of that main playlist is as follows:<br />[https://fast.wistia.com/embed/medias/HashedID.m3u8](https://fast.wistia.com/embed/medias/HashedID.m3u8)
</Callout>

## Enabling Downloads from Asset URLs

<Callout icon="🚫" theme="default">
  ### Alert

  Reminder that asset URL viewing and downloads will contribute to bandwidth usage in your account. Enabling downloads from direct assets creates the risk of a spike in bandwidth, and thereby increased bandwidth costs, but without any video stats to represent it.
</Callout>

If you are looking to allow downloads from asset URLs in your site or application, you can add the `disposition=attachment` parameter to the end of the URL, e.g.

```
https://embed-ssl.wistia.com/deliveries/061aacab996e0da67c3dd65883025aa3efa6043d.bin?disposition=attachment
```

This will automatically download the file instead of trying to play it natively in the browser.

## HTTP vs HTTPS Asset URLs

If you have an asset that's served over HTTP and you'd like to get it served over HTTPS instead, you'll need to change the subdomain from `embed` to `embed-ssl`. We  use different subdomains for SSL and non-SSL assets because they're sometimes served through different CDNs for performance reasons.

## Thumbnails & Image Assets

Using the Data API or [oEmbed endpoint](https://docs.wistia.com/docs/wistia-and-oembed), you can obtain the thumbnail URL for your video, and then manipulate it. You can request images from a specific time in your video, resize them, even crop them!

For more details, [We have a dedicated guide all about working with images!](https://docs.wistia.com/docs/working-with-images)