ShotDock - Full page screenshots that never leave your browser

by•
Open ShotDock, choose Full Page or Visible Area, and get one clean, complete image in seconds. The capture, the stitching and the encoding all happen inside your browser. There is no screenshot server, no upload step and no account to create, so a screenshot of an internal dashboard or a private document stays exactly where you took it.

Add a comment

Replies

Best
Maker
šŸ“Œ
Hi Product Hunt šŸ‘‹ I'm Rakib, and I build small Chrome tools at Degird. ShotDock started with an annoyance. I needed a full-page screenshot of an internal dashboard, installed the first extension I found, and watched it upload my dashboard to a rendering server so it could hand the image back to me. That is a completely ordinary way for these tools to work, and I found it hard to accept. So ShotDock has no server. Capture, stitching and PNG/JPG encoding all happen inside your browser. There is no account, no upload step, no watermark, and no ShotDock backend for a screenshot to travel to. The part I'd most like feedback on is what makes full-page screenshots hard rather than what makes them private: šŸ”ø Sticky headers. A fixed header re-renders into every scroll frame, which is why naive full-page screenshots have a header marching down them like a staircase. ShotDock keeps it in the first section, where it genuinely belongs, and hides it for the rest — via visibility, so nothing reflows underneath. šŸ”ø Seams. Sections overlap on purpose, and the stitcher aligns on where the page actually landed after each scroll rather than where it was asked to go — browsers clamp scrolls, lazy content shifts layout mid-capture, and scroll-snap lands where it likes. Each frame is drawn starting exactly where the previous one stopped, so rounding can't open a gap. There's a test that enforces it. šŸ”ø Restoring the page. Everything ShotDock touches is reverted in a finally block, and if the browser suspends the extension mid-capture the page restores itself on a watchdog timer. Your scroll position comes back too. šŸ”ø Really long pages. Live progress you can pause, resume or cancel — and output past the browser's canvas limit splits into numbered parts instead of failing outright. One design decision worth calling out: ShotDock requests **no host permissions at all**. It never asks to "read your data on all websites". Chrome grants access to a single tab at the moment you click capture, and that access lapses when you navigate away. It's free, MIT licensed, Chrome 116+, and there is no paid tier planned for what 1.0 does. What's next, in order: capture history, then annotation/crop/blur, then PDF and collections. None of that is in today's build. I'll be here all day. Throw your ugliest page at it — an infinite feed, a dashboard with four fixed panels, a site with a cookie banner that won't die — and tell me what breaks. Bug reports are the most useful thing you can leave me. šŸ™