Short answer
Copy the email's HTML from your editor or ESP (Mailchimp, Klaviyo, Brevo and others let you export or view the code), paste it into HTMLtoLink, and send the link to reviewers. Use a password for unreleased campaigns. A browser preview shows content and layout; still send a test email before launch, because email clients render HTML differently from browsers.
Why a link is better for review
- Reviewers do not need to be on your test-send list or dig through spam.
- Everyone looks at the same version, and you update it in place after edits.
- It opens on phones, where most email is read.
Step by step
- Export the template's HTML (or copy it from the code view).
- Check images use absolute
https://URLs — email templates usually do already. - Paste into the publisher, add a password if the campaign is confidential, and publish.
- Check it at phone width with the responsive viewer; most email layouts switch at around 600 px.
- Send the link for sign-off. After changes, update the same link.
What a browser preview will not show you
Email clients are far stricter than browsers. Outlook on Windows uses a Word-based renderer, Gmail strips some CSS, and many clients block images until the reader allows them. So a browser preview is right for copy, links, images and overall layout — and wrong as the final rendering test. Before sending, use your ESP's test send or a dedicated email-testing service.
Common gotchas
- Merge tags like
*|FNAME|*or{{ first_name }}show literally — replace them with sample values for the preview. - Tracking pixels from your ESP may fire when reviewers open the preview; remove them from the preview copy.
- Unsubscribe links in a preview should be dummies.