MLToolslabel · build · tune · ship

Developer

.env, JSON & Compose Environment Converter

The same twelve variables end up in a .env file, a compose file, a ConfigMap and a shell script. Paste any one and get the others, with quoting handled, comments preserved where the format allows, and secrets masked in the preview if you ask.

Loading the tool…

How it works

01

Paste

.env, JSON, YAML environment list, ConfigMap data, or export lines; the format is detected.

02

Review

Keys and values in a table; toggle masking for values that look like secrets.

03

Copy the target

.env, JSON, compose environment, ConfigMap, Secret (base64), shell exports, systemd Environment= lines.

Formats, limits and the numbers that matter

Quoting

Values with spaces, hashes or dollars are quoted per format; multi-line values use the format's convention.

Interpolation

${VAR} references are kept as text; the tool does not expand them.

Secrets

Kubernetes Secret output base64-encodes values as kubectl expects; nothing is stored.

Common questions

Does it validate variable names?

Yes; names must be letters, digits and underscores, and duplicates are flagged.

Can it merge two .env files?

Paste both; later values win and overrides are listed.

Export for GitHub Actions?

Yes; an env: block is one of the targets.

Next in the workflow

YAML, JSON & TOML ConverterConvert between YAML, JSON and TOML with validation, and see exactly where a config file breaks.Encoders, Hashes & IDsBase64, URL and hex encoding, JWT decoding, MD5, SHA-1, SHA-256 and SHA-512 hashes, and UUID or ULID generation.JSON Formatter, Validator & Tree ViewerFormat, validate, minify and explore JSON as a collapsible tree, with a path query and error positions.