Imagine I have a web site based on Hugo with gigabytes worth of static content, i. e. PDF and image files which never change (each file is added once, never removed, and never changed). The source code of the site is located on BitBucket and the site is hosted on Netlify.
Let’s imagine two scenarios:
Scenario 1: All static content (those gigabytes of data that never change) is saved in LFS.
Scenario 2: LFS is not used at all.
What are the advantages of scenario 1 (using LFS for big files that don’t change) versus scenario 2 (not using LFS)?
Transformations when you need them – With our image transformation service, you can serve the exact image size you need for each context, from thumbnail to retina, without having to save multiple versions or run repetitive resizing operations in your build.
And Hugo already has amazing in-built image processing. So, chances are, you won’t need Netlify LFS ever. The one time you might need it is when your repo size goes beyond the permitted repo size on Bitbucket, for example, on GitHub, the limit is 2 GB, I suppose.