How does secret redaction work?

The tool uses pattern matching to identify sensitive keys (containing SECRET, TOKEN, KEY, PASSWORD, AUTH, PRIVATE) and replaces their values with placeholders like your_api_key_here, producing a safe-to-commit .env.example.

Why are duplicate keys dangerous in .env files?

Different runtime loaders (such as Node.js dotenv, Python python-dotenv, Docker Compose) handle duplicate keys differently. Some preserve the first occurrence while others overwrite with the last, causing silent bugs between development and production.

Are my environment variables or API keys uploaded anywhere?

Never. All parsing, validation, and redaction execute 100% in your browser. No secrets or tokens are ever sent to an external server.

.env File Inspector & Redactor

Inspect environment variable files for duplicate keys and syntax violations, mask sensitive credentials, and generate safe .env.example templates in seconds.

100% Client-Side Privacy

Total Variables 0

Detected Secrets 0

Duplicate Keys 0

Syntax Errors 0

Source .env 0 lines

Sanitized Output / .env.example 0 lines

Frequently Asked Questions

What patterns trigger secret redaction?

Keys containing substrings like SECRET, PASSWORD, PASS, KEY, TOKEN, AUTH, PRIVATE, CREDENTIAL, and SIGNATURE are recognized as confidential.

Does this tool support multiline values and comments?

Yes. Comments (# ...) and blank lines are preserved in their original locations when generating .env.example templates.

Can I convert my .env into JSON for Docker or Kubernetes?

Yes. Clicking "Export to JSON" converts all parsed key-value pairs into a clean JSON object format.

Are my secrets safe from third parties?

100% safe. This utility executes purely within your local web browser tab without sending any HTTP requests.