Guides on copying, rebuilding and archiving websites

Every number on these pages comes from our own reproducible benchmark (npm run bench:rivals), rendered with the original server unreachable.

Copying a web page sounds like one job and is really four: reading what the browser rendered rather than what the server sent, collecting every asset the page depends on, rewriting the references so nothing points home any more, and choosing an output format you can still work with afterwards. Almost every complaint about a “broken copy” traces back to one of those four steps being skipped.

The guides here work through them one at a time — copying a single page, mirroring a whole site, turning a captured page into editable WordPress blocks, handing a page to a coding agent, and what copyright actually permits once you have the files.

Where a guide quotes a fidelity number, that number comes from the same harness as our comparisons: the copy is re-rendered with the original origin blocked and diffed pixel by pixel against the live page. Where a tool beats us, the guide says so — the free options are genuinely good at the pages they were designed for.

2026-09-03

How to archive a webpage as evidence

What makes a page capture credible later: format, metadata, completeness, and the mistakes that make an archive easy to dismiss.

2026-09-03

The best website copiers in 2026, measured

HTTrack, wget, SingleFile, monolith, SiteSucker and CopyAnySite — what each is for, with fidelity scores measured offline.

2026-09-03

How to convert any website into an editable WordPress page

Turn a captured page into Gutenberg section blocks with its real CSS, fonts and images — editable in the block editor instead of pasted into a Custom HTML block.

2026-09-03

How to copy a landing page you like (properly)

A repeatable process for taking a landing page you admire and turning it into your own, without shipping their fonts, images or words.

2026-09-03

Why fonts and logos break when you copy a website (and how to fix it)

The nine places a logo hides, the font race that silently reflows your copy, and how to check both survived before you rely on the file.

2026-09-03

Copying a website with AI: what actually works and what it invents

Screenshot-to-code tools rewrite a page from pixels. What they get right, what they hallucinate, and how to hand them a real capture instead.

2026-09-03

How to download an entire website

Crawl and copy a whole site — the flags that matter for wget and HTTrack, why client-rendered sites need a browser, and how to stay polite while doing it.

2026-09-03

How to copy a website (and what "a copy" actually means)

Six real ways to copy a website, what each one keeps and drops, and how to check your copy survives once the original server is gone.

2026-09-03

Is it legal to copy a website?

What copyright, trademark and font licences say about copying a page: the routine uses, the risky ones, and a checklist before you publish.

2026-09-03

How to save a webpage as a single HTML file

Why Ctrl+S gives you a folder and a half-broken page, and how to get one self-contained HTML file with its fonts, images and CSS embedded.

2026-09-03

Web scraping vs page capture: two different jobs

Scrapers extract data and throw the page away. Capture keeps the page and ignores the data. Picking the wrong one wastes weeks.

2026-09-03

Turning a real page into something Bolt, Lovable or Cursor can build from

Screenshots make coding agents guess. A capture — markup, extracted CSS, asset manifest, spec — makes them accurate. How to produce and use one.