Unable see screenshot in webmail but when forward or reply that mail I can able to see screenshot

In Outlook and Outlook on the web, images and screenshots in emails can be blocked or handled differently depending on how they are embedded and on security settings.

Key behaviors from the product behavior and documentation:

1. When replying or forwarding, attachments and some inline content can behave differently
   • When forwarding a message, any attachments included with the original message are kept in the forwarded message.
   • When replying, attachments are not included automatically and must be reattached manually.
   • However, the reply/forward editor may re-render or re-download linked content differently from the original reading view, so an image that is blocked or not rendered in the original view can appear once the message is in compose mode.
2. External/linked images can be blocked
   • Outlook and Outlook-related clients can block external (web-linked) images for security and privacy reasons. In some configurations, these images are not downloaded until explicitly allowed.
   • In some server-side configurations (for example, Exchange/OWA web beacon filtering), there are known issues where web beacon/HTML form content is treated differently when forwarding or replying than when simply viewing the message. A cumulative update was required in Exchange Server 2013 to ensure consistent behavior.
3. HTTPS-linked images can fail to display
   • In some Outlook configurations, HTTPS-linked images can show a red X or fail to display due to security settings such as “Do not save encrypted pages to disk.” When the message is opened or edited in another context (such as reply/forward), the client may attempt to re-fetch or handle the content differently, which can make the image appear.

Given the described behavior (image not visible in the original webmail view but visible when replying/forwarding), the most likely causes are:

• External/linked images being blocked in the original view but allowed or re-fetched in compose mode.
• Server-side or client-side filtering or security settings affecting how web-linked content is rendered in read vs. compose views.

Recommended checks and actions based on the documented behavior:

1. Verify whether the image is an external/linked image rather than an attached file.
2. Check any settings related to blocking external images or web beacons in the webmail/Outlook environment and adjust if appropriate.
3. If using an on-premises Exchange/OWA environment, ensure that the latest cumulative updates are installed, especially if web beacon filtering is configured.
4. If using a desktop Outlook client in combination with webmail, verify that security settings like “Do not save encrypted pages to disk” are not preventing HTTPS-linked images from being cached and displayed.

If the issue persists, capturing whether the image is a linked (web) image or an actual attachment, and whether any “images blocked” or similar banner appears, will help administrators align the configuration with the documented behaviors.

References:

• Reply to or forward an email message
• Why don’t I see images when replying to or forwarding a message?
• Outlook Web App still downloads web beacon contents when you forward email messages in Exchange Server 2013
• HTTPS linked images in HTML emails display the red X
• Inline images and text attachments are not visible in OWA
• Why am I seeing "Some images were blocked" when I open certain emails?