Share via

Outlook Addin Web Based Icons Not Showing Up on Desktop

Pope, Mike 0 Reputation points
2026-03-09T20:36:53.4233333+00:00

I'm doing developing for a web based outlook addin, using a manifest.xml file and the assets are deployed to an azure web service. When I visit the outlook addin from the browser, it shows up just fine, when trying to visit it on the Outlook Desktop app, the icons don't show up and it's blank

Has anyone experienced this? I've tried updating the panifest.xml file with query params, changing file names of icons, deleting 16.0 -> WEF file, nothing seems to work.

Outlook on web:
User's image

Outlook Desktop:

User's image

Outlook | Windows | Classic Outlook for Windows | For business

2 answers

Sort by: Most helpful
  1. Vy Nguyen 10,130 Reputation points Microsoft External Staff Moderator
    2026-03-09T21:53:36.21+00:00

    Hi @Pope Mike

    Thank you for reaching out to the Microsoft Q&A forum and for clearly outlining your concern. 

    Based on the details you shared that your web‑based Outlook add‑in displays correctly in Outlook on the web while the ribbon buttons in Classic Outlook for Windows appear with blank icons. I truly understand and appreciate your effort updating the manifest, renaming icon files, and clearing the Office cache to narrow this down. 

    In Classic Outlook for Windows, the ribbon loads command icons strictly from the icon resources declared in the manifest and it expects three PNG images at specific sizes that are served over HTTPS. When the desktop client cannot retrieve a valid image or encounters an unsupported format, it substitutes a generic placeholder or shows a blank tile even though the button is present. Additionally, Outlook caches icon assets, so updated images do not appear until the Office cache is cleared or the icon URLs change.  

    Below are some workable options that might be the most appropriate for your current situation:  

    1/ Validate the icon assets and hosting 

    • Confirm that the icons are PNG files sized exactly 16 by 16 pixels, 32 by 32 pixels, and 80 by 80 pixels, and that they are reachable over HTTPS. Avoid SVG because it is not a supported icon format for add‑in commands in Classic Outlook for Windows. 
    • Open each icon URL in a private browser session and verify it returns an HTTP 200 response with the expected image content, and does not redirect to another location or require authentication. 
    • Ensure the server does not include cache control response headers for these images because Office will replace your icon with a default image when such directives are present. If you recently changed an icon, use a new URL to force clients to download the new asset.  
    • References: 

    2/ Review the manifest references for add‑in commands 

    • In the Version Overrides section, verify that each button references the icon resource set and that the resource list includes the three required image sizes mentioned above. 
    • Make sure all resource and command entries use absolute HTTPS links and that your manifest conforms to the current add‑in manifest guidance for Outlook. Increment the manifest version before redeploying so that clients pick up the changes.  
    • Reference: Create add-in commands with the add-in only manifest - Office Add-ins | Microsoft Learn 

    3/ Refresh the desktop client cache to pull fresh assets 

    • Fully close Outlook, then clear the Office cache on Windows and restart Outlook to force a fresh download of the manifest and image resources. This step is recommended whenever you change icon file names or URLs.  
    • Reference: Clear the Office cache - Office Add-ins | Microsoft Learn 

    If the icons are still blank after these steps, I am ready to investigate further. Please share one example icon URL, the Outlook build number from About Outlook, and the icon resource entries from your manifest so I can analyze the behavior end‑to‑end. 

    I hope this response has helped address your question and clarify the behavior you're experiencing. Please feel free to reply if you have any further questions, I would be happy to assist further.   

    Thank you for your patience and your understanding. I look forward to continuing the conversation.   


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment”.     

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  


  2. Q&A Assist
    2026-03-09T20:37:19.0766667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    On classic Outlook for Windows, the most common causes for web add-in icons not appearing (blank button, missing icon) are a stale/corrupted cached manifest or an icon definition that doesn’t meet the desktop client’s requirements.

    Use the following checks and fixes:

    1. Verify Outlook has a valid cached manifest
      1. Close Outlook.
      2. Confirm the add-in is correctly installed and enabled for the mailbox in Exchange Admin Center.
      3. On the desktop where Outlook is running, check the cache folder:
              %LocalAppData%\Microsoft\Office\16.0\WEF
        
      4. Locate the subfolder for the add-in:
              <guid>\<base64 hash>\Manifests\<ManifestID>_<ManifestVersion>
        
        Ensure the manifest for the add-in is present.
      5. If the manifest was modified while Outlook was open, uninstall the add-in from Exchange Admin Center, reinstall it, then restart Outlook and test again.
    2. Clear Office cache when changing manifest or icons
      • When changing icon file names, URLs, or other manifest elements, clear the Office cache so Outlook picks up the latest manifest and assets. Follow the steps in “Clear the Office cache” referenced from the troubleshooting article, then restart Outlook and test.
    3. Validate manifest and icon definitions
      • Run the manifest through the validation guidance in “Validate an Office Add-in’s manifest” and use runtime logging if needed.
      • For the IconUrl (and HighResolutionIconUrl) elements:
        • Ensure the image format is one of: BMP, EXIF, GIF, JPG, PNG, or TIFF.
        • Ensure the resolution matches the add-in type. For a mail add-in, the icon must be 64x64 pixels.
        • The URL must be reachable from the desktop client (no auth prompts, correct HTTPS endpoint, no 404/403).
      • Remember that changing IconUrl at runtime is not supported; changes must be made in the manifest and then re-deployed/recached.
    4. Turn on UI error reporting in Outlook
      1. Remove/sideload the add-in again.
      2. In Outlook, go to File > Options > Advanced.
      3. In the Developers section, enable Show add-in user interface errors.
      4. Sideload or re-add the add-in and watch for any UI-related error messages that might explain why icons are not rendering.
    5. If seeing “This add-in is no longer available”
      • Ensure the manifest’s ID has not been changed in the deployed copy without first removing the old add-in.
      • Check that all resid values used in the manifest are defined in the <Resources> section, spelled exactly the same, and are 32 characters or fewer.
      • Clear the Office cache if the ID or resources were changed.

    If the add-in loads in Outlook on the web but desktop icons remain blank after these steps, focus on:

    • Confirming the icon URLs are accessible from the desktop environment (firewall/proxy/CDN issues).
    • Verifying the icon size and format exactly match the requirements for mail add-ins.
    • Ensuring Outlook is using the latest manifest by reinstalling the add-in and clearing the cache.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.