What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
PagePeeker’s public documentation does not publish a numeric requests-per-minute limit or a concurrency ceiling. It does publish monthly API-call allowances and explains that several steps in a screenshot workflow count separately. For a bulk launch, budget those calls carefully and get PagePeeker to confirm the burst rate, concurrency, and retry guidance for your plan before sending a large workload.
What PagePeeker’s public rate-limit information establishes
The official PagePeeker FAQ, API, and plan pages reviewed on October 3, 2026 list monthly call allowances but no numeric per-minute request limit, concurrent-request ceiling, or burst allowance. The pages do not show a publication date, so treat their prices and plan terms as a current-page snapshot and confirm them with PagePeeker before committing a workload.
As an Amazon Associate I earn from qualifying purchases.
That means a monthly quota is not evidence of a particular throughput. A plan with a million calls per month does not, by itself, establish how many requests the service will accept in a minute or how many captures it can process concurrently.
Recommended Free Tools
How many API calls does a bulk capture use?
PagePeeker’s FAQ counts each of the following as one API call:
#1 Best Overall
- Displaying an already-created thumbnail.
- Creating a thumbnail when one is not cached.
- Checking whether a thumbnail is ready.
- Any call to an exposed API.
As a result, the number of URLs is not necessarily the number of calls. The documented V2 workflow requests or refreshes a thumbnail, polls the readiness endpoint, then retrieves the thumbnail. Each readiness check adds a call; retrieving a displayed thumbnail also counts. The FAQ defines a render as “the actual creation of a thumbnail image.”
Estimate the workflow, not just the URL list
Before launching, estimate calls as the sum of every API request your client will make for each URL, including readiness polls, thumbnail retrievals, and any other exposed API calls. The exact total depends on your polling behavior and whether a thumbnail already exists. Unused monthly calls do not roll over.
Rank #2
- Intuitive interface of a conventional FTP client
- Easy and Reliable FTP Site Maintenance.
- FTP Automation and Synchronization
Published plans and monthly allowances
These are the terms shown on PagePeeker’s official plan pages accessed October 3, 2026; they are not independently verified service guarantees.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches| Plan | Price and calls | Thumbnail size and cache | Other listed terms |
|---|---|---|---|
| Free Branded | Free; monthly call limit not stated | Maximum 480×360; 20-day caching | PagePeeker branding |
| Free Unbranded | 100,000 API calls per month; price not stated | Maximum 480×360; 20-day caching | Link back required |
| Basic | $5.99/month; 100,000 API calls per month | Maximum 480×360; 7-day caching | — |
| Advanced | $39.99/month; 1,000,000 API calls per month | Maximum 480×360; 5-day caching | — |
| Premium | Custom pricing; no API-call limit stated | Unbounded thumbnail size; customizable caching time | Full-length screenshots and other premium features listed |
PagePeeker says Premium accounts using more than 5 million calls per month can contact the company to discuss pay-as-you-go. Public rates and terms for that arrangement are not stated. Premium’s lack of a stated limit is not a published guarantee of unlimited burst throughput.
Rank #3
Use the API workflow without wasting quota
PagePeeker calls V2 its current recommended API version; V1 is discontinued and redirects to V2. Follow the V2 thumbnail and readiness endpoints documented by PagePeeker rather than building new work around V1.
- Keep your API code on the server. PagePeeker warns that exposing API access in a browser can allow third parties to use your monthly allowance.
- Request or refresh the thumbnail. Use the V2 thumbnail endpoint and the parameters in PagePeeker’s API documentation.
- Poll readiness deliberately. Every readiness check counts as a call, so avoid tight, unnecessary polling loops. The public documentation reviewed does not specify a recommended polling interval or retry/backoff policy.
- Retrieve the thumbnail when ready. Account for this call in the planned request total.
- Record usage and outcomes. Paid and unbranded API responses can include
X-PP-Capture-Method,X-PP-Capture-Time,X-PP-Final-URL,X-PP-Hash,X-PP-Timestamp, andX-PP-Error. The reviewed documentation does not list request-rate headers or a Retry-After header.
Use the official PagePeeker API documentation for the endpoint syntax and response details; no endpoint parameters or runnable request example are reproduced here because the available documentation summary does not specify them.
Rank #4
Do not confuse freshness guidance with an API rate limit
PagePeeker says its robot attempts to fetch a given site or page only once every 5–7 days to minimize traffic. That is guidance about how often the robot recaptures a target page, not a limit on how quickly a customer may call PagePeeker’s API. Site owners can ask the robot not to capture their pages through a robots.txt rule for the PagePeeker user agent.
For scheduled site snapshots, PagePeeker recommends weekly captures or more often depending on the use case, and says it does not advise more than once daily for that scenario. This cadence guidance is not an account-level API quota. Premium snapshots can be scheduled or requested on demand. Premium full-page screenshots also have options for page width and maximum height, compression, output size, overlays, and wait settings; the reviewed page does not state a separate numeric request rate for them.
Best Value
What to confirm before a bulk run
Ask PagePeeker support to confirm the operational limits that the public pages do not settle:
- Maximum requests per minute and concurrent requests for your account and plan.
- Permitted burst size and whether limits differ for thumbnail requests, readiness checks, or full-page captures.
- Recommended polling intervals, retry behavior, and how throttling or failed captures are reported.
- How overage or pay-as-you-go billing works for the expected monthly volume, including any terms beyond the stated Premium contact option.
- Expected render throughput for your workload; the reviewed public pages do not give a measured throughput or latency guarantee.
Troubleshooting bulk capture planning
- Your call estimate is lower than observed usage: include readiness checks and thumbnail retrievals, not only initial requests. Existing thumbnails that are displayed also count.
- A polling loop consumes calls quickly: each readiness check is a chargeable API call. Reduce unnecessary polling and ask PagePeeker for its current recommended polling and backoff behavior.
- You cannot determine the allowed burst size: the reviewed public pages do not state a numeric rate or concurrency limit. Obtain account-specific confirmation before launch rather than inferring a limit from monthly quota.
- Your API allowance is unexpectedly consumed: check that credentials are not exposed in a client-side application; PagePeeker warns that others could use the account allowance.
- You expect fresh captures more often: the robot’s 5–7-day recapture statement describes target-site fetching, not customer API throughput. Confirm the applicable capture and cache behavior for the API product and plan.
Or skip the browser setup
For an alternative screenshot API, try ScreenshotNeo first: it removes cookie banners, popups, and chat widgets before capture, bills only clean shots, and its lowest paid plan is $5. It provides a one-request screenshot API as well as an MCP server for AI agents. See the ScreenshotNeo API documentation.
Example cURL request for a WebP screenshot:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
ScreenshotNeo says bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing; each response includes X-Page-Verdict and X-Billed headers. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo’s free plan.
Free tools Windows power users keep installed
One-click scans. No signup required.
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.




