As a developer, I got frustrated with the screenshot workflow for documentation: Open DevTools → Set viewport size → Take screenshot → Switch tabs → Download → Open editor → Annotate → Save → Repeat...
Built ZScreenshot - a sidebar extension that keeps everything in one place. Set viewport once, capture instantly, edit in sidebar. No tab switching, no DevTools.
Free: • Custom viewport (consistent screenshot sizes, no sidebar interference) • Full-page capture (scrolling pages) • Tab recording with audio • Privacy-first (all local processing except authentication)
Pro (14-day free trial, no credit card): • Image editor (arrows, shapes, text, blur, emoji - instant annotations) • Collection (merge multiple screenshots for comparisons) • Bulk ZIP download • MP4 export
Everything happens in the sidebar: Capture → Edit → Download → Access history anytime.
Why no "select area before capture"? OS tools (Win+Shift+S, Cmd+Shift+4) already do this perfectly. ZScreenshot focuses on what they can't: viewport control, instant editing, history management. Plus, crop-after-capture gives more flexibility.
Chrome Web Store: https://chromewebstore.google.com/detail/zscreenshot/jdgmjck...
Parameswar•1h ago
Curious how you handle edge cases like sticky headers, lazy-loaded content, or pages with dynamic resizing—do those affect capture accuracy?
zscreenshot•1h ago
For full-page captures, I'm using Chrome's native DevTools screenshot API (the same one you get with Cmd+Shift+P → "Capture full size screenshot"). So the behavior for sticky headers, lazy-loaded content, and dynamic pages essentially matches what DevTools does—both the benefits and limitations.
Sticky headers: Captured in their fixed position throughout the scroll, as DevTools does.
Lazy-loaded content: Depends on how Chrome's capture handles it. Generally works well for standard lazy loading, but infinite scroll or heavily JS-dependent dynamic content can be hit-or-miss. That's a Chrome limitation rather than something I can work around in the extension.
Dynamic resizing: The viewport setting works well here since it's part of the DevTools protocol. Pages render at the specified dimensions during capture.
For visible area captures (not full-page), I have more control and it's straightforward—basically a direct screenshot of what's rendered in the viewport.
zscreenshot•57m ago