How we evaluate email builders
HTML Email Builders has no single best pick for every reader, because a builder and a sending service answer different questions. A builder is judged on the output it produces and how easily a team can edit it. A sender is judged on what its plan includes and how it counts volume. Each page names a pick only for a stated audience, gives one reason that can be checked against a vendor page, and quotes the price that applies on the date shown. The example below shows the method: Sender's Standard plan at $6.30 a month covers 6,000 emails a month for 500 subscribers, and the free plan covers 2,500 subscribers and 15,000 emails a month. Those are the two numbers a reader needs to decide whether the free plan is enough. Written by Mara Levin, a pen name for the site's editorial team.
Where the numbers come from
Every price on this site comes from a vendor's own pricing page, read on the date shown in the byline. The prices in the examples on this page were checked on 7 October 2026 against the pages linked in the table below. Plan names, limits and add-on fees are copied from the pricing page, or from the vendor's billing documentation when the pricing page leaves a detail out.
Where a vendor uses a slider, such as a contact or email-volume selector, only the stops the page actually shows are quoted. Amounts between those stops are not estimated from a per-thousand rate unless the page shows the arithmetic and labels it as a calculation. When a vendor publishes no price, the page says "pricing on request" and links to the vendor's page. No estimate is made up.
| Claim type | Where it comes from | What the page writes |
|---|---|---|
| Plan names and prices | Vendor pricing page | Plan, amount, billing view (monthly or annual) and the unit it applies to |
| Free plan or trial | Pricing page, or billing documentation | Exact limits or trial length, with no ongoing free tier implied where none is shown |
| Feature availability | Vendor documentation | The feature, with the documentation page linked beside it |
| Email client support | caniemail.com feature data | The client and feature, with the feature page linked. If the client is missing, the page says so |
| Accessibility statements | WCAG 2.2 and W3C Web Accessibility Initiative pages | The success criterion named by number |
| Code samples | Vendor's current documentation | The sample copied as published, with its documentation page linked |
Worked example: reading a price
A price line is only useful if it states what it buys. The table below shows how two vendors' prices are recorded on this site. Sender's prices are per plan and depend on both emails sent and subscribers. Close's prices are per user, with separate monthly and annual figures.
| Vendor and plan | Price | Billing view | What it applies to |
|---|---|---|---|
| Sender, Free Forever | $0 | No payment | 2,500 subscribers and 15,000 emails a month |
| Sender, Standard | $6.30 | Per month; the page lists the same figure for annual billing | 6,000 emails a month and 500 subscribers |
| Sender, Professional | $10.50 | Per month; the page lists the same figure for annual billing | 12,000 emails a month and 500 subscribers |
| Close, Solo | $19 a month, or $9 a month billed annually | Per user | Core CRM for one operator; 500 AI credits per user a month |
| Close, Essentials | $49 a month, or $35 a month billed annually | Per user | Unlimited contacts and leads, team collaboration, built-in forms, email, calling and SMS; 1,000 AI credits per user a month |
Close has a 14-day free trial with no card needed and does not list an ongoing free plan. The arithmetic below is the kind of calculation the site shows when it is asked for. For a Sender Standard plan billed for a year, 12 × $6.30 = $75.60. For a five-person team on Close Essentials billed annually, 5 × $35 = $175 a month, and 12 × $175 = $2,100 a year. Calling and SMS usage on Close is passed through at cost, so the annual figure above does not include it.
Screenshots
Screenshots are taken of the vendor's public page in an ordinary browser window, on the day the page is checked. They are saved unedited: nothing is cropped to hide a price, composited or recoloured. The caption gives the vendor, the date and the address. If a capture fails, or shows a cookie wall instead of the page, the page goes without the image and says so, rather than using a picture of a different vendor.
What a comparison includes
A builder is assessed by workflow: who owns the source file, what can be exported, how a team collaborates on a template, what accessibility controls exist, and how the finished HTML reaches a real sender or a test service. A sender is assessed by what its plans include, how it counts volume, whether subscribers and emails are capped separately, and what it leaves to the user to set up. Each page ends with who should choose which option and why, and the reasoning is written out so a reader can disagree with it.
Decision guide
The questions below are the ones a reader should answer before trusting any price or feature claim on the site. Each row names the check that settles the question.
| If the question is | Check first | Why it matters |
|---|---|---|
| Can I export clean HTML from this builder? | The export section of the documentation | The exported file is what the sender receives, so export limits matter more than the editor screen |
| Will my list fit this sender's plan? | Plan limits for subscribers and emails, read separately | Some plans cap subscribers and monthly emails at different levels, and either one can force an upgrade |
| Is the price per user or per account? | The unit line under the price | Close prices per user, so a five-person team pays five times the listed figure |
| Is there a free plan or only a trial? | The free plan or trial text | A trial ends. A free plan continues within its limits |
| Does the vendor publish a price at all? | The vendor's pricing page | If not, the page says "pricing on request" and does not guess |
What we do not do
- No paid placement. A vendor cannot buy a position, a badge or a "best for" label.
- No invented tests. The editor reads documentation and pricing pages. A page does not say a tool was tested, migrated or run in production unless it describes exactly what was done.
- No scores, star ratings, review counts, customer quotes or performance statistics without a linked source.
- No promise that a builder or preview guarantees identical rendering in every email client.
- No quiet edits. A correction is dated, as described below.
Corrections
When a vendor changes a plan or a feature, or a reader shows that a page is wrong, the page is updated and the date in the byline moves to the day of the new check. Screenshots are captured again at that point rather than patched. Send corrections, with the vendor's page address, through the contact page. A correction that changes a recommendation is stated in the text of that page's verdict, not only in the figures.
Publication checklist
Before a page is published, the editor works through the steps below. A page that fails any step is held back until the gap is closed.
| Step | Done when |
|---|---|
| Pricing page read | Every plan, amount and billing view on the page is copied, with its unit |
| Documentation read | Each feature the page relies on is linked to the page that describes it |
| Limits checked | Subscriber and volume limits are stated separately where the vendor separates them |
| Arithmetic shown | Any derived figure carries its calculation on the page |
| Byline dated | The date matches the day the pricing page was read |
How a vendor gets added
A vendor is added when readers search for it, when it appears next to tools already covered, or when a reader asks through the contact page. Before a page is written, the editor needs the vendor's pricing page, the documentation for the features that matter to the page's question, and a working public page to capture. A vendor that publishes nothing checkable, or whose prices sit entirely behind a sales call, can still appear, but its page says that prices are quote-based and compares only what is documented. Sending a vendor an application, a review copy or a fee does not change the order in which pages are written or what they say.
Frequently asked questions
Why does this site not name one best email builder?
A builder's value depends on the team using it. A developer who wants code under version control and a marketer who wants drag-and-drop editing need different tools. Each page names a pick only for the audience it describes, and gives the reason in one sentence that a reader can check.
Where do the prices come from?
From the vendor's own pricing page, read on the date shown in the byline. Where the pricing page leaves out a detail, the vendor's billing documentation is used and linked. Prices are never estimated.
Why are some prices written per user and others per month of volume?
Because the vendor charges that way. Close prices each seat, so the page shows the per-user figure and a worked total for a team. Sender prices depend on subscribers and emails sent, so the page shows both limits for each plan.
What happens if a vendor changes its prices after a page is published?
The page is updated once the change is confirmed on the vendor's page, the byline date moves to the new check, and the screenshot is captured again. The change is named in the text where it affects the advice.
Does a vendor pay to be included or ranked?
No. A vendor cannot buy a position, a badge or a "best for" label, and a fee or review copy does not change what a page says.
How do I report an error?
Use the contact page and include the address of the vendor page that shows the correct information. The editor reads the vendor page first, then updates the affected page and dates the change.
Why does a page say a client is not documented?
Support claims come only from the caniemail.com feature data and from vendor documentation. If a client is not in those sources, the editor does not guess, and the page says the support is not documented.