Open Source Display Calibration and Characterization powered by ArgyllCMS

DisplayCAL

DisplayCAL 3.8.7.0

  -  24.46 MB  -  Open Source
  • Latest Version

    DisplayCAL 3.8.9.3

  • Operating System

    Windows XP / Vista / Windows 7 / Windows 8 / Windows 10

  • User Rating

    Click to vote
  • Author / Product

    Florian Hoch / External Link

  • Filename

    DisplayCAL-3.8.7.0-Setup.exe

  • MD5 Checksum

    95f747eaa09bae89fe817a9aceca1ddd

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system.

Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of DisplayCAL 3.8.7.0.


For those interested in downloading the most recent release of DisplayCAL or reading our review, simply click here.


All old versions distributed on our website are completely virus-free and available for download at no cost.


We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

  • DisplayCAL 3.8.7.0 Screenshots

    The images below have been resized. Click on them to view the screenshots in full size.

    DisplayCAL 3.8.7.0 Screenshot 1
  • DisplayCAL 3.8.7.0 Screenshot 2
  • DisplayCAL 3.8.7.0 Screenshot 3
  • DisplayCAL 3.8.7.0 Screenshot 4

What's new in this version:

- Enhancement Profile loader (Windows): A scheduled task now restarts the profile loader after resume from standby/hibernation as well as daily at 04:00 AM (whichever comes first), to mitigate the Windows GDI SetDeviceGammaRamp API leaking memory since Windows 10 1903

Fixed in this release:
- Trivial Don't automatically disable interactive display adjustment when setting calibration tone curve to “As measured” (unintended behavioral change introduced in DisplayCAL 3.8.6, SVN revision r6194)
- Minor Linux (GNOME on Wayland): Latency incurred by a large measurement window size was not accounted for, introducing the possibility of measurements failing due to loss of synchronization