How to Overclock Your Monitor (More Hz Safely, 2026)

Overclocking a monitor means asking it to refresh faster than its rated number – pushing a 60Hz panel to 75Hz, or a 144Hz panel to 165Hz. It works because manufacturers rate panels conservatively, so there is often a little unlabeled headroom on top. The catch is that “often” is not “always,” and a monitor that accepts a higher rate is not the same as a monitor that delivers it. This guide gives you the three ways to do it and the one test that separates a real overclock from a fake one.

First, the ceiling you cannot move

Before you change anything, understand what you are working against, because it explains every failure you will hit. Your maximum refresh rate is capped by the lower of two limits.

The first is the panel itself – the physical electronics that drive the pixels. This is the limit you are probing when you overclock, and it varies unit to unit.

The second is bandwidth: how much data your cable and port can carry. A refresh rate is just frames per second, and every frame is a fixed pile of data (pixels x color depth). Push more frames per second through the same pipe and you need more bandwidth. The pipe has a published ceiling:

• DisplayPort 1.4 (HBR3) runs at 32.4 Gbps of raw link rate, which delivers about 25.92 Gbps of usable video data after encoding overhead, per the DisplayPort specification.
• DisplayPort 2.1 raises that sharply with its UHBR modes – UHBR 10 at 40 Gbps, UHBR 13.5 at 54 Gbps, and UHBR 20 at 80 Gbps of raw link rate, again per the spec.
• HDMI 2.0 carries up to 18 Gbps, and HDMI 2.1 raises the ceiling to 48 Gbps, a spec set by the HDMI Forum.

Why this matters in practice: if you hit a flat wall where the monitor simply rejects anything above a certain rate no matter how gently you climb, you are probably bandwidth-limited, not panel-limited. NVIDIA’s own documentation notes the refresh rate is bounded by the display’s scan capability at the current resolution. No software trick beats a hardware pipe. The fix is a better cable or a higher-spec port – not a registry edit.

Path 1: NVIDIA Control Panel

If you have a GeForce card, the built-in tool is the easiest starting point and it has its own validation step built in.

1. Right-click the desktop and open the NVIDIA Control Panel.
2. Under Display, click Change resolution.
3. Click the Customize button, then check Enable resolutions not exposed by the display, then click Create Custom Resolution.
4. Leave the resolution at your native value and raise only the Refresh rate (Hz) field by a small amount – say from 60 to 65.
5. Click Test. NVIDIA documents that the panel will test the new mode and, if the display accepts it, ask you to confirm before saving.

If the screen goes black, do nothing – the test reverts automatically after a few seconds. If it holds and looks clean, confirm to save, then climb again in small steps until a rate fails. Then drop back to the last good one. Do not trust it yet; you still have to run the frame-skip test below.

Path 2: AMD Software (Adrenalin Edition)

The Radeon equivalent lives inside AMD’s driver suite and follows the same logic.

1. Open AMD Software: Adrenalin Edition and type Custom into the search box, then open the Custom Resolution result.
2. Click Create New. The profile opens pre-filled with your current settings.
3. Raise the refresh-rate field by a small increment, leaving resolution and color depth alone, then click Create.
4. AMD checks the new mode for compatibility, and the support article notes the screen may go momentarily blank during this step – that is normal.

As with NVIDIA, if the display refuses the mode you will see a blank screen that recovers on its own. Keep the highest rate that applies cleanly, then go verify it.

Path 3: CRU (Custom Resolution Utility) – any GPU

Custom Resolution Utility, written by ToastyX, is the tool to reach for when the vendor utility refuses a mode, when you want finer control over timing parameters, or when you are on Intel graphics. It is more capable because it works at a lower level: rather than asking the driver for a custom mode, CRU writes a software EDID override into the registry – effectively rewriting the table of resolutions your monitor advertises to Windows. It changes no hardware.

That power is also why CRU demands more respect. Because it overrides what the system believes the monitor can do, a bad entry can leave you with no usable picture until you undo it. So do two things before you start, both straight from the tool’s own documentation:

• Know how to boot into safe mode (via a Windows recovery drive, or by holding the power button during boot to reach Troubleshoot > Advanced options > Startup Settings).
• Know that reset-all.exe (shipped with CRU) wipes every override and restores defaults, and it can be run from safe mode if the screen is unusable.

The workflow itself:

1. Run CRU.exe (accept the UAC prompt – it needs registry access).
2. Pick your display from the dropdown.
3. Under Detailed resolutions, click Add, set your native resolution, and enter the higher refresh rate.
4. Click OK, then run the included restart.exe to restart the graphics driver and apply the change. CRU requires this restart step to take effect.

If the screen comes back at the new rate, good. If it does not, restart.exe usually recovers on its own after a few seconds; if not, safe mode plus reset-all.exe is your reset button.

The mandatory step everyone skips: TestUFO frame-skip check

Here is the trap that makes most “I overclocked to 75Hz” claims meaningless. A monitor will frequently accept a higher refresh rate, report it proudly in Windows display settings, and then quietly skip frames – displaying, say, only 60 unique frames inside a 75Hz cycle. You get the higher number with none of the smoothness, and in some cases worse pacing than stock. The reported Hz is a promise the panel did not keep.

The only way to catch this is to look at actual frames, and the standard tool is the free TestUFO Frame Skipping Checker from Blur Busters. It scrolls a row of numbered squares across the screen at your refresh rate. You photograph that motion with a phone camera set to a long exposure – around 1/10 second or longer – and inspect the result:

• A clean run shows an unbroken sequence of squares with no gaps. Per the Blur Busters method, a ~200ms exposure on a 144Hz display should capture roughly 28 successive squares.
• Gaps in the sequence mean frame skipping. Any gap, even one, means the overclock is fake at that rate.

Close other apps and browser tabs before testing, and dim screen brightness so the camera can use a longer exposure. If your overclock skips, step the rate back down and retest until you find the highest rate that captures zero gaps. That rate – not the highest one the monitor accepted – is your real overclock.

This is the entire point of the exercise. An overclock that drops frames is worse than useless; a verified, gap-free overclock is free smoothness. The test is what tells them apart.

Realistic expectations

Numbers vary so much that anyone quoting you a guaranteed figure is guessing. A 60Hz panel commonly lands somewhere in the 70-75Hz range, and many go no higher; a handful reach further. Two of the same model can disagree because of normal manufacturing tolerances. So the honest framing is a method, not a number: climb in small steps, run the frame-skip test at each one, and keep the best rate that passes clean. Whatever you get is a bonus.

A few practical notes worth keeping in mind. Higher-refresh OLEDs and TVs-as-monitors behave differently from cheap LCD panels – if you are running something like the Aorus FO48U or a desktop LCD covered in our 27-to-32-inch monitor guide, the same step-and-test method applies, but the bandwidth ceiling bites sooner at 4K because each frame is far larger. And remember that more frames only help if your PC can produce them – a smooth overclock pairs naturally with the frame-rate fundamentals we cover in DX12 vs DX11.

Overclock in small steps, verify with TestUFO every single time, and never trust the number the monitor reports over the frames your camera sees.