Edit CitizenFX.ini without losing your setup

CitizenFX.ini configures the installed FiveM client, not your server. Close all FiveM instances, back up the actual file, change one setting, and reproduce the same launch before deciding whether it helped. Do not paste a replacement file from a performance guide: that can discard the detected GTA path and unrelated preferences.

Locate the active file and make a backup

For a default Windows installation, enter %localappdata%\FiveM\FiveM.app\CitizenFX.ini in Run or File Explorer. A custom installation uses its own app directory. Check the target of the shortcut you actually launch instead of editing a second, unused installation.

This PowerShell snippet backs up the default file with a unique timestamp, then opens it. It does not change settings or upload anything:


$ini = Join-Path $env:LOCALAPPDATA 'FiveM\FiveM.app\CitizenFX.ini'
if (!(Test-Path -LiteralPath $ini -PathType Leaf)) {
    throw 'File not found. Locate the app directory used by your FiveM shortcut.'
}
$backup = "$ini.backup-$(Get-Date -Format 'yyyyMMdd-HHmmssfff')"
Copy-Item -LiteralPath $ini -Destination $backup -ErrorAction Stop
Write-Host "Backup: $backup"
notepad.exe $ini

Preserve the existing [Game] section. Edit a key already present rather than adding a contradictory second copy. Verify that the editor saves CitizenFX.ini, not CitizenFX.ini.txt.

Change the update channel for a controlled test

Inside the existing [Game] section, the stable-channel entry is:


UpdateChannel=production

beta and canary are testing channels, not automatic fixes for low FPS. Record the original value before a support-requested channel test. Launch once, reproduce the same action, and compare the error. Restore the previous channel afterwards unless you deliberately need that testing channel. Changing the channel is separate from choosing Legacy or Enhanced and from the GTA build a server requires.

Which settings solve which problem?

Setting	Intended use	Safe boundary
`IVPath`	The installed GTA directory	Usually leave autodetection in control. A GTA directory is not the FiveM app directory.
`SavedBuildNumber`	Preselect a game build for a compatible client track	Do not copy an old example number as “latest”; follow the server’s requirement and the track’s supported builds.
`UpdateChannel`	`production`, `beta` or `canary`	Test unstable channels intentionally, with a rollback path.
`DisableNVSP`	Control the blocked NVIDIA overlay integration	`0` allows the overlay; this is not an FPS optimization and can reintroduce crashes.
`EnableFullMemoryDump`	Capture full memory for a requested crash investigation	Large and potentially sensitive. Enable only for the reproduction, then disable and remove files when no longer needed.
`DisableCrashUpload`	Control automatic crash-dump submission	`1` disables automatic upload; it does not remove existing local dumps.
`DisableOSVersionCheck`	Suppress an operating-system warning	Suppressing a check does not make an unsupported OS compatible. Fix the OS/support problem instead.

These keys come from the official CitizenFX.ini reference . That reference contains historical build/OS examples; this guide does not treat their example numbers as current recommendations. For Enhanced restrictions, use the migration checklist.

Restore and diagnose

Close FiveM again. Copy your recorded backup back to the original path, or restore only the key you changed. Open the restored file once to check the path and values before launching. A backup restoration intentionally replaces later edits, so do not use an old backup without checking what changed since it was made.

Symptom	Check before another edit
No visible effect	Wrong installation, unsaved file, duplicate key, or another instance still running.
GTA path prompt	Verify the purchased game’s actual install directory; do not substitute a server-data directory.
Build transition still occurs	A saved preference does not override the server’s required build.
Crashes after an overlay change	Restore the original overlay setting and reproduce without the overlay.
Disk usage grows after a support test	Disable full dumps and review the locally generated files before deleting them.

Do not publish the entire INI, account identifiers or memory dump in a public support post. Share the relevant key, client track, build, exact error and the result of restoring the backup. Continue with client diagnostics, shortcut configuration, or two-client testing.