How to Calibrate a TV with DisplayCAL (2026 Guide)

Calibrate your TV with DisplayCAL over HDMI: the full workflow — TV prep checklist, pattern generator setup, Rec.709 targets, and how TV calibration differs from monitor calibration.

Can You Calibrate a TV with DisplayCAL? Yes.

TVs are just big displays with HDMI inputs — and DisplayCAL can drive them like any other monitor. Connect a laptop to the TV over HDMI, run DisplayCAL’s pattern generator fullscreen on the TV, and measure with your colorimeter. This is the same approach professional calibrators use with pattern generators costing thousands; DisplayCAL gives you the workflow for free. (SmallHD’s official user guides even reference DisplayCAL in their monitor calibration workflows — the technique is industry-recognized.)

What You Need

• A colorimeter — the Calibrite Display Pro HL or Spyder X2 Elite both work; the sensor sits on the TV screen just like on a monitor.
• A laptop with HDMI out (or DisplayPort→HDMI) running DisplayCAL + ArgyllCMS.
• 30–60 minutes in a dim room.

Disclosure: this page contains affiliate links. If you buy through them, we may earn a commission at no extra cost to you.

Step 1: Prepare the TV (Critical)

Calibration can’t fix a TV fighting itself. Before measuring, set the picture mode and disable every “enhancement”:

• Picture mode: Filmmaker Mode, ISF, or Cinema/Movie — whichever is closest to reference on your set.
• Turn OFF: dynamic contrast, dynamic brightness / eco sensor, noise reduction, MPEG artifact reduction, motion interpolation (soap-opera effect), edge enhancement, “vivid”/”dynamic” color.
• Color temperature: Warm2 / Warm (closest to D65 on most brands).
• HDMI black level / RGB range: match the laptop output (Full/Limited) — mismatch here crushes blacks regardless of calibration.
• Backlight/OLED light: set for your room; you’ll fine-tune brightness during calibration.

Step 2: Connect and Configure DisplayCAL

1. Connect the laptop to the TV via HDMI and set the TV as the display device in DisplayCAL’s dropdown (use “Identify displays” if unsure).
2. In DisplayCAL, the built-in pattern generator shows fullscreen patches on the chosen display — no extra hardware needed. (Advanced users can use madVR as an external pattern generator; see our madVR 3D LUT guide.)
3. Set calibration targets for SDR TV: D65 white point, gamma 2.4 (dark room) or 2.2 (bright room), Rec.709 gamut, ~100–120 cd/m² brightness.

Step 3: Calibrate, Profile, Verify

Run the standard workflow from our quickstart guide: interactive display adjustment (use the TV’s own brightness/contrast/RGB controls first — always prefer display controls over software correction), then calibration + profiling. Finish with a verification report to confirm the result. Note: the ICC profile mainly benefits a PC connected to the TV; the calibration itself (white point, gamma, grayscale) is baked into the TV’s settings, which is what movie watching uses.

TV vs Monitor Calibration: Key Differences

What About HDR TVs?

Be honest with yourself here: start with SDR. HDR calibration on TVs involves tone-mapping behavior that varies wildly between manufacturers, and DisplayCAL’s HDR support is still maturing (see our HDR calibration guide for the current state). A well-done SDR calibration (Rec.709, gamma 2.4, D65) already transforms most TVs, because the majority of content — broadcast, streaming SDR, YouTube — is SDR. Treat HDR as phase two, after you’ve nailed the SDR workflow on this page.

HDMI Chain Gotchas

• AV receivers / soundbars in the chain: they can alter the signal (or report a different EDID). For calibration, connect the laptop directly to the TV, then restore your normal chain afterward.
• RGB range mismatch (Full vs Limited) is the #1 cause of crushed blacks on TV setups — verify the laptop output and the TV’s HDMI black level agree before measuring.
• HDMI port matters: some TVs only enable full bandwidth / 4:4:4 chroma on specific ports — check your manual.
• Disable ALLM/VRR quirks: game-mode processing can change gamma behavior; calibrate in the mode you’ll actually watch in.

Calibrating Multiple Inputs

Most TVs store picture settings per input (and sometimes per signal type — SDR vs HDR memories are separate). Calibrate the input your main source uses; if you split viewing between a streamer box and a console on different inputs, copy the calibrated settings across and spot-check with test patterns. The measurement work doesn’t need repeating per input if the panel behavior is identical — but verify, because some TVs apply different processing per input.

How Often to Recalibrate a TV

LED/LCD TVs drift slowly — once or twice a year is plenty for most people. OLED TVs drift faster as the emitters age (especially with heavy static-element viewing), so every 3–6 months is reasonable for enthusiasts. Projectors with lamps need recalibration as the lamp dims — roughly every 500–1,000 hours; laser projectors are far more stable. See our projector guide for the big-screen specifics.

Calibrating a TV for Gaming (PS5 / Xbox)

Gamers: calibrate in Game Mode, because that’s the mode you’ll play in — and Game Mode often has different gamma/EOTF behavior than Cinema modes. Targets stay the same (D65, gamma 2.2 for a lit room), but keep input lag in mind: any extra processing you enable for “better” picture costs milliseconds. The usual recipe is Game Mode + Warm2 color temp + all enhancements off + a basic grayscale calibration. Note the same caveat as monitors: consoles don’t use ICC profiles, so what matters is the calibration baked into the TV’s settings. Our gaming monitor guide covers the PC side of the same principles.

Projector Owners: Same Ideas, Bigger Screen

Everything on this page applies to projectors, with three twists: ambient light control matters more (a projector can’t outshine a bright room), lamp age shifts color (recalibrate every 500–1,000 lamp hours; laser is stable), and screen material tints the result (measure off the screen, not the lens). We wrote a dedicated projector calibration guide covering throw distance, screen gain, and lamp vs laser maintenance schedules.

Frequently Asked Questions

Can I calibrate my TV without a colorimeter?

Not accurately — but you can get surprisingly far with the prep checklist above (Filmmaker Mode, Warm2, enhancements off) plus free test patterns. A colorimeter is what turns “close” into “correct”.

Does the ICC profile work for Netflix on the TV itself?

No. ICC profiles only apply to PC output. For the TV’s built-in apps, what matters is the calibration baked into the TV’s picture settings (white balance, gamma) — which is exactly what this guide sets.

What gamma should I target for TV calibration?

2.4 (BT.1886) for a dark home theater room, 2.2 for a bright living room. DisplayCAL lets you pick either target.

Will calibration fix motion smoothing or input lag?

No — those are processing features, not color. Turn motion interpolation off for movies (it’s a preference), and use Game Mode for gaming regardless of calibration.

]]> https://displaycal.org/calibrate-tv-with-displaycal/feed/ 0 https://displaycal.org/how-to-install-icc-profile/ https://displaycal.org/how-to-install-icc-profile/#respond Sat, 17 Oct 2026 09:17:28 +0000 https://displaycal.org/how-to-install-icc-profile/

How to Install an ICC Profile (Windows 11, macOS, Linux)

Step-by-step 2026 instructions for installing ICC color profiles on Windows 11, macOS, and Linux — plus how DisplayCAL-generated profiles differ and why borrowed profiles are unreliable.

