AMD Radeon RX 6500 XT Review: The Return of the 'Budget' GPU

We can only hope it will actually cost $199

Radeon RX 6500 XT XFX card photos
(Image credit: © Tom's Hardware)

Tom's Hardware Verdict

The AMD RX 6500 XT has all the makings of a new budget GPU, including underwhelming performance. Unfortunately, the price only qualifies as "budget" in today's world of radically inflated GPU prices, and even then, it will likely sell for far more than its official $199 MSRP.

Pros

  • +

    + Theoretically cheaper than the alternatives

  • +

    + Decent 1080p medium/high performance

  • +

    + Very high clocks

  • +

    + Doesn't need a lot of power

Cons

  • -

    Specs and features cut too far

  • -

    64-bit memory and x4 PCIe slot connection

  • -

    Likely won't sell for anywhere close to MSRP

  • -

    Slower than previous budget GPUs

Why you can trust Tom's Hardware Our expert reviewers spend hours testing and comparing products and services so you can choose the best for you. Find out more about how we test.

The AMD Radeon RX 6500 XT represents the first real attempt at a modern "budget" GPU in over two years. With GPU prices still hovering in the stratosphere and the shortages not set to ease until perhaps the end of 2022 (if we're lucky), the best graphics cards are continually overpriced and sold out, and everything in our GPU benchmarks hierarchy feels more like a theoretical upgrade rather than something you should actually consider buying. We wish things were better, and we can hope that the RX 6500 XT will actually manage to land closer to its MSRP than other recent GPU launches… but don't be fooled by that $199 starting price. It will likely end up selling at $300 or more, making this more of a mid-range offering in the traditional sense.

But let's forget about the price for a moment. AMD cut down the core features of the RDNA 2 architecture just about as far as it could go with Navi 24. The result is an incredibly tiny chip, measuring just 107mm^2, but still packing 5.4 billion transistors. It's basically half of the Navi 23 in most areas, plus AMD cut out some of the hardware video codec support for good (bad, actually) measure. Can the resulting graphics card be worth the $200 asking price, never mind the more likely $300+ street prices we're likely to see? That's what we want to find out.

Swipe to scroll horizontally
AMD GPU Comparisons
Graphics Card RX 6500 XT RX 6600 RX 5500 XT RX 570
Architecture Navi 24 Navi 23 Navi 14 Polaris 20
Process Technology TSMC N6 TSMC N7 TSMC N7 GloFo 14N
Transistors (Billion) 5.4 11.1 6.4 5.7
Die size (mm^2) 107 237 158 232
Cus 16 28 22 32
GPU Cores 1024 1792 1408 2048
Ray Accelerators 16 28 N/A N/A
Boost Clock (MHz) 2815 2491 1717 1244
VRAM Speed (Gbps) 18 14 14 7
VRAM (GB) 4 8 4 / 8 4 / 8
VRAM Bus Width 64 128 128 256
ROPs 32 64 32 32
TMUs 64 112 88 128
TFLOPS FP32 (Boost) 5.8 8.9 4.8 5.1
Bandwidth (GBps) 144 224 224 224
Power (watts) 107 132 130 150
Launch Date Jan 2022 Oct 2021 Dec 2019 Apr 2017
Launch Price $199 $329 $179 $169
Jarred Walton
Senior Editor

Jarred Walton is a senior editor at Tom's Hardware focusing on everything GPU. He has been working as a tech journalist since 2004, writing for AnandTech, Maximum PC, and PC Gamer. From the first S3 Virge '3D decelerators' to today's GPUs, Jarred keeps up with all the latest graphics trends and is the one to ask about game performance.

  • jacob249358
    that piece of **** hasnt even sold out yet its so bad
    Reply
  • Roland Of Gilead
    Tut, Tut! AMD are taking the michael here. What an awful card for the price. There simply is no buttering it up to sound good, despite the writers best efforts.
    Reply
  • InvalidError
    You threw out the highly inconsistent runs? Those may have been a side-effect of AMD only giving it an x4 interface on top of 4GB 64b memory and possibly be the most important detail people need to be aware of. AMD has cut far too many corners on this thing to be worth more than $150 were it not for current market conditions.
    Reply
  • PEBKAC6
    Been reading the content on this site for a decade and finally had to register to comment on the amount of nonsense in this 'review.'

    It's obvious this was not released with AAA-titles in mind. It was obviously released for esports games such as CS:GO / OW / DotA. Hence you excluding resolutions from the review for games that run excellently even with much less VRAM makes absolutely no sense.

    Were you aware you can run the most popular esports titles listed above on 2k resolution paired with a 165 Hz monitor comfortably with a decade old 2GB GPU such as GTX770? Apparently not.

    The price and x4 performance on PCIe 3.0 are major negative sides worth noting but given how excessively you advertise yourself as a GPU guru with nearly 20 years of experience it's shocking how ignorant a review can be. This card is literally what the community needed among the GPU shortage and it serves anyone playing some of the most popular games at 1k/2k at high refresh rates with low power draw and noise.

    Entry level cards are crucial since old hardware dies over time and the vast majority of games run exceptionally even with these specs. The target audience is far off in this review.
    Reply
  • InvalidError
    PEBKAC6 said:
    Were you aware you can run the most popular esports titles listed above on 2k resolution paired with a 165 Hz monitor comfortably with a decade old 2GB GPU such as GTX770? Apparently not.
    People generally don't buy new GPUs to run titles that already do 200fps on 10 years old cards. They buy new GPUs when their current one cannot keep up with the resolutions, details and frame rates they want to play more GPU-intensive stuff at and most of those games will quite easily pass the 4GB mark. That is where the RX6500 drops behind every other 4GB GPU from the last four years that has 3.0x16 or 4.0x8 PCIe.
    Reply
  • JarredWaltonGPU
    InvalidError said:
    You threw out the highly inconsistent runs? Those may have been a side-effect of AMD only giving it an x4 interface on top of 4GB 64b memory and possibly be the most important detail people need to be aware of. AMD has cut far too many corners on this thing to be worth more than $150 were it not for current market conditions.
    The inconsistent runs, mostly in Far Cry 6, occurred on all 4GB cards. At one point I ran the GTX 1650 Super through the 1080p Ultra + HD test sequence maybe a couple dozen times — I even restarted the game and restarted the PC a couple times just to try and get the results to stabilize at one value. Performance ranged from as low as ~7 fps average (once) to as high as ~55 fps (once). Most of the results clumped into the ~44 fps range and the ~15 fps range. At times it seemed like every other run would be "bad." It's almost certainly a game bug/issue, where the game in DX12 mode isn't managing VRAM effectively and sometimes ends up in a bad state. I could have tested in DX11 mode and hoped the drivers would "fix" things, but then that opens the door to having to test both APIs on every GPU — and then do the same for every other game that supports multiple APIs.

    For those wondering about the test suite, I need to test all GPUs on the same set of games, for the GPU benchmarks hierarchy as well as other guides. I specifically focused on the 1080p medium performance as that's what this card is designed to handle. However, even at those settings it's a questionable card. This is profiteering from AMD and the GPU market in general. The RTX 3050 will at least potentially warrant a $200-$250 MSRP (in "normal" times). The RX 6500 XT would have been a $100-$120 GPU normally. It probably would have been called the RX 6400 actually, leaving the RX 6500 name for a card with better specs and performance.

    If I were to only test lighter fare to show how this card can handle games that even cards from eight years ago run just fine, what good does that do anyone? "Hey everyone, this is PEBKAC6 Marketing, letting you know that games that don't demand much from your GPU don't demand much from your GPU! Isn't that amazing? Aren't you happy to know that CS:GO, which can run at reasonable performance even on Intel's integrated graphics solutions from five years ago, can run on a $200 graphics card? You should all just go buy it! This is the card we all need! Never mind that it's slower than the card it replaces and has worse specs (RX 5500 XT 8GB). 5-stars, would buy again!"
    Reply
  • King_V
    I was afraid of this on a few points.

    Even back in the Polaris days, while my memory is a bit hazy, I seem to recall that there was greater benefit in increasing memory bandwidth than in GPU clocks. Yes, they went with fast GDDR6, but the 4GB limit is an issue.

    Cutting down the PCIe lanes on the 5500 was a problem. Cutting it even more for the 6500 was a mistake.

    I mean, even look at the difference between the GTX 1650 GDDR5 vs GDDR6; they were able to reduce the clock speeds of the GPU, and it still performed notably better, while still keeping things in the same TDP envelope.

    Similarly, the performance/watt of RDNA with the 5000 series seemed to suffer going into the budget level. The 5500 had a notably lower performance/watt than the 5600. The 6500XT does have lower power, but the cut down GPU needs higher clocks... so the TDP is not reasonable for the performance it's delivering, especially given the RDNA2 architecture.

    On the other hand, I guess they'd need, say, a 6600 sized chip, or at least something not quite cut down THIS small... and run the clocks lower, to get decent performance with less power consumption. I'd say that they may be trying to make the most of limited supply, but this is on N6, so, I would guess there's no supply constraints on that.

    The particular cuts they made seem to be the wrong kind. Keeping in mind that I am NOT an electronics engineer of any sort.

    Call me unrealistic, but I think this is a card that should have been designed to manage at least equal the 5500 XT in performance, and do so without the need of a PCIe power connector.
    Reply
  • InvalidError
    JarredWaltonGPU said:
    The inconsistent runs, mostly in Far Cry 6, occurred on all 4GB cards.
    If repeatability is so problematic on 4GB cards overall, it may be a sign that graphs need to get variance bars to represent how (un)repeatable results are.
    Reply
  • VforV
    Assuming you can actually purchase the Radeon RX 6500 XT for $199, or at least somewhat close to it, it's not a bad card.
    Sorry, as much as I like AMD, this is a bad GPU! And unless someone is "forced", no one should buy it.

    We should not accept this kind of garbage GPUs, anymore than we should accept nvidia's scumminess with their new policy of NO reviews before launch and NO more MSRP again!
    Whatever the haters want to say about them, again HUB and GN are the voice of impartiality and say it exactly how it is: in this case a bad GPU from AMD.
    M5_oM3Ow_CIView: https://www.youtube.com/watch?v=M5_oM3Ow_CI

    ZFpuJqx9QmwView: https://www.youtube.com/watch?v=ZFpuJqx9Qmw
    Reply
  • JarredWaltonGPU
    InvalidError said:
    If repeatability is so problematic on 4GB cards overall, it may be a sign that graphs need to get variance bars to represent how (un)repeatable results are.
    Usually it's only a problem if you change settings and don't exit and restart the game (in a game that lets you do that). I've done lots of testing over the years, and generally speaking cards with 8GB and more VRAM can go from 1080p to 1440p to 4K in testing without exiting and restarting. With a 4GB card, you sometimes end up in a severely degraded performance state and need to exit and relaunch. But with low-level DX12/Vulkan APIs, sometimes it's just a periodic glitch that causes performance to suffer. I've seen issues with 4GB and even 6GB cards in Watch Dogs Legion at times. Usually, exiting and restarting the game will clear the problem. Far Cry 6 was unusual in that it had high run to run variance seemingly whenever it exceeded the card's VRAM. The game also showed changes in the amount of VRAM it thought it needed, which was certainly odd.

    Anyway, the problem with charts is that there are lots of people who can only really manage to grok relatively simple bar charts. Start adding variance and all that other stuff and only stock investors and traders, and stats majors, are likely to get what we're showing. Plus, how many runs should I do for each setting? I try to stay with three, but do more if there's clear variance happening, and sometimes a lot more if I'm just unable to figure out what's happening (e.g. with FC6). If I had to do 10 runs of each setting, then run the results through some stats to get variance bars and such, it would dramatically decrease my throughput and workflow, and likely the potential gains (people understanding a bit better what's happening) would not even be there.

    Fundamentally, I want to provide a relatively "modern" look at how graphics cards perform in a variety of situations. I have a couple of very recent games in my updated test suite, along with some slightly older games that are still useful (and relatively easy to use). I don't want to show a bunch of games that specifically won't tax 4GB cards, but neither do I only want to look at games that basically require 8GB or more. And then when I create the aggregate scores for the GPU hierarchy, I definitely don't want a bunch of random "bad" results that penalize slower GPUs. So, I figure most people will use settings that run at closer to acceptable levels of performance, and running a few extra tests to see where the high water mark is helps keep the charts more sensible. For people who care, there's the text that will call out anomalies. 🙃

    As an aside, RDR2 strictly prevents you from selecting settings that exceed a card's VRAM, but you can edit the config file to try and get around that. I was able to force 1080p "ultra" and 1440p "ultra" to run, though 1440p resulted in periodic graphical corruption. 4K ultra is too much, however, and just crashes to desktop. Anyway, I need some meaningful number to avoid skewing the overall results — not having a low score present can increase the calculated average, but putting in a "0" result can go too far the other direction.
    Reply