INI to JSON Converter
INI config ko JSON mein aur JSON ko wapas INI mein convert karein aapke browser mein. Sections, comments aur global keys sab handle hote hain. Aapka data local rehta hai.
INI to JSON Converter poori tarah aapke browser mein chalta hai. Jo INI aur JSON config aap paste karte hain woh locally parse hota hai aur kabhi aapke device se bahar nahi jaata ya ArrayKit ko upload nahi hota.
JSON Formatter kholein
INI to JSON Converter ke baare mein
INI to JSON Converter ek classic INI config file padhta hai aur use clean, structured JSON mein badal deta hai, phir JSON ko seedha wapas INI mein convert karta hai. Yeh [section] headers, key=value entries, top level par section-less global keys, aur ';' ya '#' se shuru hone wali comment lines samajhta hai, jinhe woh chupchaap skip kar deta hai. Numbers aur booleans default se coerce hote hain taaki port=5432 ek real number ban jaaye aur enabled=true ek real boolean ban jaaye, ya aap har value ko ek string ke roop mein rakh sakte hain. Doosri taraf jaate hue, top-level scalars global keys ban jaate hain aur nested JSON objects named [sections] ban jaate hain. Yeh tab kaam aata hai jab aap legacy tooling config migrate kar rahe hon, INI settings ko ek JSON-based pipeline mein wire kar rahe hon, ya do configs ko ek common shape mein diff kar rahe hon. Sab kuch aapke device par chalta hai — aapka config kabhi browser se bahar nahi jaata.
Features
- Two-way conversion: INI to JSON aur JSON wapas INI
- [section] headers ko nested JSON objects mein parse karta hai
- Section-less keys ko global top-level JSON entries ke roop mein rakhta hai
- ';' aur '#' comment lines apne-aap skip karta hai
- Optional type coercion numbers aur booleans ko real JSON values mein badalta hai
- JSON objects named [sections] ban jaate hain; scalars global keys ban jaate hain
- Unclosed sections ya malformed lines ke liye saaf line-numbered errors
- Poori tarah aapke browser mein chalta hai, kuch upload nahi hota
INI to JSON Converter kaise use karein
- INI → JSON direction chunein (ya JSON → INI par switch karein)
- Apna INI config ya JSON input box mein paste karein
- Agar aap strings ke bajaye numbers aur booleans chahte hain to Coerce types toggle karein
- Converted output copy karein ya use ek .json ya .ini file ke roop mein download karein
Example
Input
name = ArrayKit
[database]
host = localhost
port = 5432
enabled = true
Output
{
"name": "ArrayKit",
"database": {
"host": "localhost",
"port": 5432,
"enabled": true
}
}
Ek global key plus ek [database] section ek top-level field aur ek nested object ban jaate hain.
Common errors aur troubleshooting
- Ek line 'Expected "key = value"' report karti hai. — Har non-comment, non-section line mein '=' (ya ':') hona chahiye. Separator add karein, ya line ko ek comment banane ke liye use ';' se prefix karein.
- Ek [section] line par 'Unclosed section header'. — Missing ']' add karein taaki header [database] jaisa padhe. Section names multiple lines par nahi phail sakte.
- port ek number ke bajaye string "5432" ban jaata hai. — Coerce types on karein taaki bare numeric aur true/false values real JSON numbers aur booleans ke roop mein parse hon.
- JSON → INI report karta hai ki use top level par ek object chahiye. — INI mein koi top-level array nahi hota, isliye apne data ko ek object mein wrap karein. Ek top-level array ya primitive sections aur keys par map nahi ho sakta.
Aksar pooche jaane wale sawaal
- Converter INI sections ko JSON par kaise map karta hai?
- Har [section] header section name se keyed ek nested JSON object ban jaata hai, aur uske neeche ki key=value lines us object ke fields ban jaati hain. Same name waale duplicate headers ek object mein merge ho jaate hain.
- Kisi bhi [section] se pehle aane wali keys ka kya hota hai?
- Pehle section header se pehle likhi keys global hoti hain. Woh JSON object ke top level par section objects ke saath rakhi jaati hain, isliye kuch nahi khota.
- Kya ';' aur '#' comments JSON output mein rakhe jaate hain?
- Nahi. ';' ya '#' se shuru hone wali lines full-line comments ke roop mein treat hoti hain aur INI → JSON conversion ke dauran skip hoti hain, isliye woh kabhi JSON mein nahi aati. Ek value ke baad inline text us value ka hissa rakha jaata hai.
- JSON → INI kaise decide karta hai ki kya section banega?
- Top-level scalar values global key=value lines ban jaate hain jo pehle emit hote hain, aur har top-level nested object ek named [section] ban jaata hai. Nested arrays ya deeper objects ek JSON-encoded, quoted value ke roop mein likhe jaate hain.
- Kya main converter ko values ko numbers ya booleans mein badalne se rok sakta hoon?
- Haan. Coerce types off karein aur har INI value ek string ke roop mein rakhi jaati hai, isliye port=5432 JSON mein "5432" rehta hai aur enabled=true "true" rehta hai.
- Kya use convert karne ke liye mera INI ya JSON config upload hota hai?
- Nahi. INI to JSON Converter local JavaScript use karke aapke browser mein sab kuch parse aur rebuild karta hai. Jo config aap paste karte hain woh kabhi aapke device se bahar nahi jaata aur ArrayKit ko nahi bheja jaata.
Related tools
- TOML Formatter — TOML format karein aur use JSON se aur JSON tak convert karein.
- YAML ↔ JSON — YAML ko JSON mein aur wapas convert karein.
- dotenv to JSON — .env file ko JSON object mein aur JSON ko wapas .env mein badlein
- JSON Formatter — JSON ko beautify, minify aur validate karein, error ki location ke saath.
- logfmt to JSON Converter — logfmt key=value logs ko JSON mein aur wapas convert karein, seedhe aapke browser mein.
- XML Formatter — XML ko beautify, minify aur validate karein, aur XML ↔ JSON convert karein.
Saare ArrayKit tools