# Emailing an HTML Report — Why It Breaks, and What to Send Instead Canonical: https://commareports.com/email-html-report Published: 2026-08-25 > HTML attachments get quarantined, pasted report markup gets mangled by Outlook, and 30 MB never arrives. Send a link that renders faithfully and collects comments instead. # Emailing an HTML report The report is done, and the obvious move is to attach it. Three things tend to go wrong, in this order. ## 1. The attachment doesn't arrive HTML attachments are one of the standard shapes of a phishing payload — a local page that renders a convincing sign-in form. Corporate mail filtering treats them accordingly: stripped, quarantined, or delivered behind a warning banner that trains the recipient not to click. You find out about this hours later, from someone who assumed you never sent it. ## 2. It arrives, and it doesn't open The rest of the failure modes from [opening a local HTML file](/open-html-file-online) all apply: the `report_files/` folder didn't come with it, `fetch` is blocked on the `file://` origin, and on a phone the mail client won't hand the file to a browser at all. ## 3. So you paste the report into the body instead This is worse in a more interesting way. Email clients are a decade or more behind browsers: - **Outlook on Windows** renders with the Word HTML engine. Flexbox and grid don't exist there; the layout collapses into stacked blocks. - **`