AnonDrop is a file host. You drop a file in the browser and you get a direct link you can send anywhere, embed, hotlink or hand to a download manager. There is nothing to install and nothing to sign up for.

On top of that free layer we run paid plans that turn the same storage into an S3-compatible object store for applications, backups and build artefacts. Both sides use the same encryption and the same storage design, described on our security page.

No. Open AnonDrop, drop a file in and you get a share link immediately. An account only becomes useful when you want a dashboard, higher limits or long-term retention.

Never. Our website does not require you to create user accounts. Instead, every browser generates a unique user key which is utilized for login purposes.

That user key is a seed, and it is the only thing tying your uploads together, so keep a copy of it. Anyone holding it can reach your file list, and losing it means losing the dashboard view of those uploads. Individual share links keep working either way.

We do not ask for a name, an email address or a phone number, and we do not build a profile of you. An upload is identified by a random key that only you and the people you send it to know.

The site also runs behind proxy services, so your IP address is not exposed to us, and we do not log IP addresses or user agents.

No. What you upload is what everyone downloads, byte for byte. We never re-encode, repack or rewrite the content you send us.

Free costs nothing, needs no account and is not a trial. Anonymous file links stay unlimited on it: you can keep making share links for as long as you like without ever being asked for a card.

• Unlimited anonymous file links
• 100 GB of storage and 200 GB of transfer every month
• Up to 5 GB per file, at up to 20 MB/s per download
• Direct download and hotlink support, with resumable, range-capable transfers
• Torrent and web-seed export
• Automatic malware scanning
• No account, no email, no tracking

They add the developer surface and a far larger allowance. Pro is 4.99 a month, 49 a year, or 149 once for a lifetime licence. Business is 19.99 a month or 199 a year.

• Pro: 2 TB storage and 5 TB transfer every month, objects up to 5 TB, uncapped transfer speed, the S3-compatible API, private objects, presigned expiring links, password-protected and self-expiring downloads, signed webhooks, usage analytics, 10 access keys, 25 buckets and 1200 API requests a minute.
• Business: everything in Pro, plus 20 TB storage and 50 TB transfer every month, unlimited access keys with per-bucket scoping, 500 buckets, 10 team seats sharing one set of buckets, 6000 API requests a minute, bulk prefix operations and folder archives, and priority support.

The side-by-side comparison lives on the pricing page.

Cryptocurrency, credited to a wallet you top up yourself. There is no card on file, no billing address and no recurring charge to chase someone about cancelling.

Plans are settled in SOL. You top up your wallet, then spend from it when you buy or renew, so nothing is ever taken without you starting it.

USD is only the unit we quote in, because it is the one you can compare against every other provider. The charge itself is in SOL, converted at the live rate at the moment of checkout, so the SOL amount reflects what the market says a dollar is worth right then.

That is why the SOL figure moves between visits while the USD figure stays put. Whatever amount the checkout screen shows is the amount that will be taken.

Your account falls back to Free. Nothing is deleted, nothing is held hostage, and no invoice keeps running in the background.

Your stored data stays reachable and your existing links keep working. The paid-only surfaces stop authenticating until you renew, so the S3 API answers with a subscription error and access keys stop signing requests. Renew and everything resumes with the same keys and the same buckets.

A lifetime Pro licence never expires.

The free tier handles everyday transfers comfortably and paid plans lift the ceiling for large archives, video masters and disk images. Uploads are chunked, so a dropped connection resumes instead of starting over.

In concrete numbers: up to 5 GB per file on Free, and up to 5 TB per object on Pro and Business.

Free uploads stay while they are being used. Paid plans pin your files for the life of the plan, and you can delete anything yourself at any moment from the link you were given.

There is no countdown running on an ordinary upload. If you want one, paid plans let you set an expiry on an object when you store it, and the object is removed once that moment passes.

From the dashboard, pick the file and delete it. By hand, send a POST to /delete/FILE_ID?key=YOUR_KEY. Through the S3 API, an ordinary DeleteObject or multi-delete call does it, and the space the object used is credited back to your quota straight away.

Deleting an object releases the encrypted chunks behind it, so the file stops being retrievable. Because we cannot link a file back to a person, only the holder of the key can trigger this.

Downloads are never queued, and there is no waiting screen, no countdown and no captcha. Free downloads run at up to 20 MB/s each; on Pro and Business transfer speed is uncapped and fragments are delivered in parallel.

The API has a separate per-minute request allowance: 60 requests a minute on Free, 1200 on Pro and 6000 on Business. Going over it returns a standard slow-down response rather than disabling your key.

Every file is erasure coded into data and parity shards spread over independent nodes, so a node can disappear entirely and your download still completes while the missing shards rebuild.

We run EC 14+4: 14 data fragments plus 4 parity fragments, 18 in total across 18 storage nodes, and any 14 of them rebuild the file. Four nodes can fail at the same time with no data loss. There is a longer write-up on erasure coding.

Point an S3 client at our endpoint and it works unchanged. We speak the S3 REST dialect the standard tooling expects: SigV4 header and presigned authentication, buckets, objects, ranged reads, multipart uploads, copy, multi-delete and ListObjectsV2.

That covers the AWS CLI, boto3, rclone, s3cmd and Cyberduck. Bucket names follow the ordinary S3 naming rules, so any name you can create here is also legal in the tools you already use.

aws --endpoint-url https://anondrop.net/s3 s3 cp big.iso s3://my-bucket/

The endpoint is https://anondrop.net/s3, and https://s3.anondrop.net answers as an endpoint too. Whatever region string your client insists on sending is accepted. The S3 API is available on Pro and Business; there is a fuller guide on the S3 page, and the plain HTTP API is documented under Info.

Mint one from your dashboard once you are on a paid plan. You get an access key id and a secret, and each key can be named, scoped to specific buckets and marked read-only.

The secret is shown once, at the moment the key is created. Copy it then. We keep it encrypted and never display it again, so if it is lost the fix is to revoke the key and mint a new one.

Revoking takes effect immediately: a revoked key stops resolving, so the next request signed with it is refused. Pro allows 10 live keys; Business is unlimited.

On paid plans, yes. Objects can be private, and you hand out a presigned link instead: a URL carrying its own signature and expiry, valid for as long as you choose up to seven days, and refused the moment that window closes.

You can also put a password on an individual object, or give it a download limit or an expiry time so the link retires itself.

Yes. Rightsholders can file a notice through the takedown form and we act on valid reports quickly. An uploader can dispute a removal with a counter-notice.

Our content policy and DMCA page lists what is not allowed and what a formal notice must contain: a statement, sworn under penalty of perjury, that you or your company holds exclusive rights to the content, and the name of your organisation so the report is categorised correctly. Notices go to [email protected], and authorised requests are executed through the takedown form. A completed takedown permanently deletes the content and locks the file key, after which visitors to the link see a public takedown notice with the reason given.

One limit worth stating plainly: our seed-based architecture means we cannot link a file back to a person, so while we remove infringing content on a valid notice, our ability to act against repeat infringers as individuals is limited by that design.

We have a strict no-log policy. We do not log IP addresses, user agents, or any other personally identifiable information. We do not use cookies or any other tracking technologies. All files are encrypted on our servers.

Paid accounts get usage analytics, and those are counters only: bytes stored, bytes transferred, request totals. There is no request log sitting behind them.

The full text is in our privacy policy.

Yes. All uploaded files are scanned for malicious content. This process is automated and does not involve human review of your files. The contents of your files are not stored or logged during this process, and infected files are deleted automatically.

Free runs on community support through our Telegram and Discord channels. Pro adds email support, and Business adds priority support.

For anything else, including security reports, write to [email protected]. Because we hold no personal data, please include the file link or the access key id you are asking about, since there is no account name for us to look you up by.