info:To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title:Read-only namespaces
title:Read-only projects
---
{{<details>}}
...
...
@@ -12,25 +12,29 @@ title: Read-only namespaces
{{</details>}}
On GitLab.com, a top-level namespace is placed in a read-only state when it either:
A project is placed in a read-only state when it exceeds the allocated storage limit on the:
-Exceeds the [free user limit](free_user_limit.md) when the namespace visibility is private.
-Exceeds the [storage usage quota](storage_usage_quotas.md), regardless of namespace visibility.
-Free tier, when any project in the namespace is over the [free limit](storage_usage_quotas.md#free-limit).
-Premium and Ultimate tiers, when any project in the namespace is over the [fixed project limit](storage_usage_quotas.md#fixed-project-limit).
While a namespace is in a read-only state, a banner appears at the
top of the page.
When a project is read-only due to storage limits, you can't push or add large files (LFS) to the project's repository.
A banner at the top of the project or namespace page indicates the read-only status.
Your ability to write new data to read-only namespaces is restricted. For more
information, see [Restricted actions](#restricted-actions).
## Read-only namespaces
## Remove the read-only state
{{<details>}}
- Tier: Free
{{</details>}}
On the Free tier, a namespace is placed in a read-only state when it exceeds the [free user limit](free_user_limit.md), when the namespace visibility is private.
To restore a namespace to its standard state, you can:
To remove the read-only state of a namespace and its projects, you can:
- For exceeded free user limits:
-[Reduce the number of members](free_user_limit.md#manage-members-in-your-group-namespace) in your namespace.
-[Start a free trial](https://gitlab.com/-/trial_registrations/new), which includes an unlimited number of members.
-[Purchase a paid tier](https://about.gitlab.com/pricing/).
-[Reduce the number of members](free_user_limit.md#manage-members-in-your-group-namespace) in your namespace.
-[Start a free trial](https://gitlab.com/-/trial_registrations/new), which includes an unlimited number of members.
-[Purchase a paid tier](https://about.gitlab.com/pricing/).
All projects on GitLab.com have 10 GiB of free storage for their Git repository and Large File Storage (LFS).
## Free limit
{{<details>}}
- Tier: Free
{{</details>}}
All Free projects on GitLab.com have 10 GiB of free storage for their Git repository and Large File Storage (LFS).
When a project's repository and LFS exceed 10 GiB, the project is set to a read-only state.
You cannot push changes to a read-only project. To increase storage of the project's repository and LFS to more than 10 GiB,
You cannot push changes to a read-only project.
To increase storage of the project's repository and LFS to more than 10 GiB,
you must [purchase more storage](../subscriptions/gitlab_com/_index.md#purchase-more-storage).
Only the project's repository and LFS are included in the storage limit. The container registry, package registry, and build artifacts are not included in the limit.
Only the project's repository and LFS are included in the storage limit.
The container registry, package registry, and build artifacts are not included in the limit.
@@ -54,13 +63,6 @@ Storage usage is displayed in kibibytes (KiB), mebibytes (MiB),
or gibibytes (GiB). 1 KiB is 2^10 bytes (1024 bytes),
1 MiB is 2^20 bytes (1024 kibibytes), and 1 GiB is 2^30 bytes (1024 mebibytes).
{{<alerttype="note">}}
Storage usage labels are being transitioned from `KB` to `KiB`, `MB` to `MiB`, and `GB` to `GiB`. During this transition,
you might see references to `KB`, `MB`, and `GB` in the UI and documentation.
{{</alert>}}
## View project fork storage usage
A cost factor is applied to the storage consumed by project forks so that forks consume less namespace storage than their actual size. The cost factors for forks storage reduction applies only to namespace storage. It does not apply to project repository storage limits.
...
...
@@ -77,6 +79,12 @@ The cost factor does not apply to private forks in namespaces on the Free plan.
## Excess storage usage
{{<details>}}
- Tier: Free
{{</details>}}
Excess storage usage is the amount that exceeds the 10 GiB free storage of a project's repository and LFS. If no purchased storage is available,
the project is set to a read-only state. You cannot push changes to a read-only project.
...
...
@@ -131,12 +139,11 @@ In this example:
## Manage storage usage
To manage your storage, if you are a namespace Owner, you can [purchase more storage for the namespace](../subscriptions/gitlab_com/_index.md#purchase-more-storage).
Depending on your role, you can also use the following methods to manage or reduce your storage:
