For developers

Code your email exactly the way you want it

Pingovo's custom HTML email editor gives developers full control. Write raw HTML, inject Handlebars variables, preview live, and send — all in one place.

email-template.html
<html>
<body style="font-family:sans-serif">
<h1>Hi {{firstName}},</h1>
<p>Your trial at {{company}}
ends in {{daysLeft}} days.</p>
<a href="{{ctaUrl}}">
Upgrade now</a>
</body>
</html>

100%

raw HTML access

Live

real-time preview

20+

Handlebars variables

0

restrictions on HTML

Built for developers who care about email

Full HTML control

Write and edit raw HTML directly. No restrictions, no wrappers — your code, your rules.

Live preview pane

See your email render in real time as you type. Switch between desktop and mobile views instantly.

Handlebars templating

Inject personalisation variables like {{firstName}} and {{companyName}} directly in your HTML.

Import & export

Paste existing HTML from any source or export your code to use anywhere else.

From code to inbox in 4 steps

  1. 1

    Paste or write your HTML

    Open the custom HTML editor and write from scratch, paste existing code, or start from a template.

  2. 2

    Insert personalisation tags

    Drop in Handlebars variables like {{firstName}} anywhere in your HTML. Pingovo handles variable substitution at send time.

  3. 3

    Preview and validate

    Use the side-by-side preview to catch rendering issues. On save, Pingovo adds an alt attribute to any image that lacks one and scores the subject and body for spam triggers.

  4. 4

    Send or save as template

    Attach the HTML to a campaign and send, or save it to your template library for reuse.

Handlebars personalisation — built in

Use standard Handlebars syntax in your HTML. Pingovo substitutes variables for each recipient at send time.

Subject: Hi {{firstName}}, your {{planName}} trial is ending
<p>Dear {{firstName}} {{lastName}},</p>
<p>Your {{planName}} plan at {{company}} expires on {{expiryDate}}.</p>
All variables substituted automatically per recipient

Writing HTML that survives every email client

An HTML email editor gives you control; it cannot give you a modern rendering engine on the other end. Outlook on Windows still lays messages out through Word, Gmail strips what it does not recognise, and a handful of clients ignore embedded stylesheets entirely. None of that is Pingovo's doing, and all of it is predictable — these are the rules that hold across the board.

Tables for layout, not flexbox or grid

Nested tables look archaic and remain the only layout primitive every client agrees on. Modern CSS layout silently collapses in Outlook, which is the client your business recipients are most likely to be using.

Inline styles, not a <style> block

Some clients strip the head entirely. Write critical styling as style attributes on the elements themselves, and treat anything in a stylesheet as a progressive enhancement.

Around 600px wide

The long-standing safe width for a desktop reading pane. Go wider and Outlook introduces a horizontal scrollbar rather than scaling the content.

Never rely on images loading

Many clients block remote images until the reader asks for them. If your call to action lives inside an image, a blocked image is a dead email — keep the message legible in plain text.

Alt text on every image

Pingovo adds an empty alt attribute to any image missing one, because a missing attribute is what checkers flag. Writing real alt text is still yours to do, and it is what the reader sees while images are blocked.

Ship a plain-text alternative

A multipart message with a real text part reads correctly in text-only clients and looks less like a bulk blast to filters than an HTML-only one.

Two things are added to your markup on the way out, and it is better to know than to discover: a tracking pixel for open recording, and a rewrite of each link so clicks can be attributed. Everything else that reaches the recipient is the HTML you wrote. If you would rather not hand-build the table scaffolding, the drag-and-drop builder emits it for you and you can export the result and keep editing it here.

See the render while you are still writing the markup

The usual loop for coding an email is write, save, send yourself a test, squint at your phone, repeat. Each pass costs a minute and a test send, and the mistake you are hunting is usually a table cell one level deeper than you thought.

The editor puts your source and its rendered output next to each other and updates the preview as you type. Toggle the preview between desktop and mobile width to catch the layout that only breaks at 360px — before the test send, not after it.

  • Preview updates as you type — no save step, no test send to see a change
  • Desktop and mobile widths from the same pane
  • Merge tags stay visible as tags in source and resolve on the real send
sourceDesktopMobile
<td align="center">
<h1>Hi {{firstName}}</h1>
<p>Your report is
ready to download.</p>
<a class="btn">
Download</a>
</td>

Hi Alice

Your report is ready to download.

Download
Preview refreshes on every keystroke

Frequently asked questions

Yes, there are no restrictions on the HTML you write. You have full access to the raw source — inline styles, custom fonts, complex table layouts, and any HTML email pattern you want to use.

Use standard Handlebars syntax — {{firstName}}, {{company}}, {{customField}} — anywhere in your HTML or subject line. Pingovo substitutes the correct value for each recipient at send time from your CSV or contact list.

Yes. Paste any existing HTML directly into the editor. Pingovo preserves all your styles and markup. You can also import from Mailchimp, Klaviyo, or any tool that exports raw HTML.

Yes. The side-by-side preview updates as you type, and you can toggle between desktop and mobile views to catch rendering issues before sending.

Only in two places, both deliberate. Any <img> tag without an alt attribute gets an empty one added on save — spam and accessibility checkers flag a missing attribute, where a deliberate alt="" is correct for a decorative image. And at send time the tracking pixel and the link rewrites are injected. Your markup, styles and structure are otherwise stored and sent exactly as written.

Yes, and it depends on your plan — the editor tells you the cap and refuses a save that exceeds it, rather than silently dropping images at send time. Image-heavy email is also a deliverability risk in its own right, since a message that is almost entirely one image with little text is a pattern filters treat with suspicion.

No HTML email does — Outlook on Windows renders through Word's engine, which ignores much of what modern CSS assumes. Build with nested tables rather than flexbox or grid, keep styles inline rather than in a <style> block, hold the body to around 600px, and always ship a plain-text alternative. The preview catches layout mistakes; the client differences you design around from the start.

Start for free

Open the HTML editor and build your first campaign in minutes — add credits or a plan when you are ready to send.

We use essential cookies to run this site, and optional functional/analytics cookies to improve it. See our Privacy Policy for details.