.env lines → JSON

Client

Paste lines from a sample .env file— dotted keys become nested objects; quoted values stay strings.

Learn more: env lines to JSON

Split KEY=value lines and rebuild nested objects when keys contain dots—comments starting with # are ignored.

Parsing

This is a pragmatic parser, not a full dotenv implementation. Export lines with `export KEY=` are not stripped automatically—remove the prefix first if needed.

.env lines → JSON

?

Lines with KEY=value; dots in keys build nested objects. Comments and empty lines are skipped.

Common use cases

  • Convert pasted .env samples into nested JSON for documentation, tests, or comparing environments.
  • Import flat KEY=value files where dotted keys should become nested objects in app config.
  • Spot values that should stay quoted after coercion to numbers or booleans.

Common mistakes to avoid

  • Including export or shell syntax in the paste

    Strip bash export, comments, or inline shell unless your workflow documents support for them.

  • Multiline certificate or PEM blocks in env files

    Complex multiline values may need dedicated handling—confirm the parser supports your delimiter style.

FAQ

Is parsing done on your servers?

No. Lines are parsed into JSON locally in your browser.

Can I round-trip with JSON → .env?

Yes for many simple trees. Very complex values may need manual checks after conversion.

More tools

Related utilities you can open in another tab—mostly client-side.