Loading …
The result? 100 standalone HTML files, each with embedded assets. No server, no node_modules, no complex folder structure. Double-click any file and it renders perfectly.
This is the honest part. Firefox is an amazing browser, but it is a site crawler. firefoxs siterip
They’re like a Swiss Army knife—handy in a pinch, but you wouldn’t build a house with just the corkscrew. Part 3: The Real Workhorses – Firefox Extensions for Siteripping The result
Firefox is great here because you can already be logged in . Unlike wget , Firefox handles cookies, sessions, and WebSockets natively. Extensions like “SingleFile” will save the authenticated view. This is how you archive your own Slack history, Notion pages, or internal wikis (with permission). Double-click any file and it renders perfectly
Firefox’s cache stores every asset it downloads. With extensions like “CacheViewer,” you can browse and export cached files. This is a post-hoc siterip—you visit pages, then pull them from cache. Not efficient for large sites, but zero extra requests.
This is where Firefox shines. Unlike Chrome (which is slowly strangling WebRequest API power), Firefox still supports extensions that can intercept, modify, and batch-download content.