Radeon RX Vega 64 8GB
8GB HBM
Benchmark FPS at 1080p
131FPS
- Our rating /100
- 53.5/100
- Vega64s we've tested
- 14
Shared family total: Radeon RX Vega 64 8GB.
Explore this GPUHands on the keyboard?
S swap · / search · D change theme.
Off while you type.
FOR THE LOVE OF THE UPGRADE
RX Vega 64 8GB leads this benchmark at 131 FPS, compared with 102 FPS for RTX 3050 8GB. That is a 29 FPS difference in GPUsed’s continuous 1080p FurMark workload.
Powered by GPUsedGPU X
Radeon RX Vega 64 8GB
GPU Y
GeForce RTX 3050 8GB
8GB HBM
Benchmark FPS at 1080p
131FPS
Shared family total: Radeon RX Vega 64 8GB.
Explore this GPU8GB GDDR6
Benchmark FPS at 1080p
102FPS
Historical total for this model.
Explore this GPURX Vega 64 8GB records 131 FPS versus 102 FPS for RTX 3050 8GB. GPU Y is the percentage reference.
RECORDED BENCHMARKSGPUsed’s recorded 1080p FurMark benchmark averages, not predicted gaming FPS. Quantities are GPUsed’s supplied historical model totals. Exact-model and shared-family historical totals are identified on each card; they are not the retained sample size of the displayed average.
THE MATCH-UP
An 8GB badge conceals a memory-type difference here. AMD documents HBM2 on the RX Vega 64, while the RTX 3050 8GB uses GDDR6. The Vega leads by 29 FPS in this workload, so for a used purchase compare the condition and cooler design of the actual units before deciding.
| Detail | RX Vega 64 8GB | RTX 3050 8GB |
|---|---|---|
| Memory | 8GB HBM | 8GB GDDR6 |
| Documented release | first documented retail availability. documented market. | first documented retail availability. documented market. |
| GPUsed archetype | Divisive | Workhorse |
| GPUsed Legend Rating Editorial legacy rating | 5.5 /10 | 5.1 /10 |
| More about this GPU | Read the RX Vega 64 8GB profile | Read the RTX 3050 8GB profile |
The benchmark is GPUsed’s continuous 1080p FurMark workload. The figures compare that workload, rather than predict FPS in a particular game. The percentage on the bench uses GPU Y as its reference: (GPU X FPS ÷ GPU Y FPS − 1) × 100. Swap the cards and the reference changes.
Our rating compresses the benchmark scale out of 100. It does not drive the percentage calculation. GPUsed’s historical quantities retain their model or shared-family labels; they are not the retained sample size of the displayed FPS average.
Read how the benchmark and ratings workKeep one card on the bench and see how the nearby choices compare.
Figures and variant matching checked . GPUsed supplies the benchmark averages and historical quantities. The references below support the GPU identity and specification context.
The pair note comes from GPUsed’s reviewed comparison material, with current variant and numeric checks. Individual GPU profiles retain their own documented release qualifications and review dates.
02 / A DIFFERENT VIEW
131FPS
102FPS
03 / KEEP IT ON THE BENCH
Your saved match-ups.
Saved on this device
Keep a match-up here. Pin the ones worth coming back to.
04 / UNDER THE HOOD
The right numbers are useful.
Knowing what they mean is better.
GPUsed’s recorded average benchmark results from continuous FurMark runs at 1080p. They compare graphics cards under this workload. A game’s settings, your CPU, ray tracing and upscaling can all change in-game performance.
All 257 selectable variants use GPUsed’s supplied results. The reported runs were at 1080p and typically lasted 30–60 minutes. We do not add test sessions or infer gaming frame rates from those results.
GPU Y is the reference. We divide GPU X’s FPS by GPU Y’s FPS, subtract one and multiply by 100. A positive figure means X leads; a negative figure means Y leads. Swapping changes the reference, so it changes the percentage too.
It is the existing compressed benchmark scale, with the fastest card in GPUsed’s dataset at 100. It gives older cards more room on the scale. The percentage difference is always calculated from FPS, never from the rating.
These are GPUsed’s supplied historical totals for each model or recorded model family. They are distinct from the retained sample size of a particular FPS average. They show GPUsed’s experience with each model; they do not tell you how many readings went into a particular FPS average.