The page you are on, as Markdown, without leaving it.
Add it to Chrome Add it to Firefox
Press the button in the toolbar and the extension reads the page you are looking at, picks the article out of the navigation and the cookie notices, makes every link and picture address absolute, and hands back Markdown. Copy it, download it, or save the page as a self-contained `.html` file — its own design, its pictures inside the file, no requests to anything.
Documentation, a wiki, a ticket, a thread — anything that exists only rendered. It reads what your browser already has on screen, so a page only you can see converts without anybody handing over a password: Confluence, Jira and Notion need no administrator, no export and no API token.
The toolbar button opens a compact panel over the page. The side panel is the same thing kept open beside it, following you from tab to tab and converting each page as you arrive — which is what you want when you are working through a set of them rather than converting one. The right-click menu converts a selection.
The same ten conversions the site has — Word, PDF, spreadsheets, HTML, CSV, JSON, EPUB and the rest — run inside the extension. Nothing is uploaded and nothing needs a network connection, and several files picked at once become one document, in the order you picked them.
The permissions it asks for are the smallest set that does the work, and the largest of them is optional:
Sign in — the same account as the site, one click, no key to paste — and Save puts the document where the rest of them are. Share publishes a link, or names the people who may read it; they are told by email and read it signed in as themselves.
Chrome takes it from the Chrome Web Store, and so do the browsers built on Chromium: Edge, Brave, Opera, Arc. It asks for no host permission at install — until you connect an account it has no reason to talk to us — and the side panel asks for what it needs at the moment you turn it on.
Firefox takes it from Mozilla Add-ons, on the desktop and on Android. The same build from the same source; where Chrome asks for the side panel as a permission, Firefox grants its sidebar in the manifest, so there it asks for nothing at all.