Web Archive: export sites you own as validated static bundles
Web Archive is a free website-export tool for sites you own or have written permission to process. It captures a bounded same-origin copy — up to 20 pages and 4 levels deep — across desktop and mobile viewports, validates the result, and gives you a downloadable bundle with a report of what won't work offline.
Two export modes
Raw export saves a bounded copy of the site: your page budget, same origin only, unsafe or private targets rejected server-side. Script-processed export takes the same capture and processes it into deterministic static output built from facts you provide — offer name, description, locale.
Both modes require an ownership attestation and a written authorization statement before the job starts. Nothing deploys automatically — you get a bundle to download.
Limits you should know before running
- You request a page budget of 1–50; the server caps every job at 20 pages and 4 levels of depth.
- Dynamic APIs, service workers, signed media, authentication and other runtime-only behavior may not work offline.
- A job that finishes "completed with limitations" means the validation report has entries — read it. Visual similarity does not prove functionality.
- Download links expire 24 hours after they're issued.
When media buyers use it
Moving your own landing off a host you're leaving. Keeping a working offline copy of a white page before infrastructure changes, so a bad migration doesn't take a live campaign down with it. Packaging a site for script processing with your own offer facts. The rule is simple: only submit sites you own or have written permission to export.
How it works
- Paste the start URL of a site you own or are authorized to export.
- Choose raw export, or script-processed export with your offer facts (name, description, locale).
- Set a page budget of 1–50 pages; the server caps jobs at 20 pages, 4 levels deep, same origin.
- Confirm the ownership attestation and write the authorization statement — jobs don't run without them.
- Download the bundle within 24 hours and read the validation report before you rely on the copy.
FAQ
Can I export any site?
No. You must own the site or hold written permission. Every job requires an attestation checkbox and an authorization statement; the server also rejects unsafe or private targets.
How big an export can I run?
You request a page budget of 1–50; the server caps jobs at 20 pages and 4 levels of depth, same origin only.
Will the offline copy work exactly like the live site?
Not always. Dynamic APIs, service workers, signed media, authentication and runtime-only behavior may not work offline. The validation report lists what's missing — a "completed with limitations" status means review it.
Does the export go live anywhere?
No. Bundles are never deployed automatically. You download the archive; the link expires 24 hours after it's issued.
What is script-processed export?
A second mode where you supply owner facts — offer name, description, locale — and the captured pages are processed into deterministic static output built from those facts.
Export your first site
Register, attest ownership, and download a validated static copy of your landing.
Get started