nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Repository 1G new limitation storage 2025

gbiau

Hi,

I speak about the new rules of 28 APRIL 2025:

I would like know if the limitation of repositories is the sum of all repositories that we can have for 1 account or it's just limited to one repository ?

Exemple
Repository 1 = 500 mb
Repository 2 = 600 mb
TOTAL 1G1

Would I have exceeded the limit ?

Thanks

Accepted answers

All comments

paulodetarsofm

I believe it refers to the sum of all repositories that are part of the same workspace, as it is the total of the workspace that counts, I received the email and verified that my workspace is 1.2 GB, so I am trying to create different workspaces for each repository I have (they are all in the same workspace currently).

Spidex Cloud

So, if it is distributed across workspaces, this limit doesn’t apply, correct?

For example, under one Bitbucket account (e.g., account1), there can be multiple workspaces:

ws1:

Repository 1 = 400 MB
Repository 2 = 800 MB

ws2:

Repository 3 = 400 MB
Repository 4 = 500 MB

In this case:

Q1: Is ws1 violating the free account rules?
Q2: If ws1 is split into ws1.1 and ws1.2, with each workspace below 1 GB, would that be acceptable?
Q3: Can we assume ws2 is always within the free account rules?
Q4: If we restructure as ws1.1, ws1.2, and ws2 under account1, can we say the account is safe under the free tier regardless?

paulodetarsofm

Sorry, this message was meant to be a reply to Spidex Cloud. I edited it and added the reply in the right place.

paulodetarsofm

I hope so 😅, because that's what I did yesterday, I created different workspaces for each repository.

However, even after deleting the repositories from the old workspace, the total space used display did not update immediately, I checked now and the space used still did not update. I think I will transfer all the repositories from this workspace to new ones and delete it.

But anyway, let's wait and see if anyone else has any different information.

Syahrul

Hey folks,

The new changes to the free tier impose a size limit on a per-workspace basis. As previously mentioned, if a workspace contains multiple repositories and their combined size exceeds 1 GB, the workspace will be switched to read-only mode until the total size is reduced.

For example:

Workspace1:

Repository-a size: 200 MB
Repository-b size: 300 MB
Repository-c size: 600 MB

The workspace total size is 1.1 GB, which exceeds the 1 GB limit and triggers the read-only mode.

Workspace2:

Repository-a size: 200 MB
Repository-b size: 300 MB
Repository-c size: 200 MB

The workspace total size is 700MB, which does not exceed the 1 GB limit.

I hope this helps.

Regards,
Syahrul

paulodetarsofm

@Syahrul, I deleted all the repositories that I moved to new workspaces, however, the space of my only workspace that I had previously remains the same, it has not been changed.

Do you know if the size occupied by the workspaces is not recalculated when a repository is deleted? Do you guys only recalculate when a new one is added?

Syahrul

Hey @paulodetarsofm

After deletion of your repositories, please allow up to 30 days for the background cleanup job to run and the total workspace size to be re-adjusted.

Please note that the size enforcement will take place on April 28, 2025. Until that date, your workspace will not be impacted by the new limits. The new size will be reflected within 30 days of repository deletion.

Our team is working on improving the cleanup time, which is planned to be implemented before limit enforcement changes take place.

Regards,
Syahrul

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud