Share via

Photos not uploading correctly / no preview available

Blood Vine 30 Reputation points
2026-03-03T23:15:30.4666667+00:00

I'm trying to understand what's going on because I'm currently unable to see any photos uploaded in the Microsoft Teams app. This issue started today. When I use the website version (https://teams.cloud.microsoft.com/v2/), I can see every photo that has been sent, including the ones from the person I'm talking to and the ones I've sent myself. However, in the app, none of the photos are visible. I would really appreciate clarification on why this is happening and what might be causing the difference between the app and the web version.

Web version: Screenshot 2026-03-03 6.02.18 PM

App version: MicrosoftTeams-image (1)

Microsoft Teams | Microsoft Teams Free | Files
{count} votes

3 answers

Sort by: Most helpful
  1. EmilyS_726 14,860 Reputation points Volunteer Moderator
    2026-03-04T03:58:59.32+00:00

    Hello

    This is an issue on Microsoft's end. Engineering is aware and is working on mitigation.

    2 people found this answer helpful.

  2. Ruwim.B 5,830 Reputation points Volunteer Moderator
    2026-03-04T13:07:37.8033333+00:00

    In my case, the images were missing both on the Web and desktop apps. Few minutes ago, the issue was fixed. First on the desktop app, and next on the Web app. No user action was required.

    0 comments No comments

  3. Q&A Assist
    2026-03-03T23:16:23.54+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    In the Teams desktop or mobile app, image and file previews are generated by the client. When the client cannot render a preview, it shows a generic broken-image icon, while the same content can still be viewed correctly in the web version.

    From the documented behavior for Teams file and picture attachments:

    • When attaching a file or picture in Teams, the app normally generates an inline preview for images, videos, and many document types.
    • A preview will not appear if:
      • The user does not have permission to the file, or
      • The file is encrypted with certain sensitivity labels, or
      • The chat is with external users, or
      • The file type is not supported for preview (for example, .zip files).

    In the web client, these same files can still be opened directly from the message, which is why they appear correctly there even when the native app cannot render the thumbnail.

    Given that:

    • The images are visible and open correctly in the web version.
    • The desktop/mobile app shows only a broken-image placeholder.

    The most likely causes are:

    1. A temporary issue or bug in the current Teams client build affecting image preview rendering.
    2. A permissions or sensitivity-label condition that prevents the native client from generating previews, even though the files themselves remain accessible.

    To work around and validate:

    1. Confirm that the images are standard supported formats (for example, JPEG or PNG) and not inside unsupported containers such as .zip files.
    2. Open the affected messages in the web client and verify that the files themselves open correctly from there.
    3. In the Teams app, try signing out and back in, or reinstalling/updating the client, to pick up any fixes to preview behavior.
    4. If the chat involves external users or files stored in locations with strict sensitivity labels, test by sending a simple JPEG from a standard Teams channel or chat within the same tenant to see if previews work there.

    If previews work in some chats but not others, the difference is likely due to file permissions or external-user conditions. If previews fail everywhere only in the app but always work on the web, it indicates a client-side issue that should be escalated to support with screenshots and client version details.


    References:

    0 comments No comments

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.