# Use WebTorrent to load media objects

**URL:** <https://meta.discourse.org/t/use-webtorrent-to-load-media-objects/155873>\
**Category:** Feature\
**Created:** [25 juni 2020 om 02:20 UTC](https://meta.discourse.org/t/use-webtorrent-to-load-media-objects/155873 "2020-06-25T02:20:52Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![marianord](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/marianord/32/90502_2.png) [@marianord](https://meta.discourse.org/u/marianord)\
**Post date:** [25 juni 2020 om 04:05 UTC](https://meta.discourse.org/t/use-webtorrent-to-load-media-objects/155873/3 "2020-06-25T04:05:26Z")

</div>

Literally just waited for @Falco to answer (😅) as he has done a great job getting S3 to Discourse standards.

I would go to a cheaper S3 Clone option. Digital Ocean spaces would be the defacto go to after S3 if you have **a lot** of data, maybe going with bigger storage focues players like BlackBlaze or Wasabi to reduce pricing even more.

Doing this will remove most of the bandwidth cost as are rated a lot cheaper (Wasabi doesn’t charge for it).

Also, just for increased performance I would add a CDN, I just went in the search for a cheap CDN as my community is barely profitable via AdSense and I found [BunnyCDN](https://bunnycdn.com/) is not the fastest but it gets the job done and is quick to get it working.

> [BunnyCDN Referal link](https://bunnycdn.com/?ref=n6mz7mf3do) 🙈

With this setup you’d reduce the billing a lot. Either just putting the CDN in front of AWS S3 or using another S3 provider + CDN.

---

_[View the full topic](https://meta.discourse.org/t/use-webtorrent-to-load-media-objects/155873)._
