You can use a PagePeeker screenshot as a WordPress featured image by downloading the screenshot, adding it to the WordPress Media Library, and setting it in the post’s featured-image control. For automation, first make the screenshot a WordPress media attachment, then assign its attachment ID as featured_media. PagePeeker generates the screenshot; WordPress handles the featured-image assignment as a separate step.
Use a PagePeeker screenshot in the WordPress editor
This is the simplest route for an occasional post. PagePeeker documents direct image linking and a server-side API workflow, but the documented process does not establish an automatic transfer into WordPress. You will need the screenshot image file before selecting it in the editor.
- Generate the screenshot. Follow PagePeeker’s Website Thumbnails API documentation. URL-encode the target URL when passing it to the API.
- Save the image file. Obtain the generated screenshot using the method appropriate to your PagePeeker workflow. Its server-side flow describes requesting a refreshed thumbnail, polling the thumbnail-ready endpoint, and then downloading the image.
- Open the post or page in WordPress. In the editor, open the settings sidebar and find the featured-image control. WordPress’s Page/Post Settings sidebar guide describes this as Set featured image.
- Upload or select the screenshot. Choose an existing Media Library image, or upload the screenshot file. Select Set featured image to apply it.
- Preview the published page. Themes decide where and how a featured image appears, and may crop it differently. Check the result in the theme you use.
Automate the assignment with WordPress REST API
WordPress’s REST API does not use a remote image URL as the featured-image value. The page schema defines featured_media as an integer media ID. In practice, the screenshot must first be available in WordPress as a media attachment; use that attachment’s ID when creating or updating the page. See the Pages REST API reference.
The WordPress function set_post_thumbnail() also assigns a thumbnail using an ID, and the REST controller passes the requested featured-media ID to that function and can reject an invalid ID. See set_post_thumbnail() and WP_REST_Posts_Controller::handle_featured_media().
Implementation outline
- Generate and download the PagePeeker screenshot.
- Upload or sideload the image into WordPress using an implementation appropriate for your site, credentials, and permissions.
- Record the resulting media attachment ID.
- Create or update the page with that integer in
featured_media.
The cited WordPress references establish the attachment-ID model and assignment behavior, but do not specify a complete remote-image upload or sideload implementation, authentication setup, or the permissions for your site. Verify those parts against your WordPress setup before automating them.
Manual editor or automation?
| Route | Best fit | What it requires |
|---|---|---|
| WordPress editor | One-off or occasional screenshots | Generate and obtain the image, then upload or select it in the featured-image control. |
| REST API or code | Repeatable publishing workflows | Make the screenshot a WordPress media attachment and assign its ID as featured_media; upload, authentication, and permissions need site-specific implementation. |
PagePeeker details to check
- PagePeeker identifies API V2 as its currently recommended version and says the original V1 is discontinued and redirected to V2. Check its API documentation for current endpoint behavior.
- The documentation lists response headers for paid and unbranded accounts, including capture method, capture time, final redirected URL, capture hash, timestamp, and error status. Do not assume every account tier receives those headers.
- Some options, including waiting for generation, are described as premium-account features. The documentation cited here does not establish current prices, so confirm account terms directly before relying on a feature.
Troubleshoot common problems
- The screenshot does not appear in the Media Library. Generating or linking to a PagePeeker image is separate from adding an attachment in WordPress. Obtain the file and upload it, or implement a site-specific attachment workflow.
- The REST request does not set the featured image. Check that
featured_mediacontains the integer ID of an existing WordPress media attachment, not the PagePeeker URL. An invalid ID can be rejected by the REST controller. - The image looks cropped or appears in an unexpected location. Featured-image display depends on the active theme. Preview the page and check the theme’s image behavior.
- A PagePeeker option or response header is missing. Account tier can affect available options and headers. Check the current PagePeeker documentation and account terms rather than assuming the feature is available on every plan.
Or skip the browser setup
ScreenshotNeo offers a one-request screenshot API and an MCP server. Its clean-shot steps can accept cookie or consent banners and remove 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, and responses identify page verdict and billing status in headers. AI agents can use its MCP tools to take screenshots, get page information, and capture PDFs.
To save a screenshot locally, use cURL (replace the target URL as needed): curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp. See the ScreenshotNeo documentation for the API options and setup. You would still upload the resulting file to WordPress or make it a media attachment before assigning it as a featured image.
The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo to start with the free allowance.
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.
