Can a AMD Radeon RX 6800 XT run PUBG: BATTLEGROUNDS?

Yes — comfortably

The AMD Radeon RX 6800 XT handles PUBG: BATTLEGROUNDS comfortably — roughly 171 FPS at 1080p and 153 FPS at 1440p on high settings.

171FPS @ 1080p
153FPS @ 1440p
89FPS @ 4K

High preset, upscaling off, paired with a AMD Ryzen 7 9800X3D-class processor.

How the AMD Radeon RX 6800 XT measures up

RequirementAMD Radeon RX 6800 XTMinimumRecommendedResult
GPU performance score 50 7 13 Recommended
Video memory 16 GB 2 GB 3 GB Recommended
Ray tracing ✓ Supported Game has no RT N/A
Upscaling FSR DLSS, FSR Available

Recommended settings

For 60 FPS at 1080p

Use the ultra preset. You already clear 60 FPS on high, so this leaves headroom for dips in busy scenes.

At 1440p

Comfortable — around 153 FPS on high.

At 4K

Around 89 FPS on high — genuinely viable.

Upscaling

PUBG: BATTLEGROUNDS supports DLSS and FSR. Your card supports FSR — Quality mode is worth 25–40% more frames. Compare upscalers.

How other cards handle PUBG: BATTLEGROUNDS

Graphics cardTier1080p FPSvs AMD Radeon RX 6800 XT
AMD Radeon RX 6900 XT A 171 ▲ 0 FPS Compare
NVIDIA GeForce RTX 3080 12GB A 171 ▲ 0 FPS Compare
AMD Radeon RX 7900 GRE A 171 ▲ 0 FPS Compare
NVIDIA GeForce RTX 4070 SUPER A 171 ▼ 0 FPS Compare
NVIDIA GeForce RTX 5070 B 171 ▼ 0 FPS Compare
NVIDIA GeForce RTX 3080 B 171 ▼ 0 FPS Compare

Frequently asked questions

Can the AMD Radeon RX 6800 XT run PUBG: BATTLEGROUNDS?

The AMD Radeon RX 6800 XT handles PUBG: BATTLEGROUNDS comfortably — roughly 171 FPS at 1080p and 153 FPS at 1440p on high settings.

What FPS will I get?

On high settings with upscaling off: roughly 171 FPS at 1080p, 153 FPS at 1440p and 89 FPS at 4K. These are modelled estimates — see our methodology.

What settings should I use?

Start at the ultra preset at 1080p. Then enable upscaling on Quality mode before lowering anything further.

Will my processor hold this back?

These figures assume a processor fast enough not to limit the card. If yours is older, run the bottleneck calculator — this title is unusually CPU-heavy, so it matters more than usual here.