How TinyX encrypts your files in the browser
· TinyX · 4 min read
Most file-sharing tools encrypt your data. Fewer encrypt it on your device before it is uploaded. The difference is not marketing: it is where the key lives.
If you landed here after reading Dropbox is encrypted. That is not zero-knowledge., this is the sequel: how TinyX actually encrypts files, and what we store as a result.
That client-side AES-256-GCM path is a Pro and Max feature that you switch on. Free still covers outgoing shares with expiry and passwords, but not end-to-end encryption.
Encrypted storage is not the same as end-to-end encryption
Plenty of platforms encrypt files on disk (AES-256 at rest) and protect the pipe with TLS. That is table stakes. It protects against a stolen hard drive. It does not mean the vendor cannot decrypt what they store.
If the provider holds a usable copy of the key, or can mint one from their key-management stack, they can open the file for previews, scanning or support. The word “encrypted” still applies. End-to-end does not.
TinyX’s claim is narrower: client-side AES-256-GCM. With end-to-end encryption switched on, encryption happens in your browser before upload, and your password and the key derived from it are never sent to us. What we store is ciphertext.
How the upload path works
Here is the practical flow, without the theater:
- Key stays on the client. Your browser derives / holds the material needed to encrypt. That key is not sent to TinyX as a usable secret.
- AES-256-GCM in the browser. Files are encrypted with the Web Crypto API before they leave the device. GCM gives confidentiality plus authentication: tampered ciphertext fails decryption instead of silently corrupting.
- Ciphertext only on our side. What lands in storage is encrypted bytes plus the metadata needed to run the product (size, timing, link settings such as expiry and a password hash). Not plaintext. Not a recoverable master key.
- Direct-to-object upload. Uploads go to object storage via short-lived, signed URLs. TinyX authorizes the write; the encrypted blob does not need to pass through an app server as readable content.
Large files can be handled in chunks so a flaky connection does not force a full restart. Resume still produces consistent ciphertext for completed chunks. The important part is unchanged: we never need the plaintext to store or serve the file.
What we store when end-to-end encryption is on
When a link is live, TinyX holds:
- Encrypted file bytes
- Operational metadata (size, created time, expiry / download limits, password hash if you set one)
Your password and the key derived from it are not on that list. They stay in your browser.
Expiry works the same way as everywhere else in TinyX: when a link expires or hits its limit, the link shuts off, and the file stays in your library until you delete it.
What Free includes vs Pro and Max
Live pricing is the source of truth. Soft close, aligned with the cards today:
- Free: outgoing file share with expiry and passwords (caps: 500 MB per file / 10GB storage). Upload drops and end-to-end encryption are not on Free; both are crossed out on the Free column.
- Pro ($9) / Max ($29): higher caps (Pro 1GB/100GB; Max 5GB/300GB), upload drops, and end-to-end encryption, as described on features.
If you need client-side encryption and inbound client uploads, start on Pro and Max. If you need controlled outgoing shares that expire and lock behind a password, Free still earns its keep.
Frequently asked questions
Can TinyX staff read my encrypted files?
We can't read encrypted files. When end-to-end encryption is on, the file is encrypted in your browser before upload, and your password and the key derived from it are never sent to us. Files shared without end-to-end encryption don't have that protection, so switch it on for anything sensitive. We have a tight policy on who can access client data and how.
What if I forget the password / lose the key material?
Then the file can't be decrypted. The key is derived from your password in your browser and isn't sent to us, so there is no reset that brings an end-to-end encrypted file back. That is the trade-off of keeping the key on your side.
Is “AES-256” alone enough to trust a vendor?
No. Ask who holds the key, whether encryption is client-side by default for the files you actually send, and whether the share link can die. Algorithm names without custody details are incomplete.
Where do upload drops fit?
Upload drops (clients send files to you) start on Pro and Max. Each drop has a setting to require encryption, so senders' files are encrypted in their browser before upload. Free does not include upload drops.
Bottom line
“We promise not to look” is a policy. End-to-end encryption is a different arrangement: AES-256-GCM in your browser, your password and key never sent to us, ciphertext in storage.
See features for the product surface, or pricing to pick a tier. Try free on tinyx.co for expiry- and password-gated shares; move to Pro or Max when you need E2E encryption and upload drops.