How to Find Hidden Graphics Settings in Config Files (2026)

To find hidden graphics settings in config files, set everything once in the in-game graphics menu, close the game completely, then open the config file it just wrote in a plain-text editor. The file is usually in Documents, AppData or the install folder, and AppData is hidden by default so you have to reveal it first.

That first trick matters more than it sounds. Games write out only the keys they know about, but a finished config file usually contains a good deal more, including options the menu never exposes: uncapped frame rates, render scale sliders, LOD bias, wider field of view and quality levels above the top preset. Once you can see them, you can change them.

Below is the method that works on any PC game, engine-agnostic and version-agnostic, followed by concrete examples for the older GTA titles, GTA IV-style profile setups and GTA V. Exact file names and paths shift between releases and between storefronts, so treat everything game-specific as an illustration rather than a promise.

What You Need

You need four things before you touch anything: the right game version identified, the folder the game actually writes to, a backup copy of that file, and a plain-text editor.

• The active version and launcher. Steam, Rockstar Game Social Club, Battle.net, Epic and the Microsoft Store can each keep a separate save or config for the same game. Edit the one your launcher points at.
• A backup. Copy the file, paste a copy beside it, and name it something like settings backup oct.xml. This is the single step people skip and regret.
• A plain-text editor. Notepad works, but Notepad++, VS Code or Sublime Text give you search, syntax highlighting and multi-file find-and-replace across a whole folder.
• The game closed. Not minimized. Fully exited, including any background process holding the file.

One more warning before you start: file names and locations differ a lot between GTA III, Vice City, San Andreas, GTA IV and GTA V. They come from three different engine generations, three different folder conventions and three different launcher eras. Nothing you learn about one of them transfers cleanly to the others, and copying a config block between them will simply be ignored at best.

Step-by-Step

How to Find the Correct Configuration Folder

Config files live in six places on Windows, and it takes about two minutes to check all of them.

Location	What usually lives there	Example path
Documents (My Games)	Older and Rockstar-published titles, plus a lot of legacy single-player games	C:UsersNameDocumentsMy GamesRockstar GamesGTA V
AppData (Local)	Modern Windows-native titles and anything that ships with a launcher	C:UsersNameAppDataLocal
AppData (Roaming)	Games that follow the older roaming convention, many older titles	%APPDATA%
AppData (LocalLow)	Games built with Unity and some legacy engines	%USERPROFILE%AppDataLocalLow
Game install directory	Classic-era titles that keep everything next to the executable	C:Program Files (x86)SteamsteamappscommonGameName
WindowsAppsPackages	Microsoft Store and Game Pass titles, under a publisher.appid folder	%LOCALAPPDATA%PackagesPublisher.App_123

The fastest route is the address bar shortcut. Click the address bar in File Explorer, type %APPDATA% or %LOCALAPPDATA% and press Enter. AppData is a hidden folder, but these variables jump straight into it without revealing anything, which is why players on the Steam forums call it the fastest way to a config file.

AppData splits into three branches for a reason. Local holds machine-specific data that shouldn’t roam between PCs, so resolution and GPU settings land here. Roaming holds data meant to follow a profile between machines, so options and interface preferences land here. LocalLow exists because games running with reduced privileges need a writable location they can actually use, which is why a lot of Unity-built titles write there. When a game ships a profile that syncs through Social Club or the Epic launcher, roaming behaviour is often the reason a config edit seems to follow you onto another machine.

If the folder name is a guess, stop guessing and search. Open File Explorer, navigate up to C:UsersName, then use the search box on the right and search for *.xml, *.ini, *.cfg, *.json or *.config. Sorting by date modified and looking for a file written the last time you played is faster than reading names.

To see hidden files, open the View tab and tick Hidden items in Windows 10. In Windows 11 the same toggle sits on the View menu as Show, then Hidden items. From a command prompt, this reveals them all at once:

