• Use the display for about 20–30 minutes to “warm up,” and make sure to turn off anything like Night Light/Night Shift and “Vivid/Dynamic” picture modes.
• Factory-reset the monitor, and then elect for an appropriate preset (often “sRGB” or Custom/User).
• Select brightness based on your room, not maximum brightness!, and then pick contrast so you aren’t blowing out anything white.
• Use the built-in calibration wizard (Windows: Display calibration, Mac: Display Calibrator Assistant) to create a working (likely not highly accurate) profile. (support.microsoft.com)
• Check it with grayscale and gradient test patterns, and compare the result with the profile after a few days of normal work.
• If you need to match prints or clients pay for your work, get a hardware calibrator, it’s a no-brainer.

“Calibration” sounds like something only a pro would have to worry about, but most screen users really only care that their screen be (1) not too bright, (2) not hella blue or hella yellow, (3) reasonably consistent when looking at photos and videos (and web designs that have photos and videos). We’re concerned here with what you can do visually—free operating system tools plus a few test patterns—to help your colors get to a reasonable baseline, without having to buy a colorimeter.

• Profiling: describing your display’s behavior in an ICC profile so color-managed software can translate colors correctly. ICC profiles are designed to help move color between devices and systems more consistently. (color.org)

Without a measurement device, you can still create a usable calibration/profile using built-in wizards (it’s just more subjective). The practical goal is consistency: fewer surprises when you move between apps, devices, or send work to someone else.

Before you touch any settings: the “cheap wins” that matter most#

1. Warm up the display (20–30 minutes). Many panels drift slightly as they reach operating temperature.
2. Control your lighting. Avoid direct sunlight on the screen. Try to keep lighting similar day to day.
3. Turn off color shifters while calibrating. Disable Night Light/Night Shift, blue-light filters, “Reading mode,” and any dynamic contrast features.
4. Disable ‘Vivid/Dynamic’ presets. These are designed to look punchy, not accurate. Starting from a neutral preset is easier and more consistent. (A common first step is choosing a “User/Custom” mode or an “sRGB” clamp mode.) (rtings.com)
5. Use the native resolution and a normal viewing angle. Especially on TN panels, a small tilt can change perceived brightness and color.

Pick a sensible target (so you don’t calibrate yourself into a corner)#

If your work is mostly web content, YouTube, general photo editing, and everyday apps, aiming for an sRGB-like look is usually the least surprising. sRGB is also
(w3.org)

And we are ready for: Step 1: reset your monitor and select the right OSD picture mode!#

1. Reset to board defaults in your monitors OSD to clean out your old experiments.
2. Pick a neutral preset: look for “sRGB,” “Standard,” “Custom,” “User,” or “Cinema” (varies by brand). Avoid “Vivid,” “Dynamic,” “FPS,” etc. as a baseline. (rtings.com)
3. If there’s an sRGB mode, try it first. It often prevents oversaturated colors on wide-gamut monitors by clamping to sRGB. (rtings.com)
4. Turn off extra processing: dynamic contrast, black equalizer, ‘super resolution,’ sharpening enhancements, and any “auto” color temperature features.

Why start here? Because your monitor’s preset can change multiple things at once (gamma curve, saturation, color temperature). Getting to a predictable starting point makes the rest of the steps actually stick.

Step 2: Set brightness first (this is where most people go wrong)#

If your display is too bright, you’ll edit photos too dark, push contrast too hard, and think your prints look “muddy.” So brightness is priority #1.

1. Open a plain white screen (a blank document or a blank browser tab) and a mostly dark image.
2. Lower brightness until white stops feeling like a light bulb. You should be able to look at the screen for long periods without squinting.
3. Paper check (optional but useful): put a sheet of white paper next to the screen under your usual room lighting and try to get your screen’s white to feel similar in brightness. Don’t obsess—just avoid the screen being dramatically brighter than paper.
4. Re-check dark detail: in your dark image, you should still distinguish near-black shadows instead of everything collapsing into one black blob.

Step 3: Set contrast (keep highlights from clipping)#

Contrast adjustment is pretty basic: the idea is to keep bright detail visible. If the contrast is set too high, the bright tones run together into the same white, and you start to lose the texture (clouds, wedding dresses, snow scenes, etc).

1. Use a highlight test pattern (or just a picture with bright detail).
2. Turn up the contrast until you start losing detail, and then back off just a touch.
3. If your monitor has a ‘Contrast Enhancer’ feature, turn it off—this feature often alters the tone of the image dynamically for the ‘bigger picture’ and ruins consistency.

