Local data safety
Data redaction and .env comparison: what masking cannot prove
Masking reduces accidental exposure on screen; it does not remove the need to review the data and the destination before sharing.
Content updated: · Maintainer and corrections
Key presence is separate from value equality
An empty value is present, not missing. Compare by key rather than line order, and reject duplicate assignments instead of guessing which value the receiving runtime will choose. The .env Diff report contains only key names and statuses; revealing a source on screen does not add values to the export.
Sources are concealed by default and the eye button reveals one source temporarily. Browser memory still contains the original input until you clear or leave the page. Masking is not encryption, secure deletion or protection from browser extensions, screen recording or an already compromised device.
Use the documented syntax subset
There is no single universal .env standard. This tool accepts ASCII KEY=value assignments, optional export and single-line quoted or unquoted values. It rejects backslash escapes, multiline values, variable expansion, command substitution, ambiguous inline comments and duplicate keys. Comments on their own lines are supported. Syntax errors identify the side, line and reason without echoing the raw value.
Each input is limited to 1 MiB, 10,000 lines and 5,000 keys. Comparison runs in a local Worker with a five-second timeout. The table shows a bounded preview; the value-free TSV contains all keys. Different runtime parsers may interpret values differently, so test the final file with your project's loader.
Explicit redaction is not anonymization
An exact JSON Pointer selects only the value at that path. Removing or replacing a named field does not find secrets elsewhere in text, array entries, keys or nested copies. Do not label the output anonymous or free of personal data without a separate review.
Local-first processing prevents these tools from uploading your content, but a copied or downloaded report may still reveal project structure through key names and record relationships. Use synthetic examples when possible; share only with an authorized destination.
Left: PORT=3000
Left: EMPTY=
Right: PORT="3000"
PORT → same
EMPTY → missing-right
Report contains no values.Data provenance