# Unlayer review: the embeddable email builder SaaS products buy

*Source: https://www.editorstack.cc/libraries/unlayer — last updated 2026-08-19. Licensed CC BY 4.0 with attribution to EditorStack.*


## Summary

- Unlayer is a commercial embeddable email and landing page builder for SaaS products, with white-labelling included from the first paid tier and a React wrapper published to npm since October 2017.
- Vendor-published pricing: a free plan, Launch at $250 per month, Scale at $750 per month and Optimize at $2,000 per month, with a reported $149 startup option and quote-only enterprise terms including on-premise deployment.
- You are buying tested email HTML and the years of mail-client edge cases behind it — the part of an email builder that is genuinely hard and that no open-source engine gives you.

## Quick facts

| Fact | Value |
| --- | --- |
| Type | sdk |
| Licence | Proprietary |
| First release | 2017-10 |
| Language | JavaScript |
| Frameworks | Any (framework-agnostic) |
| SSR support | none |
| Bundle (min+gzip) | Not measurable |
| Pricing | from $250/mo |
| npm weekly downloads | 196,459 |
| GitHub stars | 5,223 |
| Latest version | 2.1.2 |
| Last verified | 2026-08-19 |
| Drag & drop canvas | Yes |
| Responsive breakpoints | Yes |
| Visual style manager | Yes |
| Custom components | Yes |
| Data binding | Yes |
| E-commerce blocks | Partial |
| Email HTML export | Yes |
| AI generation | Yes |
| Editor i18n | Yes |
| White label | Yes |
| Self-hosted | Partial |

## What Unlayer is, and who it is for

Unlayer is an editor you rent, embed and rebrand. Its customers are SaaS products — CRMs, marketing
platforms, e-commerce tools — whose users need to build emails and landing pages inside the product,
and whose teams have decided not to build that themselves.

The reason it exists as a business is narrow and real: email HTML is miserable. Outlook renders with
the Word engine, Gmail strips things, dark mode inverts what it feels like inverting, and the only
way to know whether a template survives is to render it across dozens of clients. Unlayer maintains
that knowledge, and every paying customer is buying a share of it.

If email is incidental to your product, or you only need page building, this is an expensive way to
solve the problem and an open-source engine is the better route. The
[email template builder use case](/use-cases/email-template-builder-for-saas) sets out the whole
decision.

## Architecture

The editor is embedded as a component — the `react-email-editor` package is the best-known wrapper,
and equivalents exist for other stacks — and it renders a vendor-hosted editing surface inside your
application. Your app configures it, listens for events, and asks it to export HTML when the user
saves.

Two consequences. First, integration is genuinely fast: this is a component with a configuration
object, not an engine you assemble. Second, the editing surface is the vendor's, so availability and
roadmap belong to them. That is the trade the whole category makes.

Custom tools and merge tags are the main extension points: you can add product-specific blocks and
expose your own data fields for personalisation, which is what makes the embedded editor feel like
part of your product rather than a rented iframe.

## How we assessed it

We have not run Unlayer hands-on — the embedded editor requires a vendor project key — so no score
and no code sample appear here, per our [methodology](/methodology). Registry metadata confirms the
React wrapper's publication history and current version; pricing and capabilities are recorded from
the vendor's published pages with the date we checked them.

## Strengths

**Email output that has been tested against real clients.** The single reason to buy in this
category, and it is not something you can shortcut.

**Fast to embed.** Weeks rather than quarters, which is exactly the point when email is a feature
rather than your product.

**White-label from the first paid tier.** Your customers see your product, not Unlayer's.

**Email and landing pages from one vendor.** Useful for marketing platforms that need both and would
otherwise integrate two products.

**Merge tags and custom tools.** Personalisation fields and product-specific blocks make the editor
feel native to your application.

## Limitations

**The entry price is high for early-stage products.** $250 per month before you have revenue per
customer to match it is a real constraint, and the reported $149 startup option only softens it.

**Standard plans are vendor-hosted.** On-premise exists under enterprise terms; if your procurement
blocks new sub-processors, that conversation happens before anything else.

**You are renting the editing surface.** Roadmap, uptime and pricing decisions are the vendor's, and
your product inherits them.

**Overkill for page building alone.** If you do not need email, you are paying for the expensive part
of the product and not using it.

**Lock-in via templates.** Templates your customers build live in the vendor's format. Migrating
away means exporting HTML and losing editability, which is the standard shape of this trade in the
email category.

## Pricing

Vendor-published: free plan; Launch $250 per month; Scale $750 per month; Optimize $2,000 per month;
reported $149 per month startup option; enterprise by quote with on-premise available. White-labelling
is included from the first paid tier.

Run the arithmetic against building it: our
[build-versus-buy calculator](/use-cases/build-vs-buy-visual-editor) puts the engineering estimate
against these numbers, and for email specifically we would weight it toward buying more heavily than
the raw hours suggest, because the mail-client work never finishes. Compare also with
[Beefree SDK](/compare/unlayer-vs-beefree-sdk), [Stripo](/compare/unlayer-vs-stripo) and the
lower-priced [Topol](/compare/unlayer-vs-topol-io).

## Questions to ask before you buy

