What the person you send it to gets
- Syntax highlighting for the language you pick, or an automatic guess if you leave it on Auto-detect.
- Line numbers, so you can say “look at line 42” and mean the same line.
- Copy in one click, with indentation and tabs exactly as you pasted them.
- Wrap lines for long lines on a phone, and Download to save it as a text file.
Nothing you paste is ever run. HTML, JavaScript and shell commands are shown as text, never executed in the reader’s browser.
Why not paste it straight into Slack or Teams?
Chat apps are built for conversation, not code. Long snippets collapse behind “show more”, some clients turn straight quotes into curly ones, and a pasted config file becomes part of the channel’s searchable history for as long as the workspace keeps messages. With TxtVanish, the chat carries a short link and the code lives somewhere with proper formatting and an end date.
Config files, .env and keys
Onboarding a developer often means handing over a .env file full of database URLs and API keys. Paste it into the Code tab, choose INI / .env or leave it on auto-detect, and set it to 1 view. If the file holds live secrets, also switch on a link password and tell it to them on a call. Rotate the keys once the person no longer needs them.
For a single password or token rather than a whole file, see sharing a password with a one-time link.
Logs and stack traces
Text is limited to 32 KB, which fits a long stack trace or a few hundred lines of log. For a full log file, attach it instead: one file of up to 10 MB per message, deleted after 7 days. Paste the interesting part as text so the reader can see it straight away, and attach the rest.
Supported languages
| Group | Languages |
|---|---|
| Web | JavaScript, TypeScript, HTML / XML, CSS, PHP, JSON |
| Backend and systems | Python, Go, Rust, Java, Kotlin, C, C++, C#, Ruby, Swift |
| Data and config | SQL, YAML, INI / .env, Markdown |
| Shell and tooling | Bash / Shell, Diff |
Anything else still displays cleanly as plain text with line numbers.
Code that changes
Code links are fixed once created. For something you’ll keep updating, such as setup instructions or a checklist, create an editable note instead. It’s plain text, but you can change it from your sender link and everyone with the link sees the latest version.