Step 4: Check gamma and gradients (to avoid “crushed shadows” and banding)#

Gamma is basically how fast your monitor goes from black to white. If gamma is set badly, it’ll make the mid tones look too dark (often called ‘crushed’), or too washed out. The easiest check without a tool is a gamma test image plus a smooth gradient.

Gamma test: Lagom LCD test pages include a quick test pattern intended to visually blend somewhere around a 2.2 target when things are close. (lagom.nl)

Gradient test: Look for a smooth transition from black → gray → white with little obvious striping (banding). Some banding is panel limitation, but extreme banding means settings are off.

Step 5 – How to neutralize the white point (color temperature) without fancy tools#

If whites are looking blue your whole edit will drift yellow, and if whites are looking yellow/orange you’ll over correct toward blue. You want a white and light grey that looks neutral under your normal room lighting.

1. Start with a colour temperature preset (6500K /D65/Normal/Warm/Cool/ etc.) names vary, but most web centric workflows will find a D65-ish feel is a common starting point. (eizo.com)
2. Open a neutral greyscale image (a ramp plus a few neutral grey patches). Example images can be found here (beetbloke.com). If we accidentally start with a file that’s tinted we’re in trouble so we do that before we begin calibrating.
3. If our grays look tinted (i.e. yellow or blue hue), switch to User colour temp and adjust RGB gains slightly:
   • Too blue/cool—reduce Blue or increase Red/Green a touch.
   • Too yellow/warm—reduce Red/Green or increase Blue a touch.
4. Make tiny changes then pause 10–20 seconds, your eyes adapt quickly and skimming over the problem will just cause you to overshoot.

If your laptop has limited controls, don’t fight it, we’ll use the OS calibration tool next in this series, and we’ll try to keep our room lighting consistent.

Step 6 – Run the built-in calibration tool (Windows and Mac (Windows 11 use Display calibration and set the resulting profile)Here we flip to running use the built-in calibration tool#

Here we flip to running use the built-in calibration tool. Specifically on Windows 11 where we’ll be using the built-in Display calibration and then set the resulting profile. (support.microsoft.com)

1. Open Settings → System → Display → Color profile choose Calibrate display and follow the prompts, this creates a new color profile for that display (support.microsoft.com)

If you use HDR:
Windows may direct you to the Windows HDR Calibration app for HDR-capable displays. (support.microsoft.com)

macOS: use Display Calibrator Assistant and verify the profile is selected#

1. Open System Settings → Displays.
2. Next to Color profile, choose Customize, then click Add to open Display Calibrator Assistant. (support.apple.com)
3. Follow the assistant through. When you’re done, macOS will assign the new profile for you automatically. (support.apple.com)
4. Confirm it’s assigned by checking System Settings → Displays → Color profile—and select it if needed. (support.apple.com)

macOS also includes ColorSync Utility. It can confirm & (sometimes) repair profiles if things seem to go off. (support.apple.com)

Step 7: Verify your results (quick tests that catch 90% of issues)#

• Black level test: You should distinguish near-black steps, and not end up with entire shadow areas turning into one flat black. (Lagom’s black level/contrast patterns are a common reference.) (lagom.nl)
• White saturation test: Bright areas should still show texture, whiter-than-whites shouldn’t display as blank paper cutouts.
• Gray neutrality: If mid-gray looks greenish, purplish, or pink—go back to your white point/tint adjustments.
• Skin tones: Get a few real photos you trust. Skin is a fast “sanity check”—your brain has been
  trained to notice when it looks off.
• Cross-device check: Open the same image on your phone and another display. You’re not seeking “identical”—just “not wildly different”.

Common mistakes (and their rapid remedies)#

When “no expensive tools” stops being enough#

Get a hardware calibrator if you:

Sell prints (or print to a lab reliably)
Deliver client work, and “close enough” can mean rework
Use multiple displays and want them to match
Do video work with specific standards and deliverables

A hardware calibrator measures your display and makes a profile based on real data (not your eye). An obvious example is a more serious monitor calibration product—most of which emphasize profiling and controlling targets, such as white point, luminance, and gamma (calibrite.com).

A simple maintenance routine (so your calibration doesn’t drift)#

Once: Calibrate when you first setup your workspace, or after a major OS or driver update
Weekly: Quick check; black level + gradient + a skin tone photo to check base skin tones in the image
Monthly: Re-run the OS calibration wizard if you’re noticing drift (older displays especially)
Anytime: If you’ve changed your room lights substantially, check brightness and white point again

FAQ#