TL;DR
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
Kage is a new tool that clones websites into local folders or single executable files, removing all scripts and tracking for offline viewing. It uses headless Chrome to capture the final page state, enabling long-term offline access.
Kage is a new open-source tool that clones websites into offline-ready folders or self-contained binaries, stripping out all scripts and tracking. It uses a real headless Chrome browser to capture the final rendered state of each page, ensuring the offline version looks and functions like the live site, but without any code execution or network calls.
Developed by Tam Nguyen, Kage automates the process of creating static, script-free copies of websites for offline browsing. It navigates each page in a headless Chrome environment, waits for the page to settle, snapshots the DOM, and then removes all JavaScript while downloading CSS, images, and fonts locally. The result is a set of HTML files that resemble the live website but operate entirely offline, with no scripts or tracking code.
Users can clone entire sites or sections, serve them locally via a simple HTTP server, or compress the clone into a single file—either as a ZIM archive or a self-executing binary. Kage supports various command-line options, including depth control, subdomain inclusion, and refresh capabilities, making it versatile for different use cases such as archiving, offline reading, or long-term preservation.
It requires Chrome or Chromium installed on the host machine, though a containerized version with Chromium bundled is available, simplifying setup. The project emphasizes privacy and permanence, allowing users to preserve websites without ongoing network dependencies or tracking concerns.
Implications for Offline Content Preservation
Kage addresses the common problem of websites changing or disappearing over time, which hampers long-term access and archival efforts. By creating static, script-free copies, it enables users to preserve web content reliably for decades, useful for researchers, educators, and archivists. Its ability to produce a single executable or compressed archive simplifies sharing and storage, reducing the complexity associated with large, multi-file site copies.
Moreover, Kage enhances privacy by removing all scripts, including trackers and analytics, offering a safer way to browse and archive sensitive or personal content offline. It also supports use cases like offline reading on airplanes or in remote locations, where internet access is unavailable or unreliable.
However, the tool’s reliance on Chrome means it depends on the browser’s rendering capabilities and may have limitations with highly dynamic or JavaScript-heavy sites. The long-term viability of the output formats (like ZIM or self-contained binaries) also remains to be fully tested across different platforms and future environments.
As an affiliate, we earn on qualifying purchases.
Background on Website Archiving and Offline Browsing
Traditional methods of saving web pages, such as browser ‘Save As’ or using static site generators, often result in incomplete or non-functional copies, especially for sites that rely heavily on JavaScript. Existing tools like HTTrack or Wget create static copies but may not accurately capture dynamic content or may include scripts that could break in the future.
Recent efforts in offline content storage, such as the ZIM format used by Kiwix, have aimed to create portable, read-only archives of entire websites or Wikipedia. However, these often require manual setup or are limited to specific formats. Kage builds on this background by automating the process using a real browser to ensure the captured content reflects the final user-visible state, not just raw HTML or cached assets.
Announced on Hacker News, Kage’s approach emphasizes privacy, simplicity, and long-term preservation, addressing gaps in existing solutions by stripping out all scripts and tracking, and packaging the content into single, easy-to-distribute files.
“Kage drives a real browser, so it captures exactly what a user would see, then removes all scripts and tracking, leaving a pure, static copy.”
— Tam Nguyen, developer of Kage
As an affiliate, we earn on qualifying purchases.
Limitations and Future Compatibility Questions
It is not yet clear how well Kage performs with highly dynamic or JavaScript-intensive websites, or how the generated archives will hold up over very long periods. The long-term support for formats like ZIM or self-contained binaries across different operating systems remains to be tested. Additionally, the reliance on Chrome or Chromium could pose compatibility issues in environments where these browsers are not available or supported.
As an affiliate, we earn on qualifying purchases.
Upcoming Developments and Community Adoption
Future updates may focus on improving support for complex sites, enhancing compression methods, and integrating with existing archiving ecosystems. Community feedback and real-world testing will determine how broadly Kage can be adopted for personal, institutional, or archival use. Developers may also explore automating periodic re-cloning or integrating with backup solutions to ensure long-term content preservation.
As an affiliate, we earn on qualifying purchases.
Key Questions
Can Kage clone websites with dynamic content?
Kage uses a headless Chrome browser to render pages fully before snapshotting, so it can capture some dynamic content. However, highly interactive or real-time sites may not be perfectly preserved, especially if content loads asynchronously after the snapshot.
Does Kage preserve tracking scripts or analytics?
No, Kage strips out all JavaScript, including tracking and analytics scripts, resulting in a clean, privacy-preserving offline copy.
What formats can Kage output?
Kage can produce a folder of static HTML files, a self-contained ZIM archive, or a single executable binary that serves the site locally.
Is Kage suitable for archiving large or complex websites?
It can handle large sites with configurable depth and scope, but performance and completeness depend on site complexity and the available system resources.
What are the system requirements for using Kage?
Kage requires Chrome or Chromium installed on the host machine, though a containerized version with Chromium bundled is available for easier setup.
Source: Hacker News
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
