Slicer is built and tested on many hardware and software platforms. 3D Slicer runs on modern Windows, macOS, and a variety of Linux distributions.
Read about system requirements.
Windows |
macOS |
Linux |
|
|---|---|---|---|
| Stable Release access older releases |
4.10.2
revision 28257 built 2019-05-22 |
4.10.2
revision 28257 built 2019-05-30 |
4.10.2
revision 28257 built 2019-05-22 |
| Preview Release | Not available | Not available | Not available |
It is a good practice to verify the integrity of your downloaded Slicer package by checking its checksum against the expected values.
| Package | SHA512 Checksum |
|---|---|
| Windows | 436cbe898eca1324d9f917c80f0223b79c89c367f09f7410eb2890a55f96bc1d69ffeb3702d5588f87aa1cb69b8fe51779c9611d5eb11bc8c5fdc32729a28bab |
| macOS | dc1c3d594456f4a5e8827e1bbe7ecefddbbea77e5494824f13475ed85bc202ae9cf8af1ed4a12a888206e9b39c00556030eafc7499c50089c35d61da25cf90f6 |
| Linux | 36f1b175f987e7d1e288f08d55c6942e494f1234bfdfb4ffae8517bb1711418c6ae3d5efd3f57dc31a7f65c451c8324d8c09d4de697b6b81d0a85ec48299c686 |
| Windows (preview) | Not available |
| macOS (preview) | Not available |
| Linux (preview) | Not available |
For each Slicer package listed above, we provide a SHA512 checksum. You can use this checksum to validate that your downloaded file has not been tampered with or corrupted during the download process.
How to verify the integrity of your downloaded package?
To verify the integrity of your downloaded package using the checksum, follow these general steps:
- Open a terminal window or command prompt.
- Navigate to the directory where your downloaded package is located.
- Calculate the checksum of your downloaded package by running the appropriate command for your operating system:
- Windows (using PowerShell):
Get-FileHash {package filename} -Algorithm SHA512 - macOS:
shasum -a 512 {package filename} - Linux:
sha512sum {package filename}
- Windows (using PowerShell):
- Compare the calculated checksum to the expected checksum listed above to ensure they match.
By verifying the checksum of your downloaded package, you can ensure that it has not been tampered with during the download process or otherwise corrupted.
Slicer packages are named based on the following naming convention:
For Stable Builds:
Slicer-X.Y.Z-<os>-<arch>.<extension>
For Preview Builds:
Slicer-X.Y.Z-YYYY-MM-DD-<os>-<arch>.<extension>
where:
X.Y.Z |
The version number of the application |
YYYY-MM-DD |
(only for Preview Builds) The date of the commit from which the package was built |
<os> |
The operating system for which the package was built (e.g. "win" for Windows, "macosx" for macOS, and "linux" for Linux) |
<arch> |
The architecture for which the package was built (e.g. "amd64" for 64-bit x86 architecture, and "arm64" for 64-bit ARM architecture) |
<extension> |
The extension indicating the file format of the package (e.g. ".tar.gz" for a compressed archive, or ".exe" for a Windows executable) |