$/transactional-email-api providers ↗
← all providers
Testing

Mailpit

Modern local SMTP catcher.

overview

Mailpit is a single-binary local SMTP server and web UI for capturing email during development and testing. It listens on the same 1025 (SMTP) and 8025 (HTTP) ports as MailHog, so it drops into existing setups, and adds faster HTML rendering, full-text search, an HTML and link compatibility check, a spam-score view, and a REST API. It is actively maintained.

for teams choosing a transactional API

Judged purely as an API. What the request contract guarantees on retry, how complete the webhook event coverage is, whether suppressions are readable and writable programmatically, and how much the message log retains when something needs debugging in production.

Against high-frequency programmatic sends where a missed delivery is a product failure, Mailpit covers none of the capabilities this audience leans on (idempotency keys, webhook coverage, event stream, the suppressions API, batch sending, and SDK breadth), so it fits only where those needs are genuinely absent.

  • Idempotency keys: No
  • Webhooks: No
  • Event stream: No
  • Operating since: Not published
  • Suppressions API: No
  • Best published rate per 1,000: Tiers not published in comparable form
  • Batch sending: No
  • SDKs: None
  • Deliverability: Not applicable; capture-only.
deliverability

Not applicable; capture-only.

best for

Replacing MailHog in any local or CI email-capture setup.

not great for

Teams that need a shared cloud staging inbox rather than a local process per developer.

pros
  • Single Go binary or small Docker image with no runtime dependencies
  • Reuses MailHog's 1025 and 8025 ports, so most existing configs work unchanged
  • Views for rendered HTML, plain text, raw source, headers, and attachments
  • Built-in HTML-compatibility check, link check, and spam-score view
  • REST API and real-time inbox updates for automated tests
cons
  • Local development and staging only, not a production sender
  • No hosted or shared team-inbox mode

Features at a glance

API Yes
SMTP Yes
SDKs None
Webhooks No
Templates none
React Email No
Batch send No
Scheduled send No
Suppressions No
Multi-tenant No
Inbound parsing No
Event stream No
Idempotency keys No
Dedicated IP No

Appears in rankings

Compared with