How to Get RHEL for Free with a Developer Subscription

People usually go looking for a free copy of Red Hat Enterprise Linux for one of two reasons: they are studying for a certification and want the real thing rather than a rebuild, or they want to run a small home server on the same platform they use at work. Red Hat supports both cases with a genuine no-cost subscription, so there is no need to hunt for an evaluation ISO that stops updating after 60 days.

The catch is not the download, which is straightforward. It is knowing which of Red Hat's several no-cost programs you qualify for, and getting the subscription attached to your account so the download page actually lets you through.

What the no-cost developer subscription includes

Joining the Red Hat Developer program attaches a Developer Subscription for Individuals to your account, and that single subscription is what entitles you to download RHEL and pull updates. Red Hat documents the following entitlements:

• 16 nodes — any combination of physical machines, virtual machines, and containers, regardless of how large each system is
• The same binaries — identical to the packages organizations run under paid subscriptions, not a stripped or delayed build
• Full update stream — releases, updates, and errata through Red Hat CDN, the same way a paid system gets them
• Development, testing, and small production use — demos, prototyping, QA, and personal production workloads all qualify
• Older releases — a back catalog covering roughly a ten-year lifespan, through the Customer Portal
• Cloud access — run those entitlements on AWS, Google Cloud, or Azure and pay only for the virtual machine

What you give up compared to a paid subscription is Red Hat's support relationship. The developer subscription is self-supported, which means documentation and knowledge base access but no technical support cases. For a study lab or a personal server that trade is usually irrelevant, and it is the only meaningful difference in day-to-day use.

The other thing to note early is that this subscription lasts one year. It does not renew silently in the background, and a lapsed subscription quietly cuts a working system off from updates, so it is worth understanding the renewal step before you get there.

Which no-cost RHEL program fits your case

Red Hat runs several no-cost programs, and picking the wrong one is the most common reason a download is refused or an account ends up out of compliance. They differ mainly in who may use them and whether production is allowed.

If you need RHEL for development inside a company, compare the current RHEL developer subscription options, including RHEL for Business Developers and the Developer Subscription for Teams. Organizations that already use Red Hat products can also review the Red Hat Developer Subscription for Teams directly.

For a home lab, a certification study machine, or a personal project, the Developer Subscription for Individuals is the one you want, and the rest of this guide follows that path. Note that only one such subscription can be attached to a Red Hat account, so a second developer in the house needs their own account rather than a second entitlement on yours.

If the individual terms do not fit your situation, a RHEL-compatible rebuild is usually the better answer than stretching the developer terms. The differences and compatibility guarantees are covered in Rocky Linux vs AlmaLinux vs RHEL, and Fedora vs CentOS Stream vs RHEL explains where each sits in the development flow.

Create your Red Hat account

Start at the Red Hat Developer registration page and create an account. You can fill in the form directly with an email address, or sign in through an identity provider such as GitHub. No payment details are requested at any point, and Red Hat states that no sales follow-up is attached to the registration.

Two details about that account save trouble later:

• Your username is usually your email address. When registration creates a Red Hat login for you, the email you signed up with becomes the login name you type at subscription-manager prompts and on the Customer Portal.
• Social sign-in only works on the developer site. GitHub and similar providers authenticate you at developers.redhat.com, but other Red Hat properties such as the Customer Portal expect the Red Hat login and password. Set that password during registration, or use the password reset link the first time you need it.

That second point catches people who registered through GitHub months earlier and then cannot sign in to check their subscription. The account exists; it just needs its Red Hat password set.

Activate the developer subscription

Activation is usually not a separate step, because joining the developer program is what attaches the subscription. Three points cover the whole flow:

• It attaches when you join — Red Hat adds the Developer Subscription for Individuals to your account automatically
• If it did not attach — open the RHEL Developer download page while signed in and select Activate your subscription
• To confirm it worked — sign in to the Red Hat Subscription Inventory, where the subscription appears with its details and validity period

Red Hat moved subscription management into the Hybrid Cloud Console, so that inventory is the current view rather than the older Customer Portal subscription pages. Check it before you spend time on a ten gigabyte download.

If the inventory shows no subscription, or a download tells you that a subscription is required, the reliable fix is counterintuitive: start a download from the developer portal. Those links handle registration, subscription attachment, and the transfer in one flow, so beginning a download triggers the entitlement. Cancel the transfer once it starts, then reload the inventory to confirm the subscription appeared.

Be careful how you check which subscription covers a system, because the answer depends on the release:

• On the RHEL 10.2 system tested here — subscription-manager list --consumed is no longer available, and list exposes only the remaining non-entitlement views such as installed products
• Why it changed — RHEL 10 uses Simple Content Access, where subscription ownership and usage are handled at the account level rather than by attaching an entitlement to each host
• Do not generalize — older RHEL releases and some Red Hat documentation still expose list --consumed

On RHEL 10 that makes the Subscription Inventory the place to check what your account holds, and it is a separate question from whether a particular host is registered, which you answer on the host itself.

