Do Forks from Paid Repositories Count Toward Free Workspace Storage Limits?

[Ideal app2]

I recently received a notice from Bitbucket stating that my free workspace has exceeded the new 1 GB storage limit and will be put into read-only mode after April 28, 2025, unless I reduce its size. However, my workspace primarily consists of forks from repositories that belong to a paid Bitbucket account. A few of these parent repositories exceed 1 GB, but I assumed that since they are part of a paid plan, the storage limits of my free workspace wouldn’t apply to them. Can someone clarify how storage limits work for forks of repositories from paid accounts? Are they treated separately from the parent repository’s storage, or should they inherit the storage privileges of the paid account? I’d appreciate any guidance on this before deciding whether to delete these forks or take other action.

[Ben]

Hi @Ideal app2 

Fork repositories are copies of existing repositories that are stored against your workspace - so they do in fact count towards the workspace storage limit regardless of the plan that the parent repo workspace belongs to.

Essentially, any repository that is stored under your workspaceID counts toward the limit.

Regards,

- Ben (Bitbucket Cloud Support)