Clone · Archive · Analyze · Anywhere
WebClone saves an entire site to your Mac — every page, every image, every stylesheet — into a folder you own. Open it in Safari with the Wi-Fi off, on a plane, or in ten years.
Requires macOS 14 or later · Free to try · No account, ever
Most tools grab the HTML and leave you with a broken page. WebClone follows every
<a>, <img>, <link>,
<script>, <source> and <iframe>,
plus every url() inside your CSS, then rewrites the links so your copy
actually works. Fonts included.
The output is a normal folder in a location you chose. Plain HTML, plain images, plain CSS. Open it in a browser, feed it to a script, commit it to a repo, hand it to a model. There is no version of WebClone that can hold your archive hostage — including a version we might ship later.
Depth limits, page caps, host and domain scoping, glob include/exclude rules, a
configurable politeness delay, a connection ceiling, and robots.txt
respected by default. Tracking parameters are stripped automatically, so a single page
isn't saved a thousand times under a thousand URLs.
Three steps. There is no fourth.
Any site. Any depth. It starts immediately.
Pages, files, errors, speed, and a live log of every request.
Reveal in Finder. Double-click index.html. Turn off your Wi-Fi. It still works.
Freeze a site's real markup so you can inspect and re-inspect it without a CDN changing underneath you.
Turn a documentation site into a clean local corpus in one pass — plain files, ready to chunk and embed, no scraper to write and maintain.
Capture a source before it's edited or taken down. Your copy is dated and it is yours.
Keep a reference with every asset intact, at full resolution.
Cite something that will still exist on the day you defend.
Take a wiki, a manual, or a guide somewhere with no signal.
These tools aren't bad. They answer a different question.
SiteSucker is the original and it works. It has been downloading sites since 2006 and it will download yours. The difference is what happens after the download: SiteSucker hands you a folder and its job is done. WebClone treats every capture as an object in a library you come back to — with its date, its size, its source URL, its file tree, and a re-crawl button.
| WebClone | SiteSucker | |
|---|---|---|
| Downloads a whole site | ✓ | ✓ |
| Rewrites links for offline use | ✓ | ✓ |
| Persistent library of past captures | ✓ | — |
| Per-capture file tree with sizes | ✓ | — |
| Quick Look on captured files | ✓ | — |
| Live per-host / per-type breakdown | ✓ | — |
| Tracking parameters stripped by default | ✓ | — |
| Native SwiftUI, current-generation design | ✓ | — |
Honestly: SiteSucker is more configurable in a few places and has two decades of edge cases handled. If you need its very specific rule syntax, use it. We think most people don't.
Offline browser apps save one page at a time, usually into their own private container, so you can read it in their reader. That's a good answer to "I want to read this article on the subway." WebClone answers a different question: "I want this entire site, structurally intact, as files I own." If the app that saved your archive disappears from the App Store, an offline-browser archive goes with it. A WebClone archive is a folder.
| WebClone | Offline browsers | |
|---|---|---|
| Whole site, recursively | ✓ | one page |
| Original HTML, CSS and JS preserved | ✓ | reader-mode |
| Output is plain files you own | ✓ | private container |
| Survives the app being deleted | ✓ | — |
| Best for one article on the subway | fine | better |
Reading List is free, built in, and for saving an article to finish tonight it is the right tool. Use it. But it stores the article's text, not the site — no other pages, no assets at original resolution, no structure, no CSS. It's a bookmark that tries harder. WebClone is a copy.
| WebClone | Reading List | |
|---|---|---|
| Cost | Paid | Free |
| Whole site | ✓ | single pages |
| Original layout and assets | ✓ | reader text |
| Files you can open, script, or commit | ✓ | — |
| Best for "read this tonight" | — | ✓ |
Downloading pages you can already view in a browser is generally fine for personal use,
research, and archiving — it is what your browser's cache does, more thoroughly. What you do
with the copy is where the law lives: copyright, terms of service, and personal-data rules
still apply, and republishing someone's site is not okay just because you have a copy.
WebClone respects robots.txt by default and rate-limits its requests. Don't turn
either off without a reason you'd be comfortable explaining.
Partly. WebClone downloads the HTML the server sends, plus the scripts and stylesheets it references. Sites that render content client-side from an API will save, but pages that fetch their content at runtime won't have that content in the copy. Documentation sites, blogs, wikis, marketing sites and most static-generated sites clone essentially perfectly. Single-page apps that are entirely API-driven do not.
No. WebClone doesn't handle authentication, and won't in v1.
An average documentation site: 20–200 MB. A large media-heavy site: several GB. Set a page cap before you start a site you don't know.
WebClone identifies itself honestly in every request —
WebClone/1.0 (+https://webclone.app; macOS) — waits between requests, and caps
concurrency at 4 by default. It does not disguise itself as a browser and does not rotate
identities. A crawler that announces itself can be allow-listed; one that hides can only be
blocked. Raise the limits only on sites you own.
Wherever you choose. WebClone asks once, remembers with a security-scoped bookmark, and writes nowhere else. It is sandboxed — it cannot read the rest of your disk.
No. No account, no sign-in, no analytics, no crash reporting to us, no cloud. The App Store privacy label says "Data Not Collected" and the app's privacy manifest declares zero collected data types. The only server WebClone contacts is the one you asked it to clone.
Every archive you've already made is a folder on your disk. It keeps working forever, with or without the app.
Not yet. Today, put your archive folder in iCloud Drive or Dropbox and it syncs like any other folder.
It can re-crawl to update today. Showing you a diff of exactly what changed is planned.