How to Preview HTML Email Templates with a Live Link

HTMLDrop6 min read1,132 words
HTML email template preview in a browser

Email HTML is weird. It uses table layouts, inline styles, and client-specific hacks that do not preview well in a code editor. Designers export from Figma or Beefree; developers generate templates with AI; marketers copy from Mailchimp — and then everyone emails .html files back and forth.

There is a better way: publish the template to a live link and let reviewers open it in a real browser.

Try it yourself — paste HTML and get a link in seconds

Open the editor →

Why email HTML is hard to review

Standard web pages and email HTML follow different rules:

  • Tables for layout<table>, <tr>, <td> instead of flexbox
  • Inline CSS — many email clients strip <style> blocks
  • Fixed widths — often 600px for desktop; mobile uses media queries
  • No JavaScript — interactivity is limited to links

Opening template.html from your Downloads folder does not match how Gmail or Outlook render it — but a browser preview is still the fastest way to catch layout breaks before you send a test campaign.

What you need

  1. Complete HTML email source (from AI, ESP export, or hand-coded)
  2. HTMLDrop editor open in your browser
  3. Reviewers who can click a link

That is it. No SMTP server. No test send. For final client rendering, you still test in Litmus or a real inbox — but live link preview catches 80% of issues earlier.

Step 1: Get clean email HTML

If you are using ChatGPT or Claude, use a prompt like:

“Write a transactional email HTML template using table layout and inline CSS. 600px width. Include header, body, CTA button, and footer. Single self-contained file.”

If you export from Mailchimp, Klaviyo, or Beefree, export HTML (not ZIP with assets unless you merge them). External images should use absolute URLs (https://...).

<!DOCTYPE html>
<html>
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Order Confirmation</title>
  </head>
  <body style="margin:0;padding:0;background:#f4f4f5;">
    <table role="presentation" width="100%" cellpadding="0" cellspacing="0">
      <tr>
        <td align="center" style="padding:24px;">
          <table role="presentation" width="600" cellpadding="0" cellspacing="0"
                 style="background:#ffffff;border-radius:8px;">
            <tr>
              <td style="padding:32px;font-family:Arial,sans-serif;">
                <h1 style="margin:0 0 16px;">Your order is confirmed</h1>
                <p style="margin:0 0 24px;color:#52525b;">Thanks for your purchase.</p>
                <a href="#" style="display:inline-block;background:#059669;color:#fff;
                   padding:12px 24px;text-decoration:none;border-radius:6px;">
                  View order
                </a>
              </td>
            </tr>
          </table>
        </td>
      </tr>
    </table>
  </body>
</html>

Add role="presentation" on layout tables for accessibility. Many AI tools skip this — worth a quick manual check.

Step 2: Paste and preview in HTMLDrop

Open HTMLDrop. Paste the full HTML. The preview pane renders the email centered in the browser — similar to how a webmail client displays HTML content.

Check for:

  • Broken images — relative paths will not load; use full URLs
  • Button alignment — CTA should be tappable on mobile (min 44px touch target)
  • Font fallbacks — Arial, Helvetica, sans-serif stack is safest
  • Dark mode surprises — some clients invert colors; test if your brand cares
Email template rendered in HTMLDrop browser preview
Browser preview catches layout issues before you send test emails.

Step 3: Publish and share with stakeholders

Publish the template. Share the link with:

  • Designers — pixel-check against Figma
  • Copywriters — proofread live text in context
  • Clients — approve without installing anything
  • QA — test links and responsive breakpoints

Mobile preview

Resize your browser window or open the link on a phone. If the template includes @media queries, you will see the mobile layout. If not, you may see a scaled-down desktop version — which is itself useful feedback before campaign send.

MethodSpeedAccuracy
Live HTMLDrop linkInstantGood for layout and copy
Test email to GmailMinutesBest for client-specific bugs
Litmus / Email on AcidSlowerFull client matrix

Use live links for early iterations. Use inbox tests for sign-off.

Common fixes after preview

Images missing. Upload images to your CDN or ESP and use absolute URLs in src.

600px content overflows on mobile. Add media queries or stack columns with display:block on <td> elements.

Fonts look wrong. Email clients limit web fonts. Stick to system stacks or accept fallback.

Dark mode breaks colors. Add @media (prefers-color-scheme: dark) overrides if your audience uses dark mode heavily.

HTMLDrop renders in a modern browser — not inside Gmail’s sanitizer. Always do one real test send before production.

When to use this workflow

  • Agency client approvals
  • AI-generated email drafts from ChatGPT
  • Developer handoff from design to ESP upload
  • Documentation (“here is what the welcome email looks like”)

Next steps

After approval, copy the final HTML into your ESP (Mailchimp, SendGrid, etc.) or your app’s email pipeline. The live link remains useful as documentation for your team.

ESP-specific upload checklist

When you move from HTMLDrop preview to your email service provider, verify:

  • All href values point to production URLs, not # placeholders
  • Unsubscribe link is present and correct (legal requirement for marketing email)
  • Plain-text alternative exists (many teams auto-generate from HTML)
  • Preheader text is set in the ESP, not only in hidden preview text divs
  • Tracking pixels and UTM parameters match campaign naming conventions

HTMLDrop gets you to approval faster. ESP upload is still the last mile for sends.

Accessibility in email HTML

Email accessibility is often ignored. Minimum bar for professional templates:

  • Meaningful alt text on images (or alt="" for decorative)
  • Sufficient color contrast on text and buttons (WCAG AA where possible)
  • Semantic heading order in text content even if layout uses tables
  • Link text that makes sense out of context (“Click here” is bad; “View your invoice” is good)

Run these checks in browser preview before sharing the approval link.

Template library workflow

Teams building multiple templates (welcome, password reset, receipt) can publish each to a distinct HTMLDrop slug:

  • /p/email-welcome-v3
  • /p/email-reset-v2

Stakeholders bookmark the set. Designers iterate HTML in their tool of choice, paste updates, re-publish. The slug URL stays stable for documentation and QA scripts.

Preview your email template now — paste HTML and share a live link.

Open the editor →