Share via

Question about WebP codecs

Anonymous
2025-04-29T22:36:41+00:00

Hi!

I wanted to restore the use of the original Microsoft application: **Windows Photo Viewer** for pictures.

I was able to successfully restore the program, but I noticed a problem with *.webp files.

The problem occurs only in the Windows Photo Viewer application – *.webp files open correctly in MSPaint.

Do any of you have an idea how to solve this?

Example problematic .webp picture:

Windows for home | Windows 11 | Display and graphics

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2025-05-01T14:58:28+00:00

    Hi SirKocur,

    Thank you for posting here in Community.

    Unfortunately, Windows doesn’t natively allow configuring different applications to use separate codec versions for the same file format. Applications typically rely on the system-wide codec registered with the Windows Imaging Component (WIC), which creates these conflicts.

    That said, there are a few workarounds you could consider:

    Use Codec-Specific Wrapper Applications

    • Create a batch file or a script that temporarily changes the system’s default WebP codec before launching a specific application. For example:
      • For Paint, keep the Microsoft Store WebP extension as the default.
      • For Photo Viewer, temporarily switch to the legacy Google codec.
      • You can toggle these using Windows commands to manage the codec registry entries. It’s a bit technical and requires care to avoid registry errors.

    Install an Alternative Lightweight Viewer

    Instead of relying on Windows Photo Viewer, consider using third-party lightweight applications designed for full WebP compatibility (like IrfanView or XnView). These tools come with their own codec implementations and won’t interfere with Paint or other apps.

    Request Codec Updates or Features

    Reach out to Microsoft or community forums to raise this codec compatibility issue as feedback. Updates to the WebP Image Extension or Photo Viewer might resolve these problems in future releases.

    While this approach requires trade-offs, I hope it gives you a starting point. Home | Microsoft Community Hub

    Best regards,

    Bo

    Microsoft Community

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-04-30T21:16:28+00:00

    Hi again,

    Thank you for the reply. Unfortunately, none of the general suggestions solve the issue.

    I have both Microsoft Paint and the restored Windows Photo Viewer on my system. After installing the WebP Image Extension from the Microsoft Store, .webp files open fine in Paint, but in Windows Photo Viewer they are displayed with incorrect contrast and colors (very dark). This seems to be a codec compatibility problem.

    On the other hand, if I install the legacy "WebP Codec for Windows" v0.19 from Google, then .webp files display correctly in Windows Photo Viewer — but Paint no longer opens them at all.

    This suggests that different applications use different versions of the Windows Imaging Component (WIC) or codecs, and they are conflicting.

    My question:

    Is there any way to configure Windows so that different applications can use different WebP codec versions?

    For example:

    • Keep using the new WebP Image Extension for Paint and modern apps
    • Force Windows Photo Viewer to use the older codec (Google’s WebP WIC)

    I believe this could be possible by manipulating WIC codec priority or registration, but I need official guidance before experimenting further.

    Thank you in advance!

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-04-30T14:07:38+00:00

    Hi

    Thank you for posting here in Community.

    Hi there! Restoring Windows Photo Viewer is a great choice for its simplicity and familiarity, but I understand how frustrating it must be to run into issues with *.webp files. I’m here to help you resolve this seamlessly—let's get it sorted out.

    WebP is a modern image format designed for efficiency, and older applications like Windows Photo Viewer may not natively support it. Here's a step-by-step guide to tackle the issue:

    Troubleshooting Steps for Viewing *.webp Files in Windows Photo Viewer:

    1. Confirm WebP Codec Installation:

    To enable support for WebP files, you need the appropriate codec. The codec essentially bridges the gap between the file format and the application. You can check online for trusted sources to download and install the WebP codec for Windows.

    Ensure you're downloading the codec from a reputable source to avoid security risks.

    1. Update Windows Photo Viewer:

    Although you’ve restored the application, confirm if it's fully updated. Outdated versions may lack compatibility improvements.

    Updating Windows itself can also improve format support across applications.

    1. Use Third-party Plugins or Tools:

    If installing the WebP codec doesn’t work, you could explore lightweight third-party tools that enhance compatibility with WebP files, enabling viewing in older programs like Windows Photo Viewer.

    1. Alternative Solution - Convert WebP Files:

    As a workaround, you can convert *.webp files to formats such as *.jpg or *.png that are fully supported by Windows Photo Viewer. Tools like Microsoft Paint, IrfanView, or online converters make this process simple.

    1. Use a Dedicated WebP Viewer (If Needed):

    If compatibility remains problematic, you might consider applications dedicated to WebP files, such as the built-in Photos app in Windows, which natively supports WebP formats.

    By following these steps, you’ll either restore full functionality to Windows Photo Viewer or find an alternative solution that works for your needs. Let me know how it goes, or if you'd like more guidance—I'm here for you!

    Best regards,

    Bo

    Microsoft Community

    1 person found this answer helpful.
    0 comments No comments