Text of docs.github.com › en › actions › reference › runners › github-hosted-runners as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

GitHub-hosted runners reference - GitHub Docs

Skip to main content Skip to content Collapse sidebar Expand sidebar GitHub-hosted runners reference Find information about GitHub-hosted runners, including their specifications and customization options. In this article Supported runners and hardware resources Ranges of GitHub-hosted runners are available for use in public and private repositories. For lists of available runners, see: Standard runners for public repositories Standard runners for private repositories GitHub-hosted Linux runners support hardware acceleration for Android SDK tools, which makes running Android tests much faster and consumes fewer minutes.

For more information on Android hardware acceleration, see Configure hardware acceleration for the Android Emulator in the Android Developers documentation. Note The -latest runner images are the latest stable images that GitHub provides, and might not be the most recent version of the operating system available from the operating system vendor. Warning Beta and Deprecated Images are provided "as-is", "with all faults" and "as available" and are excluded from the service level agreement and warranty.

Beta Images may not be covered by customer support. Standard GitHub-hosted runners for public repositories For public repositories, jobs using the workflow labels shown in the table below will run with the associated specifications. With the exception of single-CPU runners, each GitHub-hosted runner is a new virtual machine (VM) hosted by GitHub. Single-CPU runners are hosted in a container on a shared VM—see GitHub-hosted runners reference .

Use of the standard GitHub-hosted runners is free and unlimited on public repositories. Virtual machine / container Processor (CPU) Memory (RAM) Storage (SSD) Architecture Workflow label Linux 1 5 GB 14 GB x64 ubuntu-slim Linux 4 16 GB 14 GB x64 ubuntu-latest , ubuntu-24.04 , ubuntu-22.04 , ubuntu-26.04 Windows 4 16 GB 14 GB x64 windows-latest , windows-2025 , windows-2025-vs2026 , windows-2022 Linux 4 16 GB 14 GB arm64 ubuntu-24.04-arm , ubuntu-22.04-arm , ubuntu-26.04-arm Windows 4 16 GB 14 GB arm64 windows-11-arm , windows-11-vs2026-arm macOS 4 14 GB 14 GB Intel macos-15-intel , macos-26-intel macOS 3 (M1) 7 GB 14 GB arm64 macos-latest , macos-15 , macos-26 , xcode-27 Standard GitHub-hosted runners for private repositories For private repositories, jobs using the workflow labels shown in the table below will run on virtual machines with the associated specifications.

These runners draw from your GitHub account's included compute usage, and are then charged at the per-minute rates. See Actions runner pricing . Virtual Machine Processor (CPU) Memory (RAM) Storage (SSD) Architecture Workflow label Linux 1 5 GB 14 GB x64 ubuntu-slim Linux 2 8 GB 14 GB x64 ubuntu-latest , ubuntu-24.04 , ubuntu-22.04 , ubuntu-26.04 Windows 2 8 GB 14 GB x64 windows-latest , windows-2025 , windows-2025-vs2026 , windows-2022 Linux 2 8 GB 14 GB arm64 ubuntu-24.04-arm , ubuntu-22.04-arm , ubuntu-26.04-arm Windows 2 8 GB 14 GB arm64 windows-11-arm , windows-11-vs2026-arm macOS 4 14 GB 14 GB Intel macos-15-intel , macos-26-intel macOS 3 (M1) 7 GB 14 GB arm64 macos-latest , macos-15 , macos-26 , xcode-27 Note During periods of high demand, jobs that run on macOS runners may take longer to start.

GitHub monitors macOS usage and plans capacity to meet demand over time. Workflow logs list the runner used to run a job. For more information, see Viewing workflow run history . Limitations for arm64 macOS runners All actions provided by GitHub are compatible with arm64 GitHub-hosted runners. However, community actions may not be compatible with arm64 and need to be manually installed at runtime. Nested-virtualization is not supported due to the limitation of Apple's Virtualization Framework.

Networking capabilities such as Azure private networking and assigning static IPs are not currently available for macOS larger runners. The arm64 macOS runners do not have a static UUID/UDID assigned to them because Apple does not support this feature. However, Intel MacOS runners are assigned a static UDID, specifically 4203018E-580F-C1B5-9525-B745CECA79EB . If you are building and signing on the same host you plan to test the build on, you can sign with a development provisioning profile .

If you do require a static UDID, you can use Intel runners and add their UDID to your Apple Developer account. Single-CPU runners Single-CPU GitHub-hosted runners are available in both public and private repositories. These runners—specified using the workflow label ubuntu-slim —offer a lower-cost option for running lightweight operations. This type of runner is optimized for automation tasks, issue operations and short-running jobs.

They are not suitable for typical heavyweight CI/CD builds. ubuntu-slim runners execute Actions workflows in Ubuntu Linux, inside a container rather than a full VM instance. When the job begins, GitHub automatically provisions a new container for that job. All steps in the job execute in the container, allowing the steps in that job to share information using the runner's file system. When the job has finished, the container is automatically decommissioned.

Each container provides hypervisor level 2 isolation. Note The container for ubuntu-slim runners runs in unprivileged mode. This means that some operations requiring elevated privileges—such as mounting file systems, using Docker-in-Docker, or accessing low-level kernel features—are not supported. A minimal set of tools is installed on the ubuntu-slim runner image, appropriate for lightweight tasks. For details on what software is installed on the ubuntu-slim image, see the README file in the actions/runner-images repository.

Usage limits Single-CPU runners follow the same concurrency model as other GitHub-hosted standard runners. See Actions limits . The concurrency for the runners is determined by your plan. The job timeout for single-CPU runners is 15 minutes. If a job reaches this limit, the job is terminated and fails. Larger runners Larger runners are available for organizations and enterprises on GitHub Team and GitHub Enterprise Cloud plans.

Larger runners are managed virtual machines with more resources than standard GitHub-hosted runners . They offer the following advanced features: More RAM, CPU, and disk space Static IP addresses Azure private networking The ability to group runners Autoscaling to support concurrent workflows GPU-powered runners These larger runners are hosted by GitHub and have the runner application and other tools preinstalled. For more information, see Using larger runners .

Administrative privileges The Linux and macOS virtual machines both run using passwordless sudo . When you need to execute commands or install tools that require more privileges than the current user, you can use sudo without needing to provide a password. For more information, see the Sudo Manual . Windows virtual machines are configured to run as administrators with User Account Control (UAC) disabled. For more information, see How User Account Control works in the Windows documentation.

IP addresses To get the full set of IP address ranges from which GitHub-hosted runners may be assigned an IP address, use the actions key in the response from the GET /meta REST API endpoint. For more information, see REST API endpoints for meta data . These ranges are not dedicated to GitHub Actions. They cover the broader address space of the cloud provider regions where GitHub-hosted runners run, and include IP addresses used by unrelated services and customers. macOS runners are hosted in GitHub's own macOS cloud.

If you use an allowlist to control access to your internal resources from GitHub-hosted runners, we do not recommend adding these ranges to it. Allowlisting the entire set permits network access from unrelated workloads within those ranges, not just your GitHub Actions runners. This substantially broadens access and undermines the restrictions your allowlist is int

The rest of this page is on the live site.