To generate a website thumbnail automatically with Screenshotlayer, send its capture API an access key, a fully qualified page URL such as https://example.com, and a width in pixels. Use a small server-side script or publishing workflow to make the request, then save or display the returned image. Screenshotlayer’s FAQ confirms that width can request a custom-width thumbnail; the API documentation also describes viewport, output format, delay and cache controls.
How the thumbnail workflow fits a blog
Screenshotlayer captures a web page from its URL and returns an image. A blog can connect that API call to a script, scheduled task or publishing workflow: for example, when an editor adds an external URL, the workflow requests a capture and stores or references the resulting image. The reviewed official documentation does not establish a ready-made WordPress plugin or turnkey CMS connector, so plan for an API integration rather than assuming one is included.
As an Amazon Associate I earn from qualifying purchases.
- Register with Screenshotlayer and retrieve the account’s API access key.
- Build a request to the Screenshotlayer capture endpoint with the key and target URL.
- Set
widthto the thumbnail width your design needs. Setviewportto control the dimensions used to render the page before capture. - Choose output format and any needed rendering delay or cache behavior.
- Have your server-side workflow handle the response, errors and quota limits, and decide whether to store, export or refresh the image.
The capture width and viewport serve different purposes: width specifies the requested thumbnail width; viewport specifies the page-rendering dimensions. Screenshotlayer’s API documentation gives a default viewport of 1440×900. PNG is the documented default format, with format selection available. These are documented options, not a guarantee that every target page will render identically.
Recommended Free Tools
Make a request from a publishing workflow
Use the endpoint and parameter names shown in Screenshotlayer’s API documentation. The key belongs on the server, not in public page markup or browser-side JavaScript. This generic cURL example requests a 600-pixel-wide thumbnail; adjust the format or other parameters to suit the integration:
#1 Best Overall
curl -G "https://api.screenshotlayer.com/api/capture"
--data-urlencode "access_key=YOUR_ACCESS_KEY"
--data-urlencode "url=https://example.com"
--data-urlencode "width=600"
--data-urlencode "viewport=1440x900"Replace YOUR_ACCESS_KEY with the key from your account and https://example.com with the full URL to capture. The documentation requires the URL to include its protocol, such as https://. Treat the response according to the API’s response format and your own integration: check whether the request succeeded before saving or publishing an image, and do not assume an error response is a usable thumbnail.
Adjust capture behavior when needed
width: request the thumbnail width in pixels.viewport: set page-rendering dimensions; the documented default is 1440×900.format: choose an output format; PNG is the documented default.delay: allow additional time before capture when a page needs to render. The appropriate value depends on the target page.css_url,user_agentandaccept_lang: documented customization parameters for capture behavior. Their effect on a particular site has not been independently established here.
Choose image retention and refresh rules
Screenshotlayer describes snapshots as being returned as image URLs and documents optional export to S3 or FTP. Export is not required for every blog: choose a destination and retention approach that suits your publishing system and the service terms. Screenshotlayer’s terms restrict transferring, redistributing or exploiting API data and services beyond the licensed scope, so review the current terms before operating a public-facing thumbnail service or redistributing captures: Screenshotlayer terms.
The API specification lists a default cache TTL of 2,592,000 seconds (30 days), and a force option for requesting a fresh capture. The FAQ says a custom TTL can be set below the default. Decide whether an external-page thumbnail should remain as first captured or be refreshed when its target changes; use the documented cache controls accordingly. Verify parameter behavior against the live API documentation before deploying, because product behavior can change.
Protect the key and plan for errors and quotas
- Keep credentials server-side. Do not expose the access key in source code delivered to a visitor, a public repository or client-side requests. Screenshotlayer’s terms put responsibility for credential secrecy and security on the account holder.
- Check every API result. Handle returned errors instead of saving an error response as an image. The terms make users responsible for detecting and handling returned errors.
- Track request use. Every automated capture can consume plan allowance. Add quota monitoring and a fallback for publishing when requests are exhausted.
- Set refreshes intentionally. Repeatedly capturing an unchanged URL can waste requests; cache or schedule refreshes based on how often the target is expected to change.
- Test the whole workflow. Confirm the requested width, output format, saved image location and display dimensions in your own publishing setup. No specific CMS integration or target-site outcome is established by the documentation cited here.
Plans, commercial use and India-specific checks
Screenshotlayer’s pricing page, checked in 2026, listed these USD plans. The vendor’s FAQ describes the Free tier as non-commercial and paid plans as having commercial-use options; confirm the current terms for your intended use before publishing thumbnails on a monetized blog.
Rank #3
| Plan listed by Screenshotlayer | Monthly allowance | Listed price | Use and billing notes |
|---|---|---|---|
| Free | 100 snapshots per month | Free | Vendor FAQ describes this tier as non-commercial. |
| Basic | 10,000 requests per month | USD 19.99 per month | Paid plan; verify current commercial-use terms. |
| Professional | 30,000 requests per month | USD 59.99 per month | Paid plan; verify current commercial-use terms. |
| Enterprise | 75,000 requests per month | USD 149.99 per month | Paid plan; verify current commercial-use terms. |
The vendor says overage fees apply after plan request limits and describes notifications at 75%, 90% and 100% of the monthly allowance. The cited plan figures are Screenshotlayer’s listed USD prices, not an India-specific quote or tax calculation. Its FAQ lists Visa, MasterCard, Discover and Diners Club, but does not establish whether Indian-issued cards are accepted, whether billing is available in INR, what taxes apply, or country-by-country availability. Confirm those details with the provider before relying on a plan.
For larger capture workloads, the FAQ says one dedicated worker processes one screenshot at a time and ten workers enable ten concurrent captures. This is the vendor’s explanation of its worker model, not an independent performance benchmark. The same FAQ claims around 99.9% uptime but says public uptime statistics are not offered; treat that as a vendor claim, not an independently verified service-level result.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If you would rather use a screenshot API with a single GET request, ScreenshotNeo is a website screenshot API and MCP server for developers. It removes cookie and consent banners, newsletter popups and chat widgets before capture; bot checks, blank pages, failed loads and cache hits are not billed. Its MCP server lets AI agents use screenshot tools, and the free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots.
Use the API key from your ScreenshotNeo account and see the ScreenshotNeo API documentation for options:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Frequently Asked Questions
Can Screenshotlayer create a website screenshot thumbnail at a custom width?
Yes. Screenshotlayer’s official FAQ says its width parameter can generate a thumbnail at a chosen pixel width.
Does Screenshotlayer provide a ready-made WordPress plugin?
The official documentation reviewed here does not establish a ready-made WordPress plugin. Treat it as an API to connect through your own script or publishing workflow.
Can I assume Screenshotlayer accepts an Indian-issued card or bills in rupees?
No. Its FAQ lists card brands but does not confirm Indian-issued card acceptance, INR billing, taxes or availability by country. Confirm these points with Screenshotlayer before subscribing.
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.
