DripFiles
dripfiles.com · Debrid · 1 record · JSON
DripFiles (@DripFilesBot) Debrid
caveatany-phoneno cardphoneDper-object-cap
| 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 |
| 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. |
| 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. |
| 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. |
| Limits |
One number and nothing else. The terms reserve the right to suspend transfers that break the rules but publish no quota, rate or storage ceiling. |
| 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. |
| 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. |
| Notes | Recorded because it is a real hosted store-and-forward service and not an account mirror: the file goes into the operator's storage and comes back as a link. |
| Evidence rung | documented The bot description and the site's terms were both read today 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. |
| Checked | 2026-10-24 (live); stale on 2026-11-23 |
| Parsed numbers |
|
Evidence (2)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | t.me/DripFilesBot | the service exists as '@DripFilesBot - The official DripFiles bot' with the cap 'Up to 4 GB' |
| 2026-10-23 | dripfiles.com/ | the terms describe 'un servicio de envío y compartición de archivos' with upload, link or email sharing, expiry, password and premium features, last updated 23/10/2026 |
More fields (1)
{
"front_ends": "Telegram bot @DripFilesBot; website dripfiles.com"
}Unknown or withheld values (1)
$.interfaceinterface-unknown