Frequently Checked
Answers.
Find answers to common questions about direct transfers, cloud shares, encryption, and size limits.
Common Questions
No account or email is required for direct WebRTC P2P transfers. For detailed comparisons on zero-signup transfers, read our guide on sending files without accounts or email verification.
For Direct E2E transfers, file binary data is never stored on any server (0 byte cloud footprint) — it streams between the two browsers, or passes through our relay as ciphertext when a peer connection is blocked or the file is small enough that setting one up would be slower. For details on zero-cloud transfers, read our guide on sharing files without cloud storage.
Yes. Password protection uses client-side Web Crypto AES-256-GCM encryption in your browser before upload. Learn more in our step-by-step guide on how to password protect files before sharing.
You can set auto-deletion timers (1 hour, 24 hours, 7 days, or 30 days) and custom download limits. Learn how self-destructing links work in our guide to creating temporary auto-deleting file links.
Direct E2E transfers support files up to 1 GB per direct streaming session. Read our guide on sending large files without email attachment caps.
Open GetFileShare on both devices and scan the QR code to connect instantly. Read our complete guide on sending files from phone to PC without installing apps.
A file request turns the transfer around: instead of sending a file, you ask for one. The person you ask needs no account and no software — they open a link, choose a file, and it lands in your GetFileShare inbox. No. They open a link, choose a file, and send it. No signup, no email verification, and nothing to install. Only you — the person collecting — verifies an email, because that is the address the files belong to. Read the full walkthrough in our guide on requesting a file from someone.
Only if the request does not use encryption. With encryption on, the file is encrypted in the sender's browser with AES-256-GCM with Argon2id key derivation before upload, and the passphrase never reaches us — so our storage holds ciphertext we have no key for.
Direct E2E is synchronous and streams directly between online browsers. Cloud sharing is asynchronous, hosting files in temporary encrypted storage so recipients can download them at any time.
No. Passwords are processed locally in browser memory to derive AES-256-GCM encryption keys. Passwords are never sent to or stored on GetFileShare servers.