attrib -h -s -r "C:UsersNameAppData" /s /d

One trap worth naming: the file inside the install directory is often not the one the game reads. Installation files are frequently read-only and shipped for verification or first-run setup, while the live settings live in your user profile. If a value changes nothing, you edited the wrong copy.

How to Identify Hidden Graphics Settings

Hidden graphics settings are keys already present in the file but absent from the menu. Open the file and search for terms like resolution, refresh rate, shadow quality, texture quality, anti-aliasing, frame rate, vsync, draw distance, ambient occlusion, anisotropic filtering, field of view, render scale, LOD bias, ray tracing and frame generation.

A plain ini file groups keys under bracketed section headers, sets each value after an equals sign, and marks inactive lines with a semicolon. A line beginning with ; is commented out, so it is documentation or a disabled option rather than something the engine currently reads:

[SystemSettings]
ResolutionSizeX=1920
ResolutionSizeY=1080
FullscreenMode=2
VSync=0
; AnisotropicFilteringQuality=8
FrameRateLimit=0

That FrameRateLimit line is the classic example: plenty of menus do not expose a frame rate limit, and the file already contains it.

JSON uses braces and quoted keys, and its values must stay one of a few types, such as a number, a string, a boolean or an object. Watch the commas, because a stray one is the most common cause of a broken config:

{
  "vsyncInterval": 0,
  "maxFps": 0,
  "fieldOfView": 90,
  "anisotropicFiltering": 16,
  "rayTracing": true
}

XML uses angle-bracket tags, and a self-closing element ends with />:

<setting name="ShadowQuality" type="uint" value="2" />
<setting name="TextureQuality" type="uint" value="3" />

Now check whether the key you found is actually live. A key may be commented out, may be duplicated further down the file where the last occurrence wins, may use a synonym your search missed (drawdistance, DrawDistance and farClip all describe similar ideas), or may live in a second file entirely. The same setting often appears in a main config and in a secondary one, and the engine reads whichever it loads last.

And do not assume every key the file contains is honoured by your version. Developers strip options between releases, and the engine silently ignores values it no longer recognises. That is not a bug you can fix by editing harder.

How to Edit Values Safely

Edit values with the game fully closed, change one thing at a time, and keep the file’s formatting intact.

1. Close the game completely, then confirm it has exited in Task Manager.
2. Copy the config file and paste the copy next to it as your backup.
3. Open the original with Notepad++ or VS Code, not Word or WordPad. Those insert invisible formatting characters and smart quotes that break the parse.
4. Change only the value after the equals sign. Never rename keys, never delete bracketed sections you do not recognise, never reorder lines.
5. Keep the file extension exactly as it was. Saving settings.xml as settings.xml.txt makes the game ignore it silently.
6. Save with the same encoding the file used. UTF-8 is the usual one; switching to UTF-16 or adding a byte-order mark can stop the file loading.
7. Relaunch the game and check the menu before you assume it worked.

Do not copy a block of settings from another version of the same game, or from another game entirely. Value ranges change between releases, and a setting that meant 2 for ultra in one build can mean something else in the next.

How to Test Whether a Change Worked

Most games read their config at startup, so a change needs a full restart to take effect. Editing while the game is still running usually loses the change, because the game rewrites the file from memory when it exits.

Test in three layers: open the in-game graphics menu and see whether the option now appears or shows your new value; watch your frame rate and frame time with a trusted overlay or Windows’ own performance tools, comparing against a baseline you recorded before the edit; and check the file itself, since some settings are read but never written back.

Revert one change at a time. If you changed six keys and the game now starts with black screen flicker, restoring the backup tells you the edit broke something but not which key, so you are back to square one. One key per launch is slower and always faster overall.

Signs the file is malformed: the game resets everything to default, refuses to launch, or logs a parse error. Signs it was simply ignored: everything behaves exactly as before, which usually means a higher-priority profile overrode your file or the key is not supported in this version.

