By Tabvenir · Published · Updated
The save starts with your selected tabs
The side panel lists tabs using their titles and URLs. You choose the supported pages and start preparing a save. Browser-internal and extension pages are outside the readable page set; private-window and restricted-content boundaries also apply.
Listing a page is not the same as successfully extracting it. Treat unsupported-page indicators and per-page warnings as part of the result.
Readable content becomes Markdown
The extension uses Mozilla Readability and Turndown locally to identify article content and convert it to Markdown. Site-specific handling and checks supplement that process. The resulting note is designed for reading and editing rather than preserving the original CSS layout.
Headings, paragraphs, links, lists and code can transfer well on a conventional article. A dynamic application, content inside frames or a page with an unusual layout may lose relevant information. Review important exports against their originals.
Images have a separate download step
Local image saving requires requests to the original image hosts. A host may deny access, require authentication or issue a short-lived URL. An extraction can therefore contain text even when an image was not saved successfully.
Keep the resulting assets directory beside the Markdown files. Verify image display in your editor and, when offline reading matters, test without relying on a remote link.
The source URL stays with the note
Published version 0.0.1 includes the original page URL in metadata. The 0.0.2 update submitted for review additionally includes a clickable link in the note body. A source URL makes it easier to check the original; it does not certify that the extraction is complete.
The local workflow does not use a developer-hosted parsing service. Optional Notion saving in the submitted update is a separate, explicit cloud action.
Verification matters more than a successful file write
Check at least the title, opening text, relevant sections, code and images. For difficult pages, try a smaller batch after the content loads and keep the source tab open until you are satisfied.
Safe tab closing checks saving status and interaction risks. It cannot guarantee that every detail you care about was captured, so inspect critical sources yourself.