AM A screenshot of a whole web page is surprisingly hard to take on your own. Your laptop captures only what fits on the screen, phone screenshots stop at the fold, and browser extensions want permission to read every site you visit. This tool captures the full length of any public page from a URL, in a desktop or a mobile layout, without installing anything.
It uses Google's PageSpeed Insights service, which runs Lighthouse, the same page-testing engine that is built into Chrome. Google opens your page in a real Chrome browser, waits for it to load, and records the whole page as an image. You can run 10 screenshots a day with no sign-up, and a page captured in the last 24 hours comes back instantly without using one.
How to take a full-page screenshot of a website
- Copy the address of the page. Any public page works: a home page, a product page, a blog post or a landing page. You can leave out https://.
- Paste it into the box and choose Desktop or Mobile.
- Press Take screenshot and keep the tab open. A progress bar and a timer show how long the capture has been running. Most pages take 15 to 40 seconds, and heavy pages can take close to a minute.
- Review the image. The preview scrolls, so you can check the whole page. The size card shows the image dimensions in pixels.
- Crop if you only need the top. Switch to Visible area only to cut the image to what a visitor sees before scrolling. The crop happens in your browser.
- Download it. Download PNG or Download JPEG saves the view you picked, with the site name, device and date in the file name.
The page address updates with the URL you captured, so you can bookmark it or send the link to a colleague. Opening that link runs the capture again, or shows the saved copy if it is less than a day old.
Desktop and mobile: what size are the screenshots?
Lighthouse loads the page as one of two emulated devices. The screen size decides the layout you get, because responsive sites rearrange themselves by width.
| Setting | Screen Lighthouse emulates | Visible area crop | Use it to check |
|---|---|---|---|
| Desktop | 1350 × 940 pixels | The top 940 pixels at 1350 wide | Laptop and desktop layout, header and hero, wide tables |
| Mobile | 412 × 823 pixels, a Moto G Power (2022) | The top 823 pixels at 412 wide | Phone layout, menu button, sticky bars, text size |
The full-page image keeps the page width and is as tall as the page. A typical store home page comes back somewhere between 3,000 and 9,000 pixels tall on desktop, and taller on mobile because the columns stack. Very long pages, such as infinite scroll collections, can be cut off at the bottom.
What people use website screenshots for
Client reports and audits
Agencies drop before and after screenshots into monthly reports and SEO audits. Pair this tool with the website SEO checker: the checker lists the on-page problems, and the screenshot shows the client what the page looked like on the day you checked it.
Competitor research and design ideas
Save the full product pages, collection pages and landing pages of competitors so you can compare layouts, trust badges, offers and page length side by side. If you are building a new niche site, a folder of full-page captures makes the brief much clearer. The AI Site Builder in AM Jarvis builds the pages themselves once you know what you want.
Records of how a page looked
A dated screenshot is a simple record of your policy pages, prices or promotions on a given day. That helps when a marketplace, ad platform or customer later asks what your page showed. Keep the files with the date in the name, which this tool adds for you.
Mobile checks without a phone
The mobile capture shows how the page stacks on a phone: whether the menu collapses, whether buttons stay large enough to tap, and whether a popup covers the content. Checking the image is faster than borrowing phones.
Bug reports
A full-page image makes a bug report clear to a developer: you can mark exactly where the layout breaks instead of describing it.
A pre-launch review of your own store
Before you launch a store or a redesign, capture the key pages in both views and review the images together. Looking at a whole page as a still picture makes gaps obvious that you miss while clicking around. A simple pass:
- Home page, desktop and mobile. Is the offer clear in the visible area crop?
- One collection page. Do product cards line up, and do prices and sale labels show?
- Your best-selling product page. Are the photos, price, shipping note and add to cart button visible on the first mobile screen?
- Shipping, returns, privacy and contact pages. Do they have real content, and do they show in the footer?
- A blog post or guide, if you have one. Is the text readable on mobile, without tiny fonts or wide tables that overflow?
Our Shopify SEO audit guide lists what to check in the page code once the layout looks right.
Other ways to take a full-page screenshot
You do not always need an online tool. These built-in options capture the page as you see it in your own browser, including pages behind a login, which this tool cannot reach.
| Method | How | Good to know |
|---|---|---|
| Chrome or Edge DevTools | Press F12, then Ctrl+Shift+P (Cmd+Shift+P on Mac), type "screenshot" and pick Capture full size screenshot | Works on logged-in pages; use the device toolbar first for a mobile size |
| Firefox | Right-click the page, choose Take Screenshot, then Save full page | Built in, no extension |
| iPhone Safari | Take a screenshot, tap the preview, choose Full Page | Saves the full page as a PDF, not an image |
| This tool | Paste a URL | No install, exact desktop and mobile sizes, public pages only |
Tips for cleaner, more useful screenshots
- Capture the exact page, not the home page. Paste the full product or landing page address, including any path. For a product with several variants, add the variant parameter your store uses so the right color or size is selected.
- Take both views of pages that matter. Run Desktop, then switch to Mobile and run it again. Put the two images side by side in your report so the client sees both layouts.
- Use the crop for above-the-fold reviews. The visible area crop is 1350 × 940 on desktop and 412 × 823 on mobile, the exact first screen Lighthouse loads. It answers the question most clients ask: what does a visitor see before scrolling?
- Keep the date in the file name. Downloads are named like
screenshot-example-com-desktop-20260929.png, with a-visiblesuffix for crops. Keep that name when you file it, and your history sorts itself. - Shrink it before you share. Full-page images are tall. For email and chat, JPEG is usually several times smaller than PNG. For slides, crop first, then resize.
- Retake after big changes. The saved copy lasts 24 hours. If you changed the page today and need a fresh capture right away, add a harmless parameter such as
?v=2to the address so it counts as a new page.
How the capture works
When you press Take screenshot, our server checks that the address is a public web page, then asks the Google PageSpeed Insights API to test it with the device you picked. Google starts a fresh Chrome browser, sets the screen size, loads the page and waits until it stops changing. Lighthouse then measures the full height of the page, resizes the browser to fit it and records one image of the whole thing. It also records the first screen on its own, which the tool uses as a backup when a page layout cannot be captured at full length.
Our server receives the result, keeps only the images, and saves them for 24 hours. Your browser shows the image, and cropping and converting to PNG or JPEG happen on your own device in a canvas, so the downloads do not travel through our server again. Because a full PageSpeed test runs behind every capture, the wait is longer than a simple screenshot, but the page is loaded the way a real visitor's browser loads it.
Why a screenshot may look different from your screen
Google's browser is a fresh visitor with no cookies, no logins and no history. That explains most differences:
- Cookie banners and popups appear. Newsletter popups, chat widgets and consent banners show up as a first-time visitor sees them. Google's browser does not click them away, so a popup that opens after a few seconds can cover part of the page.
- Lazy-loaded images can be blank. Many sites load images only when you scroll near them. Lighthouse captures the full height, but some images lower on the page may still be empty boxes or low-quality placeholders.
- Location-based content changes. The page loads from Google's servers, which are usually in the US. Sites that switch currency, language or shipping messages by country show that version.
- Animations are frozen mid-way. Sliders and fade-in effects are captured at whatever point they reached.
- Sticky headers appear once. A header that stays at the top while you scroll is drawn at the top of the image only.
Note: Google sends the capture as a compressed image. PNG keeps it without further loss, but it cannot add detail that was not captured, so a JPEG at the same size usually looks the same and is a smaller file. Choose PNG when you will edit or annotate the image, and JPEG for emails and reports.
Troubleshooting failed screenshots
A failed capture never uses one of your daily screenshots. These are the messages you may see and what to do about each:
| Message | What it means | What to try |
|---|---|---|
| Google could not find that domain | The domain does not resolve | Check the spelling and the ending (.com, .co.uk) |
| The site answered with an error (HTTP 403 or 5xx) | The server refused or failed. Some firewalls block automated browsers from data centers | Open the page in a private window to confirm it is public. If it is your site, check your firewall or bot protection rules |
| Google's test browser could not load that page | The connection failed, often an SSL problem or a site that is down | Try again in a few minutes and check the site loads over https |
| The page did not show any content in time | Nothing appeared on screen, for example a page that stays blank until you log in or confirm your age | Capture a public page instead, or use your browser's own full-page option |
| Took longer than 60 seconds | A very heavy page | Try again, or try the other device type |
If a page loads slowly for Google, it loads slowly for your visitors too. Heavy images are the most common cause on store pages, and the free image compressor shrinks product photos before you upload them.
Privacy and limits
- The address you enter is sent to Google. PageSpeed Insights loads it from Google's servers. Do not capture private links that contain passwords, order tokens or personal data in the URL.
- Public pages only. Pages behind a login, a paywall or a private network cannot be captured. Addresses on private networks are refused before anything is sent.
- 10 screenshots per visitor per day. Saved captures of the same page and device from the last 24 hours are free. Failed attempts are not counted.
- Images are kept for 24 hours on our server so repeat requests are fast, then deleted.
Once you have the image, the image resizer can scale it down for a slide or an email, and the image converter can turn it into WebP for a web page.