Automatic preflight identifies static pages, single-page applications (SPA), login walls, long pages, media, and Cloudflare signals.
Capture, verify, replay, and export authorized websites from one native macOS workspace.
Static files, archival data, and interactive content are handled automatically.
Complete the required fields to preview the command.Verified archive
Compare rendered pages, loaded resources, broken images, and browser errors before you trust the archive.
Capture stack
Automatic preflight plans the capture, three capture engines preserve the right evidence, and verification checks the result.
Plain-language outcomes come first. Experienced archivists can still inspect every engine in the plan.
Keep a browsable static mirror beside durable WARC and interactive WACZ archives.
Refresh changed files as one complete version while keeping earlier WARC and WACZ snapshots.
Follow the current phase and failures at a glance, then open terminal output for deeper diagnosis.
https://agntc.design/case-studies/web-archives
Archived route and dependent assets
Captured scrolled page state
Rendered client-side navigation
Search the local library, inspect the latest verification, then replay, update, serve, or export the archive.
ReplayWeb.page opens and replays portable WACZ captures locally. Static mirrors can be served, updated, or packaged for handoff.
- Static folder
- WARC archive
- WACZ archive
- ZIP handoff
- Docker / Nginx
- Next.js wrapper
Authenticated capture
Login session opens an isolated Browsertrix window. You enter credentials there, and WEB MIRROR keeps them out of commands, logs, reports, and public archives.
- Accept complete HTTP or HTTPS URLs.
- Reject embedded credentials and sensitive query parameters.
- Require an explicit opt-in for private or local targets.
- Pass command arguments without a shell or secret environment values.
- Keep session profiles out of public archives.
- Reject symbolic-link traversal in reports and exports.
Current beta
First launch checks your Mac and explains any missing capture or verification tools.
Native Swift interface in a compact, resizable window.
The current beta runs on arm64 Macs.
Used by Browsertrix for interactive and authenticated captures.
Compares the source and mirror at desktop and mobile sizes.
FAQ
The limits are part of the product. WEB MIRROR reports what it could not preserve and never promises a perfect copy.
Which websites can I mirror?+
Use WEB MIRROR only for websites you own or have permission to archive. Private and local targets require a separate opt-in before capture starts.
Can WEB MIRROR guarantee a complete capture?+
No. Live backends, DRM, CAPTCHA, WebSockets, expiring sessions, and blocked third-party resources can limit a capture. WEB MIRROR records those gaps in its verification report.
How does WEB MIRROR choose a capture engine?+
Preflight checks how the site renders, then selects Wget, grab-site, Browsertrix, or a combination. You can review the capture plan before any files change.
Does it bypass Cloudflare or login protection?+
WEB MIRROR does not bypass protections. For a site you are allowed to archive, Login session opens an isolated Browsertrix window where you enter credentials.
Where does WEB MIRROR store capture data?+
WEB MIRROR writes each capture to the mirror folder you choose and lists the project in its local library. Session profiles stay outside public archive exports.
Show 7 more questionsShow fewer questions
What are WARC and WACZ files?+
WARC stores original network responses. WACZ packages an interactive browser capture for ReplayWeb.page.
How does visual verification work?+
WEB MIRROR renders the source and mirror at desktop and mobile sizes. It compares pixels, loaded resources, broken images, and browser errors.
Can I replay a capture offline?+
Static mirrors can open from local files or a loopback server. ReplayWeb.page opens WACZ captures on your Mac without publishing them.
What does the Next.js export contain?+
The export is an offline App Router wrapper. It places the static mirror under public/mirror and displays it in an iframe; it does not reconstruct private backend logic or the original component system.
What changes during an update?+
WEB MIRROR checks source files for changes, replaces the active static mirror with the complete new version, and keeps earlier WARC and WACZ snapshots.
Which Macs can run the current beta?+
The current beta runs on macOS 14 or later and requires Apple Silicon. It does not run on Intel Macs.
Is the public download available yet?+
No. AGNTC is completing production signing, notarization, and multi-architecture packaging before public release. Request beta access for build invitations and release news.
Private beta
Early access to the current beta build is for archivists, developers, and teams testing authorized sites on Apple Silicon.
- Request access and confirm your email.
- Receive an invitation when a suitable build is available.
- Share capture and verification feedback with AGNTC.