Convert between JSON and the three formats configuration actually ships in: dotenv, INI and Java properties. The format is detected from the shape of what you paste, and each is parsed by its own rules rather than a shared guess — which matters more than it sounds. In dotenv, only the first equals sign separates key from value, so a token containing one survives; double quotes process escapes while single quotes stay literal, which is the difference between a working multi-line key and a broken one; and a hash inside quotes is data, not a comment. INI sections become nested objects. Properties files accept a colon as well as an equals sign, join backslash continuations across lines, and decode unicode escapes. Because these files hold database passwords and API keys, the client-side guarantee is the point: nothing you paste leaves your browser.
| Feature | .env | .ini | .properties |
|---|---|---|---|
| Separator | = | = | = or : |
| Comments | # | ; or # | # or ! |
| Sections | No | Yes, [name] | No |
| Line continuation | No | No | Yes, trailing \ |
| Escapes | In double quotes | In quotes | \n and \uXXXX |
No. Every byte is parsed in your browser and nothing is transmitted, logged or stored. That is the reason to use a client-side tool for this particular job rather than a server-side one.
It survives. Only the first equals sign separates the key from the value, so a base64 token or a connection string ending in padding is not truncated. Splitting on every equals sign is the usual bug here.
Double quotes process escapes, so backslash-n becomes a real newline — which is how a multi-line private key is stored on one line. Single quotes are literal and keep the backslash. This follows dotenv's own behaviour, so a round trip through here matches what your app loads.
Only if it is outside quotes. A quoted value like "#fff" keeps its hash; an unquoted trailing hash is treated as a comment, which is what dotenv does.
Each section becomes a nested object keyed by its name, and any keys appearing before the first section header stay at the top level.
Yes. A line ending in a backslash is joined with the next, which is how certificates and long paths are written in Java properties files. Unicode escapes are decoded too.
The three formats look alike and differ in exactly the places that break a naive parser. In dotenv, only the first equals sign separates the key from the value, so a token containing an equals sign survives; an export prefix is stripped because shell-sourced files carry one; and quoting decides escape handling — double quotes process backslash-n into a real newline, single quotes are literal, which is dotenv's own rule and the difference between a working private key and a broken one. A hash inside quotes is data, not a comment, so a colour value like #fff is kept rather than truncated. INI section headers nest their keys into an object, keys before any header stay at the root, and both the semicolon and hash comment styles are recognised. Java properties allow either an equals sign or a colon as the separator, support backslash continuation across lines — joined here, since a certificate or long path routinely spans several — and use backslash-u escapes for non-ASCII, which are decoded so an accented value reads correctly rather than as literal escape text. Writing back out, a dotenv value is quoted whenever leaving it bare would change what it means on the way back in: empty values, anything with whitespace, a hash, a quote or a backslash. Detection distinguishes the three by shape — a bracketed section header means INI, colon-separated dotted keys mean properties — so a paste does not need a menu first. The security point is not decoration: these files hold database passwords and API keys, and every byte is parsed in your browser with nothing transmitted.