What an ICC Profile Actually Does

An ICC profile is a small file that describes how your specific display reproduces color. Your operating system (and color-managed apps like Photoshop, Lightroom, and Chrome) uses it to translate colors correctly. Installing a profile doesn’t change your monitor’s hardware — it tells software how to compensate for your panel’s quirks. Profiles you generate yourself with DisplayCAL are the most accurate; downloaded profiles are a gamble, as explained below.

Windows 11

1. Open Settings → System → Display → Advanced display, then click Color management (on older builds: search “Color Management” in Start to open colorcpl.exe).
2. Select your display at the top, check “Use my settings for this device”.
3. Click Add, then Browse and select your .icc / .icm file. (Double-clicking a profile file also offers an “Install Profile” option, which copies it to the system color folder.)
4. Select the profile in the list and click “Set as Default Profile”.
5. If you calibrated with DisplayCAL, make sure the DisplayCAL Profile Loader runs at startup — it applies the calibration curves (vcgt) that Windows alone won’t load. See our Profile Loader guide.

macOS

1. Open System Settings → Displays, select your display, and open the Color profile dropdown.
2. Click Customize… — profiles in ~/Library/ColorSync/Profiles (double-click any .icc file to copy it there) appear in the list.
3. Select your profile. macOS applies it immediately, per display.
4. To verify, open ColorSync Utility (in /Applications/Utilities) — it shows the active profile and lets you inspect its tags.

Note: on Apple Silicon Macs with Studio Display or Pro Display XDR, macOS manages some calibration through its own “Fine-Tune Calibration” flow; a DisplayCAL profile still works for verification and for third-party displays. Our macOS reboot fix covers the known issue where profiles don’t reload after restart.

Linux

1. GNOME: Open Settings → Color, select your display, click Add profile and choose your .icc file. GNOME’s colord integration assigns it to the display.
2. KDE Plasma: System Settings → Color Management → Add Profile, then assign it to the correct output.
3. Manual / window managers: DisplayCAL installs dispwin (part of ArgyllCMS) — dispwin -I profile.icc installs and activates a profile from the terminal.
4. If your instrument isn’t detected on Linux, check udev permissions — see instrument not detected.

Installing a Profile Made by DisplayCAL

When DisplayCAL finishes profiling, it can install the profile for you automatically (enable “Install profile” and “Load calibration” in the profiling options). The two parts matter: the ICC profile (color translation for apps) and the calibration curves / vcgt (loaded into the graphics card). The Profile Loader handles the second part at every login — without it, you get the profile but not the calibration. That distinction trips up many users; our troubleshooting hub covers it in depth.

Can I Use Someone Else’s ICC Profile?

Honest answer: not reliably. Two units of the same monitor model can differ noticeably — backlight tint, panel lottery, age, and even the firmware revision all shift color response. A downloaded profile for “your exact model” is better than nothing and sometimes looks fine, but it can also make things worse. If you can’t profile your own display yet, use a shared profile only as a temporary starting point, and treat any unit-specific claims (“perfect for LG 27GP950”) with skepticism. The real fix remains measuring your own panel — see why free software plus a colorimeter beats any download.

Letting DisplayCAL Handle Installation Automatically

If the profile came from DisplayCAL itself, you usually don’t need any of the manual steps above. In the profiling settings, enable “Install profile” and “Load calibration curves” before you start measuring. When profiling finishes, DisplayCAL installs the ICC profile into the right system folder, associates it with the correct display, and — via the Profile Loader — makes sure the calibration curves load at every login. Manual installation is mainly for profiles you received as files (from a colleague, a download, or an older backup).

Multi-Monitor Setups: One Profile Per Display

Every display needs its own profile — even two units of the same model. On Windows, the Color Management dialog lets you assign a different default profile per display (select the display at the top first). On macOS, profiles are per-display in System Settings. On Linux, GNOME Settings → Color handles each output separately. DisplayCAL’s workflow naturally produces one profile per display; our multi-monitor matching guide covers making them look consistent with each other.

Troubleshooting: Profile Won’t Stick

• Profile applies but colors look uncalibrated after reboot: the calibration curves (vcgt) aren’t loading — check the Profile Loader autostart. Guide · macOS-specific fix.
• Windows Update reset everything: GPU driver updates can wipe the LUT; re-apply via the Profile Loader or re-run dispwin.
• Fullscreen games look different: expected — most games bypass ICC profiles in exclusive fullscreen. Why, and the workaround.
• Two profiles fighting: make sure only one default profile is set per display, and that no vendor utility (e.g. NVIDIA Control Panel color settings) is also adjusting the desktop.

More: troubleshooting hub.

How to Remove or Switch Profiles

Windows: Color Management → select the display → pick another profile as default, or remove the file from the color folder. macOS: System Settings → Displays → Color profile → choose another. Linux: Settings → Color → remove, or dispwin -c to clear. If DisplayCAL’s Profile Loader is managing the display, disable its autostart entry first so it doesn’t re-apply the old calibration at login.

Naming and Organizing Your Profiles

Adopt a naming scheme before you accumulate a mess: DisplayModel_Date_Conditions.icc — e.g. LG-27GP950_2026-10_D65-120nits.icc. DisplayCAL can auto-generate descriptive names from its settings; keep that enabled. Store originals somewhere safe (cloud drive, NAS) because OS reinstalls wipe system color folders. When testing a new calibration, keep the old profile installed but not default — switching back takes seconds if the new one looks wrong.

Backing Up Your Profiles

An ICC profile is a small file — back it up like one. Copy .icc/.icm files to external storage after each calibration, along with a text note of the targets used (white point, brightness, gamma). If you move to a new computer with the same monitor, the old profile is a reasonable starting point — but re-profile when you can, since the graphics card and OS color pipeline differ between machines. DisplayCAL’s quickstart makes the second run fast.

Frequently Asked Questions

Where are ICC profiles stored?

Windows: C:\Windows\System32\spool\drivers\color. macOS: ~/Library/ColorSync/Profiles (user) or /Library/ColorSync/Profiles (system). Linux: ~/.local/share/icc (user) or /usr/share/color/icc (system).

Why did my profile stop applying after a reboot?

On Windows this usually means the calibration loader isn’t running at startup; on macOS it’s a known DisplayCAL issue with a documented workaround. GPU driver updates can also reset the graphics-card LUT — see troubleshooting.

Do I need administrator rights to install a profile?

For your own user account, no — installing to the user profile folder works without admin rights on all three OSes. System-wide installation (all users) requires elevation.

ICC vs ICM — what’s the difference?

None, functionally. .icm is the extension Windows historically used; .icc is the standard. They are the same file format and interchangeable.

]]> https://displaycal.org/how-to-install-icc-profile/feed/ 0 https://displaycal.org/monitor-calibration-for-photographers/ https://displaycal.org/monitor-calibration-for-photographers/#respond Sat, 17 Oct 2026 09:16:50 +0000 https://displaycal.org/monitor-calibration-for-photographers/

Monitor Calibration for Photographers (Lightroom & Print Workflow)

