The HTML of every page, plus the assets they reference: images (PNG, JPG, GIF, WebP), stylesheets, JavaScript, fonts (WOFF, WOFF2, TTF, EOT) and media files (MP4, MP3, WebM, WAV). They are sorted into images, css, js, fonts and media folders next to the pages, so the archive opens offline exactly as it looked online.
Partly. We save what the server sends, and a single-page application often sends an almost empty HTML shell that fills itself in the browser. The files land in the ZIP, but the visible text may not. Classic and server-rendered sites — WordPress, TYPO3, static site generators, most company websites — work very well.
No. The downloader requests pages the way an anonymous visitor does, without your session or cookies, so anything behind a login is out of reach. It will save the login page itself, not the content behind it.
No — the downloader does not read robots.txt and does not evaluate crawling rules. That means the responsibility is yours: only download sites you own or are permitted to copy, and respect each site's terms of use.
It depends far more on the target server than on us. We fetch five files at a time; a site of a few hundred pages usually finishes in a couple of minutes. A run is cut off after 15 minutes, so extremely large or very slow sites may end early with a partial archive.
If pages were already written, you keep them: the partial archive is packed and delivered rather than thrown away, and the progress display tells you what went wrong. Only a run that times out or fails before the first page reaches disk produces nothing.
Yes. Every file is stored exactly as the server delivered it — no recompression, no resizing, no format conversion. The ZIP is therefore about as large as the original site's assets.
Not as a restriction. Starting at example.com/blog begins the crawl there, but the downloader follows every internal link on the same domain, so pages outside that folder can be included too. Limits come from the page count of your package and a maximum link depth of ten.
Payments run through Stripe, which emails a payment confirmation immediately. Subscribers also get a proper invoice for every billing period, available any time in the billing portal linked from your account.
In your account, with one click. The cancellation takes effect at the end of the period you have already paid for — your package stays fully usable until then, and nothing is charged afterwards.
For a download: the address you entered, the resulting archive and its size. With an account, also your name, email address and payment records held by Stripe. Archives are deleted automatically — after 24 hours on the free plan, after 30 days on a paid one. For deletion of an account and everything attached to it, write to us and we will confirm once it is done.
Three usual reasons: the page limit of your package was reached, content is generated in the browser rather than delivered by the server, or files sit on a different domain — a CDN, a video platform, an external font service — which the downloader deliberately does not follow.