Secure Paste
Paste the text, set a password and expiry if you need them, and send the link—not a plaintext dump in email.
What Secure Paste is for
Secure Paste shares text, code snippets, and short notes when email and chat leave copies sitting in too many inboxes. You create a paste, receive a link, and send that link to the person who needs the content.
This is not a video URL box. Video downloads live on the downloader pages. Paste is for text. API keys for a one-time handoff, meeting notes, and code fragments fit. Multi-megabyte documents belong in a file share.
Illegal or abusive content is still forbidden under the site terms. Encryption does not change that policy. Use the tool for legitimate handoffs you are allowed to share.
Encryption on the device
Encryption runs so Vidzilla servers do not hold a readable copy of the paste body. The passphrase you choose participates in that protection. Without it, a stranger with only the link still faces the password gate when you enabled one.
Choose a passphrase you can communicate accurately. A mistyped password means the recipient cannot open the paste. Prefer a phrase you can say aloud or send on a second channel without ambiguity.
Same-channel password plus link weakens the point of the lock. Send the link on one channel and the password on another when the content is sensitive. That habit is ordinary operational security, not optional decoration.
Expiry and cleanup
Set an expiry when the text needs to stop being available after a meeting or a deploy window. Once the paste expires, the link stops serving the content. Create a new paste if you still need to share.
Do not rely on a paste as the only archive of critical secrets. Copy what you must keep into your own password manager before expiry. The paste is a handoff, not a vault.
For one-time secrets, set a short expiry and tell the recipient to open the link promptly. Do not leave a deploy key sitting for days behind a quiet link. After they confirm receipt, let expiry finish the cleanup.
How to create a paste
Open Secure Paste, enter the text, set password and expiry if you need them, and create the paste. Copy the link and send it on your usual channel. Tell the recipient the password separately when you enabled one.
Avoid creating a second paste of the same secret “just in case.” Extra live links multiply exposure. If the first paste expired unused, create a fresh one with a new password.
Paste links forwarded into group chats multiply exposure. Send the link in a direct channel when the content is sensitive. Group forwards are how short-lived secrets become long-lived screenshots.
What belongs here and what does not
Short credentials for a handoff, configuration snippets, and meeting agendas fit. Huge logs and binary dumps do not. When the recipient needs a file instead of text, encrypt the file on the encrypt-file page rather than dumping binary into Secure Paste.
Video addresses belong on the downloader. Password-protecting a PDF belongs on the PDF tool. Hashing a string for integrity checks belongs on the hash tools. Use each page for its job.
Do not paste production secrets into a paste that also has a long expiry. Short expiry plus password is the usual pair for credentials. Long expiry is for low-sensitivity notes that still benefit from a link instead of an email trail.
Code snippets and wrapping
Long lines of code stay intact in the paste body. Recipients who open on a phone may need to scroll horizontally; that is expected. Warn them if the snippet depends on whitespace that a chat app would have mangled.
Prefer Secure Paste over dumping code into Slack or email when the snippet includes tokens or internal hostnames. The paste can expire; the chat history often cannot.
When the recipient will edit the code, remind them to copy into their editor promptly. Do not treat the paste link as a permanent repository URL.
Free use and habits that keep pastes safe
Secure Paste is free to use on Vidzilla for ordinary text sharing. Keep pastes short enough for a text handoff. When you are done, you do not need to delete a local file—the paste lives behind the link until expiry.
Burn-after-read habits matter more than clever passwords. Short expiry, separate password channel, and a direct message for the link beat a long-lived paste with a weak shared password in the same thread.
If you suspect a link was forwarded too widely, treat the secret as exposed. Rotate the credential and create a new paste only if you still need to hand it off once more.
Questions about Secure Paste
Is Secure Paste encrypted?
Yes. The paste body is protected so servers do not store a readable copy. Still avoid pasting anything you are not allowed to share.
Can I require a password?
Yes. Set a password when you create the paste and share it separately from the link so the same channel does not carry both.
What happens when a paste expires?
The link stops serving the text. Create a new paste if you still need to share the content.
Can I paste a video link to download it?
No. Use the video downloader pages for that job. Secure Paste is for text and short notes only.
Is Secure Paste free?
Yes for ordinary text sharing on Vidzilla. Keep pastes sized for a handoff rather than a document archive.
Do you read my paste?
The design keeps the body unreadable on the server. Still avoid pasting anything you are not allowed to share, and use expiry for secrets.