If your prints come back darker than your screen, or your Lightroom edits look different on every device, your monitor is the weak link. This guide gives photographers the exact DisplayCAL settings for a Lightroom-to-print workflow that actually matches.

Why photographers need calibration more than anyone

Photography is one of the few crafts where what you see is literally the product. An uncalibrated monitor lies to you about exposure, white balance, and saturation — and you bake those lies into every exported file. DisplayCAL, the free open-source calibration tool powered by ArgyllCMS, is the standard fix used by working photographers who don’t want to pay for vendor-locked software. If you haven’t installed it yet, start with our download page and the quickstart guide.

The classic pain: “my prints are too dark”

Ask any print lab and they’ll tell you this is the number one complaint. The cause is almost always the same: the monitor is far brighter than the print viewing conditions. A typical uncalibrated monitor runs at 200–300 cd/m², while a print viewed under normal room light reflects far less light back at you. When you edit on a blazing screen, you unconsciously darken the image to compensate — and the print faithfully reproduces your over-darkened file.

Recommended DisplayCAL settings for photo editing

These are the settings to enter in DisplayCAL’s Calibration tab before you start measuring. They are a starting point used by many photographers — fine-tune brightness to your own print viewing setup:

Step-by-step: calibrate for a Lightroom workflow

1. Warm up the monitor for at least 30 minutes, and reset it to factory defaults. Turn off any dynamic contrast, eco mode, or blue-light filter — including f.lux and Windows Night Light. See our f.lux guide for why this matters.
2. In DisplayCAL, set the white point to D65 and the white level to your target (start at 100 cd/m²).
3. Use the interactive display adjustment step to dial in the monitor’s own brightness, contrast, and RGB gains with the OSD buttons before any software correction is applied.
4. Run the measurement with 500+ patches, then install the resulting ICC profile and let the Profile Loader keep it active. Our Profile Loader guide explains how to make sure the profile actually stays loaded.
5. Verify with a measurement report: for photo work you want average ΔE well under 2.

Soft proofing: preview the print before you pay for it

Calibration gets your screen honest; soft proofing gets your expectations honest. Both Lightroom (Develop module, press S) and Photoshop (View > Proof Setup) can simulate on screen how your image will look on a specific paper and printer, using the paper’s ICC profile supplied by the paper manufacturer or lab. The workflow:

1. Finish your normal edit on the calibrated display.

Soft proofing only works if the screen itself is trustworthy, which is exactly what calibration provides. An uncalibrated screen plus soft proofing is still guesswork.

Ambient light: the forgotten half of the equation

Your 100 cd/m² calibration assumes a dim, neutral viewing environment. Editing in a bright room with daylight hitting the screen, or under warm tungsten bulbs, shifts your perception of the image. You don’t need a perfect darkroom, but keep direct light off the screen and avoid strongly colored walls behind the monitor. Recalibrate if you move the desk or change your lighting.

Frequently Asked Questions

Why do my prints look darker than my screen?

Your monitor is almost certainly much brighter than your print viewing conditions. Calibrate the white level to 80–120 cd/m² (start at 100) so the screen brightness matches the light your prints are viewed under, then re-edit. Most photographers see this single change fix the problem immediately.

What white point should photographers use, D65 or D50?

Use D65 (6500 K) for general photo editing and screen delivery — it matches the sRGB standard and daylight. D50 (5000 K) is the prepress standard for print shops evaluating physical proofs under standard viewing booths. If you soft-proof for a lab, ask the lab which white point their viewing booth uses and match it.

sRGB or Adobe RGB tone curve for photo editing?

If you deliver mostly for web and social media, calibrate to the sRGB tone curve so what you see is what the audience sees. If you print wide-gamut work or deliver to clients who handle Adobe RGB files, Gamma 2.2 with an Adobe RGB working space in Lightroom is the traditional choice. Either way, keep the working space and the calibration target consistent.

How often should a photographer recalibrate?

Every 2–4 weeks for backlit LED monitors is a good rhythm; monthly is the minimum most working photographers accept. CCFL-backlit older monitors drift faster. If you do paid print work, verify with a quick measurement report before any important job rather than trusting the calendar.

]]> https://displaycal.org/monitor-calibration-for-photographers/feed/ 0 https://displaycal.org/displaycal-madvr-3d-lut/ https://displaycal.org/displaycal-madvr-3d-lut/#respond Sat, 17 Oct 2026 08:56:01 +0000 https://displaycal.org/displaycal-madvr-3d-lut/

DisplayCAL 3D LUT for madVR (2026 Guide)

madVR remains one of the most demanding video renderers for home theater PCs, and a proper 3D LUT is the way to get reference color out of it. DisplayCAL has had built-in madVR 3D LUT installation support for years (including the madVR HDR 3D LUT installation API), but most tutorials describe the decade-old Python 2 workflow. This guide covers the current DisplayCAL-py3 path.

What You Need

• DisplayCAL-py3 (3.9.19 current) with ArgyllCMS 3.5.0.
• A supported colorimeter. The LUT is only as good as the measurements.
• madVR installed and configured as your video renderer.
• A display warmed up for 30+ minutes, night-light features off.

Step-by-Step

1. Calibrate and profile the display in DisplayCAL first, following the quickstart. Note your white point, gamma, and black level targets. The LUT build reuses them.
2. Generate the 3D LUT. Use DisplayCAL’s 3D LUT maker with the madVR preset as the starting point. For video work, the levels handling matters enormously. See our Resolve 3D LUT settings for the levels reasoning, which applies in principle here too.
3. Install to madVR. DisplayCAL can install the generated 3D LUT directly through its madVR 3D LUT installation support. This places the LUT file where madVR expects it, rather than you copying files by hand.
4. Select the LUT in madVR for the target display and enable it.
5. Verify. Play reference content with familiar skin tones and neutrals. If you have the meter handy, run a verification measurement through the full chain.

HDR Notes

DisplayCAL’s madVR integration includes support for the madVR HDR 3D LUT installation API. Be aware that HDR calibration support in DisplayCAL-py3 is still maturing (3.9.18 improved HDR detection on Windows 11 22H2+ and fixed PQ roll-off profile saving). Treat HDR 3D LUTs as in active improvement and verify results carefully. Our HDR guide has the full honest picture.

Troubleshooting

• Washed-out or crushed image: levels mismatch somewhere in the chain (GPU output range, madVR settings, display). Check every stage.
• LUT has no visible effect: confirm madVR is actually using the LUT slot you installed to, and that no other color processing overrides it.
• Banding on gray ramps: usually a sign the underlying profile measurements were noisy. Re-measure with more patches.

LUT Size and Quality Notes

DisplayCAL can generate 3D LUTs up to 65x65x65. Larger LUTs are smoother but take longer to measure and compute. For a living-room projector or TV driven by madVR, a mid-size LUT built from a few hundred patches is usually plenty. The jump to very large LUTs pays off mainly on reference displays. Whatever size you choose, the measurement quality matters more than the grid size: a clean 1000-patch measurement beats a noisy 3000-patch one.

Do Not Stack Corrections

