Stitched Full-Page Capture

Overview

Use settled viewport screenshots instead of trusting one-shot browser fullPage captures. This is especially important for Framer pages and other lazy/scroll-animated sites where the MP4 can look correct while the tall screenshot is mostly blank.

When to use this skill

• When a full-page screenshot of a lazy-loaded, scroll-animated, Framer, WebGL/canvas, or reveal-heavy page comes back blank, gray, white, sparse, or shows only a tiny content strip.
• When a one-shot full-page screenshot disagrees with a working scroll-recording MP4 that shows the page rendering correctly.
• When article evidence or section crops must be cut from a trustworthy full-page image instead of an unreliable native fullPage capture.
• When repairing or regenerating daily UI-inspiration article captures via the bundled stitch_full_page_capture.mjs script against a manifest.json.
• When validating a stitched capture by checking dimensions, blank/gray bands, and agreement with the representative still, MP4, and motion frames.
• Not for pages that already render correctly in a single native fullPage screenshot with no lazy-load, scroll-animation, or reveal issues — a plain one-shot capture is enough there.

Core Workflow