Choose between the Boot ISO and the DVD ISO

Every RHEL release on the download page is offered as two installer images per architecture, and the difference matters more than the names suggest. Choosing wrongly means either a failed install or an unnecessary multi-gigabyte download.

The Boot ISO is the smaller download but the more demanding one, because the installer has to fetch every package from somewhere. That source is Red Hat CDN once you register during installation, or a repository you point the installer at with inst.repo. If your lab VM has working internet and you are happy registering at install time, it is the efficient choice.

The DVD ISO is the safer default for a first install, an air-gapped machine, or a slow connection you do not want to depend on mid-install. It is also what you want if you plan to serve installs from a local mirror later.

Alongside the installer images, the same page offers other formats worth knowing about:

• WSL2 image — RHEL as a Windows Subsystem for Linux distribution, with no virtual machine involved
• Cloud-ready images — prebuilt images for AWS, Google Cloud, Azure, and VMware
• Universal Base Image — freely redistributable container base images, usable without a subscription
• Developer Sandbox — a hosted environment for a quick look with no local install

Download the ISO

Open the RHEL download page while signed in, choose the release and architecture you need, and download either the Boot ISO or the DVD ISO. Releases are listed newest first, and each one expands into a row per architecture and image type. Read three things in that row before you click:

• Architecture — x86_64 for an ordinary Intel or AMD machine, aarch64 for 64-bit Arm including Apple silicon; on an existing Linux host, uname -m prints the name you want
• SHA-256 checksum — the value you compare against once the download finishes
• Release date — which minor release you are actually getting, since several are listed together

Copy that checksum somewhere before you start. You need it to verify the file afterwards, and it is easy to lose track of once the page has moved on.

The developer download page carries only the recent releases. If the release you need is not listed there, use the Red Hat Enterprise Linux Customer Portal downloads after signing in, which gives accounts with an active subscription access to older RHEL releases. Studying for a certification on the version your workplace still runs is the usual reason to go looking there.

Before starting a DVD download, make sure the destination has room for it. Check the filesystem you are downloading into rather than your home directory out of habit, because the two are often on different volumes:

df -h /var/tmp

Filesystem             Size  Used Avail Use% Mounted on
/dev/mapper/rhel-root   25G   12G   13G  48% /

My lab host reports 13 GB available on the filesystem holding /var/tmp, which is enough for a DVD ISO but leaves little spare. A download that runs out of space fails in a way that looks like corruption rather than a full disk, so it is worth a glance up front.

A headless server can still use the download page from a desktop browser. Start the download, cancel it, then copy the link from your browser's download list and hand it to curl on the server. A few details about those links matter:

• They are signed and short-lived — paste and fetch promptly, because they expire
• Set the output name with -o — a signed URL ends in query parameters rather than a clean file name
• Add -L -C - — follow redirects, and resume an interrupted transfer instead of restarting it
• An expired link still downloads something — you get a small HTML error file rather than an ISO, which the size check in the next section catches immediately

Verify the ISO before you install it

Skipping verification is how people end up debugging an installer crash that was really a truncated download. Two checks are worth the minute they take: confirming the file matches Red Hat's published checksum, and confirming it is the release and architecture you meant to get.

Start with the file size, which catches the obvious failures such as an expired link or a download that stopped early:

ls -lh rhel-10.2-x86_64-boot.iso

-rw-r--r--. 1 root root 994M Aug  8 22:13 rhel-10.2-x86_64-boot.iso

At 994 MB this is plausible for a Boot ISO. Anything measured in kilobytes is an error page that was saved with an ISO file name.

Now verify the bytes against Red Hat's published value. You can print the hash with sha256sum rhel-10.2-x86_64-boot.iso and read it yourself, but comparing 64 hexadecimal characters by eye is error prone, and checking only the first and last few is exactly how a corrupted file slips through. Let sha256sum do the comparison instead, by saving the published value and the file name into a checksum file:

echo "675001a587c15f0c56c09beca6b1576c3be63cc4a0754e375ce93a6afda3dc8a  rhel-10.2-x86_64-boot.iso" > rhel-boot.iso.sha256

Keep the two spaces between the checksum and the file name, because that is the format sha256sum expects. Then check the image against that file. Hashing is limited by disk speed rather than anything expensive, so it is quick: this 994 MB image took about seven seconds on my lab host, and a DVD ISO scales up from there.

sha256sum --check rhel-boot.iso.sha256

rhel-10.2-x86_64-boot.iso: OK

OK means the file on disk is byte-for-byte what Red Hat published, and that is the only confirmation you need before writing it to media.

It is worth seeing the other outcome once, so you recognize it on the day a download really does break. Feeding a deliberately wrong checksum to the same command shows how a corrupted image is reported:

echo "0000000000000000000000000000000000000000000000000000000000000000  rhel-10.2-x86_64-boot.iso" | sha256sum --check -

rhel-10.2-x86_64-boot.iso: FAILED
sha256sum: WARNING: 1 computed checksum did NOT match

