Offline Snapshots will preserve a readable copy of an article or a fuller version of a page, then open it beside Link Details inside WebCull.
Reader will keep the meaningful text and structure of an article, documentation page, or other text-heavy source in a clean, readable copy.
Snapshot will preserve a fuller version of a page, including its layout, images, links, and selectable text. Each bookmark can use the format that fits the page without requiring both.
Readers and full-page Snapshots will open inside the bookmark manager beside Link Details. A saved page stays connected to the bookmark it came from and can be read without opening a separate download or leaving WebCull.
The browser extension will capture the page already open on a person's device. This local path can preserve private or signed-in pages that a remote service cannot reach.
For end-to-end encrypted accounts, capture and encryption will remain on the local device before the saved content is synchronized, keeping the page inside the same privacy boundary as the bookmarks.
For a public page, the web app will be able to request a Reader or Snapshot through WebCull without requiring the browser extension.
The CLI will also be able to request a Reader copy of a public URL. One request will capture the chosen page, not automatically save pages connected to it.
When someone directly bookmarks an article, documentation page, or another text-heavy page, WebCull may save a Reader copy by default so the useful content is ready for reading and search.
This will remain a visible, controllable choice. Ordinary bookmark imports, bulk operations, and linked pages will not quietly trigger a chain of automatic captures.
Saved Reader text will let WebCull search beyond the limited page keywords collected today. A quoted phrase can find a bookmark by an exact passage, while ordinary full-text search can surface pages by the words they actually contain.
Users will be able to highlight passages in several colors and keep those highlights synchronized with the saved page across their account.
A highlight may also hold a note that opens from the marked passage. The remaining planning work will define how annotations stay attached when a saved page is replaced or its Reader extraction changes.
Build the complete path from recognizing useful article content to producing its structured Reader copy and displaying it beside Link Details in a comfortable reading view.
Finish the extension capture path so a supported page can retain its layout, images, links, and selectable text, then make the saved Snapshot available from the same bookmark on supported devices.
Add the public-page capture path to the web app and CLI while keeping local extension capture available for private pages and end-to-end encrypted workflows.
Connect saved Reader text to bookmark search, then add persistent colored highlights and notes that remain part of the saved reading experience across devices.
WebCull will invite people to use Reader and Snapshot copies for real articles, documentation, research, and pages that later change or disappear.
The beta will show which page types preserve well, where the Reader needs clearer structure, and whether search, highlights, notes, and in-app reading hold up during everyday use.
WebCull will document complete examples of saving and revisiting public, private, text-heavy, and visually rich pages through the available capture paths.
Each case study will show what was preserved, how the saved copy was used later, and what still needs improvement before Offline Snapshots are ready for full launch.
