About HTML Email Builders
HTML Email Builders is a reference site for the tools people use to build, code, embed and check HTML email: drag-and-drop template builders, markup frameworks, embeddable editors and rendering previews. The site is edited by Mara Levin, a pen name for the site's editorial team, and the method behind every page is set out on How we evaluate.
The editor
Editor, pen name
Mara Levin is a pen name for the editorial team behind this site. The monogram above is an initials badge, not a photograph. The name does not stand for a career history, a certification or a list of campaigns, and no page claims any of those. What it stands for is a routine, and the routine is written out below so that readers can judge the pages against it.
What the site covers
Each section of the site groups tools by the job they do in the email workflow. The table shows what each group contains and which questions the pages in that group answer.
| Group | Typical tools | Questions the pages answer |
|---|---|---|
| Template builders and collaborative editors | Stripo, Beefree, Topol, Chamaileon | What each plan includes, how many designs and exports it allows, and what team features are available |
| Code workflows | MJML, Maizzle, React Email | How the source is compiled, which client support data applies, and how the finished HTML reaches a sending service |
| Embeddable editors | Unlayer | How a software team puts an editor inside its own product, and what the published tiers cover |
| Testing and preview tools | Email on Acid, Parcel, Litmus | Which clients are previewed, how many previews a plan includes, and which checks are part of the plan |
| Senders and audience guides | Sender and other delivery services | Which service delivers the email once it has been designed, with pages organised by audience and language |
How a page gets built
A page starts from the vendor's own material: the pricing page, the documentation for the feature being discussed, and the changelog when a limit has changed. Plan names, prices and included limits are copied from those sources, and the page states the billing view that applies, monthly or yearly, together with the source address. The date of the check is printed in the byline, so a reader can see how old the figures are.
Statements about CSS support, dark mode or accessibility are tied to the public compatibility data they come from, and a client that is absent from that data is not described. Where a vendor publishes no price, the page says "pricing on request" and links to the vendor instead of estimating a figure.
Published prices we reference
The table lists the starting prices used on the site at the time of the last check. These are reference points taken from vendor pages. Every page that uses one of them states its plan, its billing view and the list size or user count it covers.
| Tool | Plan | Price (USD) | Billing view |
|---|---|---|---|
| Stripo | Free | $0 | Free plan, no time limit |
| Stripo | Basic | $20 | Per month |
| Stripo | Medium | $45 | Per month |
| Stripo | Pro | $125 | Per month |
| Beefree | Starter | $0 | Up to 10 designs and 6 exports a month |
| Beefree | Professional | $30 | Per month |
| Beefree | Business | $160 | Per month |
| Unlayer | Entry tier | $250 | Per month, billed annually |
| Email on Acid | Basic | $99 | Per month, 1,000 previews |
| Parcel | Production emails | $29 | Per user, per month |
| Topol | Startup | $70 | Per month, 50 prepaid users |
| Chamaileon | Published starting price | $400 | Per month, billed annually |
| Sender | Free Forever | $0 | 2,500 subscribers and 15,000 emails a month |
| MJML | No hosted plan listed | Pricing on request | See vendor pricing page |
| Maizzle | No hosted plan listed | Pricing on request | See vendor pricing page |
What each check covers
Not every page needs every check, but the table below sets out the steps the editor applies before a page is published, and what each step is allowed to support.
| Check | Source used | Where it appears on the page |
|---|---|---|
| Price and plan name | Vendor pricing page | Comparison tables and the plan list, with the billing view |
| Included limits | Vendor pricing page or documentation | Plan descriptions, quoted in the vendor's own terms |
| Feature availability | Vendor documentation and changelog | Feature lists, with a link next to the claim |
| Client and CSS support | Public compatibility data and standards documents | Setup and code sections; unlisted clients are not described |
| Editorial judgement | The editor's reading of the above | Clearly marked as judgement, with the reasons stated |
The site publishes no star ratings, scores, review counts or customer quotes. Pages that compare two tools end with a note on who should choose which, and the reasons for that advice are given in the text.
Corrections
Vendors change plans without notice, and the editor can be wrong. If you find a price, limit or claim that does not match the vendor's page, send the page address and the vendor source through the contact page. A confirmed correction is made on the page, and the date in the byline moves to the day of the new check. The earlier version of the claim is not quietly removed, so a reader who saw it can see that it changed.
Contact
Questions, corrections and vendor updates go through the contact page. For the full list of what is checked and how, read the evaluation method.
Frequently asked questions
Who is Mara Levin?
Mara Levin is a pen name for the editorial team behind HTML Email Builders. The name is used so that every page has a consistent byline. It is not a claim about a named person's career or qualifications.
Does the site test the tools itself?
The pages are written from vendor pricing pages, vendor documentation, changelogs and public compatibility data. Where a page describes how a tool behaves, the source for that description is linked on the page.
Why do some prices say "pricing on request"?
That wording is used when the vendor does not publish a price we can quote. The page links to the vendor rather than giving an estimate.
How often are prices checked?
Each page shows the date of its last check. When a page is changed, the byline date moves to the day of the change, and pages that were not changed keep their earlier date.
Can I suggest a tool to be added?
Yes. Send the tool's name, its pricing page and the documentation for the feature you want covered through the contact page. Additions follow the same sources and checks as existing pages.
What if a price I see is different from the page?
Send the address of the page, the price you see and a link to the vendor source. Corrections follow the process described in the Corrections section above.