SDB:Download help
Before you download
Before downloading your version of openSUSE there are a few things you should consider.
Recommended system requirements
Make sure you meet the system requirements. openSUSE supports most PC hardware components. The following requirements should be met to ensure smooth operation of openSUSE:
- 2 Ghz dual core processor or better
- 2 GB system memory
- Over 40GB of free hard drive space
- Either a DVD drive or USB port for the installation media
- Internet access is helpful, and required for the Network Installer
Disk space
Downloading large ISO files can sometimes cause issues; here is some advice to make it easier.
- Most openSUSE ISO downloads are DVD-sized and will not fit on a 700 MB CD.
- When delivered as a single DVD ISO, openSUSE requires one download of 4.3 GB (see footnote 1)
Choose which openSUSE distribution
The openSUSE project delivers two different versions of openSUSE that you can download, install and redistribute.
- Leap - a regular release version of Linux. This means it releases annually, with security and stability updates being the priority during each release lifetime. It is not expected to change in any significant way until its next annual release. Leap shares a Common Base System with SUSE Linux Enterprise, so major architectural changes are not expected for several years, aligned with each new Major Release (eg 12, 13, etc) of SUSE Linux Enterprise. Leap is recommended for Sysadmins, Enterprise Developers, and "Regular" Desktop Users.
- Tumbleweed - a rolling release version of Linux. This means the software is always the latest stable versions available from the openSUSE Project. Things will change regularly as Free and Open Source projects continually release new versions of their software. Tumbleweed is recommended for Developers, openSUSE Contributors, and Linux/FOSS Enthusiasts.
Choose the installation type
Local installation
When you choose this installation type, you download CD/DVD images that hold the openSUSE installation sources to your local computer and proceed from there. This has several advantages.
- You don't depend on an Internet connection during the installation
- You can share the data on different computers
- You can reuse the data at any time later
But it has its downsides as well.
- You transfer a lot of data that you don't actually need
- Due to size limitations of CDs/DVDs, you get only a subset of all packaged software for openSUSE.
Workflow for the local installation
- Download ISO images.
- Burn ISO images to blank CD/DVD
- Boot your system with the CD/DVD
- Install openSUSE
Network installation
If you choose this installation type, you download a small boot medium to start the installation from and the YaST installer does the rest for you. This method also has several advantages.
- You do not download everything, but just the data you need
- You need only one blank CD
- The Internet installation source contains all packaged software for openSUSE
Of course, it also has its downsides.
- You depend on an Internet connection during the installation
- It may be very slow depending upon the load of the server and your internet connection speed
- It may not be possible to connect to the Internet if your network card is not recognized
Workflow for the network installation
- Download the boot CD image. The latest NET CDs are in the Factory repository, but before you use it read the article about Factory.
- Burn the boot CD image.
- Boot your computer from the boot CD.
- Point the YaST installer to the installation repository (by pressing F3 and then F4)
- Install openSUSE.
Learn more about Network installation.
Choose the download protocol
Downloading via HTTP
You could download the openSUSE disk images like you would download a normal file, and just click on the link on the Download page in your web browser. However it's strongly recommended that you use a proper download manager to reduce the risk of corrupted data when doing such a large download.
- If you use Linux to download, we recommend that you use the commandline tool wget. wget is able to continue the download later after an interruption by adding -c to the wget parameters. A reconnection after a temporary disconnection happens automatically, even without -c. For more information about wget read man wget.
- If you use an older Linux or Unix to download, we recommend that you use the commandline tool curl, like this: curl -C - -O URL. For more information read man curl.
- If you use Mac OS or Windows, use your favorite download tool meeting the above requirements.
Downloading via BitTorrent
BitTorrent is an open source peer-to-peer file sharing protocol , designed for sharing large software and media files. Its advantage over plain HTTP is that the clients protect against data corruption, and when multiple downloads of the same file happen concurrently, the downloaders upload to each other, making it possible for the file source to support very large numbers of downloaders with only a modest increase in its load. If enough people participate it will also be faster than the centralized servers - for everybody.
The workflow is simple : once you have downloaded and installed a client, you can start a BitTorrent download by clicking a *.torrent download link in your browser.
- If you use openSUSE, we recommend that you use the generic BitTorrent client or the KTorrent client. An alternative light-weight command line client is aria2 (Build Service packages here)
- If you use Windows, three popular options are to use Vuze (be sure you have the Java JRE installed on your computer), the light-weight µTorrent or the original BitTorrent client.
Other BitTorrent clients programs are available for several platforms. You can find links to some BitTorrent clients on the official BitTorrent Web page. For the exact download procedure, look at the documentation for the client you use.
Downloading via Metalinks
Metalinks are an XML format, used by download managers, that contain the mirror and P2P locations of a file along with checksums. Metalink clients offer download resuming, downloading from multiple sources (both mirrors and P2P) simultaneously, automatic checksum verification, and automatic error repair (depending on client used), among other features. Hence using metalinks can deliver higher availability and reliability, self healing downloads, and very fast transfer speeds.
- DownThemAll!, a Firefox plugin, is one of the easiest way to use Metalinks.
- aria2 is the recommended Unix command line client (packages here).
- wxDownload Fast is available for some distributions and has a GUI (packages here).
- KGet is a GUI client from KDE Applications. Available with standard repositories.
- Speed Download is available for Mac OS.
- Orbit Downloader and GetRight are available on Windows. There are other clients available for Mac OS, Windows, and Unix.
The metalinks are served by the openSUSE download redirector. You can find metalinks for all ISO images below the address http://download.opensuse.org/distribution/openSUSE-current/iso/.
For usage and more information, see Metalinks.
Checksums
Before you burn your CD/DVD images, you should check the files for errors. A file named <some>.iso.sha256 is available. This file contains hashes for the corresponding ISO image that is available from that download location. The relevant line of the checksum would look like the following:
8abac6680ecc152f103006b02f9ff67f some.iso
These *.iso.sha256 files are also GPG signed by openSUSE (as an additional safeguard - read on below how to verify the signature). For newer images the signature is in a separate *.iso.sha256.asc file, for older images the signature is directly in the *.iso.sha256 file (you may see a warning when the SHA256 checksum is computed).
To be sure that the download did not contain any errors, you should create this number using the SHA256 algorithm for your own ISO image and compare with the value found in the corresponding <some>.iso.sha256 file. Your CD/DVD image burning software may have this feature built-in, in which case check you are using the newer SHA256 algorithm (instead of perhaps older the MD5).
To verify the checksum automatically at a command prompt, type:
sha256sum -c <some>.iso.sha256
If the checksum matches then amongst the output you will see a line like:
<some>.iso: OK
If there is any difference between the output of the checksum command and the above number, the download is broken and should be repeated or repaired.
With older images sha256sum will warn that some of the lines are improperly formatted, because it is doesn't understand/process the GPG signature which is also found in the checksum file.
To verify the GPG signature at the command prompt you first need to import the Project's signing key with the following commands:
gpg --recv-keys 0xAD485664E901B867051AB15F35A2F86E29B700A4 # If you experience a "Failed to receive key from key server: no name" error, try this instead: # This used to point to pgp.mit.edu, but since these servers have become so slow (nearly unusable), recommended to use other keyservers, such as # the one from ubuntu. gpg --keyserver keyserver.ubuntu.com --recv-keys 0xAD485664E901B867051AB15F35A2F86E29B700A4
gpg --fingerprint "openSUSE Project Signing Key <opensuse@opensuse.org>"
Note that as of January 2023, there is a new version (rsa4096, expiring 2026-06-19) of the project key (referenced above). The previous version (rsa2048, expiring 2024-05-02) has fingerprint 22C07BA534178CD02EFE22AAB88B2FD43DBDC284.
For Leap 15.3/Tumbleweed/MicroOS/Kubic:
Download the corresponding .asc file for your .sha256 checksum file from https://download.opensuse.org/tumbleweed/iso/ for Tumbleweed, MicroOS and Kubic. Or from https://download.opensuse.org/tumbleweed/appliances/ for Tumbleweed, MicroOS and JeOS appliances. Or from https://download.opensuse.org/distribution/leap/15.3/iso/ for Leap 15.3. (You can download it using your browser from the same address.) For example:
wget https://download.opensuse.org/tumbleweed/iso/<some>.iso.sha256.asc
Now you can verify the signature with:
gpg --verify <some>.iso.sha256.asc <some>.iso.sha256
Example: Verify Tumbleweed Netinstall
Download the following files from http://download.opensuse.org/tumbleweed/iso/ and verify checksum:
karl@erlangen:~/Downloads> ls -1 openSUSE-Tumbleweed-NET-x86_64-Snapshot20200416-Media.* openSUSE-Tumbleweed-NET-x86_64-Snapshot20200416-Media.iso openSUSE-Tumbleweed-NET-x86_64-Snapshot20200416-Media.iso.sha256 openSUSE-Tumbleweed-NET-x86_64-Snapshot20200416-Media.iso.sha256.asc
Get the openSUSE public repository key from:
- OBS (osc signkey openSUSE), or
- gpg --import < /usr/lib/rpm/gnupg/keys/gpg-pubkey-3dbdc284-53674dd4.asc from openSUSE-build-key package
- import it from here,
gpg --import <<END
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2.0.15 (GNU/Linux)
mQENBEkUTD8BCADWLy5d5IpJedHQQSXkC1VK/oAZlJEeBVpSZjMCn8LiHaI9Wq3G
3Vp6wvsP1b3kssJGzVFNctdXt5tjvOLxvrEfRJuGfqHTKILByqLzkeyWawbFNfSQ
93/8OunfSTXC1Sx3hgsNXQuOrNVKrDAQUqT620/jj94xNIg09bLSxsjN6EeTvyiO
mtE9H1J03o9tY6meNL/gcQhxBvwuo205np0JojYBP0pOfN8l9hnIOLkA0yu4ZXig
oKOVmf4iTjX4NImIWldT+UaWTO18NWcCrujtgHueytwYLBNV5N0oJIP2VYuLZfSD
VYuPllv7c6O2UEOXJsdbQaVuzU1HLocDyipnABEBAAG0NG9wZW5TVVNFIFByb2pl
Y3QgU2lnbmluZyBLZXkgPG9wZW5zdXNlQG9wZW5zdXNlLm9yZz6JATwEEwECACYC
GwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAUCU2dN1AUJHR8ElQAKCRC4iy/UPb3C
hGQrB/9teCZ3Nt8vHE0SC5NmYMAE1Spcjkzx6M4r4C70AVTMEQh/8BvgmwkKP/qI
CWo2vC1hMXRgLg/TnTtFDq7kW+mHsCXmf5OLh2qOWCKi55Vitlf6bmH7n+h34Sha
Ei8gAObSpZSF8BzPGl6v0QmEaGKM3O1oUbbB3Z8i6w21CTg7dbU5vGR8Yhi9rNtr
hqrPS+q2yftjNbsODagaOUb85ESfQGx/LqoMePD+7MqGpAXjKMZqsEDP0TbxTwSk
4UKnF4zFCYHPLK3y/hSH5SEJwwPY11l6JGdC1Ue8Zzaj7f//axUs/hTC0UZaEE+a
5v4gbqOcigKaFs9Lc3Bj8b/lE10Y
=i2TA
-----END PGP PUBLIC KEY BLOCK-----
END
# gpg --verify openSUSE-Tumbleweed-NET-x86_64-Current.iso.sha256.asc
gpg: assuming signed data in 'openSUSE-Tumbleweed-NET-x86_64-Current.iso.sha256'
gpg: Signature made Mon 07 Nov 2022 11:04:07 PM CET
gpg: using RSA key B88B2FD43DBDC284
gpg: Good signature from "openSUSE Project Signing Key <opensuse@opensuse.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 22C0 7BA5 3417 8CD0 2EFE 22AA B88B 2FD4 3DBD C284
karl@erlangen:~/Downloads> sha256sum -c openSUSE-Tumbleweed-NET-x86_64-Snapshot20200416-Media.iso.sha256
openSUSE-Tumbleweed-NET-x86_64-Snapshot20200416-Media.iso: OK
karl@erlangen:~/Downloads>
For old Leap images without separate .asc file:
gpg --verify <some>.iso.sha256
You will get output showing when the file was signed and confirming the fingerprint, like:
gpg: Signature made Fri 21 Jul 2017 11:10:22 BST using RSA key ID 3DBDC284 gpg: Good signature from "openSUSE Project Signing Key <opensuse@opensuse.org>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 22C0 7BA5 3417 8CD0 2EFE 22AA B88B 2FD4 3DBD C284
Check the key fingerprint matches the published project key (see above).
Please refer to the GPG documentation about the trusted signature warning message, it does not indicate a problem but only the fact that you have not signed the key yourself.
Again, if the output differs (words like BAD, CRC error or no signature found are a sure sign of problems) then you should check the integrity of your downloaded files and their origin.
Repairing a download
If you are using Linux as operating system, you may repair broken ISO downloads with the command rsync. To do that, choose a mirror that supports this protocol from the mirror list and enter the following:
rsync rsync://<name-of-mirror>/<opensuse-directory>/
This will show the content of the directory on the server. By appending the names of the subdirectories to the command, you can get to the directory where the ISO is located on the remote computer. Then
touch <path-to-your-local-ISO-file> rsync -avP rsync://<name-of-mirror>/<path-to-remote-ISO-file> <path-to-your-local-ISO-file>
will repair the file, only downloading the needed data to correct it. For further information please refer to the manpage of rsync, by entering (in a shell):
man rsync
Burn the ISO image(s) to DVD
Using Linux
After successfully downloading the ISO image(s), use the burning application of your choice to burn the ISO file(s) to a blank CD or a blank DVD (Note that from 12.3 on, the ISO won't fit onto a CD anymore, use a USB-stick instead). On systems running openSUSE, use the K3B or Brasero program to burn the discs. Select the option that allows burning a CD or DVD image and/or a ISO9660 file system. Do not burn the ISO image(s) the same way as you would burn files.
From the command line you can use the program cdrecord.
cdrecord dev=/dev/cdrecorder speed=44 driveropts=burnproof -dao -eject -v isofile
Using Microsoft Windows
Windows 10
- Use ImgBurn.
Windows 7/8
- Right-click on the ISO image and choose 'Burn disc image'.
- Select a disc burner (drive) and choose 'Burn'. If you check 'Verify disc after burning', it will confirm that the ISO image has been burned correctly.
Using MacOS X (10.3 and above)
In the Finder, open the Go menu and select Utilities. In the Utilities folder you will find an application called Disk Utility. Open it, then drag and drop the downloaded ISO image in to the left hand sidebar. Select the image, click Burn and insert your CD/DVD. For more information check Apple's support page on the subject.
Make a bootable Live USB stick
Refer to this how-to if using Linux, MacOS, or Windows: SDB:Live USB stick
Troubleshooting downloads
Downloading large files such as ISO images is sometimes difficult. Here are some tips for avoiding the most common issues:
- 'Not-enough-space' error may occur if the DVD ISO is being downloaded to a FAT32 file system, despite the fact that your drive may say you have enough space. The FAT32 file system has a file size limit of 4 GiB minus 1 byte (or 4,294,967,295 bytes), and therefore the DVD ISO (4.7GB = 4.3GiB) will not fit. To resolve this, download ISOs for Network install or download to another drive.
- Consider using a download manager that supports resume: we strongly suggest this kind of software because if download problems occur, the resume function allows you to continue a download made earlier rather than having to start over again. Many download managers also now support checksum verification, which is recommended. Choose a download manager with the features you need from this comprehensive list.
- Proxy has a download size limitation ? : when downloading the DVD ISO, make sure that your proxy and your download client support files 4.3GiB or larger.