Common image-related problems in signatures
You experience various problems with images in email signatures, e.g. embedded pictures are not displayed in received emails, are misplaced in the message thread, or disappear when replying/forwarding.
Embedded images are images that are inserted directly into the body of the message, as opposed to images that are attached as separate files or inserted as links. CodeTwo software allows you to embed images in email signatures, and in most cases such images are better than linked images (learn more). Occasionally, embedded images may not appear correctly. For example, if images are suddenly gone from a conversation thread, it usually means the email was either converted to a different format (e.g. from HTML to RTF) or processed in a way that removed or misplaced images. This article describes the most common problems with signature images and explains how to fix them. The problems are divided into several categories, and the most common problems are listed first.
- Images are not displayed or you get security warnings when opening emails with CodeTwo signatures
- Images are visible in the original message but disappear from replies or forwards
- Images are visible in original message but disappear or suffer quality loss with every reply
- Images embedded in email signatures created in Outlook are not visible to recipients
Problems related to email client restrictions
- Images are not displayed (and you need to download them) due to email client security restrictions or bandwidth usage protection
Problems related to undesired format conversion
- Default email format and its conversion in email clients
- Email format conversion/enforcement by Exchange Server
- Email format conversion by CodeTwo and other third-party software
- Images in signatures are not correctly displayed, e.g. disappear or lose quality, particularly in long conversation threads
Issues that occur on Apple devices, mobile devices and web-based mail clients
- Images are replaced with text filenames on Mac and iOS devices (Apple Mail)
- Images disappear because an email is converted to plain text by an Apple device
- Images in signatures are not displayed
- Images show up as attachments in Outlook for Mac
- The Tap to download button appears instead of an image on iOS devices
- Images show up as attachments on iOS devices
- Images in email signatures load very slowly in Outlook on mobile devices
- Image formatting or size changes when you use Microsoft Outlook for Android
- Embedded images disappear when using web-based email clients
Problems related to the image itself
- Outlook is not embedding images
- A signature that contains an image only is not displayed by an email client
Problem: Images are not displayed or you get security warnings when opening emails with CodeTwo signatures.
Solution: Did you insert the image from a web location into your signature? Storing pictures online is a good way of reducing email size, but it comes with several disadvantages. If your recipients have limited Internet access or no Internet connection at all, their email clients will not be able to download images from the external web locations. Furthermore, many email clients (including webmails) come with security features that prevent against automatic downloading of external content linked in emails. If your signature contains images stored in a web location, email recipients may see security warnings. Similar behavior occurs if your email includes embedded images which are also hyperlinked.
In many cases, embedding images into email signatures can be a better solution. Learn why
Problem: Images are visible in the original message but disappear from replies or forwards.
Solution: This issue is most probably caused by email client settings. An email client may be configured to always reply using a specific message format, regardless of the original format. If such format conversion occurs, it can cause problems with disappearing images, images visible as attachments, CID placeholders or picture names showing up in the message body instead of images. Similar conversion may happen on the intermediary mail servers as well. To mitigate this problem, you can tell your users about it and ask them to change their mail client settings, if possible. If you're working in an Exchange environment, you can force the HTML email format in Exchange. Some other workarounds may be available, for example some iOS versions remove images when replying but keep images when forwarding emails, so forwarding instead of replying may be an option to keep images in place.
Problem: Images are visible in the original message but disappear or suffer quality loss with every reply.
Solution: This problem might be related to unwanted email conversion by email clients, especially in long conversation threads. Go to this section for details.
Problem: Images embedded in email signatures created in Outlook are not visible to recipients.
Solution: If you experience problems with native Outlook signatures, see this section.
Images are not displayed (and you need to download them) due to email client security restrictions or bandwidth usage protection
Information gathered while opening remote resources (such as websites) may be used by their owners to identify visitors. To prevent against this, most email clients do not automatically download images from external servers. If an email contains a linked image, your email client might show a red x in a box () icon (Fig. 1.) or an empty picture frame instead, or show no linked content at all.
To solve this issue, you can enable downloading remote content from the Internet. You may find such an option directly in the opened message or in the options of your email client. However, if you have enabled this option and still experience the problem, please review your network configuration, especially bandwidth usage protection and also configuration of your security solutions, including antivirus software and SPAM filters.
Note that owners of the remote servers with images are only able to obtain your IP address and information on the mail client you used to download the images. There is no option to gather any credentials used for authentication on the mail servers.
Every mail client can use a different default message composing format. Depending on the platform, you can send your message in HTML, RTF or Plain Text. Usually, when you add any formatting or images to a message, your mail client automatically switches to the HTML or RTF format. Of course, most email clients (including Microsoft Outlook, Thunderbird, and Apple Mail) have an option to manually choose which format should be used.
If you use Apple devices, the default email format conversion might cause images in your signatures to disappear. Check this section to learn more.
Currently, we only support HTML signatures with images. Some devices (like iPhones and iPads) are, by default, sending messages in Plain Text, therefore you might need to convert them into the HTML format. You can find more information about this conversion in the sections below.
Keep in mind that the OWA app for iOS and Android supports only signatures in Plain Text.
The default settings in Microsoft Exchange Server allow mail clients to send messages in both the HTML and Plain Text formats. Still, emails might be delivered in a different format than original because, for example, third-party MS Exchange Transport agents or antivirus software is set to convert them. MS Exchange Server settings in your environment might also force email format conversion to Plain Text - in such a case, CodeTwo software will add the Plain Text version of a signature, with no images (other images included in a message will also disappear). See this Knowledge Base article to learn how to check and modify your default Exchange Server settings to avoid unwanted conversion from HTML to Plain Text.
If you need to force email format conversion to HTML, you can use CodeTwo software. See this section to learn more.
What is more, Exchange Server and email clients are using specific Content-Transfer-Encoding setting to process the messages. Some of the clients may encounter issues when downloading images and merging them directly with a message. For example, in Thunderbird you may experience a situation when images are located on the list of attachments, instead of within the body of an email. If you have similar problems, we advise you to look for another email application.
Only the HTML format is supported by CodeTwo software when it comes to stamping emails with signatures containing images. That is why sometimes you might need to convert the message body to HTML. Fortunately, some of the CodeTwo products can automatically do that:
- If you use CodeTwo Exchange Rules Pro, you can convert your emails to HTML by using the functionality called Force email format. At this point we are not aware of any possibility to properly convert messages to HTML directly on Microsoft Exchange Server (you can find more information about the Exchange-side behavior earlier in this article).
- If you use CodeTwo Email Signatures for Office 365, you can force conversion of plain text emails to HTML on the Design tab of the Manage Signatures App. Learn more
Some third-party applications may cause unwanted conversion to the Plain Text format. We strongly recommend to verify your current third-party Exchange tools, add-ins for mail clients and configuration of your security solutions (including SPAM filters and antivirus software).
Images in signatures are not correctly displayed, e.g. disappear or lose quality, particularly in long conversation threads
In a particularly long message thread, it may happen that images embedded in signatures are not displayed correctly in earlier messages in this thread (an image appears correctly only in the latest signature, as shown in Fig. 2.). These images can be completely removed, modified, or their quality significantly reduced.
This problem is often caused by unwanted email conversion, and is very likely to occur in particularly long conversation threads, where a message passes through multiple servers and is viewed on many email clients. In such cases, embedded images can be completely removed, compressed, modified, or their quality significantly reduced. Also, every time the user clicks the Reply or Forward button, their email client modifies the entire message thread – it adds a reply header, prepares a place for the reply text, etc. Since there are many email clients on the market (including smartphones and other mobile devices), each with its own rules for processing long message threads and embedded images, there is no universal solution to this issue.
When you compose a reply message using Apple's Mail, it removes inline attachments (such as embedded images) and replaces them with text filenames surrounded by angle brackets, e.g. <logo.jpg>, <doc.pdf>, <image001.jpg>. This is done to minimize the size of the email you are sending. This behavior also affects pictures embedded in email signatures as these pictures are, in fact, inline images.
- If you use a Mac, you can disable this behavior by opening the Mail app, choosing Edit > Attachments from the menu and enabling (checking) Include Original Attachments in Reply, as shown in Fig. 3. From now on, your Mac will no longer attempt to delete any attachments or images when you reply to a message. Note that this option keeps all attachments in an email conversation, and might significantly increase the size of emails, especially in longer message threads.
- If you use an iOS device (iPhone or iPad) with the latest version of iOS 12, you cannot disable this behavior. Instead, you can install Outlook for iOS or any other app that does not have this behavior implemented. Another solution is to use a dedicated action: Restore images removed by iPhone and iPad, which is available in CodeTwo Exchange Rules and CodeTwo Exchange Rules Pro.
The image removing behavior can be disabled in iOS 13 and iPadOS 13. However, both of these mobile operating systems are currently in the beta stage and will be available to public this fall. In the beta version of iOS 13 / iPadOS 13, the option that stops removing attachments (including images embedded in email signatures) is found under General > Mail > Include Attachments with Replies (Fig. 4.). Be aware that since this option keeps all attachments in an email conversation, it might significantly increase the size of emails, especially in longer message threads.
Emails sent from Apple devices such as iPhone, iPad and Mac are sometimes converted into the plain text format by the default Mail application. For example, if you compose a new message or reply to / forward an existing one and your message does not contain any text formatting, it is sent in plain text regardless of the email client settings and the original message format. Images can only appear in HTML signatures, that is why they disappear from plain text emails. See this Knowledge Base article to find out how to fix this problem.
Some Apple email clients are not able to display images that are inserted as the only element inside an HTML tag. See this section to learn more about this problem.
In Outlook for Mac, the embedded images might show up as attachments in the final message. In fact, Outlook clients designed to work on the Windows platform are changing the filenames of embedded images on each reply and forward. However, this behavior does not apply to Outlook clients on Macs. Consequently, when CodeTwo software adds an image with the same filename as already existing within a message, Outlook for Mac displays a list of all embedded images in the attachments field. Such a situation might take place e.g. when a signature including an image is added multiple times into the same message.
We have also found another problem that occurs in iOS 7 and later. Sometimes, the default mail application displays certain embedded images incorrectly - they are not downloaded to emails, but instead you see the Tap to download button. When you click it, nothing happens. The problem appears only for messages that were replied to or forwarded via the default mail app (Mail). If you are facing such an issue, you can solve it by force closing the app on your device and reopening it.
If you use an iPhone or iPad to reply to or forward an email, images embedded in a signature are sometimes removed from the email body and moved to attachments.
This issue is caused by the email client on your device, and is not related to CodeTwo. Some clients, usually the ones on mobile devices, recognize the path to embedded images in the message body and remove these images, putting them in attachments instead. This behavior helps portable devices reduce mobile data usage (the recipient can choose to download images or not).
You use Microsoft Outlook for iOS/Android. When you open an email on your mobile device, and this email contains a signature with embedded graphics, the embedded images load very slowly.
This problem relates to the mobile Outlook applications only and is not related to CodeTwo software. To fix it, try doing the following:
- force close the app and open it again
- reset the account cache in your mobile Outlook app. See guidelines below
- or reinstall the Outlook app on your device.
If none of these solutions works for you, try contacting Microsoft Support and asking them to troubleshoot your issue.
To reset the account cache (remove cached files) on your mobile Outlook app, you need to:
- Open Microsoft Outlook on your iOS or Android device.
- Go to Settings and tap the account that causes problems with image loading.
- Tap the Reset Account button and wait for the process to finish.
You use Outlook for Android to manage mail on your mobile device. When you reply to or forward an email that contains a signature with embedded images, this email falls apart and images are misplaced, resized, etc. Such an issue occurs if you use the Load Full Message option when responding to messages. See this article to learn more.
Some of the web-based mail applications do not correctly process messages while replying or forwarding. The email source code can be modified, therefore the address (i.e. content identifier / CID) of an image embedded into an email may be incorrectly defined. As a result, images are not visible.
To solve this issue, please first try using a desktop mail client instead of a web application. If you are unable to obtain or run such software, please try changing the format of the images, as described here, and check if the problem persists.
When embedding images to emails and signatures, it's best to use the most common image formats such as PNG or JPG (JPEG), as they are supported by the majority of mail clients. If your embedded pictures are not displaying correctly, check their file format and, if necessary, try converting them to one of the mentioned formats.
Incorrect file names might also prevent graphics from being displayed in emails. We recommend that you only use letters and numbers. Do not use special characters or hashtags (e.g. #myphoto).
Another problem may occur if you give generic names to your picture files. By default, Outlook changes the names of images embedded in emails into image001@someID, image002@someID, and so on. If you use a simple image name such as image001.png, and the name of your image matches the name generated by Outlook, the images might be swapped and displayed incorrectly (Fig. 5.). This problem has been addressed in all current versions of CodeTwo Exchange Rules and Exchange Rules Pro - these programs add a unique ID to every image inserted (embedded) into a signature. If you use this software to add email signatures, make sure you that you have the latest version installed.
In some environments, especially those with a higher DPI setting, you may experience problems related to the scaling of images in emails. This issue can be solved by forcing fixed dimensions of the image file. Read this article to learn how to keep the right size of images in your signatures regardless of the mail client/platform.
In Outlook 2013 and later, embedding images into emails (including email signatures created in Outlook) is sometimes not possible. Outlook does not add them to a message, but inserts references to the image files on the local disk of the email sender. As references to local files only work on the sender's machine, emails and email signatures are displayed without graphics on the recipients' mail clients.
This behavior occurs by default in certain Outlook versions. Read this Knowledge Base article to learn how to solve this issue.
If your signature template inserts an image only, and this image is placed inside an HTML tag such as <p>, <td> or <div>, then some email clients (such as Apple Mail) may not display this image. If you experience this problem, you can work it around by adding any text next to the image (inside the same HTML tag). You can hide this text so that it's not visible. For example, if your image is inserted in the <td> tag:
Then you can add a period (full stop) punctuation mark directly after the image, and change the punctuation mark's color to white so that it's not visible in your email signature. To do so, the above HTML code can be changed in the following way:
<TD><IMG src="your-image.jpg"><SPAN style="color: #fff;">.</SPAN></TD>