Website copier
What a website copier does
A website copier captures a live site and stores a local copy. The useful question is how the copy is made: by fetching raw HTTP files, or by rendering the page in a browser first.
Direct answer: A website copier is software that captures a live site and stores a local copy. Some tools only fetch HTTP files. Others, including WebCopier, open the page in a real browser so JavaScript can run before the copy is saved.
How website copying works
Most copiers follow the same outline: start at a URL, discover more URLs, download files, and rewrite links so the copy can be opened later. The difference is whether the tool sees the page the way a browser does.
Traditional HTTP crawling
A traditional crawler requests HTML and linked assets. If the server returns a complete document, that can be enough. Tools in this family remain useful for static or lightly dynamic sites. HTTrack is the well-known example: it is still maintained (version 3.50 announced 1 September 2026 on httrack.com) and is a strong fit for classic mirroring.
Browser-rendered capture and JavaScript
Many modern sites send a thin HTML shell and fill the page with JavaScript. An HTTP crawler then saves an incomplete document. Browser-rendered capture opens the URL in a real browser, lets scripts run, then saves the rendered result plus the files that page needed.
Discovery and assets
WebCopier discovers more pages from internal links and can use sitemaps. CSS, images, fonts, and client scripts are saved when the browser actually loads them. Undiscovered URLs and lazy files that never load may be missing. See discovery and missing assets.
Local projects and offline browsing
The output is a project on your Windows PC. Saved pages can be opened locally. Features that still call a live API, require login, or were never captured will not behave like the live site. See offline browsing.
Where WebCopier fits
WebCopier is a Windows desktop website copier for public frontends that need rendering first. It is not a CMS export and not a server clone.
What gets saved
- Rendered HTML after JavaScript runs
- Stylesheets, images, fonts, and client scripts the page used
- Discovered internal pages, within plan limits
- A local project and a capture report
What does not get saved
- Backend source, databases, and admin UIs
- Server-only APIs and business logic
- Pages outside discovery or your page cap
- Anything you are not allowed to copy
Who should use it
Developers, designers, agencies, QA, and researchers who need a local frontend snapshot on Windows.
Who should not
Anyone who needs the original database, admin panel, or a legally complete “own the whole site” package. Anyone without permission to capture the target. Linux/mac-only workflows — WebCopier is Windows-only.
Permission
You must have the right to capture the site. A local copy does not grant copyright. See legal terms.
Questions
What is a website copier?
A website copier captures pages and files from a site and stores them as a local copy. Approaches differ: some fetch HTTP files only; others render the page in a browser first.
Does WebCopier copy the backend?
No. WebCopier saves the rendered frontend and related assets. It does not extract databases, admin panels, or server-side application logic.
Do I need permission?
Yes. You are responsible for having the right to capture the site. A local copy does not give you copyright in someone else’s work.
Download WebCopier 1.4.0-rc1See plansRead the docs