PRIVATE BROWSER TOOL
Share API Keys & .env Files on Discord Without Leaking
Encrypt the values before handing them off through Discord. Paste a short .env snippet below, check its syntax, then send the generated link directly.
Syntax preview
Send the generated link in a Discord DM, rather than posting raw credentials. Protect the full link too. Literal values only; no expansion. One KEY=VALUE pair per line. Encrypted in this browser. No signup.
Questions about this handoff
Can I upload an entire .env file?
This tool accepts pasted text up to 4,000 characters and 6,000 UTF-8 bytes. Share only the variables the recipient needs.
Does encryption make a public Discord post safe?
No. The complete link grants access. Share it privately with a verified recipient; encryption cannot control what they do after decryption.
Share a scoped development secret
Use a restricted, temporary API key where possible. Paste the required KEY=VALUE lines; comments and literal quoted values are supported. This editor accepts short snippets, not file uploads or multiline quoted values.
Choose a note or a room
A one-open note suits a single delivery. Use the room toggle if you need a follow-up conversation. Neither mode prevents a recipient from saving the secret after reading it.
If a key has already leaked
Creating a Vanish link does not undo a previous disclosure. Revoke or rotate the exposed key at its issuing service, then share a replacement through a trusted channel. The headline describes avoiding a raw-secret post, not a guarantee against every leak.
Questions about this tool
Does Vanish expand my .env values?
No. The editor validates literal KEY=VALUE lines without expanding variables or executing values.
Does the link revoke my API key when it expires?
No. Expiry limits access to the Vanish note or room, not the underlying credential. Recipients can keep copies. Rotate credentials when appropriate.