.env to JSON

What this tool does

Lines starting with # are ignored. export KEY=value is accepted. Quoted values can contain spaces. Duplicate keys keep the last assignment, matching common dotenv behaviour.

How to use it

1. Paste a .env file. Prefer a redacted copy if the file is sensitive.
2. Copy the JSON object.
3. Reset the tool when you are finished.

Privacy

This tool processes files and text locally in your browser. Your content is not uploaded or stored by this site.

ConvertPass does not include your input in analytics, URLs, or error reports. Encoding: UTF-8. Limit: 2 MB (2.00 MB).

Limitations

• Variable expansion such as $HOME is not performed.
• Multiline values work only with double quotes and \n escapes, not every dotenv dialect.

Example

# local only
export APP_URL="https://convertpass.com"
DEBUG=true

{
  "APP_URL": "https://convertpass.com",
  "DEBUG": "true"
}

Troubleshooting

Invalid key on a line

Keys must match [A-Za-z_][A-Za-z0-9_]*. Hyphens are not allowed. Rename the variable.

FAQ

Is DEBUG a boolean?

In JSON it is the string "true". dotenv values are strings. Parse booleans in application code.

Does ConvertPass store my .env?

No. The text stays in page memory until you reset or close the tab. Avoid screenshots of the workspace.

What about .env.local variants?

They use the same syntax. Merge order between files is your process, not this tool.

Are inline comments supported?

A space-hash sequence outside quotes ends the value. Inside double quotes, # is part of the value.