Why Only Part of the Page Ended Up in Your Screenshot

You run a full-page capture on a mail client, an admin panel or a documentation site, and you get one screen. The part you wanted — the long list, the long thread, the long document — is cut off exactly where the window ends.

The capture worked. It captured the page. The trouble is that the thing you were scrolling was not the page.

What is actually happening

On an ordinary web page there is one scroll: the window moves down the document. Full-page capture is built on this. It scrolls the window, photographs each screen, and stitches.

Web applications are usually built differently. The outer page is fixed at exactly the size of your window and never scrolls at all. Inside it sit panels — a sidebar, a message list, a reading pane — and each of those has its own scroll, independent of the others.

When a capture asks that page to scroll down, the page answers honestly that there is nowhere to go. It is already showing all of itself. The content inside the panel is not part of that answer.

How to tell which one you have

Put the pointer over the part of the screen you care about and scroll. Then put it over the margin, far from that content, and scroll again.

If the second attempt does nothing, the page itself is not scrolling and you have an inner panel. If both scroll the same content, it is an ordinary page and your problem is something else.

A second tell: look for two scrollbars, one at the very edge of the window and one a little inside it. Two scrollbars means two scrolls.

What actually works

1. Make the window taller, then capture what is on screen. The panel grows with the window. A tall window plus an on-screen capture often gets the whole thing in one shot, and it is the fastest route by a wide margin.
2. Zoom out before capturing. Ctrl or Cmd and minus. At 67% or 50% far more of the panel fits, and for a list or a table that is usually still readable. The image will be less sharp — the reasons are in why your full-page screenshot came out blurry.
3. Find the plain version of the content. Mail clients have a print view. Admin tools have export. Documentation has a single-page or raw view. These are ordinary documents that scroll normally, and they capture without any of this.
4. Capture in sections and join them yourself. Scroll the panel a screen at a time, capture each, assemble afterwards. Tedious, and it is the fallback when nothing above applies.

Why no extension solves this properly

It is tempting to assume a better tool would simply scroll the panel instead. The difficulty is knowing which panel. A complex application can have half a dozen independently scrolling regions on screen at once, and nothing in the page says which one you meant. A tool that guessed would be wrong often enough to be worse than one that did not try.

So this is a genuine limit rather than an oversight, and the practical answer is to make the window do the work: a taller window, or a zoomed-out one, or a version of the content that scrolls the ordinary way.

What PageStill does

Full-page capture scrolls the window, so a panel with its own scroll has the same limit here as everywhere else. What helps is the on-screen capture: set the window up so the panel shows what you need, and take that.