DisplayCAL System Requirements (Windows / macOS / Linux)

DisplayCAL does not publish strict, formal hardware minimums – it is a relatively lightweight application whose heavy lifting is done by the bundled ArgyllCMS measurement engine. In practice, any reasonably modern computer with a free USB port for your colorimeter will run it. The tables below lay out what you need on each platform for the current release, DisplayCAL 3.9.19.

Windows System Requirements

Windows notes: only 64-bit builds are provided for current releases – the bundled Python 3 runtime and ArgyllCMS components are 64-bit. If you are still on the legacy 3.8.9.3 line for an old 32-bit system, see DisplayCAL vs DisplayCAL-py3 before deciding. Administrator rights are needed for the standard installer, since it registers components system-wide.

macOS System Requirements

macOS Gatekeeper may refuse to open the app on first launch because it is not notarized by Apple. If that happens, remove the quarantine flag with:

xattr -dr com.apple.quarantine /Applications/DisplayCAL.app

Run that in Terminal (adjust the path if you installed it elsewhere), then launch the app normally. This is a standard workaround for open-source macOS software and does not modify the application itself.

Linux System Requirements

The AppImage and Flatpak builds bundle everything DisplayCAL needs, which makes them the simplest choice if your distribution's repositories carry an outdated version. The Flatpak runs sandboxed; if your colorimeter is not detected inside the sandbox, check the Flatpak's device permissions for USB access.

Do I Need to Install Python?

No. DisplayCAL-py3 is called "py3" because it was ported from Python 2 to Python 3 – but the builds you download already include their own bundled Python 3 runtime. You do not need to install Python separately, and you do not need to manage virtual environments or pip packages. Just install DisplayCAL and launch it. This is one of the practical advantages of the py3 branch over the old 3.8.9.3 line, which depended on an end-of-life Python 2.7 installation.

ArgyllCMS 3.5.0 Requirement

DisplayCAL is a graphical front-end: the actual instrument communication, patch generation, and profile computation are performed by ArgyllCMS, the open-source color management engine by Graeme Gill. DisplayCAL 3.9.x is built to work with ArgyllCMS 3.5.0 (released February 4, 2026).

You do not normally need to install ArgyllCMS by hand – current DisplayCAL packages integrate with it – but the version pairing matters: 3.9.18 added explicit 3.5.0 compatibility, so pairing a current DisplayCAL with a much older ArgyllCMS is not recommended. If you are curious about what ArgyllCMS does behind the scenes, our ArgyllCMS overview explains the relationship between the two projects.

Colorimeter and USB Requirements

You cannot calibrate a display with software alone – you need a measurement instrument (a colorimeter or spectrophotometer) plugged into a USB port. DisplayCAL supports a wide range of instruments through ArgyllCMS, including:

• X-Rite i1Display family – i1Display Pro, i1Display Pro Plus, i1Display Studio, and the rebranded ColorMunki Display, among the most popular choices for DisplayCAL users.
• Datacolor Spyder family – including the current SpyderX2 (Spyder2024), supported since DisplayCAL 3.9.18, plus earlier Spyder models.
• X-Rite i1Pro spectrophotometers and other ArgyllCMS-supported spectrophotometers for users who want reference-grade measurements.

Practical USB advice: plug the instrument directly into the computer (or a powered hub) rather than through an unpowered hub or a monitor's USB pass-through – flaky USB connections are a classic cause of "instrument not found" errors. On Windows, let the driver installation finish before launching DisplayCAL; on Linux, make sure the ArgyllCMS udev rules are installed so the device node is accessible to your user account.

How DisplayCAL Uses Your Hardware

DisplayCAL is not a demanding application. The heavy mathematics – generating test patches and computing the profile – runs on your CPU through the ArgyllCMS engine, and applying the finished profile is handled by your operating system's color management together with your graphics card's gamma tables (the video LUT). A few practical consequences:

• Integrated graphics are fine. You do not need a discrete GPU to calibrate a display. Any modern integrated or dedicated graphics chip supports the gamma-table loading that profile installation relies on.
• Deep-color pipelines depend on your OS and drivers. DisplayCAL can generate high-quality LUT profiles, but whether a 10-bit output chain is actually active depends on your operating system, GPU driver, and display connection – that part is outside DisplayCAL's control.
• Calibrate each display separately. DisplayCAL works on one display at a time. A laptop with an external monitor means two separate calibration runs and two separate ICC profiles – never copy a profile from one display to another.
• Do not calibrate through remote desktop or a virtual machine. RDP sessions and VMs do not expose the physical display's real color pipeline, so any profile built that way is meaningless on the actual screen.

Keeping Your Setup Current

A calibration setup is not install-and-forget. Three maintenance habits keep it trustworthy:

• Re-verify after major OS upgrades. Moving from Windows 10 to 11 or installing a new macOS release can reset display settings or driver behavior. Run one verification measurement afterwards; reinstall DisplayCAL if your instrument is no longer detected.
• Watch for instrument aging. Colorimeter filters drift slowly over years. If fresh profiles stop looking right on a display you know well, compare against a second instrument or a known reference before blaming the software.
• Keep ArgyllCMS matched to your DisplayCAL release. DisplayCAL 3.9.x targets ArgyllCMS 3.5.0. Mixing a current DisplayCAL with a much older – or much newer, untested – ArgyllCMS build is asking for subtle measurement problems.

Frequently Asked Questions