# How to calculate your real GitHub Actions usage in minutes (https://depot.dev/blog/how-to-calculate-github-actions-usage)

> By John Stocks (Head of Solution Engineering at Depot)
> Published 2025-06-03

GitHub Actions usage reporting doesn't tell the full story. If you're running different types of runners (like 4-core, 8-core, or more), those minutes aren't equal, and your total usage number doesn't reflect it.

This guide will show you how to:

* Export your raw usage data
* Normalize it by runner type
* Get an accurate total you can actually budget against \\

## **Why normalizing GitHub Actions minutes matters**

Runner types in [GitHub Actions](https://www.depot.dev/products/github-actions) have different compute capacities and costs. For example, a 4-core runner can do twice the work of a 2-core runner. If you just sum the raw usage, you're underestimating your real consumption and leaving yourself open to surprise bills.

## **Step 1: Export your usage report**

1. In GitHub, click your avatar (top right) and go to **Settings**
2. Select **Billing and plans**
3. Under **Usage this month**, click **Get usage report**
4. Choose your date range (30/60/90 days) and download the CSV

You'll now have a CSV showing runner types, quantities, and costs.

<CTA>
  <a href="https://depot.dev/github-actions-price-calculator" data-ph-capture-attribute-button-id="Blog-CTA">
    Stop burning money on slow GitHub Actions runners. See how much you could save with 10x faster builds.
    <span className="font-semibold text-radix-grass12"> Calculate your savings →</span>
  </a>
</CTA>

## **Step 2: Normalize your minutes**

Open the CSV in any spreadsheet tool. Focus on the 'sku' and 'quantity' columns. Each runner type has a multiplier based on its compute capacity:

| Runner Type              | Multiplier |
| ------------------------ | ---------- |
| actions\_linux           | 1          |
| actions\_linux\_4\_core  | 2          |
| actions\_linux\_8\_core  | 4          |
| actions\_linux\_16\_core | 8          |
| actions\_linux\_32\_core | 16         |

To normalize your total usage:

* For each runner type, multiply the quantity by the multiplier
* Sum these normalized values across all runner types

This gives you the total compute-equivalent minutes your team used during the period.

## **Step 3: Use the data to control costs**

Without normalized data, you're likely underestimating usage. This normalization process gives you a real number to track, budget against, and compare over time.

## **Take it further with Depot**

Once you know how many minutes you're actually burning, the next step is cutting them down. Depot Runners can dramatically speed up your CI builds, reducing both time and cost.

If you're ready to stop guessing and start saving, give [Depot](https://depot.dev/) a try.

## For AI Agents

The full site index is at [llms.txt](https://depot.dev/llms.txt). Append `.md` to any documentation, blog, changelog, or customer URL to fetch its markdown source directly.