File size limitations of GitHub

I know GitHub is a popular place to store your website source code for Hugo users. However given the 1GB limit on repo sizes imposed by GitHub has anyone ran into issues with blogs that contain many large images or other assets? If so what was your solution?

I use Backblaze B2 for storing audio (mp3) files, which are served from my hugo site both directly and as a podcast.

I’ve not used, but I’ve heard positive things about:

  • Cloudinary is popular for images and video, it can also host other files.
  • Amazon S3 I use Backblaze over Amazon because, so far, I’ve kept within the limits of its free tier.
1 Like

You can try Git Large File Storage (LFS)

Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like or GitHub Enterprise.

*cough* the limit is per repository *cough*

Translation: open another repo as CDN for images if you need to host it there?

Do you use Backblaze’s Cloudflare Integration as a CDN or just link each media file manually? I’m thinking of switching to this and hosting all my images, podcasts and media on Backblaze. Seems like quite a good deal. The rest of the site on Netlify.

I didn’t know about the Cloudflare integration. I just link directly to the file in B2, and it works fine.

Thanks. For podcasts that probably works well. I think it’s more for directories with lots of images. The Cloudflare integration uses a CNAME addition so the URLs remain the same as your domain.