How does regular repo size and LFS size play together in bitbucket cloud?

[Eisenfresser]

Hi everybody,

how does regular repo size and LFS size play together in bitbucket cloud?

The actual size of the repo should not exceed 1GB.

(https://confluence.atlassian.com/bitbucket/what-kind-of-limits-do-you-have-on-repository-file-upload-size-273877699.html)

However, there is the LFS (1GB for a free user), where you can pay for additional 100GB+ of space reserved for "big files". 

So from my understanding, if i pay for 100 GB LFS space and my regular repo size, say a unity project with comparably small files (scripts, meta files, settings...) will exceed the 1GB limit, i will still get trouble for using too much space. 

Or will my overall repo size be able to grow up to the combined size of the storage i got (the regular 1GB for code/small files and whatever i got in LFS)?

// i already hinted it, i inquire because i want to set up a unity project in bitbucket cloud, and it got advertised for here: 

https://bitbucket.org/product/game-development-software

[jredmond]

Files uploaded to LFS only count against your LFS usage; they don't count against the repo size limit. Conversely, files uploaded to regular repo storage (that is, files that you didn't add to LFS) only count against the repo size limit; they don't count against LFS usage. The two storage pools are distinct from one another, and an overflow on one won't affect the other (for better or worse).