Does Git LFS storage count toward the 1 GB workspace limit, and can LFS garbage collection be run?

[AnToine van Maarle]

We are on a Free plan workspace and recently started seeing this warning on push:

WARNING This workspace is getting close to the 1 GB size limit

Before we decide how to act on it, I would like to get two things straight, because the documentation does not answer them and the answer changes what we should do.

What we measured

Our main repository, with all refs fully repacked, is about 198 MB. Roughly 164 MB of that is a set of 186 binary files (DLLs, EXEs and installers) that ship with our desktop application.

We also have one branch that is no longer used but still carries Git LFS pointers from an earlier migration attempt. The LFS objects behind it are around 173 MB.

Adding up every repository in the workspace that we can measure locally gets us to roughly 331 MB, so we cannot account for the remaining part of the 1 GB from our side.

Questions

1. Does Git LFS storage count toward the 1 GB workspace storage limit on the Free plan?

The plan pages list a separate LFS allowance per plan, which suggests LFS is tracked separately, but neither Storage policy for Git LFS with Bitbucket nor What are the repository and file size limits? states this explicitly. We would like a definitive answer, because it decides the next question.

2. Would migrating our active branches to Git LFS actually reduce our workspace usage?

This is where we are stuck. Git stores those binaries compressed, and they compress well:

Storage	Size
Compressed in Git today	169 MB
Uncompressed originals	324 MB

As far as we understand, Git LFS stores the original file, uncompressed. So if LFS does count toward the workspace limit, moving these files to LFS would nearly double what they consume rather than reduce it.

Is that correct? We would rather not carry out a history rewrite across three release branches only to end up worse off.

3. Can you run garbage collection on the LFS storage of a repository?

We understand that deleting the branch that references the old LFS objects does not free the storage, and that Bitbucket Cloud has no self-service garbage collection for LFS. If you can run it for us, we would like to request that for the unused branch described above. Please let us know what you need from us.

4. Where can we see the storage breakdown per repository for a workspace, and does that figure include LFS?

We can see a total, but we would like to know which repository accounts for what, and whether the number shown includes LFS objects or only the Git repository itself.

Thanks in advance.