How to Edit an INI File | Change Any Setting

Editing an INI file means opening it in a plain-text editor like Notepad, finding the right section header and key-value pair, modifying the value, and saving without changing the encoding.

A game stutters, a boot option needs adjusting, or a program refuses to launch. The fix for each of these often lives inside a single INI file. Knowing how to edit an INI file is one of those skills that takes two minutes to learn and saves hours spent hunting through menus that don’t exist. The process is straightforward: open the file in a plain-text editor, locate the section and key-value pair you need, make the change, and save.

What Exactly Is an INI File?

An INI file is a plain-text configuration file that programs use to store initialization settings. The name comes from the word “initialization.” These files use a simple structure that any text editor can read and modify.

The format has three basic elements:

• Sections: Marked by a header in square brackets, like [SystemSettings]. Everything below belongs to that section until the next header.
• Key-value pairs: The actual settings, written as Key=Value — for example, timeout=30.
• Comments: Lines starting with a semicolon (;) are human notes and are ignored by the program.

Windows apps, game engines like Unreal Engine, and embedded systems such as MiSTer FPGA all rely on INI files. The format has been around since the early days of Windows 95 and remains in wide use today.

Editing an INI File on Windows: The Standard Method

The built-in Notepad app can handle basic INI edits, but you need to take a few precautions first. Follow these steps for a clean, safe edit on Windows.

1. Locate the file. INI files are often hidden in system folders. Turn on hidden file visibility by opening File Explorer, clicking View, and checking Hidden items.
2. Make a backup copy. Right-click the INI file and select Copy, then paste it into a separate folder. Editing system files like Boot.ini can prevent the OS from booting if you make a mistake — a backup is your safety net.
3. Open Notepad. Search for “Notepad” from the Start menu and launch it.
4. Open the INI file in Notepad. Click File > Open. Change the “Files of type” dropdown to All Files (*.*), navigate to the INI file, and open it.
5. Edit the value. Find the section and key you need. Change the value after the equals sign — for instance, modify timeout=30 to timeout=60. Delete the entire line to remove a setting.
6. Save the file. Click File > Save. Keep the original filename and location. The new settings take effect the next time the application reads the file.

One warning: Notepad saves files with Windows-style line endings (CR/LF). If the INI file is destined for a Linux or embedded system, use Notepad++ instead — it can preserve Unix-style LF-only endings, which prevents file corruption on non-Windows platforms.

Editing INI Files on macOS and Linux

Both macOS and Linux have built-in text editors that handle INI files cleanly, as long as you work in plain-text mode.

On macOS: Open TextEdit, go to Format > Make Plain Text, then open the INI file. Save in plain-text format when you’re done.

On Linux: Drop to the command line and use a terminal-based editor to avoid line-ending issues. Two reliable options:

• nano — Type nano filename.ini to open the file, edit with the arrow keys, and save with Ctrl+O.
• joe — Type joe filename.ini for a lightweight editing experience with Unix-native line endings.

Either editor preserves the LF-only line endings that Linux programs expect, so the file will not break on the target system.

Common Mistakes That Break INI Files

A single typo in an INI file can cause an application to crash or a game to refuse to open. The table below shows the most frequent errors and how to avoid each one.

What Makes Game INI Files Different?

Games like Ark Survival Ascended, Skyrim, and XCOM store graphics, performance, and gameplay tweaks in INI files. The editing process is the same — open with Notepad++ or a similar editor — but a few extra rules apply.

Anti-cheat concerns. Some games detect modified INI files as tampering. Set Steam to Offline Mode before testing your changes, and never edit INI files while the game is running. A single misplaced value can flag your save as modified.

Game-specific syntax. Unreal Engine games use a [SystemSettings] section header for performance overrides. Add your key-value pairs below that header — for example, r.fog=0 to disable fog. Keep a blank line above and below the new entries for readability, and duplicate lines will cause the second entry to be ignored.

Always back up the original. Game INI files often reset after an update, so keep a copy of your tweaked version outside the game folder. Microsoft’s official documentation on editing boot configuration files reinforces the same principle — backup first, edit second.

Choosing the Right Text Editor

The editor you choose matters more than you might think. The wrong one can introduce line-ending problems or lack the features that make INI editing error-proof. This table compares the most common options.

The Core Rules for Editing INI Files

Keep these six rules in mind every time you open an INI file, and you will never corrupt a configuration or waste an afternoon troubleshooting a bad edit.

1. Backup first. One copy takes ten seconds. A missing original can take hours to reconstruct.
2. Use the right editor for the platform. Notepad is fine for Windows-only files. For anything that touches Linux, macOS, or an embedded system, use Notepad++, nano, or another Unix-aware editor.
3. Check the section header. Every key-value pair must sit below a valid [SectionName]. A header with a typo sends the whole section into limbo.
4. Match the case. false and False are not the same in many applications. Scan the existing file for the exact pattern and stick with it.
5. One key per line. Duplicate keys create confusion — the program may read the first, the last, or none at all. Delete the old line before adding a replacement.
6. Test before closing. Launch the application or reboot (for boot files) and confirm the change works. If something breaks, restore your backup and try again.