Real browser rendering, not a mockup
This renders the actual live page in a real browser environment and captures it as an image - useful for documenting how a page currently looks, building a visual archive before a redesign, or grabbing a preview image without a screen-recording tool. Full-page capture scrolls through the entire page; the default captures just the initial visible area.
Why full-page and visible-area captures serve different purposes
A visible-area capture shows exactly what a visitor sees without scrolling - useful for checking above-the- fold design or grabbing a quick preview thumbnail. A full-page capture stitches the entire scrollable page into one tall image, better suited for archiving a complete page's content or documenting a long article or landing page in full before changes are made to it.
Why this captures only what a public visitor would see
The capture happens as an unauthenticated visitor loading the URL fresh - the same as anyone opening the link in a new browser tab with no prior login or session. Pages that require sign-in to view can't be captured this way, since there's no way to pass private credentials through to the capture process.
A limitation worth knowing about dynamic content
Content that loads based on scroll position, a timed animation, or an asynchronous data fetch can occasionally be mid-transition at the exact moment the capture happens - this is an inherent limitation of any automated screenshot tool capturing a live, dynamic page, not something unique to this one.