A common mistake is applying corrections in two places at once: a GPU-level calibration from DisplayCAL’s profile loader and a 3D LUT in madVR built on top of an already-corrected signal. Decide which stage does the correction. The usual approach is to let the 3D LUT do the work and keep the signal chain before it as neutral as possible. If colors look double-corrected (washed out or oversaturated), check for stacking first.

Related: DisplayCAL troubleshooting hub | Resolve 3D LUT settings | 3D LUT video guide

Frequently Asked Questions

]]> https://displaycal.org/displaycal-madvr-3d-lut/feed/ 0 https://displaycal.org/displaycal-resolve-3d-lut-settings/ https://displaycal.org/displaycal-resolve-3d-lut-settings/#respond Sat, 17 Oct 2026 08:55:52 +0000 https://displaycal.org/displaycal-resolve-3d-lut-settings/

DisplayCAL 3D LUT Settings for DaVinci Resolve

Generating a 3D LUT for DaVinci Resolve with DisplayCAL should be straightforward, but the settings that worked in the Python 2 era do not all behave the same in DisplayCAL-py3 3.9.x. Users in GitHub issue #411 spent hours finding a working combination. This page collects what actually worked, with honest attribution.

The Settings That Worked

1. DaVinci Resolve: use video levels (not full or data levels).
2. DisplayCAL: use full levels all the way through the workflow.
3. Drift compensation: off.
4. Black level: as measured.
5. Tone curve: as measured. (The reporter noted tone curve calibration appears broken in this workflow.)
6. Black output offset: 100%.
7. Gamma: absolute gamma.
8. Rendering intent: preserve saturation.
9. Apply calibration (vcgt): on.

Why These Matter

Levels: the number one gotcha

Video (limited) vs full (data) levels mismatch is the classic cause of washed-out blacks or crushed shadows in a Resolve pipeline. Resolve and DisplayCAL must agree on what the signal means at each stage, hence video levels in Resolve paired with full levels in DisplayCAL’s processing.

Drift compensation

Normally useful for long runs, but in this workflow users found the mid-run re-measurements interacted badly with the video-level signal chain. Off is the reported-good setting.

Tone curve: as measured

Rather than forcing a theoretical curve, measuring the display’s actual response and building the LUT around it gave better results in the reported case.

Patch Count Guidance

A 3D LUT is only as good as the data behind it. A few hundred patches is a practical starting point for most displays; 1000+ patch sets suit reference monitors where you can let the meter run for hours.

Verifying the Result

After generating the LUT, load it in Resolve and check with familiar reference material. Skin tones and neutral grays reveal problems fastest. Then run DisplayCAL’s verification to get numbers: the report tells you whether the white point and gamma actually landed on target (see also our white point troubleshooting if they did not).

Known Friction in 3.9.x

The maintainer acknowledged in issue #411 that 3D LUT workflows deserve more attention in the Python 3 branch and that a bug is possible. If the settings above do not work for you, please report your display model, signal chain, and versions on the issue. That is how it gets fixed.

Related: DisplayCAL troubleshooting hub | 3D LUT video guide | 3D LUT for madVR

Frequently Asked Questions

]]> https://displaycal.org/displaycal-resolve-3d-lut-settings/feed/ 0 https://displaycal.org/uninstall-displaycal/ https://displaycal.org/uninstall-displaycal/#respond Sat, 17 Oct 2026 08:52:57 +0000 https://displaycal.org/uninstall-displaycal/

How to Completely Uninstall DisplayCAL (Windows, macOS, Linux)

Completely uninstalling DisplayCAL means more than deleting the app: you should also remove its ICC profiles, the Profile Loader autostart entry, any ArgyllCMS instrument drivers you installed, and leftover settings. This guide covers all of it on Windows, macOS, and Linux — useful when switching versions, fixing a broken install, or moving on.

Windows: Full Removal in 5 Steps

Step 1: Run the official uninstaller

Open the DisplayCAL installation folder (usually C:\Program Files (x86)\DisplayCAL) and run unins000.exe. Alternatively, use Windows Settings > Apps > DisplayCAL > Uninstall, which launches the same uninstaller. This removes the program files and Start Menu entries.

Step 2: Remove leftover ICC profiles

The uninstaller may leave calibration profiles behind. To clean them:

1. Open Color Management (search it in the Start menu).
2. Select your display, check “Use my settings for this device”.
3. Remove any profiles with DisplayCAL in the name from the list.
4. Optionally, delete the .icc files from C:\Windows\System32\spool\drivers\color — only files you recognize as DisplayCAL-generated.

Step 3: Disable the Profile Loader autostart entry

DisplayCAL’s Profile Loader (DisplayCAL-apply-profiles) is what reapplies your calibration at boot. After uninstalling, make sure it is gone:

1. Open Task Scheduler and look under Task Scheduler Library for DisplayCAL entries — delete them.
2. Check the Startup folder (shell:startup) and Task Manager > Startup apps for anything DisplayCAL-related.

See our Profile Loader guide for background on what this component does.

Step 4: Roll back ArgyllCMS USB drivers (if installed)

If you ever used Tools > Instrument > Install ArgyllCMS instrument drivers (or Zadig) to make DisplayCAL see your colorimeter, your instrument is currently bound to a libusb driver instead of the manufacturer’s. To revert:

1. Open Device Manager with the colorimeter plugged in.
2. Find the instrument, right-click > Update driver > Browse > Let me pick.
3. Choose the manufacturer’s driver (e.g. the X-Rite or Datacolor driver) from the list, or reinstall the vendor software, which restores its driver.

Skip this step if you plan to keep using the instrument with other ArgyllCMS-based tools.

Step 5: Remove settings and logs

DisplayCAL keeps its settings, logs, and stored measurement data in your user profile (including a displaycal.ini file). If you want a fully clean slate — for example before reinstalling to fix a corrupted config — delete the DisplayCAL folder from your user’s application-data directory. This step is optional; leaving settings behind is harmless if you never reinstall.

macOS: Removal

1. Delete /Applications/DisplayCAL.app (drag to Trash).
2. Remove the configuration folder ~/Library/Application Support/DisplayCAL if present.
3. Check System Settings > General > Login Items for a Profile Loader entry and remove it.
4. Remove any DisplayCAL-generated profiles in System Settings > Displays > Color profile (select the display, open the profile list, remove).

Linux: Removal

• DEB/RPM install: sudo apt remove displaycal (or the equivalent for your package manager), then delete ~/.config/DisplayCAL if present.
• AppImage/Flatpak: delete the AppImage file (flatpak uninstall for Flatpak), then remove ~/.config/DisplayCAL if present.
• Manual install: delete the extracted folder, plus the config directory above.
• Remove DisplayCAL profiles from your desktop environment’s color settings (e.g. GNOME Settings > Color).

Clean Reinstall Tips

• Reboot after uninstalling and before reinstalling — this clears any locked files and unloads the old vcgt calibration from the GPU.
• If you are reinstalling to fix crashes, delete the settings folder (Step 5) — a corrupted displaycal.ini is a known cause of startup failures.
• Reinstall ArgyllCMS separately if needed; the current version is 3.5.0 — see our ArgyllCMS page and download page.

What the Uninstaller Removes vs. What It Leaves

