CopyAnySite compared, measured side by side
Every number on these pages comes from our own reproducible benchmark (npm run bench:rivals), rendered with the original server unreachable.
Every comparison on this page is scored the same way: the same eight pages, the same renderer, three runs each, and — the part most comparisons leave out — the copy re-rendered with the original server blocked at the network layer. A copy that still fetches half its images from the site it copied is not a copy, it is a bookmark with extra steps.
That method produces boring results on simple pages and honest ones on hard pages. On Hacker News and a Wikipedia article everything scores 99–100% and no tool has earned anything. On a commercial WordPress theme demo or a heavily animated marketing page the spread runs 20–40 points, because that is where rendered-after-load content, webfonts and generated CSS live.
The harness is in the repository and runs with npm run bench:rivals, so any row here can be disputed with a number rather than an opinion. If you would rather start from a tool than from a comparison, the website copier overview lists all six.
2026-09-03
CopyAnySite vs HTTrack
One mirrors many pages from the server; the other captures the browser-rendered page. Which you need depends entirely on how the site is built.
2026-09-03
CopyAnySite vs monolith
monolith packs a page into one file from the command line. Where that model shines, where it breaks, and the measured difference offline.
2026-09-03
CopyAnySite vs SingleFile
Both save a page as one self-contained HTML file. Per-page fidelity scores with the original server unreachable, plus where SingleFile is the better choice.
2026-09-03
CopyAnySite vs wget
wget is free and everywhere. Here is exactly what its copies lose when the original server is unreachable, page by page.