Move app config between .env, JSON, and Kubernetes
.env files, Docker --env, and Kubernetes Secrets are the same keys in three costumes. Paste a dotenv file and emit JSON, Docker flags, or a Secret manifest. Or paste a flat JSON object and get .env back.
Comments and export prefixes are skipped. Quoted values keep spaces and = signs.
Parsing rules this tool follows
- Blank lines and
#comments are ignored. export KEY=valueis treated asKEY=value.- The first
=splits the key from the value. - Double quotes honor
\\nand\\".
If you need to compare two env files after conversion, use the Diff Checker.
Docker vs Kubernetes output
Docker output is a chain of --env KEY=value flags. Kubernetes output is a Secret with stringData or base64 data. Base64 here is the same encoding as the Base64 Encoder/Decoder. It is not encryption.
YAML formatting for other documents lives in YAML ↔ JSON Converter.
Secrets handling
Mask values in the preview so a screen share does not leak tokens. Copy unmasked still copies the real conversion, because that is what you need to paste into a sealed store.
How to use
- Paste a
.envor, for reverse mode, a JSON object. - Choose JSON, Docker, Kubernetes stringData, Kubernetes data, or JSON to .env.
- Copy the unmasked output.
Privacy
Parsing is local. Values are not persisted.
Frequently Asked Questions
Does a naive split on = break quoted values?
Yes. This parser keeps text after the first =, then unquotes single or double quotes. A value that contains = stays intact.
What is the difference between stringData and data?
stringData is plain text in the manifest. data is base64, which is encoding, not encryption. Kubernetes will still store it as a Secret object, not as ciphertext.
Are values stored?
No. Masking only changes the preview. Copy unmasked writes the real output to the clipboard. Nothing is written to localStorage.
Can this talk to a cluster?
No. It only writes YAML or Docker flags.
Is the file uploaded?
No.