In many setups, yes. HDMI 2.0 can often run 1440p at 144 Hz without compression, but only if the source device, monitor input, and cable all support that exact mode.
The short answer behind the spec
The 18 Gbps ceiling of HDMI 2.0 is why this question comes up at all. HDMI 2.0 was designed for much heavier video workloads than earlier HDMI versions, and 1440p at 144 Hz generally fits within that bandwidth. In practical terms, 2560 x 1440 at 144 refreshes per second is demanding, but it is still a realistic target for a well-implemented HDMI 2.0 connection.
That matters because 1440p at 144 Hz support is not usually presented as a compressed workaround. The bigger jump to HDMI 2.1 is more often tied to higher-bandwidth demands such as 4K at 120 Hz, broader gaming features, and more upgrade headroom. If your goal is QHD at 144 Hz, HDMI 2.0 is often enough both on paper and in real use.
A useful way to think about it is this: 1440p at 144 Hz sits near the upper end of what HDMI 2.0 can handle comfortably, while 4K at 120 Hz is where HDMI 2.1 becomes the clearer choice. That distinction helps you avoid overspending when your real target is a fast 27-inch or 32-inch gaming display rather than a 4K 120 Hz setup.
What “without compression” really means in buying terms
The HDMI 2.1 jump to 48 Gbps matters because that standard is associated with more demanding display modes and extra gaming features. By contrast, 1440p at 144 Hz on HDMI 2.0 is not usually treated as a case that inherently needs that extra bandwidth. For buyers, the real question is less “Will this secretly compress the image?” and more “Will this exact source port and monitor port expose the mode correctly?”
That is where product pages and spec summaries often mislead. A monitor may advertise 144 Hz or 165 Hz, yet only one input actually supports that full mode at native resolution. In practice, the panel may be fast enough and the cable may look modern enough, but the settings menu still stops below the advertised number.

Why some HDMI 2.0 setups still fail
The whole signal chain matters more than the cable label. Resolution, refresh rate, HDMI version, and graphics hardware all have to line up. That sounds obvious, but it is exactly where many setups break down.
Forum examples in the notes show the pattern clearly. In one case, a 27-inch gaming monitor paired with integrated graphics could reach 2560 x 1440 at 60 Hz or 1920 x 1080 at 120 Hz, but not 1440p at 144 Hz. The likely bottleneck was not the monitor and not HDMI 2.0 as a standard, but the motherboard’s HDMI output path and what it actually supported. In another laptop example, the limiting factor was TMDS and pixel-clock capacity, which helps explain why some ports labeled “HDMI 2.0” still miss the target.
This is the distinction that matters most: spec-level support is not the same as device-level support. A port can carry the right label and still have lower real-world limits because of GPU implementation, firmware, monitor timing support, or conservative EDID settings. That is why one setup runs 1440p at 144 Hz cleanly while another, on paper, looks almost the same and tops out at 120 Hz.

A simple example makes the risk easier to see. If your motherboard manual only promises something like 4K at 30 Hz on its HDMI output, no better HDMI cable will turn that port into a native 1440p 144 Hz gaming path. On the other hand, if both the GPU and monitor explicitly list 1440p at 144 Hz over HDMI 2.0, a certified cable and a short run under about 10 ft give you a much better chance of getting exactly what you paid for.
How to tell if your port can really do it
The best buying advice is to match the display to the hardware, not the other way around. That applies to ports just as much as it does to panel type or resolution. Before buying a cable or monitor, check the source device specs, the monitor’s per-port timing table, and whether the advertised maximum refresh rate applies to HDMI, DisplayPort, or both.
Checkpoint |
What you want to see |
What should make you pause |
Source device |
HDMI 2.0 or better with explicit QHD high-refresh support |
Vague “HDMI” wording or a low published maximum output |
Monitor input |
2560 x 1440 at 144 Hz listed on HDMI |
144 Hz listed only for DisplayPort |
Cable |
Certified high-speed cable, ideally short |
Old, unverified, or very long cable |
Settings |
Native 2560 x 1440 available at 144 Hz in the GPU or OS menu |
144 Hz appears only at 1080p, or only 60/120 Hz at 1440p |
The 144 to 165 Hz range is a major step up from 60 Hz, which is why this mode matters so much. If you play shooters or racing games, or simply spend long hours scrolling and moving windows, the difference between 60 Hz and 144 Hz is easy to notice. The gap between 120 Hz and 144 Hz is smaller, but it is still worth preserving if that is the experience your monitor and GPU were meant to deliver.
When HDMI 2.0 is the right answer, and when it is not
HDMI 2.0 still has a solid mainstream role. If you are using a 27-inch 1440p gaming monitor, a capable PC, and a monitor that explicitly supports 144 Hz over HDMI, HDMI 2.0 remains a practical and cost-effective choice. It makes particular sense when you want a simple single-cable setup and are not aiming for 4K at 120 Hz or the extra feature set tied to HDMI 2.1.
The case for HDMI 2.1 gets stronger when your priorities change. If you want 4K at 120 Hz, VRR and ALLM in a console-oriented setup, or more room for future display upgrades, HDMI 2.1 is the cleaner fit. If your monitor’s spec sheet is vague or clearly favors DisplayPort for the highest refresh rates, treating HDMI 2.0 as “good enough” can easily turn into hours of troubleshooting that a different port would have avoided.

That is why mixed-use buyers should read modern monitor recommendations carefully. The best current gaming monitor recommendations reinforce the same broader point: resolution, refresh rate, panel quality, and port selection all work together. A fast panel is only as immersive as the input path feeding it.
HDMI 2.0 can deliver 1440p at 144 Hz without compression, but only when the full connection is built for it. Treat the port label as a starting clue, not final proof, and you will make better buying decisions and spend less time troubleshooting.





