Layout
Check the hierarchy, spacing, wrapping, buttons, footer, and overall reading path at a desktop width and a narrow mobile width.
All use cases
For email review
Preview an HTML email template before sending it.
Email work is easier to improve when reviewers can open the rendered message, check the content and layout, and respond to one browser link. Upload a self-contained HTML email or a ZIP with its assets, then use the preview for a bounded review before moving the markup into your email service provider.
Review lens
What to check in the browser review
Use the browser preview to inspect the visible artifact and prepare a clear feedback pass. It is a review surface, not an email-client lab.
Content
Review the subject-supporting copy, headings, offer details, links, contact information, and any permission or unsubscribe language before handoff.
Assets
Confirm that images, styles, and other local resources load from the relative paths included in the single file or ZIP project.
A real moment for the page
A browser link makes the next conversation concrete.
Creative review
Give a designer or marketer a rendered page to check the message, visual hierarchy, image treatment, and CTA before the campaign enters the ESP.
Feedback round
Send one browser link with a focused question about copy, layout, links, or mobile width instead of asking reviewers to inspect a source file.
ESP handoff
Use the preview to catch obvious content and asset-path issues, then move the approved markup into the email platform that owns sending and delivery checks.
Why this handoff works
Keep the useful part close to the artifact.
Keep feedback close to the message
Reviewers can see the rendered HTML email and respond to the same version before it is copied into another system.
Catch browser-visible issues early
A fresh preview makes broken images, relative paths, overflow, missing links, and unclear mobile layout easier to notice.
Make the handoff explicit
Separate the browser review from the ESP workflow so the team knows which checks happened and which client or delivery checks remain.
A three-step workflow
From the right files to the right reaction.
- 01
Package the email
Use a self-contained HTML file when possible. If the email references local images or other files, include them in a ZIP with the expected relative structure.
- 02
Review desktop and mobile widths
Open the preview in a fresh browser and check layout, copy, links, images, and narrow-width behavior from the reviewer’s perspective.
- 03
Share the feedback ask
Send the link with the exact review question, then transfer approved HTML to the ESP for its client previews, sending, tracking, unsubscribe handling, and deliverability checks.
Know the boundary
A preview is useful because it is honest.
HTMLShare publishes browser-ready static output. Keep builds, source tools, private access, live data, and production operations in the systems built for them.
Not email-client simulation
The browser preview does not simulate Gmail, Outlook, Apple Mail, or their individual rendering quirks, CSS support, or authentication behavior.
No sending or deliverability
HTMLShare does not send email, manage subscribers, test inbox placement, validate authentication, or guarantee deliverability. Use your email platform for those responsibilities.
Review copy, not private data
A preview link is not a confidential mail workspace. Remove credentials, subscriber data, and other sensitive content before uploading; noindex does not restrict access.
Keep exploring
The next useful page is nearby.
Before you publish
HTML email template preview FAQ
How do I preview an HTML email template online?
Upload a self-contained HTML email or a ZIP containing the HTML and its local assets, open the browser preview, and check the rendered content at desktop and mobile widths before sharing the review link.
Can this preview simulate Gmail, Outlook, or Apple Mail?
No. HTMLShare provides a browser rendering review. It does not emulate Gmail, Outlook, Apple Mail, their CSS differences, or their authentication and delivery behavior.
Can HTMLShare send the email or test deliverability?
No. HTMLShare previews and shares static HTML. Hand the approved markup to your ESP for sending, subscriber handling, unsubscribe processing, tracking, authentication, and deliverability testing.
What should I upload for an HTML email review?
Upload one complete HTML file when its resources are self-contained, or a ZIP with index.html or the email entry file plus its images, styles, and other relative assets. Remove private data before publishing.
Ready for the next review
Put the current page in front of the right person.
Create a noindex preview link for the static HTML or ZIP project, then move approved work to production when it is ready.