Rather than consume excess bandwidth by the recipients to get your huge
e-mails because you attached photos to them (which they may not want,
anyway, and just want to read the message), why not send them URLs
pointing to the photos? You won't hit message size limits by putting
URLs into your e-mails, you don't waste your bandwidth to upload huge
e-mails, and you don't offend your recipients having to download huge
e-mails from you with photo attachments they may not care about.
You could upload you photos to an online storage service. Some are
free, like Imgur (
imgur.com). Recipients don't need to login into an
account nor be assigned permissions to see your photos at Imgur;
however, anyone else with the URL to your photos can see them, too.
https://help.imgur.com/hc/en-us/articles/115000083326-What-files-can-I-upload-Is-there-a-size-limit-
You could upload your photos to your Google Photos account which gets
them automatically reduced in size, and send URLs to the photos in your
e-mails. You will need to share the photo folder under which you store
your photos. Go into your Google Photos account to decide if original
size or reduced size are used to store your photos.
https://support.google.com/photos/answer/6220791
With URLs in your e-mail pointing to where you uploaded your photos, not
only do your save your bandwidth and that of the recipient(s), but
sending the e-mails, bouncing them between SMTP servers, and retrieving
them will be a LOT faster.
Attaching binaries to e-mails will enlarge them by about 33%. That
means attaching a 15 MB photo to your e-mail will have it enlarged to
almost 20 MB, and many e-mail services have a quota on max message size
that 20 MB could exceed. The recipient's Inbox could already have
messages stored in it (lots of users use their Inbox as an archive
instead of moving pending/old messages into archival folders), so your
huge e-mail could exceed what is left of their storage quota, or exceed
the max size per message quota. Binary attachments are converted into
long encoded text strings (because EVERYTHING in e-mail is sent as text,
including HTML which is text with tags, and attachments that are encoded
into text strings). Those encoded text strings are stored in MIME parts
within the body of the message. Whether you use inline or attached
binary attachments, the same MIME parts get created (with disposition
attributes of inline or attached as a hint to the client where to
display the attachments). Not only are you creating a huge e-mail by
attaching photos, those photos are getting inflated by another third to
encode into text MIME parts.
Be polite to your recipients by giving them URLs to your photos instead
of sending them huge e-mails.
If you are determined to send huge e-mails to your recipients, convert
PNG to JPG. Also, with JPG, you can change compression with just about
any image editor. A JPG compressed to 72% will usually look just as
good to the human eye as a non-compressed JPG at 100% of its original
resolution. You can find many JPG editor apps at the Google Play Store,
but you'll want one that lets you choose a compression level on save.
Sorry, I upload my photos and put URLs to them in my e-mails, so I don't
putz with JPG editors on my Android smartphone.
You can find JPG editor app reviews online, like:
https://fossbytes.com/best-android-photo-editor-apps/
You'd have to check if the app page or author's web site mentions a JPG
compression either as an edit function or on save. The Snapseed app is
from Google, but I couldn't find mention of compression at their web
site (
https://support.google.com/snapseed). Many JPG compress apps are
found at:
https://play.google.com/store/search?q=jpg%20compress&c=apps
If you just want to compress a photo without any editing tools (that
might include compression), there are online reviews for those, too.
https://techviral.net/apps-to-reduce-image-size/