PullFiles
- Free allowance
- 'Grab any file from a link or URL instantly with our fast and easy online downloader.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- anonymousno card, no phone
- Binding limit
- per-object-cap1 GB per file
- Evidence
- documented6 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-04checked 2026-11-03 (live); stale on 2026-12-04
| Free tier | 'Grab any file from a link or URL instantly with our fast and easy online downloader. Max. File size: 1 GB.' The page advertises 'Unlimited Downloads - No restrictions on download frequency or usage' and requires no account in the visible flow. unit requests; metered on request-count; The client sends a URL, their server pulls it, and the browser receives the stream. Nothing is stored for later re-download. |
|---|---|
| Price | USD 0 |
| Limits |
The page also says '100% Secure' and 'End-to-end encryption', which cannot be true of a relay that terminates TLS on both sides; treat the security text as marketing. |
| Binding | per-object-cap The 1 GB per-file ceiling is the only hard number: 1 TiB/month is 1024 such files, so frequency is not the wall, the single-file size is. |
| Identity | anonymous No login or account appears anywhere in the pasted-URL flow. |
| Egress | 'Unlimited Downloads - No restrictions on download frequency or usage'; no byte allowance stated. free allowance: no published allowance monthly; 1 GB per file |
| Per-object cap | 1 GB per file ('Max. File size: 1 GB'). (1073741824 bytes) |
| Retention | not applicable in the storage sense: there is a progress screen ('Preparing download... Downloading Secure Server') and no library. Nothing was found that says a fetched file persists. |
| Interface | unknown One web form: paste a direct file URL, press start, watch a progress panel. No API documentation. |
| Tooling | Browser only. A wrapper would need a headless browser because the transfer is streamed through the page. |
| Composes with | It solves the case where a user's own connection cannot reach a host but the relay can: the relay fetches and re-serves over HTTPS. It is a proxy, not storage, so it must be followed immediately by a real download. |
| Reliability | A relay is a single point of failure and a single point of visibility: the operator sees every URL and every byte, and the stream dies if the operator's egress is slow. Nothing on the page states uptime or operator identity. |
| Notes | Answers a narrower question than asked: it will not resolve a Rapidgator page into a direct link, but it will fetch a direct link a user cannot reach. Worth keeping as the last hop. |
| Evidence note | documented The page, its FAQ and its features page are captured and quoted: 1 GB per file, unlimited downloads, no registration. No URL was pulled through the relay, so neither the 1 GB ceiling nor the unlimited claim is measured. |
| Parsed numbers |
|
Evidence 6
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | pullfiles.net/ | 'Max. File size: 1 GB', 'Unlimited Downloads - No restrictions on download frequency or usage', the progress UI ('Preparing download...') and no account requirement |
| 2026-10-23 | probe: https://pullfiles.net/ | HTTP 200, 65612 bytes, sha256 0f299b37f44aadf7..., no challenge |
| 2026-11-03 | pullfiles.net/ | the page states a 1 GB per-file maximum |
| 2026-11-03 | pullfiles.net/ | no account or login is required |
| 2026-11-03 | pullfiles.net/ | the page claims unlimited downloads with no frequency restriction |
| 2026-11-03 | pullfiles.net/features | the features page states no daily limit and no paid tier |
More fields 3
| max file bytes | 1073741824 |
|---|---|
| account | none |
| api | none |
Unknown values 1
- interface: the access interface was not established