Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThumbalizr’s documented API can generate website screenshots, but its reviewed documentation does not describe a built-in recurring scheduler. To capture a site on a schedule, use an external scheduler to send a Thumbalizr API request at each interval, then check the response headers and save or forward the resulting image. For a fresh image on each run, include a changing timestamp value.
What you need before scheduling
- A Thumbalizr account and API key and secret, available through the member area as described in the API documentation.
- A scheduler capable of running a script at your chosen cadence. This can be a machine or hosted environment you already use; Thumbalizr’s reviewed pages do not endorse a particular scheduler or provide an official scheduling recipe.
- A destination for the screenshots, such as a local directory or a storage system in your existing workflow. The documentation does not prescribe a universal storage method or retention policy.
- A capture cadence that fits your account’s current quota and plan entitlements. The live Features & Pricing page lists the current offerings; check it before enabling a recurring job because limits and features can change.
Set up a recurring Thumbalizr capture
- Choose the interval. Decide how often the target page needs to be captured, and estimate the monthly total across every URL in the job. Confirm that the total fits your account’s current allowance.
- Build a valid API request. Set the page URL and desired capture options using parameters documented by Thumbalizr. The API reference describes options including width, full-page versus screen capture, delay, browser dimensions, country, watermark, and
timestamp; availability can depend on plan. - Set a changing timestamp for a fresh capture. Thumbalizr documents
timestampas a way to generate a new thumbnail. Use a current value that changes on each run; the API documentation recommends a current-date-style value and says any value can be used. Do not reuse a fixed timestamp if each scheduled run should request a fresh image. - Schedule the job externally. Configure your chosen scheduler to run the request at the intended cadence. This repeated-request approach is an implementation pattern based on Thumbalizr’s API, not a documented native Thumbalizr scheduling feature.
- Inspect the response and record the result. Check the HTTP response and Thumbalizr status headers to distinguish queued, successful, and failed requests. Save or forward the returned image only in a way that matches your workflow.
- Test before leaving it unattended. Run the job manually, verify the response and output, then confirm that the scheduler runs it at the expected time. Configure your own retry or alert behavior for failures.
Monitor API status and failures
Use the response headers to decide whether a scheduled request needs follow-up. The API documentation identifies these Thumbalizr headers:
As an Amazon Associate I earn from qualifying purchases.
X-Thumbalizr-Statuscan reportQUEUED,OK, orFAILED. Treat these as distinct outcomes: a queued job may not yet represent a completed image.X-Thumbalizr-Generatedreports the generation date.X-Thumbalizr-Errorprovides a failure reason when available.
Keep a timestamped log of the request, target URL, status, and any error text. If your scheduler supports notifications, alert on failed jobs or on runs that do not reach the completion state your workflow expects. The reviewed documentation exposes status information but does not prescribe a particular retry or alerting system.
Free tools Windows power users keep installed
One-click scans. No signup required.
Estimate capture volume and verify plan access
Multiply the number of URLs by scheduled runs per month to estimate the number of requested captures, then compare the total with your current account limit. Thumbalizr’s Features & Pricing page, accessed October 3, 2026, displayed these monthly allowances:
| Plan | Displayed screenshots per month |
|---|---|
| Free | 100 |
| Silver | 2,000 |
| Gold | 3,000 |
| Platinum | 5,000 or more |
These are plan allowances shown on Thumbalizr’s Features & Pricing page, not independent usage statistics, and the page’s prices and feature distinctions can change. Check the live page and your account before relying on a quota or assuming an API parameter is included in a tier. The API reference’s parameter table also shows plan-dependent availability.
Choose a scheduler that fits the workflow
The scheduling mechanism is outside Thumbalizr, so choose it by how you need the job to run and be maintained:
- Existing always-on machine: can run a scheduled script without adding a separate hosted service, but you maintain the machine and its schedule.
- Hosted scheduler: can run independently of a personal computer, but may add cost and requires configuring credentials, output handling, retries, and alerts.
- No-code automation: may reduce scripting, but confirm it can make the required authenticated request, pass a changing timestamp, inspect response headers, and handle the returned image.
These are general implementation choices, not Thumbalizr-endorsed integrations. In each case, protect the API credentials, avoid logging secrets, and verify where generated files are retained.
Account for Thumbalizr’s announced backend transition
On April 8, 2026, Thumbalizr announced a progressive transition from a Browshot-powered backend to ScreenshotCenter. The announcement said newly created accounts would use ScreenshotCenter first, followed by phased migration of existing accounts; it did not establish that the rollout is now complete. Thumbalizr stated: “Your thumbnails, settings, and API usage will continue to work exactly as they do today.” For present-day account behavior, use the live API documentation and your account rather than treating the announcement’s rollout plan as proof of completion.
Or skip the browser setup:
ScreenshotNeo is a website screenshot API and MCP server. A single GET request can return a screenshot or PDF; see the API documentation for parameters and response details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify page verdict and billing status. Its MCP server provides screenshot tools 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.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
Does Thumbalizr include a built-in recurring schedule?
The reviewed Thumbalizr API documentation describes screenshot requests, not a native recurring scheduler. Recurrence requires an external scheduler to repeat the API request.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →How do I ask Thumbalizr for a new image on each run?
Send a changing timestamp value with each request; Thumbalizr documents this parameter for generating a new thumbnail.
Which response headers help identify a failed capture?
Check X-Thumbalizr-Status for QUEUED, OK, or FAILED, and inspect X-Thumbalizr-Error for a failure reason.
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.
