TEMPORARY FILE SHARING

Share it now. Do not turn it into permanent storage.

this2.link creates a temporary encrypted channel for a file or text. An open browser provides the content, and the application server does not keep a file copy for later download.

Create a temporary link

Available while a source is online · no account

THIS2LINK / CHANNEL

01BROWSER AENCRYPT LOCALLY

WEBRTC / CIPHERTEXT

02BROWSER BVERIFY + RESTORE

NO SERVER FILE COPY

PROCESS

A link tied to live availability

Open the channel

Choose one file or enter text. Processing and encryption happen in the browser before anything is transferred.

Keep the tab open

The sending browser answers the channel and provides encrypted content to approved or full-link recipients.

Let the handoff end

A receiver may temporarily provide the verified ciphertext onward. Once the final source leaves, availability is no longer guaranteed.

TEMPORARY BY DESIGN

No forgotten upload folder

Traditional file-sharing services often create a durable server copy with an expiry policy. this2.link uses a different lifecycle: browsers are the temporary sources, so there is no application storage bucket to clean up later.

This makes the tool suitable for immediate exchanges, but it also means the link is not a backup and should not be treated as durable hosting.

WHEN TO USE IT

For content that only needs to get there

Use a temporary channel for a one-off handoff, a file sent during a live conversation, text too awkward to retype, or a quick transfer between your own devices.

No registration workflow
No permanent server-side file copy
Encrypted in the browser
Clear failure when no source remains

BOUNDARIES

Temporary-sharing limits

Keep an online source

Closing every source tab can make the content unavailable immediately or after local cache state is lost.

Save what you need

Recipients should save important files locally. this2.link is a transfer path, not a backup system.

One item at a time

The current preview passes text or one file at a time, with a maximum file size of 150 MB.

FAQ

Temporary file sharing FAQ

Is there a fixed expiration timer?

No fixed lifetime is promised. Availability depends on whether a browser that holds the encrypted content is still online and able to answer.

Can a receiver keep the link alive?

After a complete verified receive, that browser can temporarily become another source while its page remains open.

Can I delete the server copy?

There is no application-server file copy to delete. A receiver may still save the plaintext file locally, and browsers may temporarily cache ciphertext.

What if the sender closes the page too early?

The transfer can fail unless another completed receiver is already online as a source. Reopen the original link and retry when a source is available.

Temporary sharing for active browser handoffs.