What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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
For a long but finite webpage, ScreenshotMachine documents a full-height capture using dimension=WIDTHxfull (for example, 1366xfull). For a genuinely infinite feed, that setting does not establish that ScreenshotMachine will scroll the page and load more entries: its public API guide does not document automatic infinite-scroll traversal. Set a clear stopping point and treat the result as a capture of the content the service has loaded, rather than a guaranteed image of everything a visitor could eventually scroll through.
What ScreenshotMachine’s full-page option does—and does not promise
ScreenshotMachine’s API guide says that full is accepted as the height in the dimension parameter for a full-length webpage screenshot. A finite article or landing page has a measurable end, so it can be captured at full height. An infinite feed has no natural end, and may reveal additional items only after scroll events.
The API guide does not say that ScreenshotMachine automatically scrolls the source page or repeatedly triggers feed loading. A full-height request therefore should not be treated as a promise to capture every entry in an infinite feed. The practical target is a defined slice: for example, the entries currently loaded, a particular date range, or content through a chosen point.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Capture a finite page at full height
- Choose the page and viewport. The API request needs the target URL and your customer key. Choose
device=desktop,phone, ortabletto match the rendering you want. - Set the full-height dimension. Use
dimension=1366xfullas an example, or choose another supported width. ScreenshotMachine documents widths from 100 to 1920 pixels; numeric heights range from 100 to 9999. Its guide also gives1024xfullas an example. - Allow time for rendering if needed. The documented default
delayis 200 ms. It accepts 0 and increments of 200 ms up to 10000 ms. ScreenshotMachine suggests considering 2000 ms or more for some long pages with images or animations. This provides rendering time; it is not documented as a way to scroll an infinite feed. - Select the output. The documented formats are JPG, PNG, and GIF; JPG is the default. Pick the format appropriate to your downstream use.
- Set cache behavior.
cacheLimit=0requests a fresh screenshot rather than using a cached image. The documented cache limit can be set from 0 to 14 days, with fractional values available for shorter intervals. - Save the returned image. ScreenshotMachine’s Python example demonstrates generating the API URL and downloading the response to a local file.
The official settings and parameter details are in the Screenshot Machine API documentation; the vendor’s download example is in its Python screenshot example.
Work with an infinite feed by defining the capture boundary
Before making a request, decide what “complete” means for this feed. It cannot mean everything the user might ever load: the feed has no fixed endpoint. If the screenshot must include entries beyond those initially visible or loaded, the key question is whether the capture method scrolls the page and causes those entries to load. ScreenshotMachine’s public guide does not establish that behavior.
- For a capture of the currently available page content, use
dimension=WIDTHxfulland inspect the result to see where it ends. - If expected entries are missing, do not assume a longer
delaywill fetch them. The documented delay controls wait time, not feed traversal. - If a specific range is required, define that range in the page itself where possible, or use a capture workflow that explicitly supports scrolling and incremental loading. The cited ScreenshotMachine guide does not specify such a workflow.
Other documented controls
These options can adjust the page context or capture target, but they do not establish that ScreenshotMachine triggers infinite scrolling.
zoomaccepts 10–400 percent; 100 percent is the default.clickcan trigger a CSS-selected element, andhidecan hide selected elements.cookies,accept-language, anduser-agentlet you provide request or browser context.selectorcaptures a single DOM element instead of the whole page;cropadjusts the captured area.
Troubleshooting
The image stops before the entries I expected
The feed may load entries only after scrolling, and the ScreenshotMachine API guide does not document automatic scrolling. A larger delay may help assets on already-rendered content finish loading, but it is not a documented fix for entries that have not been triggered to load. Reconsider the capture boundary or use a method that explicitly scrolls the page.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →The screenshot is missing images or animations are incomplete
Try a longer documented delay, such as 2000 ms or more when appropriate for a long page. The guide presents this as a rendering wait for some pages, not as a guarantee for every site or a way to load additional feed content.
The result appears stale
Set cacheLimit=0 to request a fresh screenshot rather than accepting a cached image.
The requested element is absent
Check that the CSS selector supplied to selector or click matches an element on the page. selector is for capturing one DOM element; it is not a full-page or infinite-scroll setting.
Or skip the browser setup
ScreenshotNeo accepts one GET request with the target URL and returns an image or PDF. For example, this cURL request saves a WebP screenshot of a finite page:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. ScreenshotNeo accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. Its MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up for 1,000 free screenshots a month—no card required.
Quick Recap
Sources
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.
