You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hub/storage-limits.md
+94-1Lines changed: 94 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -111,4 +111,97 @@ To do that, to ensure we can effectively support the open-source ecosystem, plea
111
111
112
112
### Grants for private repositories
113
113
114
-
If you need more model/ dataset storage than your allocated private storage for academic/ research purposes, please reach out to us at [email protected] or [email protected] along with a proposal of how you will use the storage grant.
114
+
If you need more model/ dataset storage than your allocated private storage for academic/ research purposes, please reach out to us at [email protected] or [email protected] along with a proposal of how you will use the storage grant.
115
+
116
+
117
+
## How can I free up storage space in my account/organization?
118
+
119
+
There are several ways to manage and free some storage space in your account or organization. First, if you need more storage space, consider upgrading to PRO or Enterprise Hub plans for increased storage limits.
120
+
121
+
⚠️ **Important**: Deleting LFS files is a destructive operation that cannot be undone. Make sure to backup your files before proceeding.
122
+
123
+
Key points to remember:
124
+
- Deleting only LFS pointers doesn't free up space
125
+
- If you do not rewrite the Git history, future checkouts of branches/tags containing deleted LFS files with existing lfs pointers will fail (to avoid errors, add the following line to your `.gitconfig` file: `lfs.skipdownloaderrors=true`)
126
+
127
+
128
+
### Deleting individual LFS files
129
+
130
+
1. Navigate to your repository's Settings page
131
+
2. Click on "List LFS files" in the "Storage" section
132
+
3. Use the actions menu to delete specific files
133
+
134
+
135
+
### Super-squash your repository using the API
136
+
137
+
The super-squash operation compresses your entire Git history into a single commit. Consider using super-squash when you need to reclaim storage from old LFS versions you're not using. This operation is only available through the [Hub Python Library](https://huggingface.co/docs/huggingface_hub/main/en/package_reference/hf_api#huggingface_hub.HfApi.super_squash_history) or the API.
138
+
139
+
⚠️ **Important**: This is a destructive operation that cannot be undone, commit history will be permanently lost and **LFS file history will be removed**
140
+
141
+
The effects from the squash operation on your storage quota are not immediate and will be reflected on your quota within a few minutes.
142
+
143
+
### Advanced: Track LFS file references
144
+
145
+
When you find an LFS file in your repository's "List LFS files" but don't know where it came from, you can trace its history using its SHA-256 OID by using the git log command:
0 commit comments