Why I built it
It started with a new job. Since I changed jobs, a lot of my work has been documenting purchases: find the order page in a web store, save it, attach it to the paperwork. Three things kept getting in the way.
- The capture tools I tried surrounded the page with so many buttons and panels that I kept losing track of the page itself.
- The order page came with ads, cookie banners and rows of recommendations that I couldn't remove.
- When I saved it as a PDF, the text had become a picture, so later I couldn't search my own receipts for an order number.
So I wrote a tool for myself that dealt with those three. Then I gave it to friends and colleagues, and they told me what was still missing: a page it captured badly, a format they needed, a step they kept doing by hand. Page Scanner is still made that way. I build what people ask for, they try it, and their next round of feedback decides what comes after.
What I want software to be
Three rules I hold Page Scanner to.
By the third use, you should be a pro. The first time, you find the button. The second time, you notice the options. By the third, you should get what you came for without reading a manual or getting stuck. If a feature needs a tutorial before anyone can use it, the feature is not finished.
Anything you repeat should be automatable. If you save the same kind of page every week, you should not have to click through it by hand every week. A script or an AI agent should be able to do it for you, which is why Page Scanner has a command line and an MCP server beside the toolbar button.
Your sensitive data should not reach a third party. Order pages, statements and internal dashboards are exactly what people capture. Your captures stay on your computer, and the privacy policy lists what the extension sends and what never leaves your machine.
Get in touch
If a page captures badly, something breaks, or you wish it did something it doesn't, write to hello@pagescanner.app.