SingleFile GitHub Overview: How Self-Contained HTML Archiving Works
singlefile by gildas-lormeau: gildas-lormeau/singlefile
Official Firefox Add-ons page: addons.mozilla.org
SingleFile is a browser extension and CLI ecosystem for saving a rendered webpage as a self-contained HTML document. This overview explains why browser-native saves can scatter assets, how DOM serialization embeds styles, fonts, and media as data, and where the approach fits for offline research and digital preservation. It also covers the Firefox extension path, restricted browser pages, full-page and selection capture, annotation editing, filename templates, lazy-loaded content, private browsing permissions, and the CLI/Docker route. The key tradeoff: SingleFile preserves a captured DOM state, not a site's backend or continuously changing application state. The video is an architecture-focused overview; it does not establish a live installation, hands-on benchmark, or universal fidelity guarantee.
TimeStamps:
0:00 Why browser-native saves break
0:35 SingleFile's self-contained HTML model
1:17 Extension setup and browser security boundaries
2:23 Capturing a rendered page offline
3:16 Selection capture for smaller archives
3:56 Annotation editing and persistent notes
4:42 File naming with template variables
5:35 Lazy-loaded assets and deferred-content settings
6:38 Private browsing, compatibility, and format caveats
7:30 CLI, Docker, and preservation limits
🧩 Native browser saves can fracture HTML and assets
📦 DOM serialization packages page resources into one HTML file
📝 Selection, annotations, and filename templates organize archives
⚙️ Deferred content, private browsing, CLI, and Docker shape the workflow
SingleFile is most useful when you need a portable HTML snapshot of a rendered page, with selection, annotation, and naming controls for repeatable research. Keep the boundaries in view: dynamic backend behavior, protected content, and continuously changing interfaces are not preserved as live systems. For automation, compare the extension workflow with the CLI and Docker options.
#SingleFile #WebArchiving #OpenSource
2 likes · 201 views
Mentions
yes, ideally 'print to pdf' (save later for print) feature should be enough, but for more 'save for later' 'bookmark' it, i prefer and very often use gildas-lormeau/SingleFile
Free Chrome extension: save a complete page with SingleFile SingleFile is a free, AGPL-3.0 browser extension that saves a web page into one HTML file for offline reference. Install it in the free Chrome desktop browser from its official listing: chromewebstore.google.com Example: open a public documentation page, wait for it to finish loading, click the SingleFile toolbar button, then open the downloaded HTML file later. Dynamic features may not work offline, so check the saved result. This local save needs no paid browser, API or subscription. Project: gildas-lormeau/SingleFile
SingleFile GitHub Overview: How Self-Contained HTML Archiving Works singlefile by gildas-lormeau: gildas-lormeau/singlefile Official Firefox Add-ons page: addons.mozilla.org SingleFile is a browser extension and CLI ecosystem for saving a rendered webpage as a self-contained HTML document. This overview explains why browser-native saves can scatter assets, how DOM serialization embeds styles, fonts, and media as data, and where the approach fits for offline research and digital preservation. It also covers the Firefox extension path, restricted browser pages, full-page and selection capture, annotation editing, filename templates, lazy-loaded content, private browsing permissions, and the CLI/Docker route. The key tradeoff: SingleFile preserves a captured DOM state, not a site's backend or continuously changing application state. The video is an architecture-focused overview; it does not establish a live installation, hands-on benchmark, or universal fidelity guarantee. TimeStamps: 0:00 Why browser-native saves break 0:35 SingleFile's self-contained HTML model 1:17 Extension setup and browser security boundaries 2:23 Capturing a rendered page offline 3:16 Selection capture for smaller archives 3:56 Annotation editing and persistent notes 4:42 File naming with template variables 5:35 Lazy-loaded assets and deferred-content settings 6:38 Private browsing, compatibility, and format caveats 7:30 CLI, Docker, and preservation limits 🧩 Native browser saves can fracture HTML and assets 📦 DOM serialization packages page resources into one HTML file 📝 Selection, annotations, and filename templates organize archives ⚙️ Deferred content, private browsing, CLI, and Docker shape the workflow SingleFile is most useful when you need a portable HTML snapshot of a rendered page, with selection, annotation, and naming controls for repeatable research. Keep the boundaries in view: dynamic backend behavior, protected content, and continuously changing interfaces are not preserved as live systems. For automation, compare the extension workflow with the CLI and Docker options. #SingleFile #WebArchiving #OpenSource
Free browser extension: keep a web page in one file with SingleFile SingleFile is a free, open-source browser extension that saves a web page, including its layout and images, as one HTML file. It works with Chrome and several other supported browsers. For Chrome, install it from the official Chrome Web Store link in the project README. Open a tutorial or article, wait for the page to load, then click the SingleFile toolbar button. You get one file you can open later without the connection. A practical example: save an installation guide before travelling somewhere with patchy internet. Check the page owner’s terms before redistributing a saved copy, and be careful with pages containing personal information. Official repo and install links: gildas-lormeau/SingleFile