Inline and attachments: survive gateway size caps and still read on Outlook desktop, web, and mobile mail
`email-preview-visio-jpg` targets change notices, review invites, and customer briefings. Gateways cap message size and re-encode inline images, so giant JPEGs rasterized from old .vsd files may be crushed before delivery. Split “inline teaser” vs “attachment pack” art—inline should show only the title and main path; prove readability by sending through real SMTP to Outlook, OWA, and iOS Mail, not only your local client.
Email workflow: confirm per-message limits and whether inline re-encoding is mandatory, export low-res inline plus high-res attachments, then SMTP smoke-test
- Ask mail admins about limits and EXIF stripping policies; export a narrow longest-edge inline JPEG with conservative quality—do not embed a 4K panorama that triggers destructive auto compression.
- Send to an external test mailbox, forward once, and toggle remote image blocking; log client versions—if one path always blurs, simplify composition for that lane instead of chasing infinite pixels.
- State attachment vs inline relationships plus checksums in the first paragraph—avoid “see figure” without version ids; for sensitive customers prefer signed links with watermarks over massive inline images.
VSD to JPG (email) FAQ: gateway compression, inline vs attachment budgets, Outlook quirks, EXIF compliance
Sender preview is sharp but recipients see mush—remote images off or multi-hop recompression?
Have them verify image download settings and low-data modes; compare MIME part sizes after the gateway; if forwards stack damage, switch to object links with checksums.
Marketing insists on a heavy signature banner—will it steal bitrate from the architecture JPEG?
Yes—signature and body share the MIME budget; slim signature assets or move technical art to attachments.
Dark-mode mail clients paint charcoal behind white JPEGs—fake gray frames?
Usually matte plus theme interplay; ship light-gray mats or set explicit HTML backgrounds; PNG may reduce the halo effect.
Compliance demands stripping location metadata—will JPEG EXIF leak drafting context?
Never assume defaults scrub metadata—run exiftool-style pipelines and spot-check; diagrams can still carry generator fingerprints.
Clients display friendly attachment names that hide versions—how to pin identity in prose?
Open with `topic_date_shortHash.jpg` matching the storage object key—do not rely on mail UI renaming for traceability.