Add your INI file
Drop one or more .ini files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
INI to TOML
Converting a .ini font to .toml repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
Private for supported formats — processed in your browser
Runs on your deviceConvert supported files
Drop INI files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.About converting INI configuration to TOML configuration
Converting a .ini font to .toml repackages the same glyphs and metrics for a different delivery target. A .ini file is the oldest surviving configuration format in common use: key=value lines, optionally grouped under [section] headers, with no types and no nesting. Everything is a string until the program reading it decides otherwise.
A .toml file is a configuration format designed to map unambiguously to a hash table: key/value pairs grouped under bracketed section headers, with real types for strings, integers, floats, booleans, dates and arrays. It aims to be obvious to a human reading it, which is what separates it from JSON and YAML. For this route the practical draw is unambiguous — the same document cannot be read two ways, which is YAML's recurring failure and comments and real date types, neither of which JSON has — balanced against deeply nested structures become verbose and hard to follow, which is worth knowing before you commit a large batch.
Why convert INI to TOML?
The practical trigger for this conversion is usually a mismatch: with .ini, no specification, so parsers genuinely disagree on real files. Switching to .toml buys you unambiguous — the same document cannot be read two ways, which is YAML's recurring failure, which is why it is the better fit for application and build configuration where a human edits the file by hand. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
INI vs TOML at a glance
| Aspect | INI configuration (.ini) | TOML configuration (.toml) |
|---|---|---|
| Format type | Text-based — characters and structure, so there is no visual quality loss | Text-based — characters and structure, so there is no visual quality loss |
| How it stores data | structure is one level deep: sections contain keys, and sections cannot nest | types are explicit and inferred from syntax: quoted strings, bare integers, floats, booleans, and RFC 3339 datetimes |
| Strongest at | legacy application configuration, especially on Windows | application and build configuration where a human edits the file by hand |
| Weak spot | no specification, so parsers genuinely disagree on real files | deeply nested structures become verbose and hard to follow |
| Metadata | none. Comments are dropped, since the target formats mostly have nowhere to put them | none. Comments are not carried into other formats, and no format here has a comment channel to receive them |
Pick TOML as the output
Select .toml in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if TOML is selectable, the route is real and validated.
Convert on your device
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Verify and download
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid TOML file. Outputs keep the original filename with the .toml extension.
INI to TOML questions, answered
Will converting INI to TOML lose quality?
There is no visual quality to lose — ini is text-oriented and toml is text-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Is it private to convert INI files here?
Yes — the .ini file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Where will the TOML file work?
Parsers exist for every mainstream language, and Cargo, pip, Poetry, Hugo and Netlify all consume TOML natively. Browsers have no built-in support. Novus Convert reads it locally and converts to JSON, YAML, INI, plain text and ENV — the last of which accepts only flat scalars, because an environment file has no way to represent an array or a nested table.
Will the TOML file be bigger or smaller than my INI?
It depends on the content: types are explicit and inferred from syntax: quoted strings, bare integers, floats, booleans, and RFC 3339 datetimes. Convert one representative file first and compare before batch-processing a large set.
What happens to the metadata in my INI file?
In .ini, none. Comments are dropped, since the target formats mostly have nowhere to put them. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.
Can I convert TOML back to INI?
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .ini → .toml → .ini is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.