# Storage Adapter for BunnyCDN

**URL:** <https://forum.ghost.org/t/storage-adapter-for-bunnycdn/43307>\
**Category:** Using Ghost\
**Created:** [December 11, 2023, 9:09pm UTC](https://forum.ghost.org/t/storage-adapter-for-bunnycdn/43307 "2023-12-11T21:09:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jannis](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jannis/32/39718_2.png) [@jannis](https://forum.ghost.org/u/jannis)\
**Post date:** [December 11, 2023, 9:09pm UTC](https://forum.ghost.org/t/storage-adapter-for-bunnycdn/43307/1 "2023-12-11T21:09:08Z")

</div>

In the last few weeks, I experimented quite a bit with BunnyCDN and Ghost. My goal was to make Ghost sites hosted on a server in Germany available _quickly_ worldwide. Naturally, the further a user was from my server, the longer it took for the website to load.

My first approach was setting up the “classic” BunnyCDN. For an individual website this works great, in my opinion. I posted my findings here:

> [@Ghost with custom CDN is possible?](https://forum.ghost.org/t/ghost-with-custom-cdn-is-possible/30996/18):
>
> Just wanted to jump in here to update on this. I have followed @skyeto’s blog post to set up BunnyCDN with a Ghost site and the actual caching worked out of the box. What didn’t work was accessing the /ghost route to edit the site and logging in to the portal as a member. My assumption is that BunnyCDN has changed since June 2021/2022, so here’s what ended up working for me, in case anyone stumbles upon this thread in the future (just adding differences to the original post): Edge Rules To s…

However, my goal was to make the speed-benefit replicable without having to set up DNS zones etc. – specifically for some of my customers’ websites.

So…I wanted to try an approach with a BunnyCDN storage adapter for Ghost. A day later, here we are:

> **[GitHub - betschki/ghost-bunny-cdn-storage: BunnyCDNAdapter is a custom storage adapter for...](https://github.com/betschki/ghost-bunny-cdn-storage/)**
>
> BunnyCDNAdapter is a custom storage adapter for Ghost CMS, enabling you to store your media files using BunnyCDN's storage solutions.

Feedback, comments, and suggestions are welcome, of course 😊

---

<div class="post-metadata">

**Author:** ![graydon](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/graydon/32/11864_2.png) [@graydon](https://forum.ghost.org/u/graydon)\
**Post date:** [February 29, 2024, 2:39pm UTC](https://forum.ghost.org/t/storage-adapter-for-bunnycdn/43307/2 "2024-02-29T14:39:48Z")

</div>

Good morning, is the Ghost’s native image resizing still working with this BunnyCDN adapter?

---

<div class="post-metadata">

**Author:** ![jannis](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jannis/32/39718_2.png) [@jannis](https://forum.ghost.org/u/jannis)\
**Post date:** [March 27, 2024, 3:46am UTC](https://forum.ghost.org/t/storage-adapter-for-bunnycdn/43307/3 "2024-03-27T03:46:37Z")

</div>

Hey Graydon!

Sorry, missed this notification.

The image resizing doesn’t work with this adapter, no. Generally, there is a big conflict between the way Ghost handles the image resizing and storage adapters. For Magic Pages I ended up using a different approach with an S3 adapter and ran into the exact problem yesterday. Wrote a little bit about it here: [Transform image CDN to full-site CDN](https://magicpages.co/roadmap/transform-image-cdn-to-full-site-cdn/)

Long story short: the uploading to storage wouldn’t be much of a problem. Generating the `srcset` will be – because Ghost only does that when the images are served locally. I haven’t figured out a good way to “simulate” that with a storage adapter.

---

<div class="post-metadata">

**Author:** ![emma.brownt19](https://avatars.discourse-cdn.com/v4/letter/e/76d3ee/32.png) [@emma.brownt19](https://forum.ghost.org/u/emma.brownt19)\
**Post date:** [September 27, 2026, 11:04am UTC](https://forum.ghost.org/t/storage-adapter-for-bunnycdn/43307/4 "2026-09-27T11:04:58Z")

</div>

The tricky part seems to be less about where the images are stored and more about how Ghost handles responsive image sizes. Moving uploads to BunnyCDN storage works for serving the original files, but Ghost’s native resizing relies on images being served locally, so generating the usual `srcset` URLs becomes the main issue.

A possible workaround would be to keep the originals in external storage and handle resizing separately, with the CDN caching the generated versions. That would require some control over the image URLs in the theme, though, rather than relying entirely on Ghost’s built-in image handling.

---

<div class="post-metadata">

**Author:** ![muratcorlu](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/muratcorlu/32/38509_2.png) [@muratcorlu](https://forum.ghost.org/u/muratcorlu)\
**Post date:** [October 1, 2026, 7:43am UTC](https://forum.ghost.org/t/storage-adapter-for-bunnycdn/43307/5 "2026-10-01T07:43:51Z")

</div>

> [@emma.brownt19](#):
>
> A possible workaround would be to keep the originals in external storage and handle resizing separately, with the CDN caching the generated versions. That would require some control over the image URLs in the theme, though, rather than relying entirely on Ghost’s built-in image handling.

Ghost has a “urls.image” config parameter that allows you to use an external URL with the same dynamic image URLs of Ghost. So, you can upload your images to an external storage, and by handling on-the-fly image resizes by yourself, you can still use the advantage of the `img_url` helper. For more information: [Configuration - Ghost Developer Docs](https://docs.ghost.org/config#ghost%E2%80%99s-built-in-s3-compatible-storage-adapter)

This is how we at Synaps Media and Ghost(Pro) serve images over an external domain while still having auto-resized images.