FAILED also sets a non-zero exit status, so this check drops straight into a provisioning script without parsing its text. When you see it, download the file again rather than trying to repair it, and check that you copied the checksum for the matching architecture and image type.

With the bytes confirmed, the second question is whether this is the image you wanted. The file command answers that without mounting anything, because the installer media carries its identity in the ISO 9660 volume label:

file rhel-10.2-x86_64-boot.iso

rhel-10.2-x86_64-boot.iso: ISO 9660 CD-ROM filesystem data (DOS/MBR boot sector) 'RHEL-10-2-BaseOS-x86_64' (bootable)

The label reports the product, release, and architecture in one string, and (bootable) confirms a boot sector is present, which is what a machine needs to start the installer from this media. A file that identifies as anything other than ISO 9660 is not installer media at all.

What the label does not tell you is whether this is a Boot ISO or a DVD ISO. Note that BaseOS appears in the label even on a Boot ISO that ships no packages at all, so do not read it as proof that the repositories are present. Mount the image read-only and list its top level to settle it:

sudo mkdir -p /mnt/rhel-iso && sudo mount -o loop,ro rhel-10.2-x86_64-boot.iso /mnt/rhel-iso
ls /mnt/rhel-iso

boot
EFI
images

Three directories and nothing else means this is a Boot ISO. There is no BaseOS or AppStream directory here, which is a concrete demonstration of why this image cannot install packages on its own and needs a network source. A DVD ISO lists those repository directories alongside the boot files. Unmount it with sudo umount /mnt/rhel-iso when you are finished, so the file is free to write to a USB stick or attach to a virtual machine.

Keep the subscription from lapsing

The Developer Subscription for Individuals runs for one year, and Red Hat does not extend it automatically. Renewal is free and takes one checkbox, but it does require you to act:

• 30 days before expiry — Red Hat emails a reminder with a renewal button
• On the expiry date — a second email arrives
• The renewal window — you can renew inside those last 30 days or any time after the subscription has already expired
• If the email is missing or its button no longer works — go directly to the Developer Subscription for Individuals renewal page, sign in, accept the current terms, and submit the renewal

The symptom of a lapsed subscription is easy to misread. The system stays registered, so nothing obviously breaks, but dnf stops seeing Red Hat repositories and updates quietly stop arriving. If a machine that worked for months suddenly cannot find packages, check the validity period in your Subscription Inventory before you start debugging repository configuration on the host.

What to do next with the ISO

The ISO on its own is just a file, and how you use it depends on where RHEL is going:

• A physical machine — write the image to a USB stick, which Create a bootable USB from an ISO covers with dd and graphical tools
• A virtual machine — attach the ISO as a virtual optical drive and boot from it, following Step-by-step RHEL installation with screenshots through the installer
• More than one machine — skip the manual installer and drive it from an answer file, as in Automate RHEL installation with Kickstart, or serve it over the network with a Kickstart PXE boot server

Whichever route you take, the installed system needs to be registered before dnf can reach Red Hat CDN, because the subscription lives on your account rather than in the ISO. That step is covered in Register RHEL with Subscription Manager. If you are working towards a certification, the RHCSA certification course picks up from a freshly installed system.

Troubleshooting

References

• No-cost RHEL Individual Developer Subscription FAQs — entitlements, activation, and download questions
• Red Hat Developer Program Terms and Conditions — the 16-node limit, individual use, and corporate-device wording
• How to renew your Red Hat Developer Subscription for Individuals — renewal window and steps

Summary

Getting RHEL at no cost comes down to joining the Red Hat Developer program, which attaches a Developer Subscription for Individuals to your account and entitles you to 16 nodes of the same binaries paying customers run. The software is genuinely free rather than a time-limited trial, and it may be used for personal production workloads as well as study labs. What the subscription does not include is Red Hat support, and what it does not permit is use by a company or team, which is the boundary to keep in mind rather than the node count.

Most of the friction is not the download but the entitlement behind it. When the portal refuses a download or a system will not register, the subscription almost certainly never attached to the account, and starting a download from the developer portal is what fixes it. On RHEL 10 you also cannot ask a host which subscription covers it, so the Subscription Inventory in the Hybrid Cloud Console is where you confirm what your account holds.

Before writing the image anywhere, verify it. Save the published SHA-256 value into a checksum file and let sha256sum --check compare it, since reading 64 hexadecimal characters by eye is how a bad download survives to break the installer later. A quick file on the image confirms the release and architecture from the volume label, and mounting it read-only tells you whether you have a Boot ISO or a DVD ISO, which is the difference between an installer that needs a network source and one that carries every package with it.

Diary the expiry date somewhere you will see it. The subscription lasts one year and lapses silently: the host stays registered while dnf quietly loses access to Red Hat CDN, which is a confusing failure to debug a year from now. Renewal is a single checkbox once you know where to click. From here, write the ISO to media or attach it to a virtual machine, install, and then register the system so it starts pulling updates.