About billing for Git Large File Storage
Note
您必须单独管理每个帐户的计费设置和付款功能。 您可以使用每个设置页面上的上下文切换器在个人帐户、组织帐户和企业帐户的设置之间切换。 有关详细信息,请参阅“About billing on GitHub”。
Each GitHub account receives a certain amount of free bandwidth and storage for Git LFS, depending on the account's plan. Bandwidth is billed for each GiB of data downloaded. Storage is billed by calculating an hourly usage rate. To estimate costs for paid Git LFS usage, you can use the GitHub pricing calculator.
带宽和存储使用量只根据仓库所有者的帐户计数。 在复刻中,带宽和存储的使用根据仓库网络根计数。 任何可以写入仓库的人都可以将文件推送到 Git LFS,而不会影响他们的个人带宽和存储使用量。 复刻和拉取仓库根据父仓库的带宽使用量计数。
Included bandwidth and storage (per month)
The following amounts of bandwidth and storage are included for free with your GitHub account.
Plan | Bandwidth | Storage |
---|---|---|
GitHub Free | 10 GiB | 10 GiB |
GitHub Pro | 10 GiB | 10 GiB |
GitHub Free for organizations | 10 GiB | 10 GiB |
GitHub Team | 250 GiB | 250 GiB |
GitHub Enterprise Cloud | 250 GiB | 250 GiB |
Pricing for paid usage
If you use more than the included amount of bandwidth or storage for your plan throughout the month, you can still use Git LFS. GitHub bills for additional GiBs of data at the rates below.
Product | Price per-GiB (USD) |
---|---|
Bandwidth | $0.0875 |
Storage | $0.07 |
Sample storage cost calculation
For example, if you use 1 GiB above what is included for free for the first 15 days of April, then use 2 GiB starting from April 16th to the end of the month, your storage costs will be calculated in the following way.
- 1 GiB × 15 days × 24 hours per day = 360 GiB-hours
- 2 GiB × 15 days × 24 hours per day = 720 GiB-hours
- 360 GiB-hours + 720 GiB-hours = 1080 GiB-hours
- 1080 GiB-hours / 720 hours in the month = 1.5 GiB-months
In this example, GitHub would bill for 1.5 GiB of storage for the month of April.
Managing your budget for Git Large File Storage
The default budget for paid usage is $0 for accounts that do not have a payment method on file. For accounts that do have a payment method on file, the default budget is unlimited. You can take steps to manage your Git LFS budget. See "Preventing overspending."