INI File Editor
Edit .ini and .cfg files as a sectioned table, then export INI or JSON.
No rows yet — paste .ini or .cfg content above and press Parse.
Comment lines, blank lines and section order are kept. Keys outside any section are exported under the "default" group in JSON.
How to use it
- Paste your .ini or .cfg content into the text panel and press Parse.
- The content appears as rows: a section row for every
[name], a key/value row for every setting, plus comment and blank rows. - Edit keys and values directly in the table. Use Add key, Add section or Add comment to extend the file.
- Pick the mode: INI to JSON for a structured view, INI to INI to apply your edits, or JSON to INI to build a config from a JSON object.
- Press Copy or Download to take the result as settings.ini or settings.json.
Common use cases
- Editing a config without a merge mess - change one value in place instead of rewriting the whole file by hand.
- Turning legacy config into JSON - export sections as nested objects and feed them into a modern config loader.
- Generating an INI from a template - start from a JSON object of defaults and convert it to a file.
- Cleaning up a hand-maintained file - unrecognized lines are kept as comments rather than silently dropped.
- Reviewing what a file actually sets - the table view makes duplicate or empty keys obvious.
Why it stays private
Config files regularly hold database URLs, tokens and internal host names. Parsing and export happen in the page with plain string handling, so the file never travels anywhere.
FAQ
Q: Where do keys that appear before any section go? A: They stay at the top of the file. In the JSON export they are grouped under a "default" key, because JSON needs somewhere to put them.
Q: How are comments handled? A: Lines starting with # or ; are kept as comment rows and written back unchanged. An inline comment after a value is stripped from the value on parse, so it does not become part of the setting.
Q: Are duplicate keys allowed? A: The table keeps both rows and shows them separately, so you can spot the conflict. The JSON export keeps the last value, matching how most INI parsers behave.
Q: What does JSON to INI expect? A: An object. Nested objects become sections, and scalar values at the top level become keys before the first section. Arrays and other structures are serialized to their JSON text form.
Your data stays on this device
INI File Editor runs 100% locally. Everything you paste or drop is processed by your own browser and never transmitted. Nothing is stored on our servers — close the tab and it is gone.
Nothing you type is sent to a server, logged, or used for analytics. The page works even with your network disconnected after first load.