You can use a PagePeeker screenshot as a WordPress featured image by generating and saving the image, then uploading it to the WordPress Media Library and selecting it in the post or page settings. For automated workflows, first make the screenshot a WordPress media attachment: the REST API’s featured_media field takes an attachment ID, not a remote PagePeeker URL.
Choose the right workflow
| Workflow | Best for | What it requires |
|---|---|---|
| WordPress editor | Occasional screenshots | Save the screenshot file, then upload or select it in the featured-image control. |
| REST API or code | Repeatable publishing automation | Make the screenshot available as a WordPress media attachment and assign its numeric ID to the post. |
PagePeeker’s documentation identifies API V2 as the recommended version; it says the original V1 is discontinued and redirects to V2. See its Website Thumbnails API documentation for its current capture and retrieval process.
As an Amazon Associate I earn from qualifying purchases.
Set a PagePeeker screenshot manually in WordPress
- Generate the screenshot. Use PagePeeker’s direct-linking method or its documented server-side workflow. The URL supplied to the API should be URL encoded. The server-side flow requests a refreshed thumbnail, checks the thumbnail-ready endpoint, then downloads the image.
- Save the image file. Obtain the generated screenshot on your computer. PagePeeker documents thumbnail retrieval, but the cited documentation does not establish a one-step transfer into WordPress.
- Open the post or page editor. In the settings sidebar, find the featured-image control and choose Set featured image.
- Upload or select the image. Upload the saved screenshot, or select it if it is already in the Media Library. Click Set featured image to apply it. WordPress describes this editor workflow in its Page/Post Settings sidebar guide.
- Preview the published page. Themes decide where and how featured images appear, including their crop and size, so verify the result in the theme rather than assuming it will display exactly like the original screenshot.
Assign the screenshot through the WordPress REST API
For REST-based publishing, featured_media is an integer media ID. It is not a URL to an image hosted by PagePeeker. WordPress’s Pages REST API reference defines the field, and the set_post_thumbnail() function and REST controller handler describe assignment using the thumbnail ID.
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 →- Generate and retrieve the screenshot using PagePeeker.
- Upload or otherwise make the image available to WordPress as a media attachment. The site’s authentication, upload endpoint, permissions, and any remote-image sideloading code depend on its setup; verify these separately.
- Record the resulting attachment ID.
- Create or update the post with
featured_mediaset to that ID.
For example, the relevant part of a REST request body is {"title":"Example","featured_media":123}, where 123 must be replaced with the actual WordPress media attachment ID. This illustrates the field’s shape, not a complete authenticated upload or post-creation script.
PagePeeker details to check
- The API documentation describes direct image linking and a server-side refresh, readiness-check, and download flow.
- Some response headers it lists, such as capture method, capture time, final redirected URL, capture hash, timestamp, and error status, are described for paid and unbranded accounts; do not assume every account receives them.
- The documentation identifies some options, including waiting for generation, as premium-account features. Check current account terms and endpoint behavior before relying on a specific option. The cited documentation does not establish current prices.
Or skip the browser setup
For a screenshot endpoint you can call directly, ScreenshotNeo returns an image or PDF from one GET request. Its API can generate the screenshot file; you still need to upload that file as a WordPress media attachment before assigning its ID as featured_media.
Quick Recap
cURL example, saving a WebP screenshot of a 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. Cookie banners, popups and chat widgets are removed before the shot; bot checks, blank pages and failed loads are never billed. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up for free.
Troubleshooting
- The featured image does not appear where expected: Themes determine placement and cropping. Preview the post using its active theme and check the theme’s featured-image behavior.
- A REST request rejects the image URL: Pass a WordPress attachment ID in
featured_media, not the PagePeeker URL. Ensure the image has been added to the site’s Media Library and use the returned attachment ID. - The screenshot is not ready when requested: PagePeeker’s server-side flow includes checking its thumbnail-ready endpoint before downloading. Follow the documented readiness sequence rather than assuming a refreshed capture is immediately available.
- An expected PagePeeker response header is absent: The documentation lists certain headers for paid and unbranded accounts, not necessarily all account tiers. Confirm the account terms that apply.
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.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →
