- Free allowance
- "Drop a file -> get a share link.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- any-phoneno card, phone required
- Binding limit
- per-object-cap4 GB per file
- Evidence
- documented2 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | "Drop a file -> get a share link. Up to 4 GB." The bot's own description is the free offer; the site terms add that 'Puedes usar partes del servicio sin cuenta' - parts of the service work without an account. unit none; metered on none; No byte allowance and no price is published anywhere on the pages read. |
|---|
| Price | USD 0 |
|---|
| Limits | - per-object-cap (binding) 4 GB per file source
One number and nothing else. Transfers can be suspended, and no quota, rate or storage ceiling is published. |
|---|
| Binding | per-object-cap At 1 TiB a month the 4 GB ceiling is met on the first large file: a 1 TiB archive is 256 transfers. Nothing else in the published terms could bind earlier. |
|---|
| Identity | any-phone Through the bot: a Telegram account, so any phone number. Through the site: 'partes del servicio' work with no account at all, and history or paid plans need registration. |
|---|
| Egress | Files are served by the service to whoever holds the link or password; the terms add 'historial o planes de pago' as account features. No bandwidth figure or price is published. |
|---|
| Per-object cap | 4 GB per file, from the bot's description. (4294967296 bytes) |
|---|
| Retention | Not given as a number. The terms say transfers are made 'con opciones de caducidad, contraseña' - expiry and password options chosen by the sender - so retention is set per transfer rather than by a site rule. |
|---|
| Interface | unknown Two front ends: a Telegram bot (@DripFilesBot) and a website with upload, link share and email share. No API is documented on the pages read. |
|---|
| Tooling | Telegram client or browser. No API and no WebDAV, so a script would have to drive one of the two front ends. |
|---|
| Composes with | A handoff tool rather than capacity: 4 GB per transfer with a sender-set expiry is enough to move one file between two people or two machines, and it removes the need to expose a bucket for a one-off. |
|---|
| Reliability | A young service with a Spanish-language terms page last updated on the day of this read and a bot that is its own distribution channel: both are signs of one operator with no published uptime. Files expire by the sender's setting, so the loss is predictable. |
|---|
| Evidence note | documented The bot description and the site's terms were both read and agree that the service stores and re-serves files. The 4 GB figure is reported by the bot only, not measured with an upload. |
|---|
| Parsed numbers | - has-free-tier 1
- per-object-cap 4 GB
- price USD 0
|
|---|