1. **Which mail clients are in your rendering test matrix, and how often is it run?** This is the
   product. Ask for the list, not the assurance.
2. **What is included in white-labelling — editor chrome only, or exported HTML comments and asset
   URLs too?** Customers notice vendor domains in image URLs.
3. **How do merge tags work with our data model?** Personalisation that requires a data shape you do
   not have is a rebuild, not an integration.
4. **What are the on-premise terms, and at which tier do they start?** If self-hosting is a hard
   requirement, this is the first question, not the last.
5. **Who owns templates our customers create if we leave?** Ask for the export format and try it.
6. **How is the editor versioned, and can we pin a version?** An editor that changes under your
   customers without notice generates support tickets you did not budget for.

## Where it sits in this dataset

Unlayer is the middle of the embeddable email category on price and the broadest on scope: it is the
only one of the four email products here that also does landing pages seriously.

Against [Beefree SDK](/compare/unlayer-vs-beefree-sdk) it starts $100 per month cheaper and offers
less of a template catalogue and marketplace. Against [Stripo](/compare/unlayer-vs-stripo) the
difference is the meter — flat platform tiers against per-template pricing — and that difference,
not the feature lists, is what should decide it. Against [Topol](/compare/unlayer-vs-topol-io) it is
four times the entry price for a broader product.

Against building on [GrapesJS](/compare/grapesjs-vs-unlayer) with the newsletter preset, the honest
framing is that you would be taking on the mail-client compatibility work permanently. Our
[build-versus-buy calculator](/use-cases/build-vs-buy-visual-editor) understates that case, because
the maintenance line for email never trends toward zero the way it does for a page builder.

## Who it fits, and who it does not

**Good fit**

- SaaS products that need an email builder inside their app in weeks rather than quarters
- Teams that want email HTML which has been tested against real mail clients by someone else
- Marketing platforms needing both email and landing page editing from one vendor

**Poor fit**

- Products whose unit economics cannot absorb a four-figure monthly platform fee at low customer counts
- Teams requiring the editor itself to run fully inside their own infrastructure on standard plans
- Use cases that are page building only, where a general-purpose engine costs nothing


## Unlayer against its nearest neighbours

| Product | Type | Licence | Frameworks | Bundle (min+gzip) | Price from | Self-hosted | White label | Score |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| [Unlayer](https://www.editorstack.cc/libraries/unlayer) | sdk | Proprietary | Any (framework-agnostic) | Not measurable | from $250/mo | Partial | Yes | not scored |
| [Beefree SDK](https://www.editorstack.cc/libraries/beefree-sdk) | sdk | Proprietary | Any (framework-agnostic) | Not measurable | from $350/mo | No | Yes | not scored |
| [Stripo Plugin](https://www.editorstack.cc/libraries/stripo) | sdk | Proprietary | Any (framework-agnostic) | Not measurable | from $100/mo | No | Yes | not scored |
| [Topol Plugin](https://www.editorstack.cc/libraries/topol-io) | sdk | Proprietary | Any (framework-agnostic) | Not measurable | from $60/mo | No | Yes | not scored |


## Our scores

Not scored. We publish scores only for products we have run hands-on; see the methodology page.


## Alternatives

- [Unlayer vs GrapesJS](https://www.editorstack.cc/compare/grapesjs-vs-unlayer)
- [Unlayer vs Beefree SDK](https://www.editorstack.cc/compare/unlayer-vs-beefree-sdk)
- [Unlayer vs GrapesJS Studio SDK](https://www.editorstack.cc/compare/unlayer-vs-grapesjs-studio-sdk)
- [Unlayer vs Stripo Plugin](https://www.editorstack.cc/compare/unlayer-vs-stripo)
- [Unlayer vs Topol Plugin](https://www.editorstack.cc/compare/unlayer-vs-topol-io)


## Frequently asked questions

### How much does Unlayer cost?

Vendor-published tiers are a free plan, Launch at $250 per month, Scale at $750 per month and Optimize at $2,000 per month, with a reported $149 per month startup option and custom enterprise terms. White-labelling is included from the first paid tier.

### Can I white-label Unlayer?

Yes — removing Unlayer's branding from the embedded editor is part of the paid plans, which is why it appears inside so many marketing platforms without users knowing.

### Is there a free version of Unlayer?

There is a free plan suitable for evaluation and small use. Production SaaS embedding generally starts at the paid tiers where white-labelling and support are included.

### Unlayer or GrapesJS with the newsletter plugin?

GrapesJS costs nothing and produces email HTML through a plugin, but you own every rendering bug across mail clients. Unlayer costs four figures a month and hands you output the vendor tests. Which is right depends on whether email is core to your product or a feature you tolerate.

### Can Unlayer be self-hosted?

On-premise deployment is offered under enterprise terms rather than on standard plans. If self-hosting is a hard requirement, raise it in the first sales conversation.


## Sources

1. [npm registry metadata for react-email-editor (licence, first publish date, latest version)](https://registry.npmjs.org/react-email-editor) — accessed 2026-08-19
2. [Unlayer pricing page (vendor-published plan prices)](https://unlayer.com/pricing) — accessed 2026-08-19
3. [Unlayer embed documentation](https://docs.unlayer.com) — accessed 2026-08-19