Troubleshooting: Uninstaller Missing or Broken

• Install folder already deleted: Windows still lists DisplayCAL in Apps. Remove the listing by reinstalling the same version and uninstalling properly, or clean up manually with steps 2–5 above.
• unins000.exe crashes: boot into Safe Mode and run it there, or proceed with the manual steps — the program files can simply be deleted if the uninstaller will not run.
• Profile still applied after removal: you missed the Profile Loader entry or a scheduled task. Revisit Step 3, then reboot — the vcgt state clears on restart once nothing reloads it.
• Colorimeter not recognized by vendor software afterward: the ArgyllCMS/libusb driver is still bound. Do the Step 4 rollback with the instrument plugged in.

Switching Versions Without the Mess

The most common reason for a full uninstall is moving between DisplayCAL generations — for example from the legacy 3.8.9.3 to the current Python 3 branch (see version comparison). The reliable order is: uninstall old → reboot → delete old settings → install new → reinstall ArgyllCMS if prompted → recalibrate. Mixing a 3.8-era displaycal.ini with a 3.9 install is a classic source of mysterious startup failures, so do not skip the settings cleanup.

What About ArgyllCMS?

DisplayCAL and ArgyllCMS are separate installs, and removing one does not remove the other:

• Keeping ArgyllCMS is the right call if any other tool uses it, or if you plan to reinstall DisplayCAL later — reinstalling means re-downloading several hundred megabytes otherwise.
• Removing ArgyllCMS is just deleting its extracted folder (there is no uninstaller; it is a portable set of command-line tools). Also remove it from your PATH if you added it.
• If you installed ArgyllCMS instrument drivers for a colorimeter and are done with the hardware entirely, do the Device Manager rollback described in Step 4 so the instrument works with its vendor software out of the box.

After Uninstalling: Returning the Display to Stock

Once DisplayCAL, its profiles, and the loader are gone, your display is back to its factory behavior — plus whatever settings remain in the monitor’s own OSD (brightness, presets, RGB gains you changed during interactive adjustment). If you want a true factory reset, use the monitor’s Reset / Factory Reset OSD option as the final step. Note that this also wipes any settings you liked, so write them down first.

Frequently Asked Questions

Will uninstalling DisplayCAL un-calibrate my monitor?

Removing the Profile Loader means your calibration curves no longer load at boot, so the display returns to its uncalibrated state. Deleting the ICC profiles completes the job. Nothing is permanently changed in the monitor itself (unless you used a hardware-calibration-capable display’s own tools, which is separate).

Where is unins000.exe?

In the DisplayCAL installation folder, typically C:\Program Files (x86)\DisplayCAL\unins000.exe. If the folder is already gone, use a registry-safe third-party uninstaller or manually complete steps 2–5 above.

Do I need to remove ArgyllCMS too?

Only if nothing else uses it. ArgyllCMS is a separate engine; other tools (or a future DisplayCAL reinstall) may need it. When in doubt, leave it.

Can I just delete the program folder instead of uninstalling?

Mostly yes on Windows — DisplayCAL does not scatter files across the system the way some suites do. But you still need the manual steps for profiles, the loader entry, and drivers (steps 2–4), otherwise the “uninstalled” calibration keeps loading at boot and the effect lingers invisibly.

How do I switch from the old 3.8.9.3 to the Python 3 branch cleanly?

Uninstall 3.8.9.3 fully using the steps above (including profiles and the old Profile Loader entry), reboot, then install the current 3.9.x build. See DisplayCAL vs DisplayCAL-py3 for the version differences.

]]> https://displaycal.org/uninstall-displaycal/feed/ 0 https://displaycal.org/projector-calibration-guide/ https://displaycal.org/projector-calibration-guide/#respond Sat, 17 Oct 2026 08:52:54 +0000 https://displaycal.org/projector-calibration-guide/

How to Calibrate a Projector with DisplayCAL

Calibrating a projector with DisplayCAL works the same way as calibrating a monitor — with a few projector-specific twists. DisplayCAL includes a dedicated Projector display device type, and the ArgyllCMS engine behind it handles the low-light measurements projectors demand. This guide walks you through screen preparation, the Rec.709 workflow, and how often to recalibrate lamp versus laser projectors.

Before You Start: Projector-Specific Preparation

Projectors are far more sensitive to setup than monitors. Get these right before measuring:

1. Warm up the lamp for at least 30–45 minutes. Projector lamps shift color dramatically as they heat up; measuring cold gives you a profile of a state the projector is never in during actual viewing.
2. Control ambient light. Ideally a dark room. Any stray light hitting the screen washes out blacks and corrupts low-end measurements — and no software can calibrate away room light.
3. Disable dynamic features: dynamic iris, dynamic contrast, eco-mode brightness shifting, and frame-interpolation motion smoothing. These change the image based on content and invalidate measurements. Set a fixed lamp/laser power mode.
4. Choose your picture preset wisely. Start from the projector’s most accurate preset (often called Cinema, Film, or Natural) rather than Vivid/Dynamic.
5. Position the colorimeter correctly. Contact mode against the screen works for most setups; for very large screens or ambient-light-rejecting materials, a tripod facing the screen from the seating position (with the diffuser on, if your instrument supports projector mode) can be more representative. Shield the sensor from direct projector light leaking around the screen edges.

Step-by-Step: Projector Calibration Workflow

Step 1: Select the Projector device type

In DisplayCAL’s main window, set the display device type to Projector. This adjusts patch timing and measurement behavior for the slower response and lower light output of projection.

Step 2: Install ArgyllCMS and connect your instrument

As with monitors, DisplayCAL needs ArgyllCMS installed and your colorimeter connected. See our quickstart guide if this is your first run. Any colorimeter bright enough for your screen size works; our buying guide covers the options:

• Calibrite Display Plus HL — handles bright HDR-capable setups
• Datacolor Spyder X2 — solid all-rounder
• Spyder X2 Ultra — good value

Disclosure: these are affiliate links; we may earn a commission at no cost to you.

Step 3: Set calibration targets

Step 4: Run interactive display adjustment, then profile

Use the interactive adjustment to set brightness/contrast on the projector itself first (getting close optically beats correcting digitally), then let DisplayCAL run the patch sequence. Projector measurements take longer than monitor ones — plan for it.

Step 5: Verify and optionally build a 3D LUT

Run a verification report to confirm the result. If you play video through a PC (e.g. madVR or DaVinci Resolve), generate a 3D LUT with DisplayCAL-3DLUT-maker for the most accurate Rec.709 mapping — see our 3D LUT video guide.

Recalibration: Lamp vs. Laser Projectors

• Lamp projectors: UHP lamps dim and shift color as they age — noticeably within the first few hundred hours, then gradually. Re-verify every few hundred hours of use, or whenever the image visibly drifts. A fresh lamp deserves a fresh calibration.
• Laser projectors: far more stable over time, but not immortal. An annual verification is a sensible routine; recalibrate when the verification report shows drift.

In both cases, the honest rule is: re-measure when the verification says so, not on a fixed calendar. DisplayCAL’s verification report is the instrument that tells you.

Honest Limitations

• Calibration cannot create contrast. If your room or screen gives you gray blacks, no profile fixes that — only light control does.
• Streaming sticks and smart-TV apps inside the projector generally cannot load your ICC profile. The calibration applies to sources routed through your calibrated PC.
• HDR on projectors is its own complex topic; treat this guide as the SDR foundation first.

Patch Count and Session Length

Projector profiling sessions run longer than monitor ones because each patch needs more integration time at low light levels. Practical guidance:

• 500 patches is a sensible starting point — a good balance of accuracy and an evening’s patience.
• 1000+ patches pays off on projectors with visible non-uniformity (hotspotting), since the denser sampling captures spatial variation better.
• Split very long sessions if the lamp drifts: a profile built from inconsistent measurements is worse than a shorter, consistent one. If in doubt, do 500 stable patches rather than 1500 drifting ones.

Using the 3D LUT with an HTPC

If your projector is fed by a home-theater PC, a 3D LUT is the most accurate way to watch Rec.709 content:

1. Generate the LUT with DisplayCAL-3DLUT-maker: source Rec.709 (or sRGB for SDR video), destination your projector profile, 65³ for maximum smoothness.
2. Load it in madVR (via its 3D LUT calibration slot) or in DaVinci Resolve if you grade through the PC.
3. Verify with a verification report afterward — projected verification is the proof the chain works.

For streaming sticks or the projector’s built-in apps, the LUT cannot be injected — those sources will use the projector’s own presets. Calibrate the PC chain where you have control.

Screen Material Notes

• Matte white (gain ~1.0): the reference case; measures cleanly in contact mode.
• High-gain or ambient-light-rejecting screens: can hotspot or shift color off-axis. Measure from the seating position if possible, and be aware the calibration is valid mainly for that viewing angle.
• Gray screens: lower black levels help contrast; the workflow is identical, just with less light to work with — allow longer patch times.

Whatever the screen, keep a note of your settings (lamp mode, iris, preset) alongside the profile. If anything changes, the profile’s assumptions change with it.

Quick Checklist Before Each Session

• Room dark, screen clean, lamp warmed up 30–45 minutes
• Dynamic iris / dynamic contrast / eco-shifting off, fixed lamp mode
• Picture preset: Cinema / Film / Natural (not Vivid)
• Colorimeter positioned and shielded from stray light
• Same settings noted down as last time (for comparable results)

Frequently Asked Questions

Can DisplayCAL calibrate any projector?

It can profile the image chain of any projector you can put a test pattern on — which in practice means a PC-connected projector. The colorimeter measures what your screen shows, regardless of projector brand.

Should the colorimeter touch the screen or face it from the seats?

Contact mode against the screen is simplest and most repeatable for most setups. Facing the screen from the viewing position (with diffuser) better represents what you actually see, at the cost of more setup care. Either is defensible — pick one and stay consistent between sessions.

How is projector calibration different from monitor calibration?

Lower light levels, longer measurement times, a dedicated Projector device mode in DisplayCAL, and much greater sensitivity to room light and lamp warm-up. The software workflow is otherwise the same.

How often should I recalibrate my projector?

Lamp models: every few hundred hours or when the image drifts. Laser models: verify yearly. In both cases, let DisplayCAL’s verification report decide.

]]> https://displaycal.org/projector-calibration-guide/feed/ 0 https://displaycal.org/gaming-monitor-calibration/ https://displaycal.org/gaming-monitor-calibration/#respond Sat, 17 Oct 2026 08:52:47 +0000 https://displaycal.org/gaming-monitor-calibration/

How to Calibrate a Gaming Monitor with DisplayCAL

Calibrating a gaming monitor with DisplayCAL is absolutely worth doing — but you need to understand one thing first: in exclusive-fullscreen games, your ICC profile is ignored. What does still apply is the calibration loaded into your graphics card. This guide explains what DisplayCAL can and cannot do for gaming, gives you recommended settings, and covers the 3D LUT options for games.

The Key Concept: vcgt vs. ICC Profile

DisplayCAL’s calibration does two separate things:

• vcgt (video card gamma table): per-channel correction curves loaded into your GPU. These apply everywhere — desktop, borderless windowed games, and exclusive-fullscreen games. This fixes your white point and gray neutrality in every game.
• ICC profile: the full color description used by color-managed apps (Photoshop, Lightroom, Chrome). Games in exclusive fullscreen bypass the operating system’s color management, so the ICC part is ignored there.

Practical takeaway: calibrating with DisplayCAL still visibly improves games — grays become neutral, gamma becomes correct, the image looks cleaner — even though games do not use the ICC color transforms. What you do not get in exclusive fullscreen is gamut mapping (e.g. an automatic sRGB clamp).

What DisplayCAL Can and Cannot Do for Gaming

Recommended DisplayCAL Settings for Gaming Monitors

Before You Measure: Gaming-Monitor-Specific Prep

1. Warm up the panel for at least 30 minutes — gaming monitors drift noticeably when cold.
2. Disable dynamic contrast, black equalizer / shadow boost, and dynamic brightness in the OSD. These features change the image based on content and make measurements meaningless. You can re-enable them after if you like how they look, but calibrate with them off.
3. Set overdrive to a middle setting without visible inverse ghosting; leave it there permanently.
4. Use the monitor’s native/widest gamut mode during profiling, then handle sRGB clamping separately (see our sRGB clamp guide) if the panel is wide-gamut.
5. Keep the room lighting similar to your usual gaming sessions.

Then run the calibration as described in our quickstart guide. Make sure the Profile Loader is enabled so the vcgt calibration loads at every boot — without it, games get the uncalibrated GPU state. See our Profile Loader guide for details.

Option: 3D LUTs per Game (ReShade)

If you want full gamut mapping inside a game — for example an sRGB clamp or a filmic look — you can generate a 3D LUT with DisplayCAL-3DLUT-maker (source: sRGB, destination: your display profile) and load it through ReShade‘s LUT shader. This works well for single-player games.

Anti-cheat warning: ReShade and system-wide LUT injectors hook into the rendering pipeline. Many competitive online games treat injectors as suspicious, and some anti-cheat systems flag or block them. Do not use LUT injectors with competitive online games. The base vcgt calibration, by contrast, lives in the GPU driver and is not an injector — it is safe everywhere.

High Refresh Rate Notes

• Calibration does not affect refresh rate, FreeSync/G-Sync, or input lag. Set those independently.
• Some monitors shift color slightly at maximum refresh rate vs. lower rates. If you always play at 240Hz+, profile at 240Hz.
• HDR gaming is a separate pipeline — our HDR guide covers what DisplayCAL can currently do there.

You still need a colorimeter to do any of this properly. Our buying guide covers the current options:

• Calibrite Display Plus HL — best for HDR-capable gaming panels
• Datacolor Spyder X2 — solid all-rounder
• Spyder X2 Elite — good value for SDR gaming

Disclosure: these are affiliate links; we may earn a commission at no cost to you.

Step-by-Step: Your First Gaming Calibration Run

