Roadmap

Ideas, not a schedule. The product stays a local capture tool: full page PNG or a scrolling video. Files on this computer. No account, no upload.

Likely next

Context menu. Right-click the page and pick Full Page Screenshot or Record. Extra permission is only contextMenus. A context-menu click should count as the user gesture tabCapture needs. If Chrome is picky on record, fall back to opening the popup. Two items, not a long menu.

Folders in Downloads. Save into Downloads/Full Page Capture/screenshots/ and Downloads/Full Page Capture/recordings/. Chrome can only suggest folders under Downloads, not an arbitrary disk. After a save, a "Show in folder" action.

More still-image formats. Keep PNG as the default (text and UI stay sharp). Add WebP, maybe JPEG. WebM is a video format, not a still.

Visible-area screenshot. One PNG of the current viewport, no scrolling or stitching.

Copy to clipboard. Put the PNG on the clipboard so it pastes with Ctrl+V, no Downloads trip.

Start from here. Today capture always begins at the top. A "From here" option starts at the current scroll position.

Wait before capture. A short delay so cookie banners can be closed first.

Shrink huge PNGs. A max width (for example 1600 px) so a 4K-wide page does not write a 50 MB file.

Hide more overlays. Not only sticky headers: chat widgets, cookie bars, other position: fixed junk. One "Hide overlays" checkbox.

Maybe later

Short GIF. A GIF of a long page is a bad full substitute for MP4 (huge file, 256 colors, slow JS encoder). A short GIF (first seconds, low frame rate) could work for chat apps. Not a second main mode.

WebM next to MP4. Same recorder, different container. Smaller lift than GIF.

Filename extras. Title and date are already in the name. Folders would carry the screenshot vs recording split.

Not planning

Pretty frames, annotations, AI, PDF, region crop, or a URL queue. Those are a different product. Firefox can wait until the Chrome listing has some real use.