> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/usage.md). # Usage To open the Usage page, go to **Insights > Usage** on your project in the Umbraco Cloud Portal.
Umbraco Cloud Portal side menu with Insights expanded and Usage selected.

Usage in the Insights menu

On the Usage page, you can see how your project's usage compares to the limits of your plan. The page also shows bandwidth history, the largest media files, what drives bandwidth usage, and additional metrics such as database size.
The Usage page showing the monthly summary, the usage indicators counted against the plan, bandwidth history, media storage, bandwidth sources, and metrics collected for insight.

The Usage page

## Usage overview The top of the page shows your plan and when the plan figures were last collected. The **This month** summary indicates how many limits your project respects and highlights resources that are close to or over their limit.
Usage summary showing all three limits respected and usage indicators for bandwidth, media storage, and custom domains.

The Usage overview

### Counted against your plan The three usage indicators show the amount used, the available limit, and how much is left or over the limit: | Metric | What it measures | | -------------- | --------------------------------------------------------------------------------------------------------------------------------- | | Bandwidth | Data transferred from your Live environment to visitors during the current month, including responses served from the edge cache. | | Media storage | The size of all files in the Live environment's blob storage, including cached media. | | Custom domains | The number of custom domains added to your Live environment. | Bandwidth is measured from the data sent from the edge to visitors. Responses served from the edge cache still count toward the monthly total, even when the request does not reach the origin server. The Usage page marks a resource as close to its limit at 85% usage. This visual indicator is separate from the portal warning banners and email notifications, which start at 90% for bandwidth and media storage. These notifications apply when a higher plan is available. When usage exceeds a limit, the usage indicator shows the excess and a **Change plan** link. A resource without a plan limit is labeled **No limit on your plan**. Active bandwidth and media storage plan extensions increase the displayed limits. When an active extension applies, the corresponding usage indicator shows **+X GB bought**. Select this label to expand the list of active and scheduled extensions.
Bandwidth usage indicator showing +100 GB bought, a 400 GB limit, and the expanded active plan extension.

Bandwidth usage indicator with an active plan extension

### Bandwidth forecast For projects with a bandwidth limit, the summary estimates end-of-month usage after at least three days of daily data become available. The forecast takes the average daily usage from up to the last seven recorded days. The projected remaining usage is then added to the collected monthly total. If this estimate exceeds the bandwidth limit, the summary also shows approximately when the available bandwidth will run out. The projection assumes traffic continues at the recent rate; it is an estimate, not a measured monthly total. If monthly usage already exceeds the limit, the summary shows how much it is over, like **Already over by 5 GB this month**, instead of a forecast.
Usage summary showing Already over by 5 GB this month and 55 GB used against a 50 GB bandwidth limit.

Bandwidth summary when the monthly limit has been exceeded

Read [Bandwidth](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/usage/bandwidth.md) for more information about how usage is measured and how to reduce it. ## Bandwidth history and repository size The bandwidth chart has two views: * **31 days** shows daily bandwidth usage over a rolling 31-day period. * **12 months** shows monthly totals for the available history within the last 12 months. Hover over the chart to see usage for a date or month. In the monthly view, a plan-limit line is shown when the limit is within the chart's comparison range.
Monthly bandwidth chart with the 12 months view selected, a plan-limit line, and repository size below the chart.

Monthly bandwidth history and repository size

Below the chart, **Repository** shows the latest collected Git repository size in MB and an indication of its health. Repository size is separate from bandwidth usage. A large repository can slow cloning and deployment. Use **How to reduce it** to open the [Repositories in a Cloud Project](/umbraco-cloud/explore-umbraco-cloud/technology-overview/repositories-in-a-cloud-project.md#how-to-reduce-your-repository-size) guide. ## Media storage and bandwidth sources
Media storage listing the largest files alongside bandwidth sources grouped by HTTP referrer.

Media storage and bandwidth sources

### Media storage The media list loads automatically and shows the three largest files first. Select **Show all … files** to expand the list of up to 50 media files in your Live environment. Each row shows the file name, folder, file type, and size. Select a file name to open the file. When multiple categories are present, the breakdown above the list shows their share of the size of the listed files. Select a category, such as **Images** or **Video**, to filter the list; select it again to clear the filter. The breakdown covers the largest files returned by the list, rather than all files in blob storage. The media storage usage indicator includes the complete storage size, including cached media. ### Bandwidth sources Use **By path** and **By source** to investigate what contributes most to bandwidth usage in the current month. Each row shows a path or source, its request count, and the bandwidth generated by those requests. * **By path** lists the top 10 resource paths in your Live environment. The first three appear initially. Select **Show all 10**, then **Show top 50**, to load up to 50 paths when more are available. * **By source** lists the top 10 HTTP referrers. Select **Show all …** to expand the list. A referrer is an optional HTTP header identifying the page from which a resource was requested. **None (Direct)** indicates that no referrer was recorded for those requests. It does not necessarily mean the visitor entered the URL directly. {% hint style="info" %} Be aware that any third party services will also consume bandwidth. For example, an uptime service implementation can increase bandwidth usage as it pings the website more frequently. {% endhint %} ## Collected for insight The **Collected for insight** section shows additional metrics for your Live environment: | Metric | What it measures | | ------------- | ----------------------------------------------------------------------------- | | Database size | The size of the environment's database. | | Disk usage | The environment's file system usage, separate from media blob storage. | | Content nodes | The number of content nodes reported by the environment's Umbraco backoffice. | These cards provide insight into growth and are separate from the three usage indicators counted against your plan. Each card shows the latest available value and its month. When history is available, it also shows the change since the previous recorded month and up to six months of history.
Database size, disk usage, and content node cards with monthly changes and six months of history.

Additional metrics collected for insight

Use the displayed values and changes to assess growth over time. ## Data availability Usage figures are collected daily. Check **Plan figures collected** at the top of the page and the **as of** month on the insight cards when interpreting the data. New projects may show **No usage collected yet** until the first collection completes. History can be shorter than the selected range, and individual metrics may show **Not collected for this project yet**. If a section cannot load, use its retry control when available. ## Usage limits You can see the Usage limits and prices for the different plans on Umbraco Cloud on our [website](https://umbraco.com/umbraco-cloud-pricing/) or when [changing your plan](/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/change-your-plan.md). When you reach a usage limit, you can upgrade your project if a higher plan is available. Select **Management > Change Plan** to review the available plans. {% hint style="warning" %} If a higher plan is available, a portal warning banner appears when bandwidth or media storage reaches 90% of its limit. An email also notifies the project owner and technical contacts. USage Warning {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.umbraco.com/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/usage.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.