Choose the image that matches your architecture and use case.

openSUSE Leap is the regular-release member of the openSUSE family, combining community development with a stable enterprise-oriented foundation. Leap 16.0 provides graphical and server installation options, YaST administration tools and a predictable lifecycle.
openSUSE Leap is primarily suited to daily desktop use, study, web browsing and productivity; servers, virtual machines and self-hosted services; managed infrastructure where predictable maintenance is important. Before choosing it, compare the current release lifecycle with the length of support required for the machine. This distribution is based on suse, which influences package formats, repositories and much of the available documentation. The listed desktop environment is KDE Plasma, GNOME and Xfce; confirm its memory, graphics and accessibility requirements on the official project site. The best choice depends on hardware support, preferred software, update policy and the amount of system administration the user wants to perform.
Read the release notes and installation guide before downloading. Select an image that matches the processor architecture and intended use: desktop, server, live media, virtual machine or another published edition. Test Wi-Fi, graphics, audio, storage and suspend from live media when that option is available. Back up important files before repartitioning, encryption changes or dual-boot installation. For production deployment, verify application compatibility, upgrade paths, backup restoration and the project security-support policy in a non-production environment first. Download from an official project page or mirror, compare the published SHA-256 checksum, and verify a signed checksum when the project provides one. After installation, apply updates before adding third-party repositories or drivers.
10 GB is for a minimal installation; graphical installation needs at least 16 GB and Btrfs snapshots recommend a 40 GB root partition.
The download button first records an anonymous aggregated download counter and then redirects to the official source.
A project-specific post-installation checklist. Commands are displayed for your own equipment; the website never runs them. Use an authorized administrator account when required.
Save important files independently of filesystem snapshots.
Before you continue: A root snapshot is not an external backup.
Read project documentation: Back up user dataInspect repository URLs and priorities for this edition.
Before you continue: Never mix Leap and Tumbleweed repositories.
zypper lr -uRead project documentation: Check repository alignmentIf Snapper is configured, list recovery snapshots before changes.
Before you continue: Availability depends on filesystem and installation layout.
sudo snapper listRead project documentation: Inspect Snapper protectionRefresh repository metadata and stop on unexpected trust errors.
Before you continue: Verify unexpected signing keys instead of accepting blindly.
sudo zypper refreshRead project documentation: Refresh signed metadataApply routine package updates without switching release repositories.
Before you continue: Read the transaction and resolve conflicts deliberately; restart when required.
sudo zypper updateRead project documentation: Update within this Leap releaseAvoid adding an unrelated repository just to obtain one package.
Before you continue: Do not force vendor changes without understanding dependencies.
Read project documentation: Review the selected repository sourcesMonitor snapshot retention and available space after updates.
Before you continue: Do not remove the only known-working recovery point.
Read project documentation: Review snapshot storageRead the recovery procedure for your filesystem layout before attempting rollback.
Before you continue: Snapshots can exclude user and application data.
Read project documentation: Understand snapshot recovery limits