Clickdoc - step-by-step guides, on-device

Record your clicks and get a step-by-step guide with screenshots. Nothing leaves your computer.

Turn any task you do in the browser into a step-by-step guide with screenshots, without a single screenshot leaving your computer. Press record, do the task, press stop. Clickdoc writes a step for every click, every field you fill and every option you choose, with a screenshot taken just before the click and a highlight on the exact element. Edit the text, add notes, hide anything private with a permanent blur, zoom in on the click, add your logo, then download one self-contained HTML file, copy it into Google Docs, Notion or Confluence, copy Markdown, or print to PDF. WHY CLICKDOC - Nothing leaves your machine. Screenshots and guides live in your browser's local storage. There is no account, no server, no upload. That makes it usable where cloud documentation tools are blocked by policy: finance, payroll, banking portals, client systems. - Pay once. The free version makes 10 guides. A personal license is a one-time purchase of $49, not a seat per month. - Guides you can actually hand over. The export is a single HTML file that opens anywhere, with the screenshots inside it. WHO IT IS FOR - Ops and admin staff documenting internal software - MSP technicians writing client runbooks - Bookkeepers documenting Xero, QuickBooks and payroll flows for clients - Anyone writing SOPs who has been told "no cloud tools" EDITING Blur any area of a screenshot (baked into the image, not a removable overlay). Zoom to the clicked element. Notes under any step. Add text-only steps. Reorder, delete, rename. Pause and resume while recording. WHAT IT RECORDS Clicks on links, buttons, tabs and menu items. Text typed into fields (password and card fields are masked). Dropdown choices. Enter presses. Page navigations. Clickdoc does not use AI, does not read pages while you are not recording, and does not collect analytics. WHY CHROME WARNS ABOUT "ALL YOUR DATA ON ALL WEBSITES" Chrome shows one blunt warning for the two things Clickdoc needs to record a guide: permission to work on whatever site you point it at, and a small script on the page that notices your clicks. Here is every permission in the manifest, in plain words. - storage — keeps your guides, your logo and your license key in the browser's own local storage on this computer. - tabs — reads the title and address of the tab you are recording so a step can say which page it happened on, and opens the finished guide in a new tab when you press stop. - unlimitedStorage — lifts Chrome's 10 MB cap, because a guide with twenty screenshots inside it is bigger than that; the storage is still local. - webNavigation — notices when you move to a new page during a recording, so the guide gets a "Go to ..." step instead of a gap. - <all_urls> host permission — recording works on any site you choose, including internal tools and portals nobody else can reach, which is only possible if the permission is not limited to a list of sites picked in advance. - The content script on <all_urls> — the piece that watches for clicks, typing and dropdown choices; it sits idle on the page and only listens while a recording you started is running, and it sends nothing anywhere. What none of it is used for: no account, no server, no analytics, no AI, no reading pages while you are not recording, no selling or sharing of anything. Your screenshots and guides never leave the machine they were made on. THE NO-NETWORK CLAIM, AND HOW TO CHECK IT On the free plan Clickdoc makes no network request at all. Buying a license adds exactly one destination: the extension asks the store once whether the key you pasted is genuine, and asks again every 30 days so a refund ends the license. That is the whole list. You do not have to take that on trust. Open chrome://extensions, turn on Developer mode, click Clickdoc's service worker link and the extension's own pages, and watch the Network tab through a whole recording — it stays empty. The project's end-to-end suite asserts the same thing on every run: it records every request made by the extension's pages and its service worker, and fails if a single one during the unlicensed flow leaves the test page's own origin. Two controls keep that check honest — the recorder has to catch a service-worker request and the store's licence check before its zero is accepted as a real zero.