HD Photo MIME Type

What does image/vnd.ms-photo mean?

image/vnd.ms-photo is the registered media type for Microsoft's HD Photo, previously called Windows Media Photo. The associated .wdp file is a tag-based still-image container and a pre-standard predecessor of JPEG XR. Microsoft documents two four-byte signatures: 49 49 BC 00 for the pre-release version and 49 49 BC 01 for version 1.0.¹

That history makes the name confusing. An HD Photo file and a standardized JPEG XR file belong to the same technical family, but they are not guaranteed to contain the same bitstream. Microsoft says its current Windows Imaging Component codec can decode both. Since Windows 8, that codec's encoder has produced JPEG XR-compatible data, and Microsoft recommends JPEG XR rather than the older HD Photo format.²

Why was HD Photo created?

Microsoft formally announced HD Photo in March 2007 as a format for consumer and professional photography. It had already shipped in Windows Vista and was developed from technology incubated in Microsoft Research.⁴⁵ The design aimed to cover workflows that ordinary JPEG handled poorly, including high dynamic range, high bit depth, lossless compression, alpha, and selective decoding of a resolution or image region.

Later in 2007, Microsoft submitted the technology to the Joint Photographic Experts Group for standardization under the tentative name JPEG XR.⁵ The core JPEG XR coding specification became ITU-T Recommendation T.832 in March 2009, paired with ISO/IEC 29199-2.⁶ The current ISO edition continues to describe JPEG XR as a coding format intended primarily for continuous-tone photographic content.⁷

JPEG XR kept the broad capabilities of the design. The JPEG committee lists lossy and lossless coding, tile-based random access, alpha, progressive resolution and quality refinement, and integer, fixed-point, and floating-point sample formats. It supports monochrome, RGB, CMYK, and arbitrary multi-channel images.⁸

Is a .wdp file the same as a .jxr file?

Not exactly. The extensions often reach the same Windows codec, but they signal different stages of the format's history.

Microsoft explicitly notes that there are differences between HD Photo and JPEG XR. A modern WIC decoder accepts both, while the modern encoder emits JPEG XR-compatible data.² Software outside Windows may be stricter, so inspect or decode the file instead of relying only on its extension.

How to open an image/vnd.ms-photo file

Windows includes a native JPEG XR codec through Windows Imaging Component. Applications built on WIC can therefore read and write the family without implementing the codec themselves.⁹ Older Microsoft documentation also describes a Photoshop plug-in for CS2 and CS3, but that plug-in should be treated as a historical option rather than a current installation recommendation.⁴

Web support is much narrower. Internet Explorer 9 through 11 and the original EdgeHTML-based Edge 12 through 18 displayed JPEG XR. Current Chrome, Chromium Edge, Firefox, Opera, and Safari do not.¹⁰

Support in Poly

Poly has a MIME enum for image/vnd.ms-photo, categorizes it as an image, and maps .jxr filenames to that type. It does not infer the registered .wdp extension from a filename. Supplying the media type explicitly preserves the classification, but it does not add decoding support.

Poly's general image loader sends this type to the Rust image reader. That reader has no JPEG XR or HD Photo decoder in the configured pipeline. As a result:

• The file can be stored, synced, shared, versioned, and searched by name.
• Pixel dimensions, EXIF-style metadata, and visual embeddings are not produced.
• WebP thumbnails are not generated, so the in-app image viewer has no rendered preview.
• The Poly agent does not receive a decoded view of the image contents.

This is a narrower result than the generic “image” classification might suggest. Recognition means Poly knows the file category. It does not mean the codec is available.

Converting HD Photo safely

Choose the target format around the information you must preserve:

• PNG is a broadly compatible lossless choice for ordinary 8-bit images and transparency.
• TIFF is a better interchange choice when a desktop workflow needs high bit depth or richer metadata.
• JPEG works for small photographic delivery files when lossy compression and no alpha channel are acceptable.
• WebP or AVIF is practical for modern web delivery, but verify color and HDR handling in the encoder and target browsers.

HD Photo and JPEG XR can carry more than a typical 8-bit RGB display can show. A careless conversion may clip HDR values, flatten wide-gamut color, discard alpha, reduce bit depth, or strip metadata. Convert with a decoder that understands the source pixel format, choose an explicit color space, and compare the output before deleting the source.

Why image/vnd.ms-photo is uncommon on the web

The format combined ambitious photographic features with a Windows-centered deployment path. Standardization produced JPEG XR, but modern browsers adopted other image formats instead. A site that sends image/vnd.ms-photo should therefore offer a PNG, JPEG, WebP, or AVIF alternative rather than expecting current browsers to decode it.

For an archive, retain the original .wdp alongside a documented, widely readable derivative. That preserves the source's potentially higher precision while giving future users a dependable preview.