1. Do the OSD prep above (warm-up, dynamic features off, overdrive set).
2. Connect your colorimeter and launch DisplayCAL.
3. Point DisplayCAL at your ArgyllCMS bin folder if asked (first run only).
4. Set the targets from the table above: D65, 120 cd/m², sRGB tone curve, 500+ patches.
5. Run interactive display adjustment first — get brightness and RGB gains close using the monitor’s own controls. Less digital correction means less banding.
6. Run the full profiling pass. On a fast modern PC with 500 patches this typically takes 20–40 minutes.
7. Install the profile and confirm the Profile Loader is set to load it at startup.
8. Run a verification report (how to read it) to confirm the result.

What About HDR Gaming Monitors?

HDR gaming runs through a different pipeline (HDR metadata, PQ tone mapping) that DisplayCAL’s SDR calibration does not fully govern. The practical approach in 2026:

• Calibrate the SDR mode of the monitor with the workflow above — most desktop use and many games still run in SDR.
• For HDR mode, use the monitor’s own HDR presets and in-game HDR calibration screens; DisplayCAL’s HDR support is improving (see our HDR guide) but treat it as experimental for now.
• A high-brightness colorimeter like the Calibrite Display Plus HL (up to 10,000 nits) is the right tool if you want to measure HDR luminance levels at all.

Common Mistakes to Avoid

• Calibrating with HDR or dynamic contrast on — the panel changes behavior mid-measurement and the profile is garbage.
• Skipping the Profile Loader — without it, a reboot silently drops your calibration and games run uncalibrated.
• Expecting the ICC profile to fix exclusive-fullscreen color — it cannot; that is what the 3D LUT injector option is for, with the anti-cheat caveats above.
• Chasing someone else’s ICC profile download — profiles are panel-specific. A profile made for another unit of the “same” monitor model is better than nothing but never as good as measuring your own.

Verifying the Result In-Game

After calibration, sanity-check with real content rather than test patterns alone:

• Load a game with a dark scene you know well — shadow detail should be visible, not crushed to black or washed gray.
• Compare a familiar menu screen before and after by toggling the profile in Color Management (Windows) — the difference in gray neutrality is usually obvious.
• If something looks worse, re-check the OSD prep: a forgotten dynamic-contrast setting is the culprit more often than a bad profile.

Frequently Asked Questions

Does monitor calibration even matter for gaming?

Yes. The vcgt calibration (white point, gamma, gray neutrality) applies in every game including exclusive fullscreen. What does not apply in exclusive fullscreen is ICC gamut mapping — but most of the visible improvement comes from the vcgt part.

Will calibration add input lag?

No. Calibration curves live in the GPU’s lookup tables and cost no measurable performance.

Should I use borderless windowed or exclusive fullscreen after calibrating?

If you want ICC gamut mapping (e.g. an sRGB clamp) to apply, use borderless windowed. For maximum performance with correct gamma and white point, exclusive fullscreen is fine.

Can I get banned for using ReShade LUTs?

ReShade itself is allowed in many single-player games but flagged by several competitive anti-cheat systems. Never use injectors with online competitive titles; when in doubt, check the game’s policy first.

]]> https://displaycal.org/gaming-monitor-calibration/feed/ 0 https://displaycal.org/srgb-clamp-wide-gamut-guide/ https://displaycal.org/srgb-clamp-wide-gamut-guide/#respond Sat, 17 Oct 2026 08:52:44 +0000 https://displaycal.org/srgb-clamp-wide-gamut-guide/

How to Clamp a Wide-Gamut Monitor to sRGB with DisplayCAL

Clamping a wide-gamut monitor to sRGB means restricting the display’s color output to the smaller sRGB color space, so that everyday SDR content — web pages, videos, games — no longer looks oversaturated and neon. If your new monitor makes everything look like radioactive candy, this guide shows you two ways to fix it with DisplayCAL: a precise 3D LUT clamp (with a colorimeter) and a no-hardware EDID approximation.

Why Wide-Gamut Monitors Look Wrong in SDR

Most desktop applications are not color-managed. They send sRGB values straight to the screen, assuming the display can only show sRGB. On a wide-gamut panel (one covering 95%+ DCI-P3 or Adobe RGB), those same values get stretched across a much larger color volume. The result: reds that glow, skin tones that look sunburned, greens that look electric.

This is not a defect — it is the monitor faithfully showing you colors your content never asked for. The fix is to tell the system “only use the sRGB portion of what this panel can do.” That is exactly what an sRGB clamp does.

First: Check Your Monitor’s Built-in sRGB Mode

Before touching DisplayCAL, open your monitor’s on-screen menu and look for a preset named sRGB, sRGB Emulation, or similar. Many mid-range and professional monitors include one.

• If the sRGB mode looks natural and measures reasonably (you can verify with DisplayCAL’s verification report), you may not need anything else. This is the simplest clamp there is.
• If the sRGB mode is locked, dim, green-tinted, or simply missing, continue with the DisplayCAL methods below.

Keep the monitor in its native/wide-gamut mode while using the DisplayCAL clamp methods — the clamp happens in software, on top of the panel’s full capability.

Option A: Precise sRGB Clamp with a 3D LUT (Recommended)

This is the accurate route. You profile your monitor with a colorimeter as usual, then generate a 3D LUT that maps sRGB content into your display’s native color space. Because the LUT is built from real measurements of your panel, the clamp is far more accurate than any generic sRGB preset.

Step 1: Calibrate and profile normally

Follow our DisplayCAL quickstart guide: connect your colorimeter, set white point D65 and tone curve sRGB (or Gamma 2.2), and run a profile with at least 500 patches. You need a good profile of the native gamut first — the clamp is derived from it.

Step 2: Generate the sRGB 3D LUT

DisplayCAL ships with a standalone tool for this:

1. Open DisplayCAL-3DLUT-maker (installed alongside DisplayCAL on Windows).
2. Set the source colorspace to sRGB and the destination to your freshly made display profile.
3. Choose a LUT size of 33³ or 65³ (larger is smoother; 33³ is plenty for a clamp).
4. Generate the LUT and save it in .cube format.

Step 3: Load the LUT system-wide

A 3D LUT file does nothing until something applies it. Options include:

• System-wide LUT loaders (e.g. dwm_lut on Windows) apply the clamp to the whole desktop, so every SDR app benefits. These are third-party tools — check their documentation and current compatibility before relying on them.
• ReShade with a LUT shader applies the clamp per-game. Fine for single-player titles; see the anti-cheat caution in our gaming monitor guide.
• DaVinci Resolve / photo editors can load the LUT directly for a color-managed workflow — see our 3D LUT video guide.

Option B: No Colorimeter — EDID-Based Approximation

If you do not own a measurement instrument, DisplayCAL can still build you an approximate profile from the data your monitor reports about itself:

1. In DisplayCAL, go to File > Create profile from EDID.
2. Select your display and let DisplayCAL read its EDID colorimetry.
3. Install the generated profile and set it as the default for your display.
4. Optionally, generate an sRGB 3D LUT against this EDID profile as in Option A.

Be honest with yourself about what this is: an approximation. EDID data describes what the manufacturer claims, not what your individual panel actually does. It usually tames the worst oversaturation, but it cannot match a real measurement. If accurate color matters to you, a colorimeter is the upgrade that changes everything — see our colorimeter buying guide:

• Calibrite Display Plus HL — best for HDR and high-brightness panels
• Datacolor Spyder X2 — solid all-rounder
• Calibrite Display Pro HL — best value for SDR

Disclosure: these are affiliate links; we may earn a commission at no cost to you.

Honest Limitations of Clamping

• A clamp cannot fix panel uniformity issues — if one corner is pinker than the other, that is hardware, not gamut.
• Exclusive-fullscreen games bypass ICC profiles. The desktop will look right; a game in exclusive fullscreen may not, unless you use a LUT injector (with the caveats above).
• HDR is a separate pipeline. An sRGB clamp is an SDR solution. If you work in HDR, read our HDR calibration guide instead.
• Re-verify after major GPU driver updates, which can reset LUT loaders.

How to Tell If You Need a Clamp

Not every wide-gamut owner needs one. Quick self-test: open a photo of a familiar face and a red object (a stop sign, a Coca-Cola logo) side by side with the same image on your phone.

• Skin looks sunburned and reds glow — you need a clamp.
• Everything looks normal — your apps or OS may already be color-managing (macOS color-manages most things; Windows does not). You can skip clamping.
• Only some apps look wrong — those are the non-color-managed ones; a system-wide LUT clamp fixes all of them at once.

DisplayCAL’s verification report can quantify the problem: profile the native gamut, then check the measured gamut coverage against sRGB. If the panel covers 130%+ of sRGB, the oversaturation you see is real and a clamp will transform the experience.

Which LUT Format Should You Export?

DisplayCAL-3DLUT-maker offers several formats. Which one you need depends on the loader:

• .cube — the universal choice; works with ReShade, DaVinci Resolve, and most LUT loaders.
• .3dl — preferred by some video tools and hardware LUT boxes.
• eeColor / madVR formats — only if you use those specific video pipelines.

When in doubt, export .cube: it is supported almost everywhere and easy to regenerate later.

Keeping the Clamp Working Over Time

• Recalibrate on your normal schedule (every few months for critical work), and regenerate the LUT each time — the clamp is only as good as the profile underneath it.
• Do not stack clamps. If your monitor’s sRGB mode is on and a software LUT is loaded, you get double conversion and washed-out color. One clamp at a time.
• Label your LUT files with the profile date (e.g. srgb-clamp-2026-10.cube) so you always know which profile they belong to.

Frequently Asked Questions

Will clamping to sRGB make my monitor dimmer?

Not inherently. A clamp remaps colors, not brightness. If your monitor’s own sRGB preset looks dim, that is the preset lowering brightness — a DisplayCAL software clamp keeps your chosen luminance target (e.g. 120 cd/m²).

Can I clamp to DCI-P3 or Adobe RGB instead?

Yes — the same 3D LUT workflow works with any source colorspace. Photographers often clamp to Adobe RGB; video editors to DCI-P3 or Rec.709.

Do I need to redo the clamp after recalibrating?

Yes. The 3D LUT is derived from your display profile, so regenerate it whenever you make a new profile.

Is a hardware sRGB mode better than a DisplayCAL clamp?

Sometimes. A good factory sRGB mode is zero-maintenance. But many are poorly implemented (tinted or locked brightness), and a measured DisplayCAL clamp is usually more accurate on those panels. Measure both with a verification report and keep the winner.

]]> https://displaycal.org/srgb-clamp-wide-gamut-guide/feed/ 0 https://displaycal.org/multi-monitor-matching/ https://displaycal.org/multi-monitor-matching/#respond Sat, 17 Oct 2026 08:02:53 +0000 https://displaycal.org/multi-monitor-matching/

Match Multiple Monitors with DisplayCAL

Two monitors side by side, same image, visibly different colors — the classic dual-display headache. With DisplayCAL you can make multiple monitors match closely enough that the difference stops bothering you. If you have not calibrated a display yet, the quickstart guide covers the full process on a single monitor first. Here is the method.

Matching multiple monitors with DisplayCAL means calibrating each display to the same white point and luminance targets, generating one profile per display, associating each profile with its own monitor, and verifying the results side by side with Delta E reports.

The ground rules

• One profile per display. Always. Even two units of the same model differ. Never copy a profile from one monitor to another.
• The weakest panel sets the ceiling. You can only match displays within what all of them can physically do. Pick white point and brightness targets every panel can reach — usually D65 white and a luminance the dimmest panel manages comfortably.
• Match targets, not just profiles. Two profiles built to different targets cannot match, no matter how good each one is individually.

Step 1: choose common targets

Before measuring anything, decide the targets all displays will share:

Measure each panel’s native white point and maximum brightness first (DisplayCAL can report these during interactive display adjustment). If one panel cannot reach your desired luminance, lower the target for both — matching at 100 cd/m² on both beats 120 on one and a clipped 100 on the other.

Step 2: calibrate each display identically

1. Warm up both panels for 20–30 minutes with mixed content.
2. Set identical ambient conditions — same room light on both, no window glare on one panel only.
3. Calibrate display 1 to the shared targets: interactive adjustment (brightness/RGB gains to hit D65 and target luminance), then profiling.
4. Calibrate display 2 the same way — same targets, same patch count, same instrument and (if applicable) the same spectral correction family.
5. Associate each profile with its own display and make sure the Profile Loader loads both at startup.

Step 3: verify and compare

1. Run a verification report on each display separately. Both should land in the same Delta E range (average under ~2 for comfortable matching).
2. Compare visually with the same content. Open an identical neutral-gray image and a color photo on both screens, side by side. Grays reveal white-point mismatch; skin tones reveal the rest.
3. If they still differ: the usual culprit is white point — the two panels’ D65 can look different due to metameric differences between panel technologies (e.g. an IPS next to an OLED). Try a small alternate-white-point tweak on one display (see the OLED guide) until they visually agree, then re-verify.

Mixed panel technologies: IPS next to OLED

Matching two identical-technology panels is straightforward. Matching different technologies — say an IPS monitor next to an OLED — is where it gets interesting, because the panels disagree about white in a way no single target can fully fix:

• Use the right correction per panel. The IPS gets its LED-backlight correction, the OLED gets its OLED-family CCSS. Calibrating both with one generic correction bakes a systematic error into one of them.
• Expect a white-point compromise. After calibrating both to D65, whites may still look slightly different side by side — the classic metameric mismatch between narrow-spectrum OLED and broad-spectrum LED backlight. This is normal physics, not a failed calibration.
• Tune one display to the other visually. Pick the display you look at most as the reference. On the second display, apply a small alternate-white-point shift (see the OLED guide), compare neutral grays side by side, and iterate in small steps until they agree. Then run a final verification on both to make sure accuracy did not suffer.
• Accept the residual difference. Blacks will never match — OLED black is true zero, IPS black is backlight glow. Judge the match on mid-tones and whites in your actual working light, not on a black screen in a dark room.

Quick checklist

• Same white point target (D65) on every display
• Same luminance target, within reach of the dimmest panel
• Same tone curve on every display
• One profile per display, correctly associated
• Profile Loader active so calibration survives reboot
• Verification reports compared, then a visual side-by-side check

Frequently asked questions