Websites & SEO
Check an HTML email for risky code before you send it
Upload the HTML file. It flags scripts, forms, missing alt text and a missing mobile viewport, and can give you a copy with scripts and event handlers removed.
or drop it here
- HTML
- Up to 1 documents
1 prepared source file · 92 bytes
- Bytes: 92
- Findings: 0
- Safe repair: true
email.html · change-hash.txt · manifest.json
One clear job, from source to download
- 1
Add the source
Supported formats and limits are visible before the upload.
- 2
Confirm the settings
Review the exact source, options, units and access before processing.
- 3
Inspect and download
Check the preview and warnings, then unlock the complete package.
Catch risky markup in an HTML email
What you upload
You upload one HTML email file per job. The check flags script tags, inline event handlers, forms, images without alt text and a missing mobile viewport. Mail clients often strip or block that markup. To check a whole campaign, run each template separately and keep one result per version. You get 3 free jobs a day without signing up.
What comes back
The download holds email.html, change-hash.txt and manifest.json. Every finding is listed in manifest.json with its location. If you asked for a repair, email.html is the cleaned copy. change-hash.txt records a fingerprint of the file before and after, so you can show which version you checked. Open the copy in your sending tool and compare it with your original, which is not changed.
Safe repair and real inboxes
Create safe repair writes a copy with scripts and inline event handlers removed. Layout tables, inline CSS and your text are left alone. Missing alt text is flagged but not filled in, since only you know the right words. The tool does not preview the email in Outlook, Gmail or any other client. How it looks in real inboxes still needs a separate rendering test.
Questions before you run it
Which markup does it flag as unsafe in an email?
Script tags, inline event handlers, form elements, images without alt text and a missing mobile viewport declaration. Each finding is recorded in the manifest with its location.
What does Create safe repair change in my HTML?
It writes a copy with scripts and inline event handlers removed, using an allowlist. Layout tables, inline CSS and your content are left alone, and change-hash.txt records the before and after hashes.
Will this tell me how the email renders in Outlook or Gmail?
No. Client rendering parity is not claimed and nothing is previewed in a real mail client. Use it to catch markup that clients strip or block, then run a rendering test separately.
Why does it complain about missing alt text?
Many clients block images by default, so alt text is often the only thing a subscriber sees in that block. Missing alt attributes are flagged per image rather than repaired, since only you know the right wording.
Can I check a whole campaign folder at once?
Not in one job: the tool takes a single HTML document per run. Send each template through separately and keep the manifests if you need a record per version.