Skip to content
ConfigurationDiagnosticsPC GAMING

PS5 120 Hz Option Appears but a Game Runs at 60 Hz

The console reports a 120 Hz-capable display but a chosen game remains at 60 fps. This guide distinguishes game has no 120 fps mode from performance setting disabled using controlled comparison tests.

Quick Answer

Enable the game's supported performance mode and PS5 output setting, then use direct HDMI if needed. Confirm by checking: A genuinely 120 fps-compatible title reports the intended mode while incompatible titles remain at 60.

The console reports a 120 Hz-capable display but a chosen game remains at 60 fps. The aim is to find the first failing boundary, compare it with a working case, and correct only what is necessary. Begin with a harmless reproduction before any reinstall, account reset or deletion.

Define the symptom before changing settings

Write down the exact result and where the process stops. Check whether the game itself advertises 120 fps and inspect TV information overlay. Keep the affected console and a working control as comparable as possible: same time, same connection or account when relevant, and the same small sample of content.

When a feature works in one context but not another, that contrast is stronger evidence than a generic error message. For this case, note the current version, the selected mode or account, and whether the problem started after a driver, app, game or system change. Do not change several settings simultaneously; otherwise a later success cannot be linked to one correction.

Three explanations to separate

Potential cause What would support it Next check
Game has no 120 fps mode. The affected operation fails consistently while the control works. Check whether the game itself advertises 120 fps and inspect TV information overlay.
Performance setting disabled. The result changes with a particular account, profile or device choice. Enable the game's supported performance mode and PS5 output setting, then use direct HDMI if needed.
HDMI chain limits the current resolution. A version, permission, connection or local state differs from the working case. Compare 1080p/4K signal modes and HDMI receiver bandwidth without altering TV service menus.

Treat these as hypotheses rather than proof. Game has no 120 fps mode. This may create the visible symptom without indicating permanent damage. Performance setting disabled. A mismatch here can make otherwise healthy features appear unavailable. HDMI chain limits the current resolution. The third possibility is worth investigating only after the easier controlled tests are complete.

Safe checks in the right order

  1. Preserve the working state: Record the original setting, version and account or device combination. Protect game saves, entitlements and parental/party privacy before testing. Do not erase the existing data or configuration.
  2. Reproduce with a minimal example: Check whether the game itself advertises 120 fps and inspect TV information overlay.
  3. Confirm the boundary: Test the same action where it is known to work, and document what changes. A control that fails identically points to a shared service or hardware dependency.
  4. Check the first cause: Game has no 120 fps mode. Use the product UI to confirm this condition instead of relying on an assumption.
  5. Check the second cause: Performance setting disabled. Look for the specific mismatch between failing and working runs.
  6. Look for the third cause: HDMI chain limits the current resolution. Evaluate it only if initial controlled fixes have not restored function.
  7. Apply the smallest correction: Enable the game's supported performance mode and PS5 output setting, then use direct HDMI if needed.
  8. Repeat without additional changes: A genuinely 120 fps-compatible title reports the intended mode while incompatible titles remain at 60.

First repair: restore the intended configuration

Enable the game's supported performance mode and PS5 output setting, then use direct HDMI if needed. This is the preferred starting point because it tests a concrete explanation. After the change, completely exit and reopen the affected app or reconnect only the affected device if the product requires it. Leave unrelated settings, account details and systemwide security policy unchanged.

Observe the outcome under the same conditions used at the start. If behavior improves only once or only in an easier test case, the issue may be intermittent or partially repaired. Record that finding before declaring success. If there is no measurable improvement, return the modified setting to its earlier value and try the next documented route.

Step-by-Step Troubleshooting

Use Beginner for the reversible comparison and Advanced to isolate the remaining dependency safely.

Make a safe baseline

The console reports a 120 Hz-capable display but a chosen game remains at 60 fps. Keep game saves, entitlements and parental/party privacy protected. Write the exact result before changing settings, and note the current version and account.

Run a side-by-side comparison

Check whether the game itself advertises 120 fps and inspect TV information overlay. Use the same small, non-sensitive example on the working and failing side. Record the first visible difference.

Try the supported correction

Enable the game's supported performance mode and PS5 output setting, then use direct HDMI if needed. Change only one setting or connection at a time. Do not change account recovery details or reinstall unrelated apps.

Check the intended outcome

A genuinely 120 fps-compatible title reports the intended mode while incompatible titles remain at 60. Restart or reconnect only as necessary, then repeat the same test. If it fails, restore the original configuration and move to deeper diagnosis.

Fix path B: isolate the remaining component

Compare 1080p/4K signal modes and HDMI receiver bandwidth without altering TV service menus. Use the result to decide whether the owner of the problem is the application, the operating system, an account entitlement, a peripheral, or an external service. Examine only logs or diagnostic screens you are authorized to access, and remove tokens, addresses and private identifiers before sending a report.

A helpful comparison changes one variable at a time: the same content on another device, another account with permission, a supported mode instead of a custom setting, or another network that you control. Choose the comparison relevant to the actual symptom; switching all of these simultaneously makes diagnosis weaker.

Solution Checklist

0/12 completed

What counts as fixed?

Passing result: A genuinely 120 fps-compatible title reports the intended mode while incompatible titles remain at 60. Repeat the successful scenario once after a normal close/reopen or reconnect. Check a second unaffected feature, so the solution does not merely relocate the problem elsewhere. If the feature has an eligibility or hardware limit, correctly identifying that limit is a valid diagnostic outcome, not a defect that must be bypassed.

If the issue persists

Return to the original comparison: Check whether the game itself advertises 120 fps and inspect TV information overlay. Then collect the current software and device versions, the exact error text if present, what worked in the control run and whether the change helped. Compare 1080p/4K signal modes and HDMI receiver bandwidth without altering TV service menus. With these details, an official support team can reproduce the problem more reliably than from a request to “fix everything.”

Prevent a repeat and protect your data

Do not imply every game supports 120 fps just because the TV does. Retain a minimal record of the working version and setting, avoid unnecessary simultaneous updates, and retest the exact workflow after major supported upgrades. For managed equipment, ask the administrator before changing policy; for subscriptions or purchases, verify ownership through official account pages.

Did this solution fix your problem?

Optional feedback helps us improve this guide. Never send private data.

PRBLEM / COMMUNITY

Discuss This Solution

Ask a question, compare results, or share a safe fix that worked for you.

Describe the exact issueInclude the error, device or software version, and what you already tried.
Protect your informationNever post passwords, recovery codes, private logs or personal data.
Retry if the discussion does not load

Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.

Can't find your answer?

Tell our editors which problem needs a guide. Do not include passwords, API keys, email addresses, private URLs, or full error logs.

Analyze Error

Paste an error message to identify its likely category. Analysis takes place in your browser; only a short error category will be used if you choose to search.

Do not paste passwords, tokens, private URLs or full logs.