How to use Dotenv Inspector and Example Builder
- Paste single-line assignments or choose one UTF-8 .env text file up to 256 KiB. A chosen file replaces the pasted text. Use sample values where possible.
- Read the key, line and syntax report. Choose whether the example’s distinct keys should keep their input order or sort alphabetically.
- Download .env.example or the JSON inspection report. Review the retained key names before sharing, and clear private input when finished.
Example: Dotenv Inspector and Example Builder
Create placeholders for APP_ENV and API_KEY while leaving the comment out.
Options
- Choose an .env text file
- Optional, up to 256 KiB. A chosen file replaces pasted text. File values remain local and never appear in the example.
- .env assignments
- Up to 256 KiB and 5,000 lines. Inspects single-line KEY=value assignments and an optional export prefix. Values are neither displayed nor evaluated; every example value becomes REPLACE_ME.
- Sort example keys alphabetically
- When selected, the example lists distinct keys alphabetically. Otherwise it keeps their first-appearance order. Every value becomes REPLACE_ME in either case; the inspection report keeps line references.
Supported inputs and limits
- 256 KiB and 5,000 lines.
- Reports key names, line numbers and error kinds without returning source values.
- Every example value is REPLACE_ME; comments are omitted.
- No shell evaluation, interpolation, deployment validation or guarantee that key names themselves are non-sensitive.
- Chosen-file input takes precedence.
More details
The page retains its distinct inspection task; it does not load values into this application or connect to services.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
The inspector does not load an environment
Assignments are parsed as text. There is no interpolation, shell execution or configuration loading. Quoted multiline values and shell expressions are outside the supported syntax. A report of distinct names does not prove that a particular application accepts those names or will boot with them.
Placeholder files can still reveal context
Replacing every value reduces accidental secret disclosure, but names and line numbers can identify services or application structure. Comments and original values are absent from the output. Inspect the example before sharing and do not treat a cleaned placeholder file as a working production configuration.
Questions about Dotenv Inspector and Example Builder
Are source values included in the example?
No. Every value is replaced with REPLACE_ME.
Can variable expressions execute?
No. The tool does not evaluate shell commands or interpolate variables.
Can key names reveal information?
Yes. Review the retained names before sharing the example.