Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If a URL2PNG screenshot shows only the top of a page, add fullpage=true to the request. URL2PNG defaults to a viewport-only capture; its full-page option asks it to attempt to capture the entire document canvas. If the bottom is still missing, check whether that content has rendered before capture, and whether you are seeing a cached image.
Enable full-page capture in the URL2PNG request
Add fullpage=true to the URL2PNG request parameters. The default is false, which captures only the viewport. URL2PNG describes full-page mode as an attempt to capture the entire document canvas, rather than a guarantee that every page element will be captured.
For example, add this parameter to your existing request:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
fullpage=trueKeep this setting separate from the viewport dimensions. URL2PNG documents a default viewport of 1480×1037 and allows a custom viewport. Changing the viewport changes the browser render dimensions; fullpage=true requests a capture of the document canvas. A larger viewport alone does not enable full-page capture. See the URL2PNG quickstart and parameter documentation.
#1 Best Overall
If the full-page screenshot is still cut off
Once fullpage=true is present, investigate when the page content appears and whether the returned image is fresh. These settings solve different problems: full-page mode requests the document canvas, timing options wait for content, and cache controls affect freshness.
Wait for content that renders late
If lower-page content is added after the page initially becomes ready, configure URL2PNG’s delay option. The documented delay is a fixed wait after document readiness and asset loading. Choose a wait appropriate to the page; a longer delay can increase capture time and does not itself request a full-page image.
Rank #2
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL160_.jpg)
- Intuitive interface of a conventional FTP client
- Easy and Reliable FTP Site Maintenance.
- FTP Automation and Synchronization
If your page can expose a readiness signal, URL2PNG also documents say_cheese=true. It waits for the page element <div id='url2png-cheese'></div>. Add that element when your application knows the content intended for capture has finished rendering. This can be more specific than relying only on a fixed wait.
Check for a cached screenshot
If the image looks stale rather than merely short, use URL2PNG’s unique option to force a fresh screenshot by varying its value. The documentation lists a default cache TTL of 2,592,000 seconds (30 days). That is a cache setting, not a performance benchmark.
Inspect how the page itself renders
URL2PNG says full-page mode will attempt to capture the document canvas. If it is already enabled and the image remains incomplete, inspect the target page’s scrolling and rendering behavior, including whether the missing region is created dynamically or only appears after scrolling. Increasing viewport dimensions blindly may change the render without fixing how the page exposes its content.
Quick troubleshooting checklist
- Only the initial screen appears: confirm the request includes
fullpage=true; the documented default is viewport-only. - The bottom is blank or missing content: determine whether the page fills that area after initial readiness, then try a suitable
delayor the documentedsay_cheese=truereadiness element. - The screenshot shows old content: vary
uniqueto request a fresh capture rather than relying on the default cache TTL. - The page is still incomplete with full-page mode and adequate timing: inspect the page’s own scrolling and dynamic-rendering behavior. Full-page mode is documented as an attempt, not a universal guarantee.
- You changed viewport dimensions but still see a viewport-sized image: set
fullpage=trueas well; viewport size and full-page capture are distinct options.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. One GET request can return an image or PDF, without you needing to configure a browser capture flow. Its clean-shot options accept cookie and consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; those steps can each be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf.
For a full-page capture, use the API’s documented full-page option as needed. The following one-call cURL example uses the supplied API pattern; see the ScreenshotNeo documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe free plan includes 1,000 screenshots a month with no card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Sign up for ScreenshotNeo and start with 1,000 free screenshots a month, no card required.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
Does increasing URL2PNG’s viewport make a screenshot full-page?
No. Viewport dimensions set browser render size; use fullpage=true to request the document canvas.
Best Value
Is URL2PNG full-page capture guaranteed to include every element?
No. URL2PNG documents it as an attempt to capture the entire document canvas, so page rendering behavior can still matter.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
