Download limits and results
Zipasite is currently free to use. These limits keep downloads manageable for visitors and source websites. Updated 27 September 2026.
Before you start
The default is 50 HTML pages, with a selectable maximum of 200. Zipasite starts at the homepage and the address you enter, then follows links and sitemaps across the same host. Other subdomains stay outside the page search. A limit of one can save the homepage first, even when you enter another page address.
Current limits
| Item | Limit |
|---|---|
| HTML pages | 1–200; default 50 |
| Supporting files | 2,000 |
| One file | 50 MB |
| ZIP size | 500 MB |
| Transferred source data | 500 MB per job |
| Job duration | 60 minutes for fetching source files |
| Started jobs | 5 per browser in a rolling 24-hour window |
| Concurrent jobs | 1 per browser, 2 across the service |
| Shared network protection | 15 starts per network in a rolling 24-hour window |
| Discovery and requests | Up to 15 sitemap requests, 5,000 discovered addresses and 2,400 file requests |
| Text processing | 12 MB of source HTML; 16 MB of HTML and CSS combined |
These are upper bounds. Browser memory, source-site rules and available files affect the result. The ZIP reserves space for pages and reports, so file collection may stop before the displayed ZIP limit. A job counts when the server accepts the start, including jobs later stopped or interrupted. Failed security checks and requests rejected while the service is busy leave the start allowance unchanged.
Zipasite spaces request starts to the same origin by at least one second and follows longer supported crawl delays. A source request has a 120-second timeout. Images, fonts and documents add requests. Keep the tab open while the job runs. Downloading the prepared ZIP again uses the same completed job.
Read the result
ZIP ready: the archive was created. Open the saved pages and test them with your internet connection switched off.
ZIP ready with download notes: review missing files, source restrictions and reached limits. The copy may be partial.
ZIP not ready or download stopped: start a fresh job after reviewing the error. “Download notes” exports a report for troubleshooting. A failed file transfer can be skipped before that file enters the ZIP; a failure while writing the ZIP ends the job.
Cookie notices and scripts
“Keep website scripts” is selected by default to preserve more original behaviour where supported. Turning it off removes original scripts and inline event handlers, with an exception for recognised homepage Google Tag Manager loaders. Zipasite adds a small local helper for supported navigation. External image, style and service references can still cause network requests in either mode.
Recognised Google Tag Manager loaders stay on index.html and are removed from inner pages. The homepage may load its cookie notice when online. Other saved scripts may also contact online services.
When Zipasite detects cookie notice text in the original HTML, it adds saved-cookie-notices.html with reference text, source links and a capture date. This is a text record, rather than an active consent form. Banners created by JavaScript, preference panels, their appearance and screenshots require a separate browser capture. A saved notice may reflect only part of the original notice.
Open and check your copy
Extract the ZIP and open index.html in the website folder. Check navigation, images, fonts and documents with the connection switched off. Some JavaScript features need a local web server; forms, accounts and checkout still rely on the live service. Read the opening checklist.
Help
Email zipasite@gmail.com with your browser, approximate time, source domain and the relevant download notes. Review a report before sharing it. Queries are removed from reports, while original addresses can remain in page content.