⚙️INI & .properties ↔ JSON Converter Documentation & Guide
📋How to Convert Config Formats
- Select Conversion Direction: Choose INI/.properties to JSON, JSON to INI, or JSON to Java .properties.
- Paste Configuration Text: Paste your INI sections, Spring/Java properties, or JSON payload.
- Convert & Copy: Click Convert Config to transform keys cleanly with boolean and number coercion.
⚙️Section Mapping & Dot-Notation Flattening▼
INI `[section]` headers map cleanly into nested top-level JSON objects while booleans (`true`/`false`) and numbers coerce safely. Going the opposite direction unfolds JSON hierarchies back into `[section]` blocks or `a.b.c=value` Java property lines.
📐Formula & Mathematical Architecture▼
a.b = val ↔ { "a": { "b": val } }
🧮Concrete Worked Examples▼
[server]\nhost = 127.0.0.1\nport = 8080{ "server": { "host": "127.0.0.1", "port": 8080 } }Numeric strings like 8080 become JSON numbers cleanly.
{ "app": { "offline": true } }app.offline=trueRecursively flattens nested objects into dot-separated Java property keys.
⚠️Common Pitfalls & Edge Cases▼
- ⚠️Passing JSON arrays (`[...]`) into INI or `.properties` converters without an object key.
- ⚠️Assuming INI comments (`;`) survive roundtrip into strict JSON (JSON does not support comments).
- ⚠️Forgetting quotes if an INI value has meaningful leading/trailing spaces.
💡DevOps & Backend Config Workflows▼
- Migrating legacy PHP/Windows `.ini` settings into modern JSON config schemas.
- Flattening nested JSON configs for Spring Boot `application.properties` files.