[jasode]

Some meta-commentary about some of the replies ... so far, there are 4+ replies suggesting the obvious step of storing in the images on the same web server host. But I notice the submitter is software engineer ex-Stripe, ex-Yelp, ex-Adobe... so I'm guessing he already knows that simple setup but doesn't locally host gifs & vids for technical reasons (bandwidth?, latency?).

Maybe recalibrate the suggestions based on the above. (Or the submitter can further clarify why hosting local image assets instead of using a CDN is not feasible in his particular case so the crowdsourced answers can be more productive to his goals.)

EDIT add: Sure, obvious technical answer may be applicable but some replies have a bit of condescension that doesn't seem appropriate and respectful of this person's tech background.

[uptown]

Sometimes the best answer is still the obvious one, regardless of the audience.

[dewey]

Seems even more appropriate to reply with the most obvious answer and not some overengineered / "will it scale" setup then.

[akshaykumar90]

OP here. All answers are good. I was looking for a lay of the land and appreciate all the options people are chipping in with.

[jasode]

>I was looking for a lay of the land

Why & how did you arrive at the decision to use Cloudinary to host images for your Savory website instead of locally hosting them yourself?

Have you looked at your Cloudinary analytics dashboard to quantify what magnitude of bandwidth you're dealing with?

Are you currently on Cloudinary's free tier plan or paid? Since you mentioned the Github image hack, are you looking for a zero cost hosting of images?

The more datapoints and constraints you provide as background, the better the advice in your replies will be.