PC requirements and a repeatable performance check

Use the official PC baseline

The Steam listing is the authority for the PC requirements below. Minimum requirements are an entry baseline, not a frame-rate promise. This page does not assign hardware requirements to console or PUBG MOBILE.

Official Steam requirements · reviewed 12 Nov 2026

Record the machine before changing settings

Record CPU, GPU, memory, free storage, operating system and driver version. Also record resolution, render scale, display mode and preset. A later improvement may otherwise come from an unrecorded change instead of the option you meant to test.

Distinguish consistently low frame rate, intermittent stutter, network delay and a crash. Graphics settings may affect the first two but do not explain every delayed action. Capture the symptom and when it occurs before choosing a remedy.

A repeatable comparison

Choose a short route containing the problem scene. Run it once to settle initial loading, then repeat under the same conditions. Change one setting at a time and compare the same measurement window. One good moment in a quiet scene is weak evidence for a broad performance claim.

Log the route, duration, resolution, changed option, symptom and measurement method. If combat, weather or player count changes, mark the comparison as limited instead of treating it as controlled. The goal is to learn what helps this machine.

If the issue follows a driver or game update, note the version and date before troubleshooting. Use official game and hardware support for persistent failures. A reproducible report is more useful than a speculative list of tweaks.

Separate eligibility from observed performance

A specification check answers whether the machine resembles the published entry or recommended baseline. It does not measure the experience of a particular match. Conversely, one playable session does not establish that all scenes, updates and background workloads will behave similarly. Keep two records: the hardware comparison and a repeatable observation of the symptom you want to improve. They answer different questions.

Define the symptom without diagnosing it prematurely. “The camera pauses when entering this area” is an observation; “the CPU is too weak” is a hypothesis. A graphics change, background download or loading state may affect what you see. If you begin with a diagnosis, it is easy to treat every later result as confirmation and overlook a more direct explanation.

Choose a measurement that matches the symptom. A longer observation window helps reveal repeated pauses; an average alone can conceal them. A network-delay complaint needs connection observations as well as frame information. This article provides a comparison method, not an instrument that can read your hardware or diagnose a crash remotely. Write down the measurement method so that another run can use the same one.

An example log, with invented results clearly labeled

Suppose you run a fixed 90-second route three times at one resolution. You record four, five and four visible pauses using your stated pause definition. After changing one option, you record two, two and three. These numbers are invented solely to explain comparison; they are not measurements of PUBG or evidence for any specific setting. The example suggests a difference worth investigating, not a guaranteed improvement.

Next restore the original option and repeat, if doing so is reasonable for your setup. If the original pattern returns, confidence in the comparison improves; if every run now looks better, warm-up or another time-dependent factor may explain it. Record the order of runs. Changing several options and the driver together would prevent this example from isolating the effect of one option.

Preserve adverse results too. If a change makes pauses less frequent but visibility worse, the tradeoff matters. A useful record includes what became harder, not just the number that improved. Avoid carrying a setting from another machine into your own baseline as if it were a verified fix; hardware, display choices and the tested scene are part of the result.

Turn an observation into a useful support report

A compact report contains the game version, driver version, hardware baseline, reproduction route, approximate frequency and the smallest change that affects the symptom. Include a short recording only when it helps show the issue, and avoid sharing account or unrelated desktop information. “It feels bad” may be sincere but gives a helper little to reproduce.

If the problem cannot be reproduced, mark that limit instead of inventing an explanation. Keep the last known working configuration so that future comparisons have an anchor. The practical outcome of this page is a defensible local record and a clearer next question, rather than a universal collection of performance tweaks.