Game-Specific Configuration Examples

Older GTA titles (GTA III, Vice City, San Andreas). These run on the RenderWare era engine and keep a simple, flat ini. Files typically sit in the install folder or in Documents, use lowercase section names, and store a handful of numeric values from 0 to a few. The set of readable keys is small, so the wins here are frame rate caps and draw distance rather than modern quality tiers. Editing these while Social Club is syncing can cause a conflict, so sync first, then edit.

GTA IV-style profile setups. Newer titles in this family separate graphics into their own profile file rather than dumping everything into one config, which is why people report editing a setting and seeing no effect. Open the file the game actually loads, change the value, and confirm after restart.

GTA V settings.xml. This is the most edited file in the series, sitting under DocumentsMy GamesRockstar GamesGTA V. A clean, useful sequence is: set everything in the graphics menu, exit the game, open settings.xml in a text editor, then change values such as FXAA, MSAA, texture quality, shadow quality, grass quality and frame rate limits. Save and restart. Community trainers and mod managers edit the same file through their own interface, so mixing manual edits with a trainer running at launch can have one overwrite the other.

Official settings, community tools and mod managers are three different layers. The official layer is what the game exposes. Community tools add keys the developer never shipped. Mod managers can rebuild the whole profile on launch. Know which one you are editing before you change anything, and never run a mod manager and hand edits against the same file at the same time.

Common Mistakes

Almost every bad outcome traces back to one of these, and all of them are avoidable.

• Editing the wrong folder. You changed a file in the install directory instead of the user profile. Confirm which one the game rewrites after you tweak an in-game setting.
• Editing while the game is running. The game overwrites your edit on exit. Close it fully first.
• Deleting comments or required sections. A game that cannot parse the file falls back to defaults. Remove nothing you do not understand.
• Using Word or WordPad. Smart quotes and invisible characters corrupt the file. Use Notepad++ or VS Code.
• Wrong value format. Typing a word where a number belongs, or a boolean where an integer is expected. Match the type used by neighbouring keys.
• Saving in the wrong encoding, or letting the editor append .txt to the filename.
• Assuming a visible option is active. Greyed-out entries in a menu often mean the quality preset is not set to custom. Set the preset first, then edit the key.
• Changing everything at once. You lose the ability to identify the culprit when something breaks.
• Forgetting cloud sync. Launcher profile sync can push the old config back over your edit. Sync, then edit, then restart.
• Forgetting the backup. Then a patch night ruins the afternoon.

Tips for Finding More Advanced Graphics Options

Once the basics work, widen the search. Diff your tuned file against a clean backup and every key you never touched is visible in one view. Search synonyms, including the abbreviated forms engines use internally. Check the game’s own support page and community wiki, which often list keys the menu omits.

Isolate variables by changing one key per launch and noting the frame time. Document the game version and patch number with each change, because a key that exists in one patch can vanish in the next. And keep a plain-text note of the settings you care about, so rebuilding after a patch takes a minute instead of an evening.

Know the ceilings before you chase them. Some options are limited by the engine rather than the file, some are locked to the display mode your monitor and GPU support, some require the game to run as administrator, and console or mobile ports expose a different set entirely. If a key refuses every reasonable value, that is usually a hard limit, not a syntax mistake.

Two faster alternatives sit alongside config editing. Launch options such as unlock-max-settings style flags change what the menu offers, and in-game console commands apply instantly for testing. Both are different mechanisms from editing a file, and mixing them without understanding which one wins leads to confusing results.

Frequently Asked Questions

Conclusion

Start with one thing: identify which config file the game actually writes, copy it as a backup, and make a single documented change with the game fully closed. Relaunch, check the in-game menu, and measure before you decide whether it worked.

Everything past that is repetition of the same loop. Keep the file open only while the game is shut, preserve the formatting, and expect the values to be game-specific, version-specific and platform-specific, which is why a setting that works on one machine may do nothing on another.