Troubleshooting full-page screenshots
A normal screenshot only records what fits on your screen. When you need the whole webpage from top to bottom, several things can break the result: content that loads late, headers that follow you down the page, panels that scroll on their own and pages Chrome does not let extensions touch.
Print Screen, Windows + Shift + S and Command + Shift + 3/4 on a Mac capture only the visible screen. To capture the entire page, use a scroll-and-stitch tool such as Capture’s Full Page mode, or Chrome DevTools’ Capture full size screenshot command. If parts are still missing, check the fixes below.
Symptom → cause → fix
Each problem below applies to any full-page method. Capture handles several of them automatically; the others have simple workarounds.
Cause: operating-system shortcuts (Print Screen, Windows + Shift + S, Command + Shift + 3 or 4) and Chrome’s default screenshot option capture the current viewport only.
Fix: use a full-page capture. In Capture choose Full Page; it scrolls through the page and stitches the sections into one image.
Cause: lazy loading. Many sites only load images when they scroll into view. Methods that resize the page instead of scrolling it can miss them.
Fix: Capture’s Full Page mode scrolls through the page as it captures, which triggers most lazy loading. For very slow sites, scroll to the bottom once before capturing so the content is already loaded.
Cause: sticky or fixed navigation, cookie bars and chat buttons stay attached to the viewport while the page moves underneath, so naive stitching repeats them.
Fix: Capture’s stitching includes handling for common fixed and sticky elements. Pro adds manual hide for anything that still gets in the way.
Cause: some web apps (mail, chat, dashboards) scroll an inner panel rather than the page itself, so full-page tools see a page that is only one screen tall.
Fix: open the long content in its own tab or a print/reader view if the app offers one, or capture it in sections and keep them together in a report. No full-page method handles every custom scrolling panel.
Cause: carousels, animations and auto-playing sections change between scroll steps.
Fix: Capture can temporarily reduce animations and transitions during capture for a more consistent result. Pausing a carousel before you start also helps.
Cause: Chrome blocks every extension on protected pages such as chrome:// settings pages and the Chrome Web Store. Capture is also not enabled in Incognito.
Fix: open a normal webpage in a regular window. For Chrome’s own pages, use your operating system screenshot shortcut.
Cause: very long pages produce very tall images that are hard to read at a glance.
Fix: use Fit Page, Fit Width and numeric crop controls in the editor. Pro’s professional PDF splits long captures across readable pages instead of shrinking them.
Cause: the DevTools command renders the page at full height in one pass instead of scrolling, so lazy content, fixed elements and inner panels can behave unexpectedly.
Fix: scroll through the page first, or use a scroll-and-stitch extension that opens the result in an editor.
Mac and Windows
The keyboard shortcut you already know is not the problem; it simply captures the screen, not the page. These are the methods that capture the full page.
Good for occasional use; there is no editor.
These never include content below the fold, which is why they cannot produce a full-page screenshot.
Works the same in desktop Chrome on Windows, macOS and Linux.
Common questions
Standard screenshot shortcuts only capture what is visible on screen. To capture a whole webpage you need a full-page method that scrolls and stitches the page, such as Capture’s Full Page mode or Chrome DevTools’ Capture full size screenshot command.
The site probably lazy-loads images when they scroll into view. Capture’s Full Page mode scrolls through the page while capturing, which triggers most lazy loading. On slow sites, scroll to the bottom once before starting the capture.
Use a tool that accounts for fixed and sticky elements. Capture’s full-page stitching includes handling for common fixed and sticky interface elements, and Capture Pro adds manual hide for elements you want to remove.
Command + Shift + 3 or 4 only captures the screen. For the entire page, use Capture’s Full Page mode, or open DevTools with Command + Option + I, press Command + Shift + P, type screenshot and choose Capture full size screenshot.
Print Screen and Windows + Shift + S capture only the visible screen. In Chrome, use Capture’s Full Page mode, or open DevTools with F12, press Ctrl + Shift + P and run Capture full size screenshot.
Chrome does not allow any extension to run on protected pages such as chrome:// pages and the Chrome Web Store. Capture is also not enabled in Incognito windows. Use a regular window and a normal webpage.
Related guides
FREE SCREENSHOT EXTENSION FOR CHROME
Install Capture by RATdeck from the official Chrome Web Store. Full Page and responsive capture, annotation and unlimited Copy Image are free, with no watermark and no ads.
