SUMMARY
Although some newer versions of Nuke may work on older operating systems, they are not officially supported, and could have some issues as the application becomes updated for newer platforms. There is limited support we are able to offer in such cases, and we recommend using Nuke on a supported operating system to avoid problems. This article will outline the compatibility of Nuke and specific operating system versions.
MORE INFORMATION
Windows
Windows has had multiple iterations since Nuke’s inception, including Windows 7 through 11. Please find the supported list of Nuke versions in Windows below:
Nuke |
Windows (64-bit) |
|||
|---|---|---|---|---|
Windows 11 |
Windows 10 |
Windows 8 |
Windows 7 |
|
17.0 |
✓ |
|
|
|
16.1 |
✓ |
|
|
|
16.0 |
✓ |
✓ |
|
|
15.2 |
✓ |
✓ |
|
|
15.1 |
✓ |
✓ |
|
|
15.0 |
✓ |
✓ |
|
|
14.1 |
✓ |
✓ |
|
|
14.0 |
✓ |
✓ |
|
|
13.2 |
|
✓ |
|
|
13.1 |
|
✓ |
|
|
13.0 |
|
✓ |
|
|
12.2 |
|
✓ |
|
|
12.1 |
|
✓ |
|
|
12.0v8+ |
|
✓ |
|
|
12.0 |
|
✓ |
|
✓ |
11.3 |
|
✓ |
|
✓ |
11.2 |
|
✓ |
|
✓ |
11.1 |
|
✓ |
|
✓ |
11.0 |
|
✓ |
|
✓ |
10.5 |
|
|
✓ |
✓ |
10.0 |
|
|
✓ |
✓ |
9.0 |
|
|
✓ |
✓ |
Windows Server versions are not supported, and although Nuke may function, it could require additional setup. Please find more information in the following article: Q100575: How to resolve the “Failed to load studio-##.#.#.dll” error when launching Nuke on Windows Server
Linux
The latest Nuke versions support Rocky 9 but, previously, CentOS had been officially supported for many versions, up to CentOS 7.9. Please find the current supported list for Nuke versions on Linux here:
Nuke |
Linux (64-bit) |
|||||
|---|---|---|---|---|---|---|
Rocky 9 |
CentOS 7.6-7.9 |
CentOS 7.4-7.6 |
CentOS 7 |
CentOS/ |
CentOS/ |
|
17.0 |
✓ |
|
|
|
|
|
16.1 |
✓ |
|
|
|
|
|
16.0 |
✓ |
|
|
|
|
|
15.2 |
✓ |
|
|
|
|
|
15.1 |
✓ |
|
|
|
|
|
15.0 |
✓ |
|
|
|
|
|
14.1 |
|
✓ |
|
|
|
|
14.0 |
|
✓ |
|
|
|
|
13.2 |
|
|
✓ |
|
|
|
13.1 |
|
|
✓ |
|
|
|
13.0 |
|
|
✓ |
|
|
|
12.2 |
|
|
✓ |
|
|
|
12.1 |
|
|
✓ |
|
|
|
12.0 |
|
|
✓ |
|
|
|
11.3 |
|
|
|
✓ |
✓ |
|
11.2 |
|
|
|
✓ |
✓ |
|
11.1 |
|
|
|
✓ |
✓ |
|
11.0 |
|
|
|
✓ |
✓ |
|
10.5 |
|
|
|
|
✓ |
✓ |
10.0 |
|
|
|
|
✓ |
✓ |
9.0 |
|
|
|
|
✓ |
✓ |
Although Nuke may function on other Linux distributions, such as Ubuntu or Fedora, they are not officially supported, so there could be unforeseen issues and performance problems.
MacOS
Changes between macOS versions, most notably in 10.15 Catalina, have made older versions of Nuke incompatible. This stems from the Catalina update where stricter requirements for signing applications affected the compatibility of Foundry products.
Upgrading to macOS 10.15 or later can sometimes prevent you from opening older versions of Nuke (12.0 and earlier), so we recommend that users remain on the currently supported version of macOS found in the matrix below or in the release notes for each version.
Additionally with macOS 10.15 Catalina, Apple has removed support for 32-bit applications, including QuickTime Helper, which Nuke relies on to support several QuickTime codecs. As a result, these codecs will not be supported when using Nuke 12.1, or newer, on macOS 10.15+.
As such, Nuke versions 12.0 and below are not compatible with newer versions of macOS 10.15+, and will generally fail to launch. Please view the tested macOS versions in the following table:
Nuke |
macOS |
||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Tahoe 16 | Sequoia 15 | Sonoma 14 | Ventura 13 | Monterey 12 | Big Sur 11 | Catalina 10.15 | Mojave 10.14 | High Sierra 10.13 | Sierra 10.12 | El Capitan 10.11 | Yosemite 10.10 | Mavericks 10.9 | |
| 17.0 | ✓ |
✓ |
|
|
|
|
|
|
|
|
|
|
|
| 16.1 | ✓ |
✓ |
|
|
|
|
|
|
|
|
|
|
|
| 16.0 |
|
✓ |
✓ |
|
|
|
|
|
|
|
|
|
|
| 15.2 |
|
✓ |
✓ |
|
|
|
|
|
|
|
|
|
|
| 15.1 |
|
|
✓ |
✓ |
|
|
|
|
|
|
|
|
|
| 15.0 |
|
|
|
✓ |
✓ |
|
|
|
|
|
|
|
|
| 14.1 |
|
|
|
✓ |
✓ |
|
|
|
|
|
|
|
|
| 14.0 |
|
|
|
|
✓ |
✓ |
|
|
|
|
|
|
|
| 13.2 |
|
|
|
|
✓ |
✓ |
|
|
|
|
|
|
|
| 13.1 |
|
|
|
|
|
✓ |
✓ |
|
|
|
|
|
|
| 13.0 |
|
|
|
|
|
✓ |
✓ |
|
|
|
|
|
|
| 12.2 |
|
|
|
|
|
|
✓ |
✓ |
|
|
|
|
|
| 12.1 |
|
|
|
|
|
|
✓ |
✓ |
|
|
|
|
|
| 12.0 |
|
|
|
|
|
|
|
✓ |
✓ |
|
|
|
|
| 11.3v2+ |
|
|
|
|
|
|
|
✓ |
✓ |
|
|
|
|
| 11.3v1 |
|
|
|
|
|
|
|
|
✓ |
✓ |
|
|
|
| 11.2 |
|
|
|
|
|
|
|
|
✓ |
✓ |
|
|
|
| 11.1 |
|
|
|
|
|
|
|
|
✓ |
✓ |
|
|
|
| 11.0 |
|
|
|
|
|
|
|
|
|
✓ |
✓ |
|
|
| 10.5 |
|
|
|
|
|
|
|
|
|
|
|
✓ |
✓ |
| 10.0 |
|
|
|
|
|
|
|
|
|
|
|
✓ |
✓ |
| 9.0 |
|
|
|
|
|
|
|
|
|
|
|
|
✓ |
Apple has confirmed that macOS Tahoe (26) is the final version to support Intel based Mac machines. All future macOS releases will require Apple silicon exclusively. To align with this transition, Nuke 17.0 and 16.1 are the last release lines to support Intel based Mac machines. Starting with Nuke 17.1, Foundry updates for macOS will require Apple silicon hardware.
Nuke 14.1 and 14.0 are supported under Rosetta emulation on Apple silicon hardware. Native support is available in Nuke 15.0 and 15.1 for Apple silicon hardware.
We are aware of a change on macOS 15 (Sequoia) that could potentially prevent Foundry licensing from working, a fix was introduced in Nuke 15.1v4. More information here: Q100689: macOS 15 (Sequoia) not supported across Foundry products
FURTHER READING
- Please find additional information for installing Nuke on macOS here.
- Further macOS compatibility information is available here: Q100592: Compatibility of Foundry products with the latest Apple macOS updates
- Installing Nuke on Catalina can give a “Nuke is damaged...” error, this problem and its resolution are described here: Q100579: Nuke fails to launch on macOS with a "Nuke is damaged..." error
- Previous versions of Nuke are available for download here.
- Please find the full operating system compatibility for Nuke in each version’s release notes.
FURTHER HELP
If you are still experiencing issues when launching Foundry software after ensuring the correct software is installed for your compatible operating system, please open a Support request and let us know the exact issue encountered, and the troubleshooting steps that have been taken.
For more information on how to open a Support request, please refer to this article:
Q100064: How to raise a support ticket
We're sorry to hear that
Please tell us why