Request for official Spotlight description for Windows Spotlight Image of Thean Hou Temple

Question

Request for official Spotlight description for Windows Spotlight Image of Thean Hou Temple

Kevin Sun 0

Hi Microsoft Community,

I am looking to locate the official Windows Spotlight background description text and landing link associated with a specific Windows Spotlight wallpaper asset

Here are the exact file properties and metadata details for the asset in question (derived from https://windows10spotlight.com/images/40752):

Image Title: Chinese lanterns in Thean Hou Temple during New Year of water Rabbit, Kuala Lumpur, Malaysia

Resolution: 1920 × 1080 (q:90)

File Size: 558,292 bytes (~545 KB)

SHA-1 Hash: b06a74027134fea29430ae7123293d3659c4a0d4

SHA-256 Hash: 35d580f33f3226d730cfecf4e1e87ed7640cfec9bb6ce224bf81189dded2547e

SHA-256 (Base64): NdWA8z8yJtcwz+z04eh+12QM/sm7bOIkv4EYnd7SVH4=

Since lock screen images are served dynamically without storing text descriptions inside the raw .jpg file assets, I would like to check if there is an active Bing Spotlight web endpoint ([bing.com/spotlight](https://bing.com/spotlight)) or an archived JSON payload snippet available for this specific asset ID that includes the official caption text originally paired with the image.

Any guidance or direct link to the associated Spotlight metadata feed for this hash would be greatly appreciated!

Thank you.

Kevin

0 comments

1 answer

Your answer

Answer 1

Microsoft does not document a public Windows Spotlight archive or hash-based API that can retrieve the historical caption and Bing landing URL for this specific JPEG.

The official Windows documentation identifies client-facing services that retrieve Spotlight metadata—such as references to image locations, tips, and notifications—but it does not publish request formats, asset identifiers, retention rules, or a supported historical lookup interface. For Windows 11 Pro, the documented metadata endpoints include api.msn.com and arc.msn.com; additional Windows 11 endpoints include ris.api.iris.microsoft.com and fd.api.iris.microsoft.com.^1^^2^

What can be established for this image

The public third-party catalog entry associates the image with this caption:

Chinese lanterns in Thean Hou Temple during New Year of water Rabbit, Kuala Lumpur, Malaysia

However, that entry does not contain either of the supplied SHA-1 or SHA-256 values. It instead lists two different hash-like identifiers, so it supports an image/title match but does not provide first-party confirmation that the text is the exact caption delivered with your binary asset.^3^

Consequently:

Probable caption: the text above.
Official archived JSON payload: none is identified in Microsoft’s public documentation.
Permanent Bing landing URL for this hash: not recoverable from the documented endpoints alone.
bing.com/spotlight: not documented as a public historical lookup service for an asset hash.

Supported way to obtain the landing page

If Windows serves the image again, use its live Spotlight UI:

Enable Windows spotlight under Settings > Personalization > Background.
Right-click the Spotlight desktop icon to open its flyout.
Double-click the icon or select Learn more to open the image’s Bing landing page.^4^

The landing URL and displayed text should be saved while that image is active. Spotlight is a connected experience that delivers changing images and dynamic text, rather than a static metadata catalog embedded in each JPEG.^5^

Capturing traffic to the documented service endpoints may reveal a payload currently delivered to your own device, but it would not provide a supported query for an older SHA-1/SHA-256 value. The image hash also may not be the service’s metadata key because resizing, recompression, or regional variants produce different file hashes.

For authoritative confirmation of the historical wording or destination URL, the remaining route is Microsoft support or Feedback Hub (Windows+F), supplying the hashes, dimensions, approximate display date, locale, and the third-party catalog ID. Microsoft’s public documentation does not expose the archive needed to independently complete that lookup.

References