GitHub Actions runner specs: CPU, memory and disk of every Linux runner

Updated · prices and specs read on 24 Oct 2026

GitHub's standard Linux runner (ubuntu-latest) has 2 vCPU, 8 GB of memory and a 14 GB SSD in a private repository, and 4 vCPU and 16 GB in a public one; larger runners go from 2 to 64 cores at 4 GB per vCPU with 75 GB to 2,040 GB of disk.

Standard GitHub-hosted Linux runners

Label Repository vCPU Memory SSD Architecture
ubuntu-slim any 1 5 GB 14 GB x64
ubuntu-latest, ubuntu-24.04, ubuntu-22.04, ubuntu-26.04 public 4 16 GB 14 GB x64
same private 2 8 GB 14 GB x64
ubuntu-24.04-arm, ubuntu-22.04-arm, ubuntu-26.04-arm public 4 16 GB 14 GB arm64
same private 2 8 GB 14 GB arm64

The same label is twice the machine in a public repository. A workflow that passes in an open-source project can run out of memory once the repository is private.

GitHub larger runners

Cores Memory SSD Architectures
2 8 GB 75 GB x64, arm64
4 16 GB 150 GB x64, arm64
8 32 GB 300 GB x64, arm64
16 64 GB 600 GB x64, arm64
32 128 GB 1,200 GB x64, arm64
64 256 GB (x64), 208 GB (arm64) 2,040 GB x64, arm64

Memory is always 4 GB per vCPU (except the 64-core arm64), so the memory a job needs fixes the number of cores you pay for.

Managed alternatives

Vendor Memory per vCPU Example sizes
Blacksmith 4 GB (x64), 3 GB (ARM) 2 vCPU / 8 GB to 32 vCPU / 128 GB; ARM 2 vCPU / 6 GB to 32 vCPU / 96 GB
Ubicloud 4 GB (x64), 3 GB (arm64) 2 vCPU / 8 GB to 30 vCPU / 120 GB
FlameWill up to 8 GB (arm64) 2 vCPU / 8 GB, 2 vCPU / 16 GB, 4 vCPU / 32 GB

Check what your job got

- name: Machine
  run: |
    nproc            # cores
    free -h          # memory
    df -h "$GITHUB_WORKSPACE"   # disk where the job works
    uname -m         # x86_64 or aarch64

To size a job, measure what it used, not what the machine had: see GitHub Actions out of memory.

Questions

How much disk space does a GitHub Actions runner have?

Standard runners have a 14 GB SSD for your work (in public and private repositories). Larger runners have 75 GB (2 cores) up to 2,040 GB (64 cores). FlameWill's machines work on local NVMe of about 110 GB (2 vCPU) or 220 GB (4 vCPU).

What is ubuntu-slim?

A 1-vCPU, 5 GB Linux runner at $0.002 a minute, for light jobs; GitHub limits its jobs to 15 minutes.

How do I see the runner's CPU and memory from a workflow?

Add a step that runs nproc, free -h and df -h. They print the cores, the memory and the free disk of the machine the job got.

Sources

Read on 24 Oct 2026. Prices change: check each vendor's own page before you decide.

This page as Markdown: /guides/github-actions-runner-specs.md