Ubuntu 26.04 Tutorial / Choose an LTS Image and CPU Architecture

For Ubuntu 26.04 server exercises, select an Ubuntu Server installation image and verify whether the target architecture is amd64 or arm64. Check the actual point release and filename in the official 26.04 LTS directory alongside support scope, applications, and virtualization compatibility.

Understand 26.04 LTS and 26.04.1

Ubuntu release numbers identify the release year and month: 26.04 is the April 2026 release. LTS stands for Long Term Support. This tutorial follows the 26.04 LTS series, so do not automatically pick the highest version number just because a newer interim release appears on a download page.

The official 26.04 release directory also contains point releases such as 26.04.1. A point release updates installation media within the same LTS series with accumulated fixes and other changes. Installing 26.04.1 does not restart the support period from your installation date. For a new installation, select the current official 26.04 image for your architecture and record its exact filename.

The amd64 example is ubuntu-26.04.1-live-server-amd64.iso. When the point release changes, use the actual listed filename and verification files from that same directory. Do not combine an old example name with another release’s checksums.

Check both the support period and package coverage

The standard security-maintenance period for Ubuntu LTS is generally five years. Extended coverage through Ubuntu Pro and additional options is separate, and not every installed package automatically has the same support conditions. Check repository components such as Main and Universe along with the coverage of the services you use. Refer to Canonical's release lifecycle for current schedules.

A long support period is only one selection criterion. Also check that the software you intend to practice supports 26.04. If a third-party repository, driver, or container tool documents support only for another LTS, do not paste its commands into 26.04 without checking compatibility. Replacing a distribution codename in a repository address is not a substitute for confirming support.

The existing Ubuntu LTS lifecycle guide covers support end dates across releases and Ubuntu Pro in more detail. This article focuses on the decisions needed to select installation media for a 26.04 lab.

amd64 and arm64 describe architecture, not CPU brand

amd64, also called x86_64, is the architecture used by typical 64-bit Intel and AMD PCs. Despite its name, it also runs on compatible Intel 64-bit processors. arm64, also called aarch64, is the 64-bit ARM family. For an ARM host such as Apple Silicon or some Windows on ARM devices, check both an arm64 guest image and virtualization software that supports the specific host and guest.

Environment you confirmed Image to consider first Additional checks
Intel or AMD x64 PC, or an x64 VM on it amd64 Host virtualization features and the selected tool's requirements
ARM64 VM on an ARM64 host arm64 Virtualization support for that host and guest
Installation directly on a specific ARM board An official image for that device Board, boot firmware, and device support
WSL on Windows An Ubuntu distribution image supplied through the WSL installation route Ubuntu release, WSL version, and host requirements

Conventional hardware virtualization normally runs a guest from the same CPU architecture family as the host. Emulation that translates another CPU's instructions is a separate capability, with different performance and support limits. Renaming an ISO or changing the operating-system label in a VM does not convert an amd64 image into an ARM64 image.

Identify your computer's architecture

  1. Windows: Open Settings → System → About and check System type. Distinguish an x64-based processor from an ARM-based processor; “64-bit operating system” alone does not identify which family you have.
  2. macOS: Open the Apple menu → About This Mac and inspect the chip or processor. Distinguish Apple Silicon from Intel, then check the virtualization tool's supported guests.
  3. An existing Linux environment: Run the following commands in a terminal to inspect the current environment's architecture and distribution.
uname -m
cat /etc/os-release

Typically, x86_64 corresponds to amd64 and aarch64 to arm64. If you run the commands inside a VM, container, or emulated environment, they describe that execution environment. Compare them with host operating-system information when you need to identify the physical host. The guide to checking a Linux distribution and version explains why distribution, kernel, and architecture information differ.

Distinguish Server ISOs from WSL images

Select 26.04 LTS and its architecture on the Ubuntu Server download page. If ARM images use a different directory, still match filename, version, architecture, and checksums.

A Server live-server ISO starts the server installer. A .wsl file or WSL distribution image is installed through Windows WSL and differs from an ISO booted through a conventional VM’s optical drive.

A filename ending in .torrent is metadata for a BitTorrent download, rather than the ISO itself. A .manifest or .list file describes packages or files and is not an installation disk image. If the expected image does not appear in a VM's ISO selection dialog, first check the extension and whether the download has finished.

Record your choices before installation

Use the following as a planning template. Replace host and tool details with your actual environment, and match the image filename exactly. This information makes an installation question or comparison more useful than simply saying “Ubuntu does not work.”

Goal: SSH and web-service practice on Ubuntu Server
Ubuntu series: 26.04 LTS
Example image: ubuntu-26.04.1-live-server-amd64.iso
Guest architecture: amd64
Host OS and CPU: record the values you checked
Virtualization tool and version: record your selection
Image source: official download page and final release directory
Verification files: SHA256SUMS and SHA256SUMS.gpg from that directory

Selecting a file is only part of installation preparation. You also need to identify the destination disk, available host storage, console recovery route, and image-verification result. Recording that the ISO and checksum list match the same release and architecture helps avoid